Jump Drive Not Recognized After XP Pro Upgrade

[Guest]

Yesterday, I asked a question on how to upgrade XP Home to XP Pro, because
the XP Pro disc I had didn't have SP2 (when my XP home version did). With
help, I slipstreamed SP2 into XP Pro, and upgraded successfully.

I just noticed a major problem today. I bought a jump drive yesterday
(needed for school), and on XP home, the drive worked fine - it was assigned
drive letter F:, and showed up in Windows Explorer and My Computer. Since
the upgrade, Windows Explorer/My Computer does NOT show the jump drive.

I reassigned the jump drive manually to drive f:, and I was able to click
into it due to a desktop shortcut to that drive that I put on yesterday;
however, it still didn't show up in Windows Explorer, and when I rebooted,
the jump drive was once again unaccessible.

Does anybody know why this is occurring? I'm going to try reassigning the
drive to a higher letter, rebooting to see if that fixes the problem. Let me
know though if you have any info on this matter.

Thanks,
John

 

[Guest]

No luck with the reassigning. I don't know if it matters, but I noticed that
the jump drive is in FAT format. I tried formatting the drive to FAT32
format, but it tells me that the device is not enabled. It then says, "to
enable the device, restart your computer." When I do this though, I don't
get anywhere. Can somebody please help?

 

[Guest]

Unfortunately, after a week on the microsoft newsgroups, this post failed to
generate one response. Luckily, I found another website outside of microsoft
where others offered assistance, and somebody found the solution for me.


Thanks for everyone that offered help, and especially to JThom for finding
the solution!




[quote name='Jthom203' date='Apr 13 2006, 09:01 PM' post='107961']
i had a similar problem after i upgraded from home to pro and i searched the
net and found this on another forum.

Explorer was not recognizing any USB mass storage device including
ipod and sandisk although they appeared in device manager. After tearing out
what little remaining hair I have left, tracked the problem to the existance
of three driver files in windows\system32\drivers :
secdrv.sys
sptd.sys
sptd409.sys
All dated around when the probelm surfaced.
One is related to anti-piracy software that probably came with a computer
game, the others were installed as part of a failed attempt to install daemon
tools 4.0. In any event, I deleted those 3 files and rebooted. The system
then "saw" the devices and asked me to reboot again afterwhich everything
behaved properly. All is well although I am tired and bald.

Here is the link the quote above is comment 13

this solved my problem and i hope it helps
[/quote]