M
Michael
Hello, I'll start by saying that other than some XP updates (I have XP sp2),
I haven't made any changes to my PC for over 8 months and up until now all
has worked fine. The problem is that XP no longer will read any of my
thumbdrives (I have several and they all work OK in other computers). The
drives show up in My Computer and Windows Explorer as removable disks, but
when I try to open them I get the message "G:\ Not accessible. Incorrect
Function". At the same time this happened both my DVD rom and CDROM started
having problems. If I boot/restart the computer with a disc in either drive
that drive will function normally until I eject the disc. Once the disc is
removed the drive no longer will read any discs. The CDROM shows in Windows
Explorer but nothing happens when I click on it. The DVD rom appears in
Explorer but when I click on that I get the same "not accessible, incorrect
function" message as I get with the thumbdrive. All 3 devices show up in
device manager as functioning normally. I have been unable to find any
references to this problem on the MS support site. Any ideas?
mike
I haven't made any changes to my PC for over 8 months and up until now all
has worked fine. The problem is that XP no longer will read any of my
thumbdrives (I have several and they all work OK in other computers). The
drives show up in My Computer and Windows Explorer as removable disks, but
when I try to open them I get the message "G:\ Not accessible. Incorrect
Function". At the same time this happened both my DVD rom and CDROM started
having problems. If I boot/restart the computer with a disc in either drive
that drive will function normally until I eject the disc. Once the disc is
removed the drive no longer will read any discs. The CDROM shows in Windows
Explorer but nothing happens when I click on it. The DVD rom appears in
Explorer but when I click on that I get the same "not accessible, incorrect
function" message as I get with the thumbdrive. All 3 devices show up in
device manager as functioning normally. I have been unable to find any
references to this problem on the MS support site. Any ideas?
mike