BSOD on Hotsync

[lagomilo]

Hello, Has anybody been getting a BSOD when doing a usb hotsync. I keep getting the blue screen of death with PALMUSBD.sys as the problem. I have uninstalled and reinstalled the palm desktop several times. Can anybody help.

p.s. I can do a wifi hotsync but I also want to use card export II. Thanks in advance.

Lago

[jjesusfreak01]

Hello, Has anybody been getting a BSOD when doing a usb hotsync. I keep getting the blue screen of death with PALMUSBD.sys as the problem. I have uninstalled and reinstalled the palm desktop several times. Can anybody help.

p.s. I can do a wifi hotsync but I also want to use card export II. Thanks in advance.

Lago
Ugh, thats happened to me once. You dont by any chance have multiple PDAs on one PC? If one of them is significantly older, then there can be conflicts. Try removing CardExport temporarily, and see if it fixes the problem.

[lagomilo]

I had upgraded from a T3 and the TX was working fine for a while. The hotsync started giving me problems so I removed the palm desktop, used norton to clean my registry and reinstalled. Stil wont sync using usb.

[WildCelt]

Yes, this happens to me every time. Even when I simply plug it into the hotsync cable, it immediately BSODs on me. I am currently forced to hotsync via wifi (which is an exercise in frustration most of the time as well, since about half of my hotsyncs crap out on me).

This handheld does not act the same as my T3 when plugged in. I hear the Windows "You've plugged something in" sound whenever it is attached to the cable, and the unit powers on even when off. When plugging the T3 in, my PC sits there oblivious until I press the hotsync button. I assume everyone else has the same experience, but does anyone know why? I know my wife's T5 does that as well, but I assumed it was because of the extended drive (or whatever its called). The T|X does not have that, so shouldn't it just sit there until a hotsync is initiated?

I think the PC crashes has something to do with how I installed. I plugged the cable in, attached the T|X, and it immediately it recognized something was plugged in and attempted to install drivers. I had not installed the T|X software on the desktop, however, so I cancelled the driver install. BIG mistake. When I did install everything, well you know the rest.

I installed Palm Desktop on my work machine as well, but before plugging in the handheld. This time, it worked fine.

The install card that came with the T|X shows one is to plug in everything first, then install the software. Obviously this caused problems for me.

[mrdeucie]

Ugh, thats happened to me once. You dont by any chance have multiple PDAs on one PC? If one of them is significantly older, then there can be conflicts. Try removing CardExport temporarily, and see if it fixes the problem.

I experienced the same problem trying to keep a Handspring Visor Deluxe and a Sony Clie SJ30 on the same XP Pro machine. My only solution was to sync them on different machines.

[WildCelt]

I had a very strange thing happen last night.

I uninstalled Palm Desktop and went into my registry and hacked away anything Palm-related. I reinstalled Desktop, and since I had forgotten my sync cable at work I used my minisync cable I just received from Boxwave. Lo and behold I could sync normally! Well yesterday I finally brought home my sync cable that came with my T|X, and as soon as I plugged it in my PC crashed. I took it out and plugged the minisync in, and it synced fine. This of course leads me to believe it is actually the cable itself that is causing the problem.

I'm not quite sure why this is happening though. The cable that crashes my home PC is working fine on my work PC.

[2XS]

i have the same problem on my PC at work ... workaround via Bluetooth-dongle :(

[lagomilo]

For me I found a solution. Did some checking on the net and found that switching to a different usb port might solve the problem. Now my palm is recognized correctly and I can hotsync.