Puppy Linux Discussion Forum

[nooby]

Do not use develop versions of Puppy.

Ooops, I am that naive, I never even thought about it.

Which version of Luci do you see as a proven version then.

No the recoveery was a one time test to see if it could really rescue.

I always use exclusively puppy, quirky on Acer since luci fail to boot so many times.

Quirky boots 9 out of ten boots.
Lucy boots 2 times then fail 5 times then boot 1 time then fails 3 times then ...

Not reliable booting habit.

so which Luci is seen as stable for rescue?

[shinobar]

[nooby]

Now that makes me even more confused. Sure Barry use the word Quirky to remind us that he test quirky ideas and that it is a test version for his recent ideas on how to make a puppy.

But Quirky did things me could not do in 4.3.1 so I preferred to use Quirky.

Then maybe me should use Puppeee on the Acer and puppy 431 on a general version of rescue?

[shinobar]

[nooby]

I have three 1GB mem sticks so I decide to make


1. Fluppy 007 as a way to boot Acer D250 if the HDD fails in the future
I only need to change the boot code for it, So I will ask how to do this.

2.. Luci/Lupu 1GB or a 4GB memstick. to start modern computers
For to help neighbor if something happen to his computer.

3. Multiboot several frugal installs of Puppy different version on a 4GB
Good to have as a reserve.
4. Puppy 431to start old computers.

That way I feel more secure to always be able to boot.
Or else they just lay there to no usage. What a waist.

Thanks for your patience.

[nooby]

Shinobar,
Thanks for your patience.

I have to ask further on the boot up of Netbooks like my Acer D250.

I fail to boot it using Grub4DosConfig

It booted the recover partition instead of the real Win7Starter partition.

Now it looks like this on the usb.

Quote:
# Windows

title Windows Vista/2008/7\nBoot up Windows Vista/2008/7 if installed
map (hd1) (hd0)
map (hd0) (hd1)
map --hook
find --set-root --ignore-floppies /bootmgr
chainloader /bootmgr


but that load the recovery instead of the real win OS.


But on the older grup on hdd which do load the real Win 7.

Quote:
title Windows Vista (loader)
rootnoverify (hd0,0)
#savedefault
chainloader +1


# This entry automatically added by the Debian installer for a non-linux OS
# on /dev/sda2
title Windows Vista (loader)
rootnoverify (hd0,1)

chainloader +1


So how does one change your menu entry so it comply with this.

There are three partitions on the win 7 hdd.

I go change the usb again now and try to start all over to see what it do this time.

[shinobar]

menu.lst:

[nooby]

Shinobar, you made my day. That worked flawlessly. I booted using the usb mem stick and walked all the way down to boot windows and it booted the usual screen me always get and I booted fluppy 007 from that one.

The boot being on that usb does that mean taht even if I ahve booted on the HDD it still need the usb to shut down? Or can one do as with a CD/DVD that one take out teh usb after boot?

So now knowing me can boot the using the usb if something happen to the HDD then I can
try your grub4dosconfig to change my hdd then.


Now it has the menu.lst deep down in jolicloud subdir on Home.

Where will your new menu.lst end up? on home under root? or in some subdir named grub4dosconfig?

And if it fails how do I restore so it boot as it do now from Hdd?

Which of the 4 choices should I tick. None?

Thanks indeed for all help with this.

[shinobar]

[nooby]

Thanks again,
we wrote at same time so I skipped the edit and ask here.

I want to take away the Jolicloud that created the dualboot.

Now that I ahve a booting usb stick I can use that one as you describe and it will be dual boot instead of tripple boot.

Seems fool proof as I get it. I just wonder how one tell jolicloud to remove itself safely. hmm

[shinobar]

[nooby]

good that you ask before I do anything drastic.

I go and test now I get back within 15 minutes at most but try to be quicker than that.

I am back online having booted jolicloud from hdd the usual grub legacy made by wubi I guess

but it failed to boot jolicloud on the mem stick it was not even listed there.

It seems that grub4dosconfig did not find my SuperOS frugal install and did not find Jolicloud at all.

So what does that tells you?

[shinobar]

[nooby]

oops

that is good but should I just go ahead and install grub4dosconfig then and remove jolicould manually maybe to be the safest way?

[shinobar]