===================================================================== ===================================================================== DisplayLink Software Release: External Release Note Software Package: ASUS EzLink Display Version: 4.3.9931.0 ===================================================================== ===================================================================== EXECUTIVE SUMMARY This is R4.3 M3, the third Maintenance Release for software release R4.3. It has completed system test, both in-house and externally. It is suitable for deployment to end-users. DisplayLink Software Release 4.3 delivers the following features: - Vista Aero support - Improved video playback on Windows XP - Improved handling of monitor resolutions - Auto-Update mechanism. Recommendations for use: If using with more than one device, make sure each device is fully installed and working before adding the next. There are many minor issues. They can generally be resolved by - detaching and reattaching the DisplayLink device - changing the display mode via the DisplayLink GUI, or - changing the display mode via Windows Display Properties. On Vista WDDM (Aero and basic): DisplayLink software works closely with the graphics card and there may be interoperability issues with some graphics cards. If this happens, (1) try to upgrade to the latest graphics drivers (2) try to upgrade to latest DisplayLink software (3) report the issue via your support channel (4) if necessary, boot into Safe Mode and use Vista's Backup and Restore Center to recover. Video: video generally works using the most popular video players on Vista WDDM aero. Video works in extend mode on XP. Video support is limited in other configurations such as on Vista WDDM basic and in mirror mode on XP. ===================================================================== ===================================================================== A. Introduction =============== This is R4.3 M3, the third Maintenance Release for software release R4.3. It has completed system test, both in-house and externally. It is suitable for deployment to end-users. B. Contents =========== Executive Summary A. Introduction B. Contents C. New Features C1. Bug Fixes C2. Vista SP1 status D. Note on Vista Modes E. How to Install F. How to Use G. Supported Operating Systems H. PC Minimum Specifications I. Language Support J. Supported Hardware K. Summary of Software State and Issues - Vista WDDM K1. Vista WDDM graphics card support K2. Normal use K3. Video players, rendering technologies and applications K4. Installer and auto-update function L. Summary of Software State and Issues - Vista XDDM, XP, 2K L1. Normal use L2. Video players, rendering technologies and applications L3. Installer and auto-update function C. New Features =============== New features in R4.3 are: - Vista Aero support - Improved video playback on Windows XP - Improved handling of monitor resolutions - Auto-Update mechanism. Vista Aero support ------------------ R4.3 software supports the Vista Aero Glass look, including - extend - mirror - off mode - support for multiple monitors - DisplayLink GUI. R4.3 supports 32-bit but not 64-bit versions of Vista. Improved video playback on Windows XP ------------------------------------- Video playback performance has improved on Windows XP compared to previous DisplayLink releases. Improved handling of monitor resolutions ---------------------------------------- Monitors that successfully transmit EDID to the PC have all their resolutions supported, up to the limits of the DisplayLink ASIC. The EDID modes are checked for validity against ranges specified in the EDID data. This is to ensure that monitors are not set into a mode that might damage them. Monitors that do not successfully transmit EDID to the PC benefit from an improved resolution list, including some widescreen modes. Auto-Update mechanism --------------------- The Auto-Update mechanism alerts users if newer software is available and allows them to download it. Users can configure whether or not to allow for periodic automatic checks for newer software. It is always possible to check manually using the DisplayLink GUI. The Auto-Update mechanism is optionally included depending on the product supported by the software package. C1. Bug fixes ============= The following improvements have been made since 4.3.8432 (R4.3 Full Release): Fixes included in R4.3 M1 (4.3.9110) ------------------------------------ - Show auto-update dialogs in English on US English machines (2338) - Install correctly when there are Far Eastern / non-English characters in the user name (2340, 2415) - Better handle the situation where the user sets their main monitor into an unsupported mode (with their native graphics driver bump- scrolling) (2350, 2375) - Verify support for Windows XP SP3 Fixes included in R4.3 M2 (4.3.9674/9677) ---------------------------------------- R4.3 M2 brings some significant enhancements over R4.3 Full Release: - On Vista WDDM, detection of directly-attached screens and mode switching using Fn-F7 or equivalent keys are now supported in general. Note that machines with the ATI Catalyst Control Centre installed may find it crashes when a second VGA/DVI screen is attached. The workaround is to uninstall the ATI Catalyst Control Centre. - On Vista WDDM, playing DVDs using Windows Media Player or Windows Media Centre now works. Note that a problem has been observed when trying to play a Blu-ray disk on a PC with two Nivo screens attached. In this situation the main PC screen stopped working. The workaround is to ensure there is at most one Nivo screen attached when playing a Blu-ray disk. List of changes in R4.3 M2: - Fix a rare blue screen. (2483) - Cope better with the situation where the user has uninstalled their primary graphics driver. (2351) - Reduce the likelihood that multiple reboots will be needed after installation on XP. (2518) - Reduce screen flicker at startup and when unplugging DisplayLink devices. (2085) - The TMM (Transient Multi-Monitor) subsystem is no longer disabled when DisplayLink software is installed. TMM is a Vista subsystem that detects when a screen is attached and allows the user to configure the screen. TMM can detect directly attached screen but not DisplayLink screens. Note that machines with the ATI Catalyst Control Centre installed may find it crashes when a second VGA/DVI screen is attached. The workaround is to uninstall the ATI Catalyst Control Centre. (1831, 2054) - Work around a Windows Vista problem where the operating system sometimes shows the logon screen offset from its intended position. (2269) - Work around problems in third party software so as to allow Fn-F7 type operations for changing the configuration of attached screens. Fn-F7 type operations work with directly attached screens but not with DisplayLink screens (2277) - Work around the behaviour of the Windows Display Properties dialog box (WDP) for small screens in portrait mode. WDP will not show resolutions below 640 horizontally or 480 vertically. This can cause problems with low resolution screens when they are placed into portrait mode. This workaround gets around these problems by presenting the screens to WDP as if they were in landscape mode. (1049) - Apply embedded signatures to all kernel drivers. This fulfills a requirement that Microsoft are making mandatory on Windows Vista, and speeds up boot time. (2379) - Reduce the occurence of an occasional 'mouse freeze' issue, where a DisplayLink screen and the mouse pointer occasionally fail to update for a couple of seconds. (2505) - Remove the console windows that used to flash up briefly at install and uninstall. (896) - Ensure that only users with admin privileges can uninstall DisplayLink software. This gets around a problem where an uninstall started by a non-administrator could leave DisplayLink software in an inconsistent state. (1755) - Enable DVD playback from Windows Media Player and Windows Media Centre on Windows Vista in aero mode. (2382) - Enable video in most circumstances on Windows Vista SP1 in WDDM basic mode. Note that video is not supported in WDDM basic mode, however it often works. (1609) Fixes included in R4.3 M3 (this release) ---------------------------------------- - Cooperate with 'safely remove hardware' requests. This is provided as a convenience to customers incorporating DisplayLink technology into products, such as Docking Stations, that require the user to click 'Safely Remove Hardware' before detaching. Note that DisplayLink screens are fully plug-and-play, and do not require 'Safely Remove Hardware' before removing. (1575) - Improved latency and performance under Vista Aero. (2505) C2. Vista Service Pack 1 Status =============================== R4.3 M2 has been tested in detail with Vista Service Pack 1 (SP1). It works well with both the RTM and the General Release of Vista SP1. Microsoft previously signalled a significant defect when operating with multiple displays: resuming from sleep, and then changing resolution, results in black screens and the user must reboot. This problem has been solved in the RTM and General Release of Vista SP1. It is no longer a concern. D. Note on Vista Modes ====================== Normally, Vista is in WDDM mode. In this mode, Vista graphics drivers are used, and the Vista Aero Glass and Vista Basic looks are available. Vista PCs whose graphics drivers are not Vista ones run in XDDM mode. In this mode, the Aero Glass look is not available. PCs that were upgraded from XP to Vista and PCs with low-end graphics cards run in XDDM mode. DisplayLink software supports both modes in different ways, and the level of support and issues are different in the two cases. E. How to Install ================= Important note: users who have v3.x âUSB Display Adapterâ software installed in Add/Remove Programs must uninstall it before installing this release. Devices using v3.x software will continue working after this release is installed. Important note: if you are installing several devices, make sure that each is fully installed and showing an image before attaching the next. Software-first install ---------------------- - Unzip the release package - Run âsetup.exeâ - Once installation is complete, attach a DisplayLink device / screen to the PC and wait for it to come up. Hardware-first install from release package (.zip) -------------------------------------------------- - Unzip the release package to a convenient place, - Connect the DisplayLink device - Point the âNew Hardware Foundâ wizard at the unzipped release package. Hardware-first install from CD ------------------------------ - Put the CD into the PC's drive - Connect the DisplayLink device / screen - Point the âNew Hardware Foundâ wizard at the CD drive. Uninstalling the Release ------------------------ - Go to âAdd or Remove Programsâ dialog box (XP or 2K) - Go to 'Uninstall a Program' or 'Programs and Features' dialog box (Vista) - Select the customer product you installed - Choose âRemoveâ. F. How to Use ============= DisplayLink screens can run in three modes: - extend mode: the screen is part of the extended desktop - mirror mode: the screen copies the contents of the primary screen - off mode: the screen is black. Display modes can be controlled through the DisplayLink GUI (DL-GUI) and through the Windows Display Properties dialog box (WDP). DL-GUI ------ This is an icon in the systray that looks like a monitor. Click on the icon to bring up the menu. You can control - screen resolution - colour quality - rotation - mode (extend, mirror, off) - extend position (right, left, above, below) - auto-update configuration - manual check for newer software. WDP --- To open WDP on XP / 2K - right-click on the desktop - select 'Properties' from the context menu - go to the Settings tab To open WDP on Vista - right-click on the desktop - select 'Personalize' from the context menu - click on Display Settings link To open WDP from DL-GUI - bring up the DL-GUI menu - click 'Advanced...' With WDP you can control - screen resolution - colour quality - extend position - primary screen - refresh rate - whether the device is enabled (= part of the extended desktop) or not (= mirror or off mode). G. Supported Operating Systems ============================== This release supports the following operating systems: - Windows 2000 SP4 - Windows XP SP2 - Windows XP SP3 - Windows Vista 64 bit operating systems are not supported. H. PC Minimum Specifications ============================ The minimum hardware requirements for the PC are: - PC with 1.2 GHz or higher processor clock speed, with an Intel Core 2 Duo or equivalent power CPU. - 512 megabytes (MB) of RAM for a single attached screen, 1 gigabyte (GB) of RAM for two attached screens, more for more attached screens. - At least one USB 2.0 port - 30 megabytes (MB) of free disk space - Computer screen for use with the DisplayLink device, if it is not integrated. - CD-ROM or DVD drive if installing from CD. I. Language Support =================== DisplayLink software is localised in the following languages: - English - French - German - Dutch - Italian - Spanish - Portuguese - Polish - Hungarian - Russian - Traditional Chinese - Simplified Chinese - Japanese - Korean J. Supported Hardware ===================== - Certified DL120 / DL160 devices are supported. - Earlier devices are supported for backwards compatibility. - DL1x5 sample devices are supported, but R4.3 software does not fully exploit their capabilities. Each install package supports a range of hardware variants: - DisplayLink Early Access supports all DisplayLink internal USB devices and internal Ethernet devices but no customer branded devices. Ethernet devices require running a separate configuration application. - Customer branded releases only support the customer allocated Product IDs (PIDs). This package supports up to 6 devices with these PIDS: USB_018A: ASUS EzLink Display USB_01BE: ASUS EzLink Display (VW202B) K. Summary of Software State and Issues - Vista WDDM ==================================================== K1. Vista WDDM graphics card support ------------------------------------ Because of restrictions in Vista WDDM support for graphics cards, the DisplayLink software works closely with the graphics drivers for the PC's graphics card. We support interworking with single graphics cards from Intel, ATI, Nvidia and Via. We have interoperability tested against a representative selection of each of these cards, and continue to expand our test coverage in this area. We cannot exclude severe problems in the case of graphics cards or driver versions that have not been interoperability tested with DisplayLink software. Should such problems arise, - First, upgrade to the latest graphics drivers for your PC. Latest drivers can be found on the PC manufacturer's or graphics card manufacturer's website. - Second, upgrade to the latest DisplayLink software available for your device. Use 'Check now...' from the DisplayLink GUI to find and download latest software. - If this does not help, please inform your DisplayLink device manufacturer's support line. Please give these details: + PC make, CPU and memory + graphics card make, model and driver version. Known issues - general DisplayLink screens are not supported on systems with two graphics cards used simultaneously (supporting separate screens, or in SLi or Crossfire configuration). (1704) Known issues - Intel graphics Some older versions of Intel graphics drivers will cause corruption on the Nivo screen. The solution is to upgrade them to version 7.14.10.1111 or later. This is with Vista WDDM. (2164) Users of Vista WDDM with Intel graphics should exercise caution if using two or more DisplayLink screens at a time. Very occasionally, mode changes or detach/reattach of two Nivos at once has been observed to cause a complete machine lock-up. (2264) On Vista WDDM with Intel graphics, the Transient Multi-Monitor subsystem gets confused when there are more than 2 attached screens. For instance, if there are two directly attached screens and a DL screen is attached, it always comes up in mirror mode. If there are two directly attached screens and a DL screen present, and if one of the directly attached screens has been disabled via TMM, the user needs to detach the DL screen and then use the display switching function keys to re-enable it. (2549) Known issues - ATI graphics The ATI Catalyst Control Centre is a tool provided by ATI to control ATI graphics cards. In the presence of DisplayLink attached screens, some parts of the tool, such as its adjustments submenu, do not work. This is on all OSes. (1596) Some versions of the ATI Catalyst Control Center crash in the presence of DisplayLink software. This has been observed with versions since ATI driver version 8.360. This can cause problems when a screen is attached to the PC. To work around the problem, uninstall the ATI Catalyst Control Center. On Vista WDDM with ATI graphics, TMM does not kick in when DisplayLink screens are attached. It works normally when no DisplayLink screens are attached. (2569) Known issues - Nvidia graphics With Vista, a maximum of four DisplayLink screens are supported on machines with Nvidia graphics. In certain rare cases, exceeding this has been seen to cause repeated serious crashes. (1781) On Vista WDDM, older versions of Nvidia drivers with versions prior to 7.15.11.146 can behave badly in the presence of DisplayLink software. For instance they can cause blue screens when applications are maximised on DisplayLink screens. Also, if DisplayLink devices are attached or detached during restart, it may be necessary to press the reset button on the PC to restore normal functioning. (2119) K2. Normal use -------------- System behaviour with up to six DisplayLink attached screens has been well tested. Testing covers plug/unplug, mode changes, playing video, hibernate, sleep/standby, multiple users, different user rights, attached screen as primary screen, attached screen as only screen, and other aspects. There are many minor issues. General recommendations if something goes wrong: - detach then reattach the DisplayLink device's USB cable - change display settings using DL-GUI - change display settings using WDP. Known issues - hibernate / sleep / monitor power save / screensavers On Vista, very occasionally, DisplayLink devices fail to resume from hibernation or sleep. This is due to issues in the Vista USB subsystem. Hotfix http://support.microsoft.com/kb/941600 should help. This is believed to be fixed in Vista Service Pack 1. (2126) On Vista WDDM, DisplayLink attached screens can be slow when resuming from hibernation or sleep. This is a Vista problem and is believed to be improved in Vista Service Pack 1. (2165) On all OSes, the desktop background is occasionally missing after restart or after resume from sleep or hibernation. The screens are still usable, and the background can be set again to the desired picture. (2154, 2072) On all OSes, detaching or attaching DisplayLink attached screens while a screensaver is running may cause strange effects. Sometimes it is necessary to detach and reattach the DisplayLink attached screen after exiting the screensaver. (1984) 3D screensavers do not run well on DisplayLink devices and can cause flicker. This is on all OSes. (1150, 1177) If devices are detached from the PC before going into standby, then reattached during standby, very occasionally they may not resume when the PC comes out of standby. If this happens, detach and reattach the devices to make them work again. (1492) Known issues - other In Powerpoint, the "Display slide show on:" menu has a bug which means that it does not work when there are gaps in the numbering of enabled displays (as shown in WDP). Users of Powerpoint 2007 can get round this by using "Show presentation on:" in the ribbon, rather than the "Set up slide show" box. (2337) Vista WDDM: it's best to avoid switching between 32 bit and 16 bit colour quality on DisplayLink attached screens. Occasionally, this causes the DisplayLink screen to stop working. Detach and reattach it to get it to work again. Very occasionally, this has caused a complete machine lock-up. (2070, 2260) On Vista WDDM, if a DisplayLink screen is primary, it is not possible for another DisplayLink screen to mirror it. (1870) CRT monitors may show speckles at very high resolutions. This is because the DisplayLink device cannot always support the high pixel clock required with high CRT refresh rates. (2155) After a reboot, the numbers used in Windows Display Properties to identify the attached screens may change. This is normal. (596) On Vista WDDM, when using the DisplayLink GUI to set rotation, occasionally the screen rotation will fail to match the GUI's rotation setting. To fix this, apply the setting again, or retach and reattach the DisplayLink screen. (2186) K3. Video players, rendering technologies and applications ---------------------------------------------------------- On Vista WDDM Aero, video playing largely works. Video playing and rendering using hardware overlays is not supported. The following players work: - Windows Media Player 11 (www.microsoft.com/windows/windowsmedia/default.mspx) - WinDVD 8 (www.intervideo.com) - PowerDVD 7 (www.cyberlink.com) - RealPlayer 11 (www.real.com). This table shows what rendering interfaces are supported: Interface Supported on Vista WDDM Aero? DxVA Yes, if supported by the GPU D3D Yes, but not if the DisplayLink screen is primary DirectDraw Yes OpenGL Yes, but not fullscreen, windowed only GDI+ Yes, but not fullscreen, windowed only On Vista WDDM Basic, video is not supported. It may work in some cases but exhibits poor performance. It may stop working after an update from Windows Update that affects the graphics subsystem. (2028) On all platforms, depending on the player, there may be problems if the video window is moved between screens while video is running. It may be necessary to close and restart the video player. With Vista WDDM, on some lower-spec PCs, videos on DisplayLink attached screens pause frequently for several seconds at a time. This is because there is insufficient system performance to display video smoothly. (1798) Known issues - general Don't change the display mode, position or arrangement of attached screens while a video is running. This usually confuses the video player and the video may stop playing. (1982) On Vista WDDM, video players sometimes use hardware overlays to display video. DisplayLink software does not support hardware overlays and these videos do not display on DisplayLink screens. Examples: PowerDVD 7 uses overlays when playing DVDs and so cannot display DVDs on DisplayLink screens. vlc can be configured to use overlays and will not work on DisplayLink screens if so configured. (1807) On Vista WDDM, some graphics-intensive applications use the GDI or OpenGL interfaces. On DisplayLink attached screens, such applications can display in a window but not full screen. Examples of such applications are Starcraft, Quake 3. Also, video players such as Windows Media Player, WinDVD fail to play in full screen mode on DisplayLink screens on some PCs. (1655, 2134) On Vista WDDM, applications such as games that use Direct3D will not display on a DisplayLink attached screen that is set to primary. (1815) Some players, including Windows Media Player, do not play well on DisplayLink attached screens which are set as primary. (2084) Known issues with specific players and applications On Vista WDDM, if Windows Media Player is moved to the DisplayLink screen and is then made full-screen, the screen blanks. To get out of this situation, either double click on the blank screen and the player window is restored to non-full screen mode, or right click on the blank screen to invoke the player context menu and select exit full screen. (2032) Skype video is believed to be unreliable with Vista. It may cause crashes. On Vista WDDM, if WinDVD is asked to play High-Definition content on a DisplayLink screen, the content will not display and the player may crash. This is because the player uses hardware overlays, which are not supported by DisplayLink software. (1986) On Vista WDDM, if PowerDVD 7 is playing video on a DisplayLink attached screen, and if the screen is rotated, then PowerDVD 7 crashes. The workaround is to apply rotation to the screen before launching PowerDVD 7. (2013) On Vista WDDM, a problem has been observed playing a Blu-ray disk. When two DisplayLink screens were attached, and a Blu-ray disk was inserted, the directly attached screen froze. To avoid this problem, ensure that only one DisplayLink screen is attached when attempting to play a Blu-ray disk. (2637) K4. Installer and Auto-update function -------------------------------------- The installer and auto-update function work on all supported operating systems, both hardware-first and software-first. USB drivers have been signed. Known issues Do not attach two new DisplayLink devices at once as software for one of them may fail to install. Instead, fully install one device and see it working before attaching a second device. (2022) On Vista WDDM, the machine may drop to basic mode when a new DisplayLink screen is connected. This is because of Vista's normal performance calculation when new screens are attached. Aero mode can be restored through Control Panel -> Windows Colour and Appearance -> Open classic appearance properties for more colour options -> Windows Aero. (2069) If you attach a new DisplayLink device, allow software to start installing, then cancel the install part way through, hardware-first install may no longer work. To complete the install, it may be necessary to run setup.exe directly. (1573) Virus checkers set to very high security may prevent the installer from running. They should be set to lower security during installation and restored to high security once installation is complete. (935) When installing, make sure that only a single user is logged into the PC. That user needs administrator privileges. (1112) On PCs where vbscript.dll is not registered with the DLLServer, the DisplayLink installer cannot run. (1824) AutoUpdate dialogs and menus are not yet localised in Hungarian, Portuguese and Traditional Chinese. Other languages are complete. L. Summary of Software State and Issues - Vista XDDM, XP, 2K ============================================================ L1. Normal use -------------- System behaviour with up to six DisplayLink attached screens has been well tested. Testing covers plug/unplug, mode changes, playing video, hibernate, sleep/standby, multiple users, different user rights, attached screen as primary screen, attached screen as only screen, and other aspects. There are many annoyances and intermittent issues. General recommendations when something goes wrong: - try detaching then reattaching the DisplayLink device's USB cable - try changing its display settings using the DisplayLink GUI or the Windows Display Properties dialog box. Known issues - hibernate / sleep / monitor power save / screensavers On all OSes, the desktop background is occasionally missing after restart or after resume from sleep or hibernation. The screens are still usable, and the background can be set again to the desired picture. (2154, 2072) On all OSes, detaching or attaching DisplayLink attached screens while a screensaver is running may cause strange effects. Sometimes it is necessary to detach and reattach the DisplayLink attached screen after exiting the screensaver. (1984) 3D screensavers do not run well on DisplayLink devices and can cause flicker. This is on all OSes. (1150, 1177) When the machine is set to ask for a password after standby / sleep / hibernate / screensaver etc, sometimes the login screen displays on all attached screens and sometimes it displays on a single screen only. If devices are detached from the PC before going into standby, then reattached during standby, very occasionally they may not resume when the PC comes out of standby. If this happens, detach and reattach the devices to make them work again. (1492) Known issues - Windows 2000 Installation of DisplayLink driver on Windows 2000 SP4 requires patch SP4 Rollup 1. This is available from www.microsoft.com. See Microsoft Knowledge Base article KB891861. It is important to check in Windows 2000 that full USB2 is available, otherwise performance will be impaired. To do this, look in Device Manager under Universal Serial Bus Controllers for an item called "USB 2.0 Root Hub". If it is not there then performance will be USB1. (1188) On Windows 2000, when many devices are attached to the PC and the PC is hibernated then woken up, not all the devices come back to life immediately. It is occasionally necessary to detach and reattach the USB connection to a device to coax it back to life. (1293, 1302) Foreign language support on Windows 2000 has not been fully tested. Known issues - other In Powerpoint, the "Display slide show on:" menu has a bug which means that it does not work when there are gaps in the numbering of enabled displays (as shown in WDP). Users of Powerpoint 2007 can get round this by using "Show presentation on:" in the ribbon, rather than the "Set up slide show" box. (2337) CRT monitors may show speckles at very high resolutions. This is because the DisplayLink device cannot always support the high pixel clock required with high CRT refresh rates. (2155) The ATI Catalyst Control Center is a tool provided on machines with ATI graphics cards for managing extra screens. Some versions of this tool crash in the presence of DisplayLink software. This has been observed with versions since ATI driver version 8.360. The workaround is to uninstall the ATI Catalyst Control Centre. (2054) After a reboot, the numbers used in Windows Device Properties to identify the attached screens may change. This is normal. (596) L2. Video players, rendering technologies and applications ---------------------------------------------------------- On Vista XDDM, video support is very limited. With extended screens, video or DVD playback are not supported in general. Exceptions: PowerDVD7 and Quicktime are able to display video on a DisplayLink attached display, so long as that display is the primary display. Video is not supported in clone mode. It works, but exhibits poor performance. (1495) On XP, video support is limited to players that support hardware overlays. In extend mode, the following media players work: - Windows Media Player 11 (www.microsoft.com/windows/windowsmedia/default.mspx) - WinDVD 8 (www.intervideo.com) - PowerDVD 7 (www.cyberlink.com) - RealPlayer 11 (www.real.com) There is limited support for other video players, and for video in mirror mode. This table shows what rendering interfaces are supported: Interface Supported on XP extend? DxVA No D3D No DirectDraw Yes OpenGL No GDI+ No On all platforms, depending on the player, there may be problems if the video window is moved between screens while video is running. It may be necessary to close and restart the video player. Known issues - general Don't change the display mode, position or arrangement of attached screens while a video is running. This usually confuses the video player and the video may stop playing. (1982) Some players, including Windows Media Player, do not play well on DisplayLink attached screens which are set as primary. (2084) DVD movies will not play back if they are dragged to an extended DisplayLink screen while running. They play OK if the player starts up on the extended screen. (no bug number) Known issues with specific players and applications Skype video is believed to be unreliable with Vista. It may cause crashes (no bug number). Skype video does not work on DisplayLink screens with Windows XP. This is because Skype video uses VMR9, which is supported by DisplayLink software on Vista WDDM, but not on Vista XDDM or on XP. Trying to use skype video on XP may cause black screens or freeze the DisplayLink attached screen. (1651) L3. Installer and Auto-update function -------------------------------------- The installer and auto-update function work on all supported operating systems, both hardware-first and software-first. USB drivers have been signed. Known issues On Windows 2000, DisplayLink software fails to install on PCs where Service Pack 4 was installed before installing a MUI pack. This is a Windows issue - see Microsoft Knowledge Base article 263212. To work round this problem, go to Control panel, Regional Options, select the General tab and change the Menus and Dialog combo box to English. You will need to log off, and log back on. Install DisplayLink software, and then set the language settings back to their original settings. (1010) Do not attach two new DisplayLink devices at once as software for one of them may fail to install. Instead, fully install one device and see it working before attaching a second device. (2022) If you attach a new DisplayLink device, allow software to start installing, then cancel the install part way through, hardware-first install may no longer work. To complete the install, it may be necessary to run setup.exe directly. (1573) Virus checkers set to very high security may prevent the installer from running. They should be set to lower security during installation and restored to high security once installation is complete. (935) When installing, make sure that only a single user is logged into the PC. That user needs administrator privileges. (1112) On PCs where vbscript.dll is not registered with the DLLServer, the DisplayLink installer cannot run. (1824) AutoUpdate dialogs and menus are not yet localised in Hungarian, Portuguese and Traditional Chinese. Other languages are complete. (Vista XDDM) Occasionally, after install and reboot, the DisplayLink devices are not operational. In this case, reboot again and they become operational. (969)Download Driver Pack
After your driver has been downloaded, follow these simple steps to install it.
Expand the archive file (if the download file is in zip or rar format).
If the expanded file has an .exe extension, double click it and follow the installation instructions.
Otherwise, open Device Manager by right-clicking the Start menu and selecting Device Manager.
Find the device and model you want to update in the device list.
Double-click on it to open the Properties dialog box.
From the Properties dialog box, select the Driver tab.
Click the Update Driver button, then follow the instructions.
Very important: You must reboot your system to ensure that any driver updates have taken effect.
For more help, visit our Driver Support section for step-by-step videos on how to install drivers for every file type.