Plug And Play Drivers For Mac

Microsoft Plug And Play Driver
Plug And Play Drivers For Macbook Pro
Install Plug And Play Driver
Plug And Play Driver Download
Plug And Play Driver Mac Os

(includes drivers for all of our products and the RIGblaster COMport Splitter software). Mac OSX Drivers: Linux Drivers: RIGblaster Plus: Owner's Manual: USB Adapter Drivers: RIGblaster Plug & Play: Owner's Manual: Windows Drivers: Mac OSX Drivers: Linux Drivers: RIGblaster Nomic: Owner's Manual. For some 3rd party tools like external Audio/Video systems you may have to install the drivers supplied with the tools, but you should be able to discover the devices through the System-Profiler. For devices and services available through the network Apple has developed a plug and play system called Bonjour. Mac driver installation (optional) Your M2 interface is plug-and-play with a Mac: no driver required. However, the optional Mac driver covered in this video gives you the best possible speed (USB latency performance) from your host audio software, plus convenient 'loopback' channels that let you easily capture your computer's output.

-->

This article describes the steps to add Original Equipment Manufacturer (OEM)-supplied drivers to Windows installations.

Original product version: Windows Server 2003
Original KB number: 254078

Summary

This article only includes drivers that are typically installed during graphical user interface (GUI)-mode Setup or after Setup by Plug and Play enumeration. This lets you pre-load OEM Plug and Play drivers that you can use if the associated hardware is added to the system later.

This article describes how to add OEM Plug and Play drivers in the following situations:

Unattended Setup
Sysprep Setup
Remote Installation Service (RIS) installations
Riprep images
Existing Windows installations For more information about how to add OEM supplied mass-storage devices during text-mode Setup, click the following article number to view the article in the Microsoft Knowledge Base:

220845 Adding third-party or updated driver during Windows Setup

More information

Drivers that are installed during the 'Installing Devices' part of GUI-mode Setup have to be found in certain locations. At this point, Setup is installing the devices by using Plug and Play IDs that have been enumerated by Windows Plug and Play. Setup searches a predefined path on the drive, looking in .inf files to find the best match for the Plug and Play ID of the device. By default, this path is defined in the following registry location and is set to %SystemRoot%Inf:HKEY_LOCAL_MACHINESoftwareMicrosoftWindowsCurrentVersionDevicePath: REG_EXPAND_SZ:%SystemRoot%InfSetup uses this path to locate .inf files for device installation. After Setup, this path is also used for any new hardware that is found and installed. If you modify this key during Setup by using the Sysprep.inf file or the Unattended answer file, the value is saved and is also used after Setup.

The following sections contain steps to add OEM-supplied drivers to unattended or Sysprep Setup installations of Windows.

For Microsoft Windows 2000

Unattended setup

When you add drivers to unattended Setup, follow these steps. If the OEM-supplied drivers are not digitally signed, you may receive a message about the drivers during Setup. For more information about how to disable this message, click the following article number to view the article in the Microsoft Knowledge Base:

236029 How to set the driver signing policy for Windows 2000 Unattended Setup

Create your distribution share on a server by copying the contents of the Windows installation disc I386 folder. You can use the Setupmgr.exe program to create this share and the Unattended.txt file. You can find the Setupmgr.exe program on the Windows installation disc in the SupportTools folder in the Deploy.cab file and the Unattend.doc file that contains information about Windows unattended Setup.
Create a $oem$$1Drivers folder in the I386 folder. You may want to create additional folders in the Drivers subfolder, depending on the hardware that you want to install. For example, you may install a network adapter, a modem, or a video. The $1 folder resolves to %SystemDrive%. During text-mode Setup, these folders and files are copied to the %SystemDrive%Drivers folders as follows:
Copy all the OEM-supplied driver files for the device in the folders that you created in the previous step.
Add the OemPnPDriversPath = Driver_Paths entry in the [Unattended] section of the Setup answer file. You can list multiple paths in this key by separating them with a semicolon (;). For example, add the following entry.
[Unattended]
OemPnPDriversPath = 'Driversnetwork adapter;DriversModem;DriversVideo'
Note
The %SystemDrive% environment variable string is automatically inserted before each of the listed search paths.
Save the answer file. During GUI-mode Setup when the system is searching .inf files for Plug and Play IDs, it also looks in the paths that are noted in the OemPnPDriversPath and the standard default path of %WinDir%Inf. The %WinDir%Inf path is listed first in the search order, but if you have a device that is supported by more than one .inf file, Setup continues to search all paths that are specified in the OemPnPDriversPath entry. ((Windows may include a driver that offers generic functionality.) Although it may find multiple matches, Plug and Play uses the .inf file that has the best match, and then installs the associated device driver to support the device.

Sysprep setup

The steps to add OEM-supplied drivers to a Windows Sysprep Setup resemble the steps in the 'Unattended Setup' section, except that you do not have to create the distribution share. To add drivers to the mini-wizard of Sysprep, follow these steps.

Note

To add OEM third-party mass-storage drivers to the Sysprep image that you use to start the computer, you require at least version 1.1 of Sysprep. There have been many updates to the Sysprep tool and to the deployment tools that include Sysprep. Therefore, we recommend that you use the latest version of the Sysprep tool and the deployment tools that are specific to the operating system that you deploy.

On the root of the volume where the %WinDir% folder is located, create a folder structure to hold the OEM-supplied drivers as follows:
Copy the OEM-supplied drivers to their appropriate subfolders.
Add the OemPnPDriversPath = Driver_Paths entry in the [Unattended] section of the Sysprep.inf file. You can list multiple paths in this key by separating them with a semicolon (;) as shown in the following example.
[Unattended]
OemPnPDriversPath = 'Driversnetwork adapter;DriversVideo'

Note

The %SystemDrive% environment variable string is automatically inserted before each of the listed search paths.If you do not want the OEM-supplied drivers to remain on the volume after the mini-wizard is completed, you can add the folder structure that you created in the previous step under the Sysprep folder. You have to adjust the OemPnPDriversPath = key appropriately. The Sysprep folder and its subfolders are automatically removed after Setup is complete.

Save the Sysprep.inf file in the Sysprep folder, and then run Sysprep.exe. Any Plug and Play devices are automatically installed during the mini-setup wizard on the target computers. (These files include those found by using the OEM driver .inf files.)

Note

You do not have to specify the -pnp command-line switch unless there are earlier (ISA) devices on the target computers. If you use the -pnp command-line switch, a full Plug and Play re-enumeration of all devices is performed that adds 5-10 minutes to the Sysprep mini-wizard process. Also, if you specify additional mass-storage controllers by using Sysprep version 1.1 or later versions, the -pnp command-line switch may cause some additional hard disk controllers to appear in Device Manager.For more information, click the following article numbers to view the articles in the Microsoft Knowledge Base:

253340 Non-present SCSI devices appear in Device Manager when you are using Sysprep version 1.1

216937 Windows 2000 System Preparation tool and Answer File usage

Note

If the OEM-supplied drivers are not digitally signed, the mini-wizard postpones the installation of the device until an administrator logs on to the computer. This is referred to as client-side versus server-side installation that occurs during mini-wizard Setup.

For more information, click the following article number to view the article in the Microsoft Knowledge Base:

256204 Unsigned drivers not installed during Sysprep Mini-Wizard without '-pnp' switch

RIS installations

Adding OEM Plug and Play drivers to RIS installations involves the same steps that are listed in the 'Unattended Setup' section, with two small adjustments:

Put the $oem$ folder at the same level as the I386 folder of the RIS image. For example, use the following folder structure:
RemoteInstallSetup%languageImages%dir_name%i386
RemoteInstallSetup%languageImages%dir_name%$oem$$1Drivers
network adapter
MODEM
VIDEO
Modify the RIS image default template (Ristndrd.sif). In the [Unattended] section, change the OemPreinstall = key value from No to Yes, and then add the OemPnPDriversPath = Driver_Path entries. You can list multiple paths in this key by separating them with a semicolon (;) as shown in the following example.
[Unattended]
OemPreinstall = Yes
OemPnPDriversPath = 'Driversnetwork adapter;DriversModem;DriversVideo'
Note
The %SystemDrive% environment variable string is automatically inserted before each of the listed search paths.
Note
If one of the OEM-supplied drivers is for a network adapter device, the RIS server must have this file available when it restarts in text-mode Setup. For more information about this process, click the following article number to view the article in the Microsoft Knowledge Base:
246184 How to add third-party OEM network adapters to RIS installations
If you copy the additional network adapter or mass-storage drivers to the i386 folder as described in Knowledge Base article 246184, stop and restart the BINL service on the RIS server. To stop and restart the BINL service, type the following commands at the command prompt, and then press ENTER after each command:
- net stop 'boot information negotiation layer'
- net start 'boot information negotiation layer'

Riprep images

Riprep and Sysprep share much of the same functionality. Therefore, adding OEM Plug and Play drivers to computers that will be imaged involves steps that resemble those that are used for Sysprep. Before you run Riprep against the image computer to copy it to the RIS server, follow these steps:

Create a folder named Sysprep on the %SystemDrive% folder. (This is most likely drive C because Riprep.exe can only copy one volume/partition.)
On the root of the same volume, create a folder structure to hold the OEM-supplied drivers as follows:
Copy the OEM-supplied drivers to their appropriate subfolders.
Create a Sysprep.inf file in the Sysprep folder, and then add the [Unattended] and OemPnPDriversPath = Driver_Path entries. You can list multiple paths in this key by separating them with a semicolon (;). For example:
[Unattended]
OemPnPDriversPath = 'Driversnetwork adapter;DriversVideo'
Note
The %SystemDrive% environment variable is automatically inserted before each of the listed search paths that are specified.
Note
If the device has already been recognized by the operating system as a known or unknown device, you must remove the device by using Device Manager before you run Sysprep or the updated drivers are not installed on startup during mini-Setup.
Run the Riprep.exe program from the RisServer ReminstAdminI386 folder on the client computer to copy the image to the selected RIS server. Riprep looks in the Sysprep folder for a Sysprep.inf file, reads the OemPnPDriversPath= key, and then updates the following registry subkey:HKEY_LOCAL_MACHINESoftwareMicrosoftWindowsCurrentVersionDevicepathThen, Riprep copies the registry up to the server so that it can be used during the mini-Setup wizard.

Note

The default Riprep.sif file that is created during this process is not affected by the entry in the Sysprep.inf file that was created in the previous steps.

Note

If one of the OEM-supplied drivers is for the primary network adapter, the RIS server must also have this file available from a typical RIS flat image before the Riprep image is downloaded. If this is the case, you must also follow the procedure that is described in the 'RIS Installations' section or use the procedure that described in the following Microsoft Knowledge Base article:

246184 How to add third-party OEM network adapters to RIS installations

If the image is already created and you want to add OEM-supplied Plug and Play drivers, we recommend that you use RIS to download the image to a computer, follow the steps listed in the previous 'Riprep Images' section, and then Riprep the image back to the RIS server.

Note

One side effect is that the driver paths are entered two times in the SoftwareMicrosoftWindowsCurrentVersionDevicePath key.

For more information, click the following article number to view the article in the Microsoft Knowledge Base:

258862 Riprep.exe adds duplicate paths to the registry

Existing Windows installations

You may have to add new hardware devices to existing Windows-based computers that require OEM-supplied drivers. Although this process requires that you install the new device, you may want the OEM-supplied drivers to be distributed in a controlled manner or to be centrally located on one server. To do this, follow these steps:

Decide whether you want to copy the drivers locally or if you want to store them on a central distribution server. If you want to store the drivers locally on the computer's hard disk, you must have a procedure to copy the drivers to the computer. (For example, use logon scripts, Microsoft Systems Management Server (SMS) batch jobs, or other methods.)
After the distribution method is determined, obtain the path for the device drivers. If you want to copy them locally, the path may be C:Driversnetwork adapter. If you want them copied to a centrally located server, the path may be ServerName Drivers network adapter (where Drivers is a shared folder).
The DevicePath key in the local computer's registry has to be updated to reflect the new OEM driver locations. You must have an automated method of remotely updating the registry key. You can use Regedit files together with logon scripts or with an SMS batch job. The default value is located in the following registry key:HKEY_LOCAL_MACHINESoftwareMicrosoftWindowsCurrentVersionDevicePath: REG_EXPAND_SZ:%SystemRoot%Inf
Edit the DevicePath key by using Regedt32.exe so that path where the drivers are located is included in the search path.

Important

This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base: 322756 How to back up and restore the registry in Windows

For example, if the drivers are copied locally to the root of the drive where the %WinDir% folder resides (Driversnetwork adapter), the DevicePath final value must read:DevicePath: REG_EXPAND_SZ:%SystemRoot%Inf;%SystemRoot%Driversnetwork adapterIf the drivers are kept on a centrally located server or distribution point, you have to add the UNC path to the OEM-supplied drivers. For example:

DevicePath: REG_EXPAND_SZ:%SystemRoot%Inf; ServerName ShareName Driversnetwork adapter

Microsoft Plug And Play Driver

Note

%SystemRoot% is not automatically appended because the Setup process does not add the values. You must manually type the value of %SystemRoot% if you edit the registry.After you have completed these steps and new hardware is installed, when a user logs on, Plug and Play locates the new hardware and searches the device paths you specified to locate the OEM-supplied drivers. Notice that all the rules that apply to signed/unsigned drivers also apply to devices that are installed after Setup. If the OEM-supplied drivers for the new device are not digitally signed and a non-administrator user logs on to the computer after the new hardware is installed, the user cannot complete the installation of the device until an administrator logs on to the computer.For more information, click the following article number to view the article in the Microsoft Knowledge Base:

219435 Non administrator permissions to load and unload device drivers

Note

If the device has already been recognized by the operating system as a known or unknown device, you must remove the device through Device Manager before you run Sysprep or the updated drivers are installed on startup during mini-setup.

Plug And Play Drivers For Macbook Pro

For Windows Server 2003

Unattended setup

236029 How to set the driver signing policy for Windows 2000 Unattended Setup

Create your distribution share on a server by copying the contents of the Windows installation CD-ROM I386 folder. You can use Setupmgr.exe to create this share and your Unattended.txt file. You can find Setupmgr.exe on the Windows or service pack CD-ROM in the SupportTools folder in the Deploy.cab file and the deploy.chm and ref.chm Help files that contain information about Windows unattended Setup. You can also download the latest files from the Microsoft Web site.
Create a $oem$$1Drivers folder in the I386 folder. You may want to create additional folders in the Drivers subfolder, depending on the hardware that you want to install (for example, network adapter, modem, or video). The $1 folder resolves to %SystemDrive%. During text-mode Setup, these folders and files are copied to the %SystemDrive%Drivers folders. For example:
Copy all the OEM-supplied driver files for the device in the folders that you created in the previous step.
Add the OemPnPDriversPath = Driver_Paths entry in the [Unattended] section of the Setup answer file. You can list multiple paths in this key by separating them with a semicolon (;). For example:
[Unattended]
OemPnPDriversPath = Driversnetwork adapter;DriversModem;DriversVideoUpdateInstalledDrivers = Yes | No
Note
The %SystemDrive% environment variable string is automatically inserted before each of the listed search paths.
Save the answer file. During GUI-mode Setup when the system is searching .inf files for Plug and Play IDs, it also looks in the paths that are noted in the OemPnPDriversPath and the standard default path of %WinDir%Inf. The %WinDir%Inf path is listed first in the search order, but if you have a device that is supported by more than one .inf file (Windows may include a driver that offers generic functionality), Setup continues to search all paths that are specified in the OemPnPDriversPath entry. Although it may find multiple matches, Plug and Play uses the .inf file that has the best match, and then installs the associated device driver to support the device.

Sysprep setup

Note

We recommend that you use the latest version of Sysprep that is available for your operating system.

On the root of the volume where the %WinDir% folder is located, create a folder structure to hold the OEM-supplied drivers. For example:
Copy the OEM-supplied drivers to their appropriate subfolders.
Add the OemPnPDriversPath = Driver_Paths entry in the [Unattended] section of the Sysprep.inf file. You can list multiple paths in this key by separating them with a semicolon (;). For example:
[Unattended]
OemPnPDriversPath = Driversnetwork adapter;DriversVideoUpdateInstalledDrivers = Yes | No

Note

The %SystemDrive% environment variable string is automatically inserted before each of the listed search paths.If you do not want the OEM-supplied drivers to remain on the volume after the mini-wizard is complete, you can add the folder structure that you created in the previous step under the Sysprep folder. You have to adjust the OemPnPDriversPath = key appropriately. The Sysprep folder (and its subfolders) is automatically removed after Setup is finished.

Save the Sysprep.inf file in the Sysprep folder and run Sysprep.exe. Any Plug and Play devices (including those found by using the OEM driver .inf files) are automatically installed during the mini-setup wizard on the target computers. Notice that you do not have to specify the -pnp command-line switch unless there are earlier (ISA) devices on the target computers. If you use the -pnp command-line switch, a full Plug and Play re-enumeration of all devices is performed, that adds 5-10 minutes to the Sysprep mini-wizard process. Also, if you specify an additional mass-storage controller, the -pnp command-line switch may cause some additional hard disk controllers to appear in Device Manager.For more information, click the following article number to view the article in the Microsoft Knowledge Base:

892778 Updated System Preparation tool for Windows Server 2003 Service Pack 1

Note

For more information, click the following article number to view the article in the Microsoft Knowledge Base:

256204 Unsigned drivers not installed during Sysprep mini-wizard without '-pnp' switch

RIS installations

Adding OEM Plug and Play drivers to RIS installations involves the same steps that are listed in the 'Unattended Setup' section, with two small adjustments:

Put the $oem$ folder at the same level as the I386 folder of the RIS image. For example, use the following structure:
RemoteInstallSetup%languageImages%dir_name%i386
RemoteInstallSetup%languageImages%dir_name%$oem$$1Drivers
network adapter
MODEM
VIDEO
Modify the RIS image default template (Ristndrd.sif). In the [Unattended] section, change the OemPreinstall = key value from No to Yes, and then add the OemPnPDriversPath = Driver_Path entries. You can list multiple paths in this key by separating them with a semicolon (;) as follows:
[Unattended]
OemPreinstall = Yes
OemPnPDriversPath = 'Driversnetwork adapter;DriversModem;DriversVideo'
UpdateInstalledDrivers = Yes | No
Note
The %SystemDrive% environment variable string is automatically inserted before each of the listed search paths.
Note
If one of the OEM-supplied drivers is for a network adapter device, the RIS server must have this file available when it restarts in text-mode Setup. For more information about this process, click the following article number to view the article in the Microsoft Knowledge Base:
246184 How to add third-party OEM network adapters to RIS installations
If you copy the additional network adapter or mass-storage drivers to the i386 folder as described in Knowledge Base article 246184, stop and restart the BINL service on the RIS server. To stop and restart the BINL service, type the following commands at the command prompt, and then press ENTER after each command:
- net stop 'boot information negotiation layer'
- net start 'boot information negotiation layer'

Riprep images

Create a folder named Sysprep on the %SystemDrive% folder. (This is most likely drive C because Riprep.exe can only copy one volume or partition.)
On the root of the same volume, create a folder structure to hold the OEM-supplied drivers as follows:
Copy the OEM-supplied drivers to their appropriate subfolders.
Create a Sysprep.inf file in the Sysprep folder, and then add the [Unattended] and OemPnPDriversPath = Driver_Path entries. You can list multiple paths in this key by separating them with a semicolon (;) as follows:
[Unattended]
OemPnPDriversPath = Driversnetwork adapter;DriversVideoUpdateInstalledDrivers = Yes | No
Note
The %SystemDrive% environment variable is automatically inserted before each of the listed search paths that are specified.
Note
If the device has already been recognized by the operating system as a known or unknown device, you must remove the device through Device Manager before you run Sysprep or the updated drivers are not installed on startup during mini-Setup.
Run the Riprep.exe program from the RisServer ReminstAdminI386 folder on the client computer to copy the image to the selected RIS server. Riprep looks in the Sysprep folder for a Sysprep.inf file, reads the OemPnPDriversPath= key, and then updates the following registry subkey:HKEY_LOCAL_MACHINESoftwareMicrosoftWindowsCurrentVersionDevicepathThen, Riprep copies the registry up to the server so that it can be used during the mini-Setup wizard.

Note

The default Riprep.sif file that is created during this process is not affected by the entry in the Sysprep.inf file that was created in the previous steps.

Existing Windows installations

Decide whether you want to copy the drivers locally or if you want to store them on a central distribution server. If you want to store the drivers locally on the computer's hard disk, you must have a procedure to copy the drivers to the computer. For example, use logon scripts, Microsoft Systems Management Server (SMS) batch jobs, or other methods.
After the distribution method is determined, obtain the path for the device drivers. If you want to copy them locally, the path may be C:Driversnetwork adapter. If you want them copied to a centrally located server, the path may be ServerName Drivers network adapter. (**Drivers are a shared folder.)
The DevicePath key in the local computer's registry has to be updated to reflect the new OEM driver locations. You must have an automated method of remotely updating the registry key. You can use Regedit files together with logon scripts or with an SMS batch job. The default value is located in the following registry subkey:HKEY_LOCAL_MACHINESoftwareMicrosoftWindowsCurrentVersionDevicePath: REG_EXPAND_SZ:%SystemRoot%Inf
Edit the DevicePath key by using Registry Editor so that path where the drivers are located is included in the search path.

Important

For example, if the drivers are copied locally to the root of the drive where the %WinDir% folder resides (Driversnetwork adapter), the DevicePath final value must read as follows:DevicePath: REG_EXPAND_SZ:%SystemRoot%Inf;%SystemRoot%Driversnetwork adapterIf the drivers are kept on a centrally located server or distribution point, you have to add the UNC path to the OEM-supplied drivers. For example:

DevicePath: REG_EXPAND_SZ:%SystemRoot%Inf; ServerName ShareName Driversnetwork adapter

Note

%SystemRoot% is not automatically appended because the Setup process does not add the values. You must manually type the value of %SystemRoot% if you edit the registry.Assume that you have completed these steps and new hardware is installed. When a user logs on, Plug and Play locates the new hardware and searches the device paths that you specified to locate the OEM-supplied drivers. Notice that all the rules that apply to signed and unsigned drivers also apply to devices that are installed after Setup. Assume that the OEM-supplied drivers for the new device are not digitally signed and a non-administrator user logs on to the computer after the new hardware is installed. In this case, the user cannot complete the installation of the device until an administrator logs on to the computer.For more information, click the following article number to view the article in the Microsoft Knowledge Base:

219435 Non administrator permissions to load and unload device drivers

Note

Install Plug And Play Driver

If the device has already been recognized by the operating system as a known or unknown device, you must remove the device by using Device Manager before you run Sysprep or the updated drivers are installed on startup during mini-Setup.

You can attach up to 4 additional displays on any Intel Mac OS X system with DisplayLink-based USB virtual graphics adapters. Whenever images are redrawn, the CPU is heavily involved, so it may not be as snappy as your main monitor — but it’s the easiest way to build an amazing, plug and play multiple monitor setup on the Mac.

Plug And Play Driver Download

If you’ve never installed DisplayLink’s Mac drivers, here’s a walk-through of the steps (using OS X 10.6.7 and DisplayLink’s v1.6 Mac driver):

1. Fire up Safari, go to this page to download the Mac driver :
http://www.displaylink.com/support/mac_downloads.php

You’ll want to download the latest driver, because DisplayLink’s Mac drivers are still improving, and because new Apple OS updates often require updated drivers from 3rd parties.

2. Once there, make sure you tick the ‘I agree to the terms of the DisplayLink End User License Agreement (EULA)’ and then click on ‘Download Driver’.

Plug and play drivers for mac windows 10

3. Safari will instantly start downloading the driver and automatically mount it on your desktop. Once the download is done you should see a ‘DisplayLink installer’ icon on your desktop. Double click on the ‘DisplayLink Installer’ on your Desktop.

4. The ‘DisplayLink Installer’ will pop up. Double click on ‘DisplayLink Software Installer.pkg’

5. You may get a warning: “This package will run a program to determine if the software can be installed”. Click ‘Continue’.

6. On the ‘Install DisplayLink Software’ window click ‘Continue’ to proceed.

7. The ‘Software License Agreement’ will be presented. Proceed by clicking ‘Continue’ again.

8. Click ‘Agree’ to agree with the software license agreement.

9. You’ll get the ‘Select a Destination’ screen. Click on the disk where you want to install the DisplayLink Software, and click ‘Continue’ to proceed.

10. Install to the standard location – just click ‘Install’.

11. You should get a pop up for your password to alow the installer to make changes. Type in your password and click ‘OK’.

12. You’ll get a warning that the computer will need to restart. This is normal, click ‘Continue Installation’.

13. The installation will finish. You should get a message that ‘The installation was successful’. Click ‘Restart’ to finish installing.

14. When the computer finishes restarting, log in and plug in the USB-VGA-165. As soon as you plug it in, the secondary monitor should be autodetected and ready for use.

15. To further configure your monitors, do the following: Click on ‘System Preferences’->

Under ‘Hardware’ click on ‘Displays’

Click on ‘Arrangement’ to re-arrange your displays.

Finally to change your primary monitor, all you have to do is go to ‘Arrangement’. Click on the white bar and drag it to the other screen. As soon as you release the mouse the primary monitor will change.

Notes:

DisplayLink’s virtual USB graphics don’t support OpenGL or Quartz Extreme, so apps that do high-end 3D or video should stay on your main monitor.
DisplayLink adapters can support VGA, DVI, and HDMI as outputs (below is a high end one that supports all three, and a less expensive one that’s VGA only). They don’t support DisplayPort or any of the earlier Apple proprietary connectors, so watch out with Apple Cinema displays.

[amtap amazon:asin=B0038P1TP4][amtap amazon:asin=B004AIJE9G]

Plug And Play Driver Mac Os

Hope this helps! If you have any trouble at all, feel free to contact us at http://support.plugable.com/ or email support@plugable.com

Regards,

Lampros (Plugable Support)