Unhide partition with lilo
 

Ok, I've determined that when I set up my dual-boot frickin' Partition Magic hid hda1, the partition where XP Pro is installed. I can boot into Mandrake 10 fine, but whenever I try to boot XP, I get the dreaded "xmnt2002" error. What I need to do, I believe, is unhide the first partition. I'm using lilo as a bootloader... how do I do this? Specifically,

-how do I edit lilo's config file? I can find it easy enough, but I can't save any changes
-what commands do I add to the config file?

<a href="http://supportforum.sun.com/sjds/index.php?t=msg&goto=2762&rid=0#msg_2762">Here</a> is a record of a similar problem that the guy solved by editing Grub. I seem to have Grub (there's a Grub folder in my boot folder), but it doesn't have the config file mentioned and I don't think it's being used in booting.

Lastly, if I'm going about this all wrong, someone point me in the right direction please?

Thanks muchos,
Dan

to edit the lilo configuration:

vi /etc/lilo.conf


to write the new configuration to the mbr or wherever you installed lilo:

lilo

or

lilo -v

or

lilo -v -v

or

lilo -v -v -v

etc...

=)


just curious, did you do a windows partition resize with partition magic??

perhaps the error has something to do with the way windows is detecting the drive geometry or something (i'm not sure)??

i remember when i used to dual-boot sometimes i'd have to run "fixboot" or something like that from the windows xp recovery console (booting from xp cd) after doing a resize...

Yeah a dual-boot geometry with Partition Magic... the problem was that PM had, by default, hidden my windows partition- set the System ID to 0x17, which is lilo's change-rules is for hidden ntfs. I fixed the problem by using fdisk to change the system ID to 0x07, for normal NTFS. I should write up the entire process and post it somewhere, 'cause a lot of people seem to have this problem...

yeah, sorry... i realized geometry had nothing to do with your issue as it's the same drive...

*blush*

i remember correctly now why i had needed "fixboot"... it was when i copied the content of a fat32 windows partition to another drive (from within linux)... on the new (destination) drive, fixboot would be needed in order for windows to boot correctly... as it would spit-out an NTLDR is missing error...

anyways, i'm really glad you got it working...

=)


if you really want to post the solution on a separate thread i suggest you use for the subject the error message and some relevant keywords that you feel someone with the problem will use when searching this site or google...

by the way, just curious... is it possible to use the type changing feature of "cfdisk" for doing what you did??