Easy CD creator fighting W2k with NTFS. HELP!

[DrJeff]

:QSomething just went horribly wrong. I don't know if it was a virus, but here goes.

Stable W2k machine 9 months old, xp 1800+, 512mb DDR, Soyo Dragon Plus, Maxtor d740 40Gb 7200, One HD installed, no RAID, using NTFS. I was installing Roxio CD Creator 5 basic, then installed CD Creator 5 Platinum over it once I found the disk. My CDRW is too new for the ECDC 5 Platinum, so I DLed the update from Roxio. Would not install, saying something like NO compatible product found. I shutdown cold and restarted; still the update installer would not recognize the 5 plat. installation. So I uninstalled the 5 basic, then uninstalled the 5 platinum, and restarted warm to clear decks and start over with the 5 plat. install.

When restarting, I get POST, W2k startup screen with progress bar, then BLUE SCREEN:

"STOP: 0x0000007B ... blah, blah
INACCESSIBLE_BOOT_DEVICE

If this is the first time you've seen this Stop error screen,
restart your computer. If this screen appears again, follow
these steps:

Check for viruses on your computer. Remove any newly installed HD or HD Controllers.
Check your hard drive to make sure it is properly configured and terminated.
Run CHKDSK /F to check for HD corruption, and then restart your computer."

I had a McAfee Emergency Boot disk which I used. It scanned the C drive using the definitions on the diskette and found no viruses. HOWEVER, MORE TROUBLING, it reported two MBRs on the C drive and NO OTHER FILES!

Am I dead? Who has seen this before? What should I do to investigate? I have McAfee Internet Security 4.0, Norton Systemworks 2002 Professional, and Norton Internet Security 2002 sitting here on CD. And I have the original W2k install CD as well as my WinXP Pro on CD.

I am afraid to do anything else to it until I hear from you guys. Help, please.

 

[DrJeff]

Bump.

Won't anyone help me out of this spot?

 

[rbV5]

Can you boot with the Win2k disk and use the recovery console? Check This. Uninstalling EZCD creator may have simply hosed your HD controller drivers, and does that McAfee Emergency Boot disk support NTFS? If not, it simply can't read the drive, so all may not be lost.
Good luck.

 

[DrJeff]

Thank you, Thank you, Thank you, rbV5 !

That's just the help I needed, and I am loving that Labmice site. Lots of good info. I owe you one.

 

[FrankWhite21044]

i still think you could recover from this error if you need to without wiping the whole system. the fact that the W2k startup screen with progress bar appears means that some files are still intact right?

 

[DrJeff]

Yes, the OS starts because I get the W2k splash screen and the beginning of the progress bar before it goes to the blue stop and gives the INACCESSIBLE_BOOT_DEVICE error.

Using the new knowledge of the W2k Recovery Console, I should be able to iron it out when I get back to the machine after work.

 

[DrJeff]

Okay, I rebooted to the W2k pro CD and found the partition that I wanted repaired, ran the Emergency Repair Disk repair plan, let it restore any changed system files. But it still gives me the blue screen saying

STOP: 0x0000007B ... blah, blah
INACCESSIBLE_BOOT_DEVICE

If I go back into Recovery Console to the C:/WINNT command prompt, can I use a command line function to replace my registry file to its backup? Wouldn't that give the OS the settings it needs about the drive controller, etc, so it can boot? I am stuck with the install still not recognizing the NTFS IDE drive.

Waiting...

 

[Tal]

I've had this problem before as well... I'm assuming you did Last Known Good Configuration from the boot menu for windows 2000????

If so, if you know which files to replace, and from what you are saying, it seems like ASPI drivers, then you can use NTFS4DOS Professional to add the files back manually. Email me if you need more info about this product................. (adam@propeck.com)

Also, if you just wanna get your files off and reinstall, NTFS4DOS the free version allows reading the NTFS partition just fine. I would use Partition Magic to split your drive making a Fat16 or Fat32 partition to copy data to.

Here is a link to the NTFS4DOS site. Linky

The download link is at the bottom of the page.

-TAL

 

[rbV5]

I think you want to look at the console commands to fix the MBR.

 

[DrJeff]

Originally posted by: rbV5
I think you want to look at the console commands to fix the MBR.

Do you mean just run FIXMBR? I don't know what MBR does, basically.

 

[rbV5]

I don't know what MBR does, basically

MBR = Master Boot Record, At the end of the ROM BIOS bootstrap routine, the BIOS reads and executes the first physical sector of the first floppy or hard disk on the system. This first sector of the hard disk is called the master boot record (or sometimes the partition table or master boot block). There is a small program at the beginning of this sector of the hard disk. The partition information, or partition table, is stored at the end of this sector. This program uses the partition information to determine which partition is bootable.

Here is a Link scroll down the the link concerning the specific stop message, it covers the approach you should take specifically.

 

[DrJeff]

Kewl.
Soooo...
when I start Recovery Console, pick a partition, put in my PW, and it gives me a lonely C:/WINNT prompt, I have told RC which partition I want to address. Then I tell it to FIXMBR and it corrects the pointers in the MBR to look in the right spot for the partition table. Right? In that case, nothing on the rest of the HD has changed, and my files, Dir tree, and apps should all work dandy fine, I am hoping...

Thanks for educating me, and for the linky.

 

[DrJeff]

Well, Fixboot and FixMBR worked fine, but did not fix the problem. Comes up with the same INACCESSIBLE... message. Does anyone know how I can put a new copy of the HD drivers on the HD? I have access to C:/WINNT via the Recovery Console. Is there a GUI drag&Drop type file mover that will run from W2k's DOS prompt? I have gotten spoiled enough to hate command line syntax on any large scale.

I have this suspicion that I am not going to get this NTFS W2k Pro build to reboot from this HD. I have an identical HD available that I could do a fresh install of W2k Pro or XP Pro onto, make the current boot HD a secondary containing all of my files, and move them to the correct dirs when apps are installed onto the new HD. I REALLY loathe doing this. Can a new install of W2k be done on top of the old HD and have the files remain unscathed? I know the apps would have to be reloaded. Any advice appreciated.

 

[rbV5]

OK, I found this:

1) Open the Recovery Console and type LISTSVC. A list of drivers loaded on startup will be displayed.

2) Locate the IDE drivers and type DISABLE name.ext (where name.ext is the driver name and extension).

3) Once the IDE drivers are disabled, exit and reboot. On reboot, Win2k will load the standard default IDE driver and should startup

Those ide drivers are the culprits it seems, that should allow you to get up and going. Here's the Link , IBD Solution 4: Delete Drivers using Recovery Console:

Good luck

 

[DrJeff]

Good God! There's a site for everything, isn't there?
windowsreinstall.com
Now I HAVE seen everything.

Great site for all tweakers and builders. Highly recommended. (No affiliation on my part.)

Thanks, rbV5