Main question: is there anything I could have done software-wise to kill my CD/DVD-ROM. My laptop CD/DVD has stopped reading.
Current:
I put it a Windows ME boot disk. It finds the drive and boots with the drivers. Put it a CD. Type CD f: from command prompt. Fine. Type dir and get abort, retry, etc.
I put in Norton Ghost emergency boot disk. It can see the drive, but says no disk in it.
I put it Boot-it ng. It can see the drive but can't read it.
I can't boot with any bootable CD's. Bios is set to start with CD 1st.
Light comes on when I put disk in and it spins. It tries repeatedly to read.
History:
Was working fine today until I decided to use boot-it NG to blow away an extended partition that contained windows 2000 operating system. I created a primary partition in it's place and used Norton Ghost to move an image of the partition onto that newly created primary partition.
Needless to say, it won't boot. I get "couldn't find NTLDR" I'm sure the boot.ini is all messed up since I re-adjusted things.. I can go into norton ghost or boot from ME disk and see that all the files are there in the right place and on the right drive letters. I've been playing with the MBR, etc. and sliding things around. I finally gave up and decided to just re-install Windows on that partition until I realized that the CD won't read.
Could I have done something at such a low system level that I killed it? Seems almost impossible that the laser could have died at the precise moment that I was messing around with the system. It would just be too much of a coincidence.
I've been thinking I should keep trying to alter the boot.ini to see if I got Windows to boot, if the CD would come back to life. I can't think of a utility on a floppy I could use to access it, however.
This might be too much for this forum. Is there another newgroup you might suggest I post my question?
I've been searching for an answer. Closest I found was this:
________________________________________________________
"I have a similar problem with an HP omnibook xp1000s where I deleted XP home partition (C
using PartitionMagic in order to re-install from scratch. When I loaded the XP bootable installation cd, I got the message "couldn't find NTLDR". Before going through the PartitionMagic process, I could boot from CD without a hitch.
I then restored an earlier XP version using DriveImage from diskettes. I had no trouble booting into that restored installation from hard disk. Using PartitionMagic I noticed that the first three zones on the hard disk, from left to right, were as follows :
Empty Space of 7.8MB
Type 84 zone (hidden) occupying 47.1MB
Partition C of my restored XP
Should something be going into that empty space? Should I use FixMBR or will that destroy the whole boot setup?"
Current:
I put it a Windows ME boot disk. It finds the drive and boots with the drivers. Put it a CD. Type CD f: from command prompt. Fine. Type dir and get abort, retry, etc.
I put in Norton Ghost emergency boot disk. It can see the drive, but says no disk in it.
I put it Boot-it ng. It can see the drive but can't read it.
I can't boot with any bootable CD's. Bios is set to start with CD 1st.
Light comes on when I put disk in and it spins. It tries repeatedly to read.
History:
Was working fine today until I decided to use boot-it NG to blow away an extended partition that contained windows 2000 operating system. I created a primary partition in it's place and used Norton Ghost to move an image of the partition onto that newly created primary partition.
Needless to say, it won't boot. I get "couldn't find NTLDR" I'm sure the boot.ini is all messed up since I re-adjusted things.. I can go into norton ghost or boot from ME disk and see that all the files are there in the right place and on the right drive letters. I've been playing with the MBR, etc. and sliding things around. I finally gave up and decided to just re-install Windows on that partition until I realized that the CD won't read.
Could I have done something at such a low system level that I killed it? Seems almost impossible that the laser could have died at the precise moment that I was messing around with the system. It would just be too much of a coincidence.
I've been thinking I should keep trying to alter the boot.ini to see if I got Windows to boot, if the CD would come back to life. I can't think of a utility on a floppy I could use to access it, however.
This might be too much for this forum. Is there another newgroup you might suggest I post my question?
I've been searching for an answer. Closest I found was this:
________________________________________________________
"I have a similar problem with an HP omnibook xp1000s where I deleted XP home partition (C
I then restored an earlier XP version using DriveImage from diskettes. I had no trouble booting into that restored installation from hard disk. Using PartitionMagic I noticed that the first three zones on the hard disk, from left to right, were as follows :
Empty Space of 7.8MB
Type 84 zone (hidden) occupying 47.1MB
Partition C of my restored XP
Should something be going into that empty space? Should I use FixMBR or will that destroy the whole boot setup?"
