Sorry for not reporting back more promptly. Needed to spend a bit of evening time with my bride ;)) Regrettably, the 'mkinitrd initrd-win4lin ...' command did not work (and I got called to dinner, so was not able to report that result). I had simultaneously sent an inquiry with all the details to support@win4lin.com so I'll be checking with them first thing in the morning and I certainly will report whatever I eventually find to be the solution. In fact, I definitely do plan to prepare a detailed "how-to" covering all aspects of this installation as soon as I get everything to work correctly. At least, I can confirm that I have gotten Mandriva 2006 (the "free" version) installed on two systems, so I offer this comment as encouragement to Mike, the other Plugger currently inquiring about this. I wish I could offer some help, but I have notes scattered all over dozens of handwritten and printed pages as I've been working on this for more than two weeks and still have a ways to go. It just shouldn't be this difficult, but sadly, it seems to be. Most of the obstacles turn out to be easy to fix, but regrettably, I was unable to find a concise, complete, step-by-step how-to that covered all (or even most) of the bases. What a shame. Joe ---------- Original Message ----------- From: Craig White To: plug-discuss@lists.plug.phoenix.az.us Sent: Mon, 02 Jan 2006 20:43:14 -0700 Subject: Re: How to fix /boot/grub/menu.lst - part 2 of 2 parts > On Mon, 2006-01-02 at 18:10 -0700, Craig White wrote: > > On Mon, 2006-01-02 at 20:01 -0500, joe wrote: > > > Thanks very much, Craig. > > > > > > Just to be sure that I am understanding you correctly, > > > are you saying that while booted in to the mandriva > > > partition, as root, at the command line, I just type this: > > > > > > mkinitrd initrd-win4lin-2.6.12-12mdk.img win4lin-2.6.12-12mdk > > > > > > ... and the system will (or should) reboot to the win4lin kernel? > > ---- > > I'm thinking yes. I know on Red Hat / Fedora systems, you need an initrd > > image to boot and judging from your grub.conf, Mandriva is no different. > > The above command should create the initrd image. > > ---- > > > > > > Then, I'm assuming that if this works, I'll need to build a > > > new /boot/grub/menu.lst in the mandriva partition to replace > > > the one currently being used in the mepis partition. Is that > > > right? I know, one step at a time, but just trying to get > > > this all in focus. ;)) > > ---- > > interesting point - my thinking is that the only time that this is > > referenced is at the original boot which I am assuming means that > > your /dev/hda grub is set to pull this info from hd(0,0) - the /boot > > volume from your original install (Mepis?) and I can't see the need to > > have it all duplicated in the Mandriva /boot hd(0,5). In fact, I am > > thinking that having multiple '/boot' partitions is a source of > > confusion and I probably would have wanted it all consolidated within > > one boot partition because I am not smart enough to keep it all > > straight. Thus, copying grub.lst from the one to the other shouldn't be > > necessary but it shouldn't hurt anything either. > ---- > report? > > Craig > > --------------------------------------------------- > 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 ------- End of Original Message ------- --------------------------------------------------- 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