12-23-2013, 12:14 AM
Yeah, on Windows the driver install process is (in brief):
1. User installs the driver package, which just stages the drivers for full installation when hardware is connected
2. When hardware that isn't recognized is connected, the OS looks for possible drivers, and finds the drivers that were staged in step 1
3. The OS completes the installation of the drivers from the staging location to the active driver location
I think that what's happening here is that, regardless of what mode (admin, etc.) you install/run in, if you start the SCP software after installing but before actually plugging the hardware in, you're going to hit this situation.
As an end user, I think you've got 2 ways to deal with this:
- Plug in the hardware and complete the driver loading before starting the software
- Manually put the required file where the SCP software can find it
As an application developer, you've also got 2 choices:
- Gracefully recognize the lack of required drivers, and offer appropriately degraded functionality
- Just bail out and deal with the support issues as they come up
It *may* be that on Win 8 the FTDI drivers are already installed, or you're on a machine that's already had them installed for some other piece of hardware, or previous SCP install, or some other thing. But, I can repro this 100% on a clean install of Win 7.
Some interesting details:
http://msdn.microsoft.com/en-us/library/...s.85).aspx
Cheers,
Robert
1. User installs the driver package, which just stages the drivers for full installation when hardware is connected
2. When hardware that isn't recognized is connected, the OS looks for possible drivers, and finds the drivers that were staged in step 1
3. The OS completes the installation of the drivers from the staging location to the active driver location
I think that what's happening here is that, regardless of what mode (admin, etc.) you install/run in, if you start the SCP software after installing but before actually plugging the hardware in, you're going to hit this situation.
As an end user, I think you've got 2 ways to deal with this:
- Plug in the hardware and complete the driver loading before starting the software
- Manually put the required file where the SCP software can find it
As an application developer, you've also got 2 choices:
- Gracefully recognize the lack of required drivers, and offer appropriately degraded functionality
- Just bail out and deal with the support issues as they come up
It *may* be that on Win 8 the FTDI drivers are already installed, or you're on a machine that's already had them installed for some other piece of hardware, or previous SCP install, or some other thing. But, I can repro this 100% on a clean install of Win 7.
Some interesting details:
http://msdn.microsoft.com/en-us/library/...s.85).aspx
Cheers,
Robert