Registered: Jan 2001
Location:
Posts: 16

BSOD on XP during hotsync

I've recently installed WIndows XP Pro (clean installation). When I installed Palm Desktop (4.01Hb--the XP version), everything goes fine until the first hotsync. THe system finds the hardware and installs the visorusb.sys file. However, when I hotsync, the hotsync starts normally, but then crashes windows (usually while transfering datebook, but not always). I get a blue screen stop error "driver_irql_not..." and must reboot.

My cradle is plugged into the USB hub on my monitor (Hitachi CM814), which is plugged in to an Adaptec USBConnect USB 2.0 PCI card. My motherboard is an Abit VP6 with dual P3-1GHz. Onboard USB is isabled in the BIOS.

If I use my travel hotsync cable, plugged directly into one of the Adaptec USBConnect connectors, then I can hotsync with out error (except for the need to reset my visor between hotsyncs or the visor crahses with a fatal error--but that is another problem).

Given my physical setup, it is much more convenient to use the crable through the monitor's hub. This setup worked fine previously with windows 98SE and Windows 2000 Pro.

I have tried uninstalling, clearing the registry, and reinstalling. I have tried disabling the USB power management features. Neither helped.

Any suggestione would be appreciated.

Thanks,
Bob

Registered: Dec 1999
Location: Connecticut USA
Posts: 2682

Re: BSOD on XP during hotsync

quote:

---

Originally posted by rewilson
My cradle is plugged into the USB hub on my monitor (Hitachi CM814), which is plugged in to an Adaptec USBConnect USB 2.0 PCI card. My motherboard is an Abit VP6 with dual P3-1GHz. Onboard USB is isabled in the BIOS.

---

__________________

God bless America, my home sweet home...

Registered: Jan 2001
Location:
Posts: 16

Re: Re: BSOD on XP during hotsync

quote:

---

Originally posted by MarkEagle
I would try enabling and using a standard USB port. XP doesn't have any native support for USB 2.0 yet (MS is supposed to add it in a Service pack sometime later).

---

The reason I have the on-board USB disabled is that they caused all sorts of instability problems (VIA chipset and all ). The adaptec card was purchased to replace them. I got the 2.0 card for future 2.0 use, but presently, I do not have any 2.0 devices. The sync works off the 2.0 card--when plugged in directly and not through the hub.

Bob

Registered: Dec 1999
Location: Connecticut USA
Posts: 2682

Re: Re: Re: BSOD on XP during hotsync

quote:

---

Originally posted by rewilson
The sync works off the 2.0 card--when plugged in directly and not through the hub.

---

__________________

God bless America, my home sweet home...

Registered: Jan 2001
Location:
Posts: 16

Re: Re: Re: Re: BSOD on XP during hotsync

quote:

---

Originally posted by MarkEagle
Is the hub self-powered? I've had trouble syncing through a non-powered hub before. Never had any problems through a self-powered one. Sounds to me like that's your problem.

---

Registered: Dec 1999
Location: Connecticut USA
Posts: 2682

Re: Re: Re: Re: Re: BSOD on XP during hotsync

quote:

---

Originally posted by rewilson
The hub is part of the monitor and is therefore powered via the monitor.

---

I can't find any info on that particular monitor, but my guess is that it's a non-powered hub (drawing its power from the USB master).

Since you said you can sync when attached directly to the card, would it be that much of an inconvenience to attach the cradle there? I know we're all creatures of comfort, but sometimes we need to sacrifice...

__________________

God bless America, my home sweet home...

Registered: Jan 2001
Location:
Posts: 16

Re: Re: Re: Re: Re: Re: BSOD on XP during hotsync

quote:

---

Originally posted by MarkEagle
I can't find any info on that particular monitor, but my guess is that it's a non-powered hub (drawing its power from the USB master).

Since you said you can sync when attached directly to the card, would it be that much of an inconvenience to attach the cradle there? I know we're all creatures of comfort, but sometimes we need to sacrifice...

---

Registered: Aug 2001
Location: Cuyahoga Falls, Ohio
Posts: 51

Have you tried plugging your travel cable into the hub to see if that works? Just wondering. I would say though to plug the hub into the computer directly like Mark says. Let us know what happens.

Registered: Jan 2001
Location:
Posts: 16

quote:

---

Originally posted by PlantATree
Have you tried plugging your travel cable into the hub to see if that works? Just wondering. I would say though to plug the hub into the computer directly like Mark says. Let us know what happens.

---

Registered: Jan 2001
Location:
Posts: 16

Reinstalled Palm Desktop today. Had a few blue screens using the travel cable plugged directly into the Adaptec USB card. Also had one successful hotsync using the cradle plugged into a hub (which was plugged into the Adaptec card).

In other words, plugging directly into the USB card (bypassing the hub) does NOT appear to reliably solve my problem. Somewhat better odds of having hte hotsync succeed, but not good enough.

However, I found a reference to a similar problem someone else who was also running a dual processor system (I'm running dual P3-1GHz processors). If I set the affinity of hotsync.exe to use only CPU 0 I can hotsync using my original cable, plugged into the hub. I did about 5 hotsyncs, with only one crash. Not sure if the crash was caused by something else or not as it did not occur again. I could probably improve the stability by booting into single CPU mode, but that would slow down everything (and I'm not sure XP has the same single CPU mode as 2K has).

The biggest problem with this setup is that I need to remember to set the affinity for hotsync.exe every time I log in, as it is reset to use both CPU's everytime the program is started. If someone knows how to make the affinity setting "stick" across reboots, please let me know!

--Bob

Registered: Feb 2001
Location: Atlantic Rim
Posts: 570

Assumptions...

Assuming that you've installed the Windows XP drivers for USB 2.0, this could be a compatibility issue with Palm Desktop 4.

Just because USB 2.0 says its backwards compatible with USB 1.0 devices doesn't mean that there aren't kinks. Any other Visor users out there synching with a USB 2.0 card using Windows XP and the Palm 4 desktop?

Registered: Jan 2001
Location:
Posts: 16

Re: Assumptions...

quote:

---

Originally posted by Keefer Lucas
Assuming that you've installed the Windows XP drivers for USB 2.0, this could be a compatibility issue with Palm Desktop 4.

---

Registered: Aug 2001
Location: Cuyahoga Falls, Ohio
Posts: 51

What OS where you using when you were using the on-board USB ports? Maybe it will work with XP if you haven't tried that yet. Also, do you have the latest drivers installed for your motherboard, such as the infamous Via 4 in ones? They have released new ones since the release of XP. Have you checked to see if any bios updates have been released for your motherboard?

I really would suggest trying the on-board USB ports again under XP if you haven't tried it and hold off on the new USB 2.0 until new drivers are released and you really need it. Your system already sounds pretty complex and at the edge of technology with dual processors and all, and then throwing in a new USB 2.0 card could be just making matters worse. XP can be very finicky if everything isn't working just right and it doesn't have stable approved drivers to support everything.

Registered: Feb 2001
Location: Atlantic Rim
Posts: 570

Orange you glad....

Orange has released XP drivers for their USB 2.0 products.

http://www.orangemicro.com/updateusb2win.html

Trying to run the card on a system without proper drivers....I guess I wouldn't spend too much time wondering what the problem is. Guess you'll have to wait and see.

Registered: Jan 2001
Location:
Posts: 16

In answer to some recent questions:

I was previously using Win 2000 Pro. I have NOT tried re-enabling the onboard USB ports under XP as everything else works better with the Adaptec 2.0 ports. XP DOES support the card, just not the 2.0 features--it is supported as a USB 1.1 device.

I've updated EVERYTHING I can--latest winXP patches, latest VIA 4in1, checked for Adaptec USB drivers (none yet for XP except those on the XP disc), using the latest desktop from handspring site.

My hotsync problem appears to NOT be related to the USB hub or card as I originally thought. As long as I only allow hotsync.exe to run on ONE processor, it works. Therefore, it appears that my problem is due to an incompatibility in hotsync related to SMP.