dvd-rom I/O device error 1

[FBAOsvaldo]

OS win 2k upgraded from win me...dvd-rom and cd/rw both work fine.
Re-did my system and did a full win 2k install.
Cd/rw drive (philips) works fine ! Pioneer 106s dvd-rom drive ceases to work.
'D:| is not accessible. The request could not be performed because of an I/O device error '
Sometimes the drive shows disk info, sometimes not !!
Anyone got any ideas as to why it worked previously but not after full 2k install.

 

[gargouille]

Visit the Pioneer website and look around...you may need a firmware upgrade for Win2K. Make very sure it will fix it, tho, before you do it.

 

[FBAOsvaldo]

Thanks for the tip, I anticipated your response and have the firmware ready to go but was hoping it might be something obvious that I was missing ! If nowt else is suggested methinks the firmware's gonna get a run out.

 

[FBAOsvaldo]

Well, I've installed the latest firmware revision to no avail. I still get the I/O device error message ! The drive seems to be recognizing the data on any given disk, i.e. audio, video, data but refuses to perform in each of these instances. Anybody out there got any ideas ??

 

[gargouille]

DITO=Don't Ignore The Obvious

Look at the cabling...drive is sometimes there sometimes not?
Try another cable...

 

[FBAOsvaldo]

Cabling is fine, the drive is always recognised in sys. props and the bios. I need to find out if there is anything I can change concerning this I/O device error ! If not, I might have to accept that this drive is a dead duck and save for a dvd/rw. Anybody that has experienced this I/O device error, HELP !

 

[roamer1]

Hi FBAOsvaldo

Longshot, but are the MB drivers installed? Updated? BIOS updated?

 

[FBAOsvaldo]

Hiya, yes the motherboard drivers are loaded and up to date, as for the bios, there is a new revision but it does not seem to deal with my probs. As you suggest, it might be worth a go as a last resort. Ta for the feedback )

 

[FBAOsvaldo]

Another one bites the dust.........bios and mobo. drivers revised and up to date, still no change in dvd-rom. Win2k issue perhaps ? Anyone out there had any similar I/O device problems that they have managed to sort out ? In the words of Penelope Pitstop....Heyulp, Heyulp.....

 

[FBAOsvaldo]

Righty-ho, here's just a quick update. I've discovered that this has something to do with a file MSDEX.EXE which the OS needs to access the drive. The file should have been present when I installed 2k but was not. I also seem to have some kind of residue of my previous OS install, namely from win.ME to 2k. I have an autoexec.bat and config.sys file which I believe 2k shouldn't have but ME did. These seem to be the residue from my previous OS on my old damaged drive, which I have now removed.
I'm afraid I have not had too much time to look into this as xmas is frighteningly busy.
So, in a nutshell, thx fer the help thus far, any ideas on how to resolve my problem would be great.
If I stumble upon a solution I'll post it straight away.
Happy Xmas and a trouble free New Year

 

[gargouille]

Puzzling news in light of your opening statement of doing a fresh install...but remedy shouldn't be too severe. Just remove it in Safe Mode (looking for any duplicates) and reboot...the machine should find and reinstall it and you'll be good to go! (fingers crossed)
Happy Holidays!

 

[chethardcastle]

I seem to be having the exact same problem but with a Cendyne burner. At first it was intermittent and now it always has the i/o error. I have replaced cables and other fixes. Did you ever get to the bottom of the issue?

 

[j3r3my]

I too am having the same problem.
I have a RICOH CD-R/RW running under win2k

If anyone finds a solution can they host it here

Cheers!

 

[Arnstein]

Same problem here. I have two burners; one Yamaha (SCSI) and one Aopen (IDE). The Explorer reads the Yamaha OK, but not the Aopen (Explorer locks)
I have been a computerfreak since 1983 (I'm 47 yrs) and havn't asked for help the last 10 years, but this time I'm really stuck.
Does anyone else of you have Virtual Daemon Manager (v2.29)installed? I suspect that it can have something to do with the problem...
Tried to uninstall the program. Also tried a lot of other solutions. Can't remember the last time I rebooted 15 times the same night....