Foosinho
17 Aug 2004, 01:28 PM
OK, so maybe somebody here can provide some insight...
I replaced a CDRW with a DVDRW in a Dell 2.5GHz here at work. Thing boots up, XP recognizes it, installs the drivers, and all is hunky-dory. Except I cannot read any discs. Commercial, audio, CDRW, DVDRW... nothing. I've cleaned out everything (all the old burning software, since I read that could cause a problem), reinstalled multiple times, and never once has Windows ever said there is any kind of conflict.
Now, here is where it gets interesting. The device manager shows the main hard drive as being connected to the primary IDE controller, and the DVD drive as being connected to the secondary IDE controller. However, if you bring up the drive properties from the My Computer screen and select the "Hardware" tab, the OS says the DVD drive is at "Location: Location 0 (0)", which is identical to the hard drive's location... and "0 (0)" is the location for the IDE Primary Master (at least, that's the only coding that makes any sense to me).
Any ideas on how to fix this damn problem? I don't want to end up destroying any of these 17" LCD monitors in a fit of rage...
I replaced a CDRW with a DVDRW in a Dell 2.5GHz here at work. Thing boots up, XP recognizes it, installs the drivers, and all is hunky-dory. Except I cannot read any discs. Commercial, audio, CDRW, DVDRW... nothing. I've cleaned out everything (all the old burning software, since I read that could cause a problem), reinstalled multiple times, and never once has Windows ever said there is any kind of conflict.
Now, here is where it gets interesting. The device manager shows the main hard drive as being connected to the primary IDE controller, and the DVD drive as being connected to the secondary IDE controller. However, if you bring up the drive properties from the My Computer screen and select the "Hardware" tab, the OS says the DVD drive is at "Location: Location 0 (0)", which is identical to the hard drive's location... and "0 (0)" is the location for the IDE Primary Master (at least, that's the only coding that makes any sense to me).
Any ideas on how to fix this damn problem? I don't want to end up destroying any of these 17" LCD monitors in a fit of rage...