Why can’t I get new system to recognize optical drives?
Moderators: NeilBlanchard, Ralf Hutter, sthayashi, Lawrence Lee
-
- Patron of SPCR
- Posts: 15
- Joined: Thu Nov 15, 2007 11:25 pm
- Location: San Diego, California
Why can’t I get new system to recognize optical drives?
Does anyone know what I’m doing wrong to cause my new system to not recognize IDE CD or DVD drives? Excluding case & cooling, the system consists of:
Processor: Intel Core 2 Duo E6850 3.0GHz
Motherboard: ASUS P5E
Memory: Corsair PC2-6400 2x1024 MB
Graphics card: EVGA GeForce 8800 GT 512MB
Hard drive: WD 3200AAKS (SATA)
I created a bootable CD with the WD “Data Lifeguard Toolsâ€
Processor: Intel Core 2 Duo E6850 3.0GHz
Motherboard: ASUS P5E
Memory: Corsair PC2-6400 2x1024 MB
Graphics card: EVGA GeForce 8800 GT 512MB
Hard drive: WD 3200AAKS (SATA)
I created a bootable CD with the WD “Data Lifeguard Toolsâ€
-
- Posts: 1839
- Joined: Mon Feb 05, 2007 2:10 pm
- Location: Northern New Jersey
- Contact:
-
- Moderator
- Posts: 7681
- Joined: Mon Dec 09, 2002 7:11 pm
- Location: Maynard, MA, Eaarth
- Contact:
I seem to remember seeing this before...
put the CD in a working computer, and look for an 'autoexec.bat' and/or 'config.sys' file and paste their contents in this thread.
I suspect part or all of the problem is the OS thats installed on the bootable CD doesnt recognize your sata drive (or mabye all sata drives in general). Which (I think) is causing the boot sequence not to find drive letters in the order it expects, and then failing.
put the CD in a working computer, and look for an 'autoexec.bat' and/or 'config.sys' file and paste their contents in this thread.
I suspect part or all of the problem is the OS thats installed on the bootable CD doesnt recognize your sata drive (or mabye all sata drives in general). Which (I think) is causing the boot sequence not to find drive letters in the order it expects, and then failing.
-
- Patron of SPCR
- Posts: 15
- Joined: Thu Nov 15, 2007 11:25 pm
- Location: San Diego, California
ok I actually follow whats supposed to be happening in those files..
However - im at a loss as to where the whole mess starts - which i think is the root of the problem. Somewhere in one of your folders is going to be an autoexec.bat and/or config.sys file these are whats supposed to start the whole process. Unless you can find documentation elsewhere saying what starts the process along.
If i remember correctly this setup procedure assumes drives will be named a certian way, and when they are not - the startup process breaks.
namely:
A: - floppy
C: - HD
D: - ramdrive
E: CD drive
so if your HD isnt recognized by the very old dos (not suprising), then the ramdrive will show as drive C: and the CD as D: - which is not whats expected, and either the internal checks fail and the program spits out errors, or their are no internal checks and the program does odd things.
However - im at a loss as to where the whole mess starts - which i think is the root of the problem. Somewhere in one of your folders is going to be an autoexec.bat and/or config.sys file these are whats supposed to start the whole process. Unless you can find documentation elsewhere saying what starts the process along.
If i remember correctly this setup procedure assumes drives will be named a certian way, and when they are not - the startup process breaks.
namely:
A: - floppy
C: - HD
D: - ramdrive
E: CD drive
so if your HD isnt recognized by the very old dos (not suprising), then the ramdrive will show as drive C: and the CD as D: - which is not whats expected, and either the internal checks fail and the program spits out errors, or their are no internal checks and the program does odd things.
-
- Patron of SPCR
- Posts: 15
- Joined: Thu Nov 15, 2007 11:25 pm
- Location: San Diego, California
Some brief excitement but no resolution
Well, I couldn't see where the whole mess started either. I don't know what other kind of files the BIOS will execute, but it must be something besides autoexec.bat or config.sys. Do you know if there are other files that will run just from the BIOS - like maybe START.EXE or one of the other .sys files?im at a loss as to where the whole mess starts - which i think is the root of the problem. Somewhere in one of your folders is going to be an autoexec.bat and/or config.sys file these are whats supposed to start the whole process
I did get some excitement out of the last thing I tried.
Since the system seems to want a floppy drive and I had set it to "Disabled" in Setup, I decided to give it one (even though there would be no floppy disk in it). I took the floppy drive out of my wife's computer and installed it in the new one. It had not been used for a long time and was quite dusty, so I used some "Dust Off" (compressed air in a can) to blow the dust out of it. I was through messing around in the case, so I reinstalled the side panels and then turned on the power. That action was follwed by a high pitched sound and dense white smoke billowing out of the vents. I yanked the plug as soon as I could get to it. I removed the side panels and made a quick but unsuccessfull search for something hot or burned. Unfortunately, I had turned the computer on just a few minutes before my wife and I were supposed to leave for a luncheon, so by this time she was waiting for me to get in the truck and leave. Gave me something to think about while we were at lunch. When we got back I had time for a better search and founfd the cause.
Fortunately, it turned out to be the FDD that caused the problem. The power cables were fried from the plug out to about six inches. There doesn't appear to be any other damage, but I haven't gone back to investigate the original problem again yet. I'll let you know if I find out anything. I'm sure you're not dying to know, but I figure if you're interested enough to give me this much of your time, you might be interested to know if I find an answer.
Thanks for your time.