System: I have Win98, Win2k and WinXP booting from my first drive, a PATA; My second drive is also a PATA being used only for backup and storage; I have Win7 and Linux Debian 5 installed on my third drive, a SATA. All was well here until Debian 5, my last installation, somehow must have added SATA drivers somewhere on my main drive and my BIOS/DOS/Win98 could then suddenly see the FAT32 partition at the end of my third drive. At that point, Win98 could not boot because its partition had just been bumped from “E” to “F”. Note: I had used Debian’s installer to add LiLo to Debian’s “/boot” on my third drive, and then I had used EasyBCD to add Debian to Win7’s BCD ... and all of the above (except for Win98) was working well until this: To resolve Win98’s boot problem after its drive letter had been bumped, I re-installed Win98 back onto its own partition as “F” (where it used to be “E”) ... ... and now the “boot.ini” loader on “C” (for Win98/2k/XP) offers the only boot menu I ever get to see: Win7’s “repair startup” on its original DVD does not find that “boot.ini” on “C”, and neither can Win7’s “repair startup” make Win7 show up at startup even by itself ... and neither does EasyBCD 2.0 make Win7’s BCD show up at startup. ----> Notice: In my pictures, “C” and “R” have been switched between Win7 and Debian, and that makes me suspect Win7 and Debian now think (after Debian’s installation) they are on the first drive rather than the third. That makes no difference for running since they are each still right where they were when installed, but I suspect Win7 and Easy BCD are now not looking at “C” because they think they are already on it. What should I do?! I thank you.