Grub4DosConfig
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?
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?
I use Google Search on Puppy Forum
not an ideal solution though
not an ideal solution though
Stable Puppy
I do not call it stable if 1 out of ten fails.nooby wrote:Quirky boots 9 out of ten boots.
Lucy boots 2 times then fail 5 times then boot 1 time then fails 3 times
How about Puppy 4.x series?
You can install the grub4dos-0.4.4.v1.6.0.pet on any Puppy 4.x/5.x.
Downloads for Puppy Linux [url]http://shino.pos.to/linux/downloads.html[/url]
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?
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?
I use Google Search on Puppy Forum
not an ideal solution though
not an ideal solution though
Quirky or Puppeee
If Quirky makes you content, use Quirky.nooby wrote: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?
I do not use any of the ones if it fails to boot 1 out of ten.
The Puppeee is atractive for net books.
Downloads for Puppy Linux [url]http://shino.pos.to/linux/downloads.html[/url]
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.
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.
I use Google Search on Puppy Forum
not an ideal solution though
not an ideal solution though
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.
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.
I use Google Search on Puppy Forum
not an ideal solution though
not an ideal solution though
Dual Windows
menu.lst:
For Windows NT/2000/2003/Xp, 'ntldr' insyead of 'bootmgr':
Using grub4dosconfig v1.6.1 and later automatically makes these multiple Windows entries.
Add new entry:# 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
EDIT:title Windows 7 on /dev/sda2\nBoot up Windows Vista/2008/7 if installed
map (hd1) (hd0)
map (hd0) (hd1)
map --hook
rootnoverify (hd0,1)
chainloader /bootmgr
For Windows NT/2000/2003/Xp, 'ntldr' insyead of 'bootmgr':
Or, simply:title Windows NT/2000/2003/Xp on /dev/sda2
map (hd1) (hd0)
map (hd0) (hd1)
map --hook
rootnoverify (hd0,1)
chainloader /ntldr
The 'map' lines are for USB devices. As for the internal HDD, simply:title Windows on /dev/sda2
map (hd1) (hd0)
map (hd0) (hd1)
map --hook
rootnoverify (hd0,1)
chainloader +1
Note (hd0,1) can be other numbers.title Windows on /dev/sda2
rootnoverify (hd0,1)
chainloader +1
Using grub4dosconfig v1.6.1 and later automatically makes these multiple Windows entries.
Last edited by shinobar on Thu 25 Nov 2010, 02:47, edited 3 times in total.
Downloads for Puppy Linux [url]http://shino.pos.to/linux/downloads.html[/url]
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.
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.
I use Google Search on Puppy Forum
not an ideal solution though
not an ideal solution though
CONGRAT agin
If you boot up the OS inside the USB, you cannot remove it before shutdown.nooby wrote:The boot being on that usb does that mean that even if I have booted on the HDD it still need the usb to shut down? .
If you boot up any OS on HDD, you can remove the USB after boot.
The grub4dosconfige saves 2 files at the top layer of sda1, /mnt/sda1/grldr and /mnt/sda1/menu.lst.nooby wrote:Where will your new menu.lst end up? on home under root? or in some subdir named grub4dosconfig?
Remind you need to edit /mnt/sda1/menu.lst manually, add entry:
Code: Select all
title Windows 7 on /dev/sda2\nBoot up Windows Vista/2008/7 if installed
rootnoverify (hd0,1)
chainloader /bootmgr
You are better to keep the backup of the current menu.lst, maybe at /mnt/<somepartion>/boot/grub/menu.lst.nooby wrote:if it fails how do I restore so it boot as it do now from Hdd?
If you copy it to /mnt/sda1/menu.lst, you can see old boot menu.
On the first dialog of the grub4dosconfig?nooby wrote:Which of the 4 choices should I tick..
Usually all OFF for MBR.
Downloads for Puppy Linux [url]http://shino.pos.to/linux/downloads.html[/url]
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
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
I use Google Search on Puppy Forum
not an ideal solution though
not an ideal solution though
jolicloud
nooby, i'd like to ask you on the jolicloud before you taking it away .nooby wrote: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.
Did the grub4dosconfig detect the jolicloud automatically?
Have you succeed to boot up the jolicloud directly from the boot menu?
Or from Windows to Jolicloud?
Downloads for Puppy Linux [url]http://shino.pos.to/linux/downloads.html[/url]
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?
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?
I use Google Search on Puppy Forum
not an ideal solution though
not an ideal solution though
SuperOS, Jolicloud
Your report will brush up future grub4dosconfig.nooby wrote:It seems that grub4dosconfig did not find my SuperOS frugal install and did not find Jolicloud at all.
Thanks so much for the information.
Downloads for Puppy Linux [url]http://shino.pos.to/linux/downloads.html[/url]
SuperOS and Joicloud
Please go ahead so far you don't care SuperOS and Joicloud.nooby wrote: should I just go ahead
Downloads for Puppy Linux [url]http://shino.pos.to/linux/downloads.html[/url]
I should be able to add SuperOs later if I want it. The bad thing with doing frugal on Ubuntu is that it can not save on NTFS yet.
Using grub2 it shoudl be able to do a real frugal install that saves on NTFS but I ahve seen no description.
Netrunner maybe is like that? that is a kind of ubuntu if I get it.
okay I give it a try and save a copy of the menu.lst somewere deep so I can add sueros later. no big deal.
Don't hold breath I am a slow tester.
Using grub2 it shoudl be able to do a real frugal install that saves on NTFS but I ahve seen no description.
Netrunner maybe is like that? that is a kind of ubuntu if I get it.
okay I give it a try and save a copy of the menu.lst somewere deep so I can add sueros later. no big deal.
Don't hold breath I am a slow tester.
I use Google Search on Puppy Forum
not an ideal solution though
not an ideal solution though
I have tested Super OS now and that works and booting up all Puppies work very good except for Murky puppy which I seem to have mistreated in some way.
So great thanks.
The menu.lst and the back up of mbr ended up on sda1 instead of sda3 which I expected.
I think sda1 is the recovery but I am not sure. I don't get how one see if sda 1 or 2 are the recovery.
Never mind windows works now after your latest change of how to write the menu.lst
But typical for the person I am, I had forgot how to log in to windows. hope I noted that down somewhere.
I am writing this from SuperOS as a live CD mode.
So great thanks.
The menu.lst and the back up of mbr ended up on sda1 instead of sda3 which I expected.
I think sda1 is the recovery but I am not sure. I don't get how one see if sda 1 or 2 are the recovery.
Never mind windows works now after your latest change of how to write the menu.lst
But typical for the person I am, I had forgot how to log in to windows. hope I noted that down somewhere.
I am writing this from SuperOS as a live CD mode.
I use Google Search on Puppy Forum
not an ideal solution though
not an ideal solution though
But i am afraid i cannot follow the problem you are listing up on the UUID.
Shall we talk at another topic?
Code: Select all
# Full installed Linux
title Puppy 430
uuid CDROM
/
/
/
14b40b44-9c87-4221-94ec-68f784eb8f1b
/
/
/
/
/
/
/
/
/
6d9a8e91-c301-4ff8-9875-97ec708cbee8
/
CDROM
kernel /boot/vmlinuz root=/dev/sda1 ro video=640x480 panic=300 debug
title Puppy 430 1
uuid CDROM
/
/
/
14b40b44-9c87-4221-94ec-68f784eb8f1b
/
/
/
/
/
/
/
/
/
6d9a8e91-c301-4ff8-9875-97ec708cbee8
/
CDROM
kernel /boot/vmlinuz root=/dev/sda2 ro video=640x480 panic=300 debug
.
.
.
title Lighthouse Pup 443 1
uuid CDROM
/
/
/
14b40b44-9c87-4221-94ec-68f784eb8f1b
/
/
/
/
/
/
/
/
/
6d9a8e91-c301-4ff8-9875-97ec708cbee8
/
CDROM
kernel /boot/vmlinuz root=/dev/sdc10 ro video=640x480 panic=300 debug
# Windows
I've got 11 entries like that (1 is out of the boot range of the Bios: I use this as Backup-partition which is mount- and useable from booted puppies).
The 1. UUID is sdb1 which had been mounted though I did not choose to mount a found wary070-savefile. After finishing the installation and runnig grub4dos I detected that I could have unmounted sdb1 via rox filer.
The 2. UUID is sdc8 (hd2,7) ((?while wary-098 had been frugally installed on sdc7 (hd2,6)?)).
Code: Select all
# blkid
/dev/sdb1: UUID="14b40b44-9c87-4221-94ec-68f784eb8f1b"
/dev/sr1: LABEL="Vodafone MCInsta"
/dev/sdc10: LABEL="/" UUID="1b68d71e-9a29-4d83-8dbd-01f71248e7a1"
/dev/sda2: LABEL="/" UUID="06e3798e-9ebf-4577-b5ec-dbcbcaba41d9"
/dev/sdc9: LABEL="/" UUID="8a64b67d-ed13-411b-a176-6b064653bf3c"
/dev/sdc8: UUID="6d9a8e91-c301-4ff8-9875-97ec708cbee8"
/dev/sdc5: LABEL="/" UUID="07443de5-1fab-4656-a3ab-7b1c14ccc8c8"
/dev/sdc12: LABEL="/" UUID="3c1b56dd-e0a1-4b28-b38c-d4172f81f720"
/dev/sdc4: LABEL="/" UUID="03020cb0-d7ae-4684-adac-0ed9bfa68165"
/dev/sde1: LABEL="RDYVHBBEAST" UUID="4F97-54FE"
/dev/sdc3: LABEL="/" UUID="04f6c08a-0af3-4d95-8b3e-c7eb057bbb98"
/dev/sdc11: LABEL="/" UUID="b9e29e1a-e306-4f27-ab34-7c4532286ff4"
/dev/sda3: LABEL="/" UUID="b9df22eb-a9de-4e5b-8b08-f38594058ef7"
/dev/sda1: LABEL="/" UUID="045a68d4-a1ac-4840-9d76-30820b36ae50"
/dev/sdc6: LABEL="/" UUID="f28bc57e-d1a8-4599-839b-4e30525f554c"
/dev/loop1: UUID="39a31570-33fb-45b8-862e-b7f59760bb74"
/dev/scd0: LABEL="CDROM"
/dev/scd1: LABEL="Vodafone MCInsta"
/dev/sdc1: LABEL="/" UUID="25512db1-adf1-4adf-915b-a4f0df91ef6b"
/dev/sdc7: LABEL="/" UUID="429ee1ed-70a4-43a5-89f8-33496c489260"
/dev/sr0: LABEL="CDROM"
Bugfix: v1.6.1 available
Thanks Karl Godt.
Found the version 1.6.0 makes Improper entry for full install with Wary-098 and in some case with Puppy 5.x. Please try the new v1.6.1.
Found the version 1.6.0 makes Improper entry for full install with Wary-098 and in some case with Puppy 5.x. Please try the new v1.6.1.
Downloads for Puppy Linux [url]http://shino.pos.to/linux/downloads.html[/url]
installed the 1.6.1 on Macpup F 3 full install on /dev/sdc5 :
the blkid entries for the full installs at the menu.lst are correct now :
I haven't booted yet.
One thing is confusing me a little :
It still does not recocnize sdb or sdb1 mounted or unmounted.
sda1,2,3 and all sdc are recocnized.
sdb holds a suse9.2 full install on reiserfs with several puppy frugals.
I think it might be the filesystem-type :
the blkid entries for the full installs at the menu.lst are correct now :
but the frugals seem not to accept additional kernel parameters :# Full installed Linux
title Puppy 430 (sda1/boot)
uuid 045a68d4-a1ac-4840-9d76-30820b36ae50
kernel /boot/vmlinuz root=/dev/sda1 ro panic=300 debug
title Puppy 430 (sda2/boot)
uuid 06e3798e-9ebf-4577-b5ec-dbcbcaba41d9
kernel /boot/vmlinuz root=/dev/sda2 ro panic=300 debug
.
.
.
title Lighthouse Pup 443 (sdc10/boot)
uuid 1b68d71e-9a29-4d83-8dbd-01f71248e7a1
kernel /boot/vmlinuz root=/dev/sdc10 ro panic=300 debug
tried three times deleting pfix=fsck and typing panic=9 debug .title dpup-001 (sdc3/dpup001)
find --set-root --ignore-floppies /dpup001/initrd.gz
kernel /dpup001/vmlinuz pmedia=atahd psubdir=dpup001 pfix=fsck
initrd /dpup001/initrd.gz
I haven't booted yet.
One thing is confusing me a little :
It still does not recocnize sdb or sdb1 mounted or unmounted.
sda1,2,3 and all sdc are recocnized.
sdb holds a suse9.2 full install on reiserfs with several puppy frugals.
I think it might be the filesystem-type :
Code: Select all
# probepart
/dev/sda1|ext2|2457882
/dev/sda2|ext3|2457944
/dev/sda3|ext4|2457944
/dev/sda4|swap|1092420
/dev/sdb1|reiserfs|35648172
/dev/sdb2|swap|3453974
/dev/sdc1|ext2|20755916
/dev/sdc2|none|2
/dev/sdc3|ext3|20627460
/dev/sdc4|ext4|29929094
/dev/sdc5|ext2|30780540
/dev/sdc6|ext3|30732282
/dev/sdc7|ext4|31117842
/dev/sdc8|ext2|30892932
/dev/sdc9|ext3|495765836
/dev/sdc10|ext3|31760442
/dev/sdc11|ext2|16996706
/dev/sdc12|ext3|229102902
/dev/sdc13|swap|2040128
/dev/sdc14|swap|2056256
/dev/sdc15|swap|2104452
/dev/sdc16|none|2104452
/dev/sdd|none|0
/dev/sr0|iso9660|253612
#