Error waking up from standby

[perf]

When my computer wakes up from standby, I get an error message saying the USB-UIRT can not be found, and the unit does not work until I have restarted the computer, or disconnected the device and connected it again. How can I troubleshoot?

(BTW, I can get the USB-UIRT to wake up the computer, but from then on it does not work.)

[jrhees]

perf,

I'll take a look at this and see what I can find. What OS are you using?

-Jon

[perf]

I use Windows 2000.

While searching for solutions today, I downloaded and upgraded to a newer version of the FTDI D2XX driver, but it made no difference.

This is a shame, since the unit does everything (else) I expected very well. I (intend to) use it for tuning the correct channel on my cable box when the PC wakes up to start a scheduled recording.

Is some way of turning off the USB driver, so the "OnStandby" event in Girder could be used to "protect" good operation? Or is there some way of restarting the driver using the "OnResumeStandby" event?

Other units connected to my computer via USB manage the wakeup fine.

/Per

[jrhees]

perf,

We definitely need to get this working for you. If you could test one thing for me, I would appreciate it:

1. Launch Girder and enable devices and verify the USB-UIRT is working.
2. DISABLE all devices by pressing F9
3. SUSPEND the computer
4. RESUME the computer (by pressing the power button)
5. When resumed, press F9 in Girder to enable devices and see if you get the error message, etc.

Then, repeat steps 1-5 again but this time in step 4 resume the computer using the remote control via the USB-UIRT.

Thanks,

Jon

[perf]

Both scenarios give the same result: When I press F9 after resuming the PC, I get the error message. (I actually need to press F9 twice. After the first keypress, nothing happens - the Girder tray icon still shows devices disabled. After the second F9, I get the error message and the icon changes to normal.)

/Per

[jrhees]

Thanks for testing,

I'll let you know what I find.

-Jon

[jrhees]

perf,

Could you do a few more tests for me?

1. Plug in the USB-UIRT, but do *not* launch Girder.
2. Open up Device Manager and look under the 'USB...' tree and verify that you see the USB-UIRT listed.
3. Close Device Manager
4. Suspend and Resume the machine.
5. Go back into Device Manager and look to see if you can see the USB-UIRT device.
6. Try launching Girder as well at this point.

Some questions:
1. Are you using any other USB devices?
2. If so, do they appear in Device Manager after resume?
3. After resuming, does the indicator LED on the USB-UIRT blink when you press a remote control button?
4. If you're using other USB devices, can you try suspending/resuming with these devices unplugged?

Thanks,

Jon

[Guest]

Did the test:
- The USB-UIRT is listed in device manager when the computer starts
- The USB-UIRT is still listed after suspend and resume
- Starting Girder at this point gives the error message

The questions:
1. I also use a USB WLAN adapter
2. The WLAN adapter appears in device manager before and after suspend/resume
3. The indicator LED always (before, during and after suspend) blinks when I use the remote
4. I have tried disconnecting the WLAN adapter and uninstalling its drivers. There is no change in what happens with the USB-UIRT

Some interesting findings from my own tests:
- I can get the USB-UIRT to work again after resume by inactivating and reactivating it in device manager (If I could get Girder to do this for me, I would have a workaround.)
- The USB-UIRT and Girder show exactly the same behaviour on my second computer, a Win2000 Toshiba laptop with an ALI USB controller. My first computer is a Shuttle SK41G with VIA USB 2.0 controllers.

[perf]

Oops, missed logging in.

The above post from "Guest" is of course from me.

/Per

[jrhees]

OK - last question (sorry no answers yet)

Could you go to \Windows\System32\Drivers\ and find FTD2XX.SYS and right click on it and choose 'Properties' and go to the 'Version' tab and list what version it says. You also mentioned you found another version driver (may I ask what version and where?)

Thanks,

Jon

[perf]

I got the newer version of the driver from

http://www.ftdichip.com/FTD2XXDriver.htm

The version I downloaded is version 1.05.04. I changed the .inf file so it corresponded to the file in the .zip file from you. According to FTDI's release info a "Suspend / Resume Problem with open devices (Win2000/WinXP)" was fixed in version 1.04.01 - this is what made the upgrade unresistable for me , and the disappointment even greater .

The FTD2XX.sys in \WINNT\system32\drivers is version 1.5.4.1. (I have not gone back to the previous version.)

/Per

[perf]

Jon,

Any ideas?

/Per

[jrhees]

Per,

I'm evaluating a new driver from FTDI. However, I have been unable to duplicate your issue on any of my Win2K boxes. Very strange. After a bit more testing I'll forward this driver onto you for testing.

-Jon

[perf]

Jon,

Interesting that you do not have this problem with W2k. Since both my computers had the problem, I thought it was a general issue.

Then I should do more testing. Both my PCs have W2k SP3 and perhaps "overzealous" application of Windows updates in common. I have had Windows updates breaking things (like IRDA support) before. I will test removing the updates. Do your boxes run SP3?

/Per

[perf]

Did some more testing:

Removed all Windows 2000 updates (except SP3) - made no difference.

Tried on my girlfriend's W2k laptop - same behaviour upon resume.

Dug out my old WinME box: The USB-UIRT works after resume on this machine, so there is no hardware problem with it.

So now I have tried three different, albeit similarly configured W2k PCs, and I get the same results. All three have SP3, but I am a bit reluctant to remove it. All three also have the Swedish version of W2k, but I doubt that that could be the problem. I will have to think about what else they have in common.

/Per