Just came across this topic which has confused a lot of people so far.
It was (and so still IS, I hope ) easy to solve however. I hope I don't repeat anybody in this thread (I am in a HURRY!).
Never mind jiffyboot rewriting Lilo as long as it writes it .. correct.
Normally all I use to do is open /etc/lilo.conf and adjust the following order (or remove non existant drives which sometimes also accure after having connected a "alien" hdd) of the required startup following order.

I also make sure there's some space between the various info (by group) for clarity (to me that is, Linux seems to know its way anyway).

Your sample modified:

other=/dev/hda1
label=W<>_98

image=/boot/vmlinuz-2.4.23
label=L<>|_4.5.122
vga=0xf04
root=/dev/hda5
initrd=/boot/initrd-2.4.23.gz
append="resume=/dev/hda5 resume_block=0x2014"

image=/boot/vmlinuz-2.4.23
label=Redetect
vga=normal
root=/dev/hda5
initrd=/boot/initrd-2.4.23.gz
append="noresume redetect resume=/dev/hda5 resume_block=0x2014"

image=/boot/vmlinuz-2.4.23
label=Diagnostics
vga=normal
root=/dev/hda5
initrd=/boot/initrd-2.4.23.gz
append="noresume resume=/dev/hda5 resume_block=0x2014 single"


Then simply safe the new file.

BUT (now it comes): Before restarting open first a console and then run lilo by simply typing lilo and hit enter. Now you see in your console the new following order.
Now jiffyboot will rewrite all everytime you start up but .... the correct way. The way you wanted it.
That was end of my problems and .. the whole "mistery".

Other solutions also worked but I found this one very easy.
Hope it works for you as well (think so).

Hello Bicol_Willem,

Perhaps you can mention on which version of Lindows/Linspire you have had success with this method. This method will not work with my version (4.5.316).

That was the very first thing I tried. I changed lilo.conf, reran lilo, rebooted and all was good, until I booted back into Lindows and the MBR was re-written by the evil jiffyboot.

This is the only linux distribution I have found to be so arrogant as to re-write the boot loader at every boot and make itself the default. The lilo.conf that is installed on Lindows says that it will no longer be automatically updated after it's been changed, but it LIES!

Anyway, it doesn't bother me anymore.

:-)
--Nathan

O well, if it doesn't bother you you either never really bothered or ... gave up

Serious now: OK I run later versions: Linspire 4.5.xxx (I am going to install today the latest Linspire 4.5.499 on one of my machines).
My last remaining LINDOWS-OS version right now is 4.5.374 and runs like a train as well.

But if jiffyboot still bothered you you should open de properties/permissions and simple uncheck the exe functions.
Jiffyboot will then eat from your hand and won't bother you anymore against your will.

There are really nice improvements in the latest versions. CNR was a bit "overacting" for a while (wanted to update the same programs over and over again) but also this seems solved now. Just like any other Linux, Linspire is a work in progress. One got to love or hate it. Make up your mind.

O and ... have a lot of fun anyway.

Tip of the day: Get Linspire 4.5.499 and stay tuned!

Hi Bicol_Willem,

Do I have to change the properties/permission of jiffyboot file from inside Lindows or can I do it from inside Mandrake10.0 ?. I can not find it, although I have mounted the linux partition into .mnt/lindows in Mandrake10.0
Thanks in advance.

You should find jiffyboot in /sbin and I guess you should configure it while running Lindows. That's what I would do anyway.
Don't know why you can't see Lindows though.

Thanks Bicol_Willem.

May be you're right, I have to change the jiffyboot file's properties from within Lindows
Will try again, but afraid to be victimized by Lindows' default lilo rewritten.

You can always edit lilo.conf and rerun lilo after booting into Lindows. Then run:
chmod 444 /sbin/jiffyboot
to disable it from running next time.

--Nathan Chilton

Thanks GentooJava for this advice.
You just save my day . It didn't even cross my mind.

I just installed the latest version of Lindows (4.5.499), and am stuck trying to change the booting lineup. I tried to have Win98 as default, but when I run lilo, I get this error:

I tried to copy this file from the other hard drive that used to have Lindows 4.5.329, but I couldn't... permissions. I have been root for both installations, so I don't understand why I can't copy this file... anyway, I think that the installer is not good at putting the bootloader in the right place, because it will use the /etc/ folder from another drive to put the bootloader in....

I'll probably have to reinstall Linspire, without that drive connected.

This version is a "goody"!

Don't know HOW and WHAT you did in lilo.conf but it is really easy to change.
First (for clarity) devide the entre's and then simply place the win entre ("other") on top of the list (cut and paste). Then safe it all and open a console and run lilo by simply typing "lilo".
Then the same console shows the new boot order.

You can also remove the eventual extra entre's for "DOS" whatever that are in fact only non bootable partitions.

The whole jiffyboot story is no topic any longer in this version and jiffyboot will not override it.

Got to work!

I didn't do anything to LILO. It's just that I had Lindows on one drive, it stopped booting up while I was trying to install my new video card, so I decided to just upgrade to Linspire 4.5.499, and fix my system. What happened was that the installation used the bootloader from the other disk, and didn't install LILO in the new one. So that's why it isn't working. I already edited lilo.conf with Win98 as default, but I can't run LILO, because it isn't on that same drive. It's on the old Lindows drive. I tried to change that, but permissions locked me out.

This isn't the first time I'm dealing with this, but it is the first time now that I can't fix it how I used to. This time, I'm going to have to format the old Lindows drive, to get rid of leftover, and reinstall Linspire.

Yes, sometimes all cannot easy be explained
I never came across such problem but ... that isn't telling much.
However, did you try the "Redetect" option by chance?
Just curious.

I did try Redetect, but it doesn't fix it. Anyway, I got it fixed, by formating the partition altogether, and starting fresh. Now, the edited boot lineup stays the way it is, with WIn98 as default.

Advice for new people, make sure that you if you end up reinstalling Linspire, erase the previous instance of it, so that the new installtion won't used the old LILO to boot, that way it will be editable in the new install. Not to mention the hours of time you'd save .....