Aha, thanks Marrea,
So, a windows boot loader that allows for <cough> another non windows OS </cough> to be available to boot. Crikey !. Are you sure it's not some insidious plot. It sounds to good to be true, but then ... i have become somewhat suspicious over time (grin). I'll have to remember that though
If you want to use the Windows boot loader, when you install Linux you put Grub on the first sector of the boot partition rather than the MBR and then post-installation you copy the Linux boot sector across to the root C drive on Windows, and put an entry in the boot.ini file, which will give you Linux as an option on the menu at boot up
So, do you mean by the "Linux boot sector" the 1st stage loader that you installed on the 1st sector of the Linux boot partition ?. hmmmmm, makes a kinda sense....
So -> mbr -> generic bootstrap with the partition that Windows is installed on set active, -> at boot, it reads the table, goes to the windows partition and loads the first stage windows boot-loader into low ram -> 2nd stage etc win loaders will be in the root C:\ drive, as they always are -> at some stage, probably with the 1st stage loader, it brings up a menu -> if a Linux is chosen, it goes to its' C:\ root looking for the file thats mapped to the menu item -> which just happens to be a copy of the Linux 1st stage that was installed to the linux boot sector, hmmmmm. Interesting. Windows insisting on only looking to its' own C:\ root makes sense.
If your using Grub as a Linux loader in that senareo, as Grub will always read its' config when its' booting so there is no need to update any config changes ... if thats the process above is correct, then it sounds like it should work quite well. I wonder how Lilo would work there ?. I haven't been able to decide if, after /sbin/lilo is re-run after a change to /etc/lilo.conf, whether only the map file in /boot is the file that is updated to reflect changes, or whether there are changes made to the lilo 1st stage it self as well. I really need to check on that. If it's just the map file that is updated it may work with Lilo too, with out having to copy over a new copy to Windows after each config change in lilo.conf.
NTLDR = NT Boot Loader = Windows half assed attempt at something like LILO
Must admit, i'm a little suspicious of the motive at least (grin)
... there must be a catch some where ... oh the joys, and the pains of the cynical