Hopefully a simple problem here, I feel like I'm just too tired to see it. Sorry if I ramble..
Basic setup here; 1 CDROM, 1 HDD carved up for OSes
part1 = 5G NTFS
part2 = 32M FAT (for XOSL, my multiboot loader)
part3 = 5G NTFS
extended part = many more logicals, etc
I have a bootable DVD I made last year with XOSL on it, and installed the loader to the 32Meg chunk as a dedicated partition (I don't have DOS anymore).
This is the same setup I use on the computer I'm using right now, and for the life of me I can't remember what I did at the stage I'm at with this new one.
The problem is that after installing XOSL, it says to reboot. Fair enough, but my BIOS boot seqence still has the CDROM as #1 so it just boots back to my custom menu from which I won't get into the loaders GUI.
If I pull the DVD out before the reboot, or even if during that reboot I stop off at BIOS to switch the sequence to HDD as #1, I get hung up at "Verifying DMI pool data......".
I can't remember what I did last year with what sounds like a pretty common and inevitable problem with the boot sequence. I'm assuming the obvious; that I need to yank the DVD, just like someone would do with a floppy before rebooting, but then why the halt during the HDD boot?
I mean, if XOSL is installed properly (which it seems to be since the MBR shows 'unknown IPL' like it should), and the MBR is pointing at the second partition (I assume, since the 32M partition is flagged as bootable/active), why is it acting as if there's no loadable data by simply hanging on this DMI message?
It's my understanding that the odd BIOS might not handle boot sequences at all, and will stop after the first device fails no matter whatelse it's told to check next. I'm a little suspicious of this BIOS, for what that's worth (I could elaborate).
I've got several tools for partition data editing, and I'm not completely new to this, so please fire off some suggestings, I'm too tired to think anymore.