I did some more digging on the deployment issues between win7 on 64 bit laptops and this is what I have found to date.
Microsoft is aware of some devices not waking up after hibernating and I tried every suggestion they had and none worked except on a temporary basis. Some would work until a full reboot of the laptop.
Before I installed service pack one the port that the Panda was hooked to would not redeploy a Panda, or work with anything else after the first deployment. If you move to a second (and third) port they would work once and then become essentially dead and not recognize anything, not even a mouse or thumbdrive.
After installing service pack one the port would work with anything except the panda until the panda was rebooted.
If the code on the panda has a single Debug.Print, when the laptop goes into hibernation the Panda will freeze. This timing became apparent when I added a serial lcd to the panda.
If the panda has no Debug.Print lines it will happily go on working but if you try to redeploy after restarting the laptop it will not be recognized.
This happens regardless of what is running on the laptop. If there are no programs running and the panda is plugged in it will freeze if it has a Debug line.
The workaround I have been using is to unplug the panda before the laptop hibernates, and plug it back in after a reboot and view the debug info through MfDeploy, or just shutdown the hibernate function which is really not a good option in the field running on batteries.
I put a scope on the usb port to see if I could see what it was saying to drive the Panda into a catatonic state, but my coal fired dual trace has no record facility. The DSO Nano is only single trace which is not useful on D+ D- lines.
While on the Scope subject, has anyone actually received a DSO Quad, and are they worth the postage?