mrfusion Posted October 2, 2004 Report Share Posted October 2, 2004 Nope, it gives me the same BOD in safe modeI can use the recovery console (I realized I was not actually *selecting* the os I wanted to boot to and that by just hittingenter it went into rebooting.) So it seems strange that the main os causes the BOD but the recovery doesn't Quote Link to comment Share on other sites More sharing options...
spikeychris Posted October 2, 2004 Report Share Posted October 2, 2004 The recovery console does not boot the OS. It only allows access to %systemroot% and %windir% so it cant BSOD. Quote Link to comment Share on other sites More sharing options...
nellie2 Posted October 2, 2004 Author Report Share Posted October 2, 2004 Can I just clarify something, when you are booting with the floppies, you press enter at the "Setup Notification" screen then hit R to repair a Windows2000 installation, and then press C to use the Recovery Console. Are you pressing C? Quote Link to comment Share on other sites More sharing options...
mrfusion Posted October 2, 2004 Report Share Posted October 2, 2004 No, when I boot up the machine (from the C: drive)it gives me the option to boot windows 2000 or the recovery console and I choose the recovery consoleWhen I did the repair earlier I did not open the console, I wentstraight into the repair windows.(Sorry if this is getting foggy - I've tried so many thingsover the last week it's hard to remember what happened at each step) Quote Link to comment Share on other sites More sharing options...
spikeychris Posted October 2, 2004 Report Share Posted October 2, 2004 You're right this is a bit foggy. Have you run the repair option? Have you booted to the recovery console and tried chkdsk? Would formatting the machine be out of the question? Quote Link to comment Share on other sites More sharing options...
mrfusion Posted October 2, 2004 Report Share Posted October 2, 2004 I did run the repair , that's when I got the inaccessible_boot_deviceBSOD.I'm running chkdsk /p right now (it didn't seem to understand /f)When I just ran chkdsk by itself, It reported: the volume appeared to be in good condition but was not checkedUse /p if you want to check the volume anyway.So I ran it again with the /pIt just finished and did not report any errors. Quote Link to comment Share on other sites More sharing options...
mrfusion Posted October 2, 2004 Report Share Posted October 2, 2004 I REALLY rather not re-format the disk if I can avoid it.Have I mentioned how much I hate Pinnacle System? Quote Link to comment Share on other sites More sharing options...
mrfusion Posted October 2, 2004 Report Share Posted October 2, 2004 I've got to take my kids to a class so I have to dissappear for about 1 hour. I'll check in as soon as I get back.Thanks again everyone for the support! Quote Link to comment Share on other sites More sharing options...
nellie2 Posted October 2, 2004 Author Report Share Posted October 2, 2004 Now you can get into the recovery console how about trying fixboot Quote Link to comment Share on other sites More sharing options...
nellie2 Posted October 2, 2004 Author Report Share Posted October 2, 2004 Oh no... I see you have already done that here, ok back to head scratching Quote Link to comment Share on other sites More sharing options...
spikeychris Posted October 2, 2004 Report Share Posted October 2, 2004 OK, lets assume that your boot.ini file is damaged. boot into Recovery Console and type "MAP ARC"MAP ARC will tell you what the arc path *should* be. Exit.TYPE BOOT.INI, this will show you boot.ini file; compare against the results of the map arc command.If the boot.ini is different then use another 2K machine and knock up a bootable Windows 2000 disk(edit the boot.ini on the floppy to reflect the correct arc path), and boot with that. Quote Link to comment Share on other sites More sharing options...
mrfusion Posted October 2, 2004 Report Share Posted October 2, 2004 Ok, I'm gonna type all this in because I don't want to skip over somethingthat might mean more to you.In the recovery console I type:c:\winnt>map arc? 0MB multi(0)disk(0)rdisk(0)partition(0)? 31MB multi(0)disk(0)rdisk(0)partition(1)C: NTFS 34695MB multi(0)disk(0)rdisk(0)partition(2)? 0MB multi(0)disk(0)rdisk(1)partition(0)D: NTFS 17359MB multi(0)disk(0)rdisk(1)partition(1)A: \device\floppy0E: \device\CdRom0F: \device\CdRom1c:\winnt>cd ..c:\type boot.ini[boot loaded]timeout=30default=multi(0)disk(0)rdisk(0)partition(2)\WINNT[operating systems]multi(0)disk(0)rdisk(0)partition(2)\WINNT = "Microsoft Windows 2000 Professional"/fastdetectc:\CMDCONS\BOOTSECT.DAT="Microsoft Windows 2000 Recovery Console" /cmdcons Quote Link to comment Share on other sites More sharing options...
nellie2 Posted October 3, 2004 Author Report Share Posted October 3, 2004 we haven't forgotton or forsaken you mrfusion.... I've sent a message to spikeychris to come and have another look when he has a moment! ;) Quote Link to comment Share on other sites More sharing options...
mrfusion Posted October 3, 2004 Report Share Posted October 3, 2004 :flowers: Thanks! You may be nellie2, but you're number one with me! Quote Link to comment Share on other sites More sharing options...
mrfusion Posted October 3, 2004 Report Share Posted October 3, 2004 I found this article about the current problem but I haven't quite figured out what to do about it.... There are 9 different methodsto correct this so I'm going to start with one of the easy ones.http://support.microsoft.com/default.aspx?...duct=Win2000Dev Quote Link to comment Share on other sites More sharing options...
spikeychris Posted October 3, 2004 Report Share Posted October 3, 2004 Your boot.ini file is OK. What stage are you at? Quote Link to comment Share on other sites More sharing options...
mrfusion Posted October 3, 2004 Report Share Posted October 3, 2004 I'm running some disk diagnostics on the scsi drive.I figured it can't hurt to check everything.I reran the rescue just to double check and I still get the same BSOD.I went through the list on the microsoft site that mentions thisboot problem (see link two messages previous to this one). Here's my response to the methods they posted to fix thisMethods:1) I'm as sure as I can be that my machine is not infected with a virus. I've got the latest updates from Norton always on my machine, and I ran several different virus checking programs when I was still able to get into the machine.2) Not sure what to do with this one.3) I have not added anything new to the system.4) I haven't changed any of the SCSI settings. The disks should be the same as when I got the machine.5) I've run chkdsk on the drive and it reported that everything was fine. I haven't tried installing w2k in a different location on the drive yet.6) I've not seen anything in the repair screens that mention checking the regestry. But I've run the complete repair several times.7) I do not have a duel floppy drive.8 & 9) There doesn't seem to be a device driver problem since I can get to it through the recovery console. Quote Link to comment Share on other sites More sharing options...
spikeychris Posted October 4, 2004 Report Share Posted October 4, 2004 Well as you have said you could run a parallel installation of 2K. You could then try and drag the files you need across to the new version then delete the old version. You could also try this....click here and download the prog, then click here and download also.Before you download this tool, you will need to download the Windows XP Professional. Its the six disks again. These disks work, I have used them before and know of others who have done the same. You do need the XP disks as well as the 2K ones. Quote Link to comment Share on other sites More sharing options...
spikeychris Posted October 4, 2004 Report Share Posted October 4, 2004 BTW. 2K will always boot to recovery console, whether or not it has a driver problem. Quote Link to comment Share on other sites More sharing options...
mrfusion Posted October 4, 2004 Report Share Posted October 4, 2004 Ok, I'll grab this stuff and give it a try. I'm pretty sure we've donethis earlier, but that was when the problem was different. I'lltry this again tonight and let you know what happens. Quote Link to comment Share on other sites More sharing options...
mrfusion Posted October 5, 2004 Report Share Posted October 5, 2004 <sigh> No luck. Same BSOD about inaccessible boot device. Quote Link to comment Share on other sites More sharing options...
mrfusion Posted October 5, 2004 Report Share Posted October 5, 2004 Going to try a fresh install in a different directory.:( Quote Link to comment Share on other sites More sharing options...
mrfusion Posted October 5, 2004 Report Share Posted October 5, 2004 Ok, the good news is after doing the second install of win2K I can boot to and load up the "virgin" copy. I still get the boot error if I try to load the old version.Now that I can get into the machine, will it be possible to restore the old version and get rid of the new one? :huh: Quote Link to comment Share on other sites More sharing options...
Scarecrow Man Posted October 5, 2004 Report Share Posted October 5, 2004 do sfc /scannow on the other partition? Quote Link to comment Share on other sites More sharing options...
mrfusion Posted October 5, 2004 Report Share Posted October 5, 2004 They're both on the same drive on the same partition.I just installed windows into a different directory. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.