Boot Loaders

That XOSL loader with all success is not much stable and might start to oscillate between GRUB sector and XOSL sector. That is due to the fact that it is inside an extended partition at the beginning of the disk. That is less likely and less devastating if the extended partition was after primary partitions. A good observation is to go to Windows disk manager and delete the extended unstable partition and create a primary partition instead of that and formatted as NTFS. You become surprised that GRUB will disappear and in its place XOSL safely has kept its place at the beginning of hard disk and works perfectly loading any other bootable NTFS partition on the disk. You can open physical disk by a hex editor and see that affirmatively XOSL files still are there un-deleted, and un-touched. It is not at a place that through a simple reformating gets lost. XOSL is a nice small piece of software and can cosily reside at its snugging home that it has built at its installation and you cannot get rid of it that easily. What does it remind, then? This observation gets to the idea by some users that XOSL is a virus software. Well, it is not the case. But study of its source code is useful for people who are learners for developing anti-virus software against boot-sector-residenting malwares.I could sum it up for me that if I use only different flavours of Microsoft operating systems on the same machine it is wise to follow the procedures of Microsoft as they are well documented by Microsoft and if I use UNIX types only or mixed with Windows I can use GRUB. I know that Solaris of Sun Microsystem manages that automatically, if you follow their Big Admin procedure for multi-booting. Remains no place for good old XOSL.