-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Would it be possible for someone to summarize Lilo's size limitations a bit? I'll try and explain my situation the best I can. In some situations, my boot images won't work and other deals they do. The background here is I have an 80 gig hard drive on primary IDE master and a 20 gig on a primary slave connector. I intend to have this a dual boot machinw with win2k and Linux. The first 30 gig partition I set asside for win2k, the second 30 gigs a shared FAT32 partition, and the remaining space on that drive to be for linux and a swap partition. Now, when I run lilo in a normal fashion from the /hda3 partition with the boot record to go on the /dev/hda MBR, lilo fails to boot. But if I run lilo -r to my old 20 gig drive on /hdb3 to also point to the /dev/hda MBR and have root be /dev/hda3 (my new drive), all seems to work fine. Fwew, after all that, my question is what actual size limits play in here? I use the LBA option in all my lilo conf parameters. It would appear that lilo's map generation and source drive has a lot to do with this. The lilo docs don't seem to dig down this far. Can anyone help me out? - -- HolmesGrown Solutions The best solutions for the best price! http://ld.net/?holmesgrown -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFBSCiJWSjv55S0LfERAlCXAKCfogagOkJKv4oeYxryYEQSCLu2EwCgmEY4 NEPUAUQa/tbMimJOo21VL7w= =7szn -----END PGP SIGNATURE----- --------------------------------------------------- PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us To subscribe, unsubscribe, or to change you mail settings: http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss