Yes, and the $40.00 I spent in order to do that with complete confidence is not even a drop in the bucket of time it would take me to go back to the beginning and put this system back together for the third time ...!!
Lemme go print this thread so I have everything right in front of me when I begin clicking ...
Here is the drive order XP sees, and I suspect EasyBCD just wrote to the SATA, which is actually third in line when this machine is first started up.
The screen shots you show are telling you that the first parameter to bootsect.exe is not optional. The first parameter tells bootsect.exe whether to install boot code for NTLR (/nt52) or for BOOTMGR (/nt60).
Code:bootsect.exe /nt60 ALL /force /mbr bootsect.exe /nt60 ALL /force
Back in a few ...
Well! Here is my Win7 once again! I have not shut down and done a cold boot just yet, but this first go-round showed the last EasyBCD boot menu I made while in XP ...
I will go try for Debian now, then do an EasyBCD in Win7 to get XP's "boot.ini" back into the mix ... then come back a little later with a final report I suspect we will all appreciate!
I truly thank each and all of you.
Okay, here is my Win98 and with Debian's SATA drivers still intact, but EasyBCD did not find 2k/XP's "boot.ini" (with its own option for Win98 inside it). Rather, it (EasyBCD) only found and added Win98's *usual* boot even though I had recently "repaired" my XP installation so its (XP's) "boot.ini" would be called instead. Doing another "repair" of my XP *installation* would likely accomplish that once again, but then Win7's BCD would be knocked back out of the picture.Suggestions?!
I think having "/mbr" in those last EasyBCD commands over-wrote whatever had been pointing to XP's "boot.ini".
Win7's "startup repair" would have picked it up and included it ... so maybe we tried to do too much with EasyBCD in this particular situation?
Last edited by leejosepho; July 14th, 2010 at 11:48 PM. Reason: Automagically-merged double-post.
First Win98 was installed on "D" (placing its boot on "C"), then 2k went in on "C" (and hijacked 98's boot), then XP went in on "E" and hijacked 2k's "boot.ini" on "C". So, we are now not trying to find XP on "E" unless we are going to also go find 2k on "C" at risk of losing 98. In place of all of that, we need to simply bring "boot.ini" on "C" into Win7's BCD so the 98-2k-XP "boot.ini" menu can appear from there.
multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Windows XP Pro" /noexecute=optin /fastdetect
multi(0)disk(0)rdisk(0)partition(1)\WINNT="Windows 2K Pro" /FASTDETECT
C:\ = "Windows 98 se"
The screenshot below shows the assigned drive letters as EasyBCD will see them while running here in Win7. 0/0 is "0_SYS2K (R)" where XP's "boot.ini" is located, and XP is in "E".
I wonder whether all of this could be as simple as replacing 98's "msdos.sys" with the version in use prior to its (98's) re-installation knocking 2k and XP out of the lineup, but I do not know how, where or when XP's "boot.ini" actually gets called.
Okay, here is where I am at the moment:
I ran "FIXBOOT C:" from XP's Repair Console, and that put XP's "boot.ini" (offering 98-2k-XP) back in as this system's boot menu. And as a result, of course, Win7's BCD no longer showed anywhere.
At that point, I used EasyBCD in XP to delete all entries from that dysfunctional Win7 BCD, then I ran Win7's "startup repair" from its DVD to make a new BCD ... and that new BCD did *not* take notice of XP's "boot.ini", and neither did it get placed as this system's new startup menu. Rather, XP's "boot.ini" yet remains the boot menu shown at startup even after Win7 made a new BCD ... and re-running Win7's "startup repair" now shows no errors to be repaired.
After I ran "FIXBOOT C:" in XP's console, I also typed "FIXMBR" but was given a warning about having a non-standard MBR and that the execution of "FIXMBR" could ruin my partition tables and keep this computer from booting. So, I did not proceed with that command.
I could re-install Win7 (or repair its installation), but I wonder whether that would resolve the problem of its installer not being able to place its BCD on "C".
I could easily live without Win7 altogether and use that partition for something else, but then how could I add Debian to XP's "boot.ini" or whatever? I know my Debian installation is still good, but now I no longer have Win7's BCD available for using EasyBCD to get to it.
Ah, maybe I need to go see how people dual-boot Debian and XP ...
Run EasyBCD in Windows XP.
Add New Entry -> Linux
Go back to the main EasyBCD page. You'll see the entry there, together with the path for the entry in the form of "X:\NST\nst_grub.mbr" or something like that.
Open boot.ini and add a new entry to there:
X:\NST\nst_grub.mbr = "Debian"
I began with a "mess" and seem to have ended up with some kind of anomoly, but it works and I thank you for your time and effort in helping me get there!
Note: Please excuse my bad lens on an old camera ...
Last edited by leejosepho; July 15th, 2010 at 11:15 PM.
The matter of my BIOS and drive order is still a question rolling around in my mind. Sometimes this machine comes up quickly, but sometimes my BIOS takes several seconds doing whatever it does before letting the machine proceed. My "reset configuration data" switch does not automatically disable itself the next time around after being enabled, and I actually find it best (usually quicker boots) to just leave it enabled ... and I installed a new battery last week because my BIOS sometimes seemed a bit shaky. In any case, that "reset" switch had been disabled for a while until yesterday when I enabled it again while re-installing Debian, and that is when Debian's installer suddenly again began seeing my third drive first (like it occasionally had in the past) and was able to find/see *all* systems for GRUB to then begin handling.
Later on today (after having booted into each of the systems here at least once) I will likely disable that "reset" switch again, but either way never renders any OS unbootable.