(old)Puppy Linux Discussion Forum

Posted: **Sat 13 Nov 2010, 12:59**

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.

nooby, i'd like to ask you on the jolicloud before you taking it away

.
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?

Posted: **Sat 13 Nov 2010, 13:08**

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?

Posted: **Sat 13 Nov 2010, 13:34**

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

Your report will brush up future grub4dosconfig.
Thanks so much for the information.

Posted: **Sat 13 Nov 2010, 13:38**

oops

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

Posted: **Sat 13 Nov 2010, 13:48**

nooby wrote: should I just go ahead

Please go ahead so far you don't care SuperOS and Joicloud.

Posted: **Sat 13 Nov 2010, 14:05**

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.

Posted: **Sat 13 Nov 2010, 15:22**

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.

Posted: **Sun 14 Nov 2010, 15:34**

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

the panic and debug parameters I added myself.

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"

Posted: **Mon 15 Nov 2010, 12:05**

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.

Posted: **Mon 15 Nov 2010, 22:55**

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 :

# 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

but the frugals seem not to accept additional kernel parameters :

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

tried three times deleting pfix=fsck and typing panic=9 debug .

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
#

Posted: **Tue 16 Nov 2010, 00:31**

Karl Godt wrote:the frugals seem not to accept additional kernel parameters

Thanks Karl. There is a bug.
/usr/sbin/grub4dosconfig at line 606

<entry tooltip-text="$_Puppy_opt_tip"><variable>$PUPPYOPTIONS</variable><input>echo -en "$PUPPYOPTIONS"</input></entry>

Remove '$' from the first '$PUPPYOPTIONS', leave it as for the second.

<entry tooltip-text="$_Puppy_opt_tip"><variable>PUPPYOPTIONS</variable><input>echo -en "$PUPPYOPTIONS"</input></entry>

Karl Godt wrote: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 :

Sorry but the reiserfs not supported.

Posted: **Tue 16 Nov 2010, 13:52**

Karl Godt wrote:but the frugals seem not to accept additional kernel parameters

I find this is true too... Not sure if it is GRUB or not.

I can use the 'nox' option, and the 'ram' option - they both work..
But not together!

I have this in my menu.lst

Code: Select all

title Puppy LupQ-511 in safe mode
  find --set-root --ignore-floppies /lupq/initrd.gz
  kernel /lupq/vmlinuz pfix=ram pfix=nox acpi=off apm=off nosmp noapic nodma nopcmcia i915.modeset=1 video=800x600
  initrd /lupq/initrd.gz

The no X option (nox) works, but the no save file (ram) option does not..
My 'safe mode' still loads a save file..

I have tried

Code: Select all

pfix=ram,nox

and

Code: Select all

pfix=ram pfix=nox

The no X option always works, but LupQ still loads a save file in safe mode...

(Note this problem is not only with LupQ - it happens with all my 'safe mode' entries)

Posted: **Tue 16 Nov 2010, 23:23**

shinobar wrote: NOTE on the MBR:
Grub4DosConfig usually overwrites the existing MBR.
If you like to recover the MBR of windows, you can use Windows Installer CD.
But you cannot recover for the PC's which has special MBR made by the manufacturer.

I have never seen such PC's but hear some PC's without CD drive and the Windows recovery system is on the HDD.
In this case from the beginning, it cannot boot up the Puppy Live CD.

My Acer netbook has such a MBR, and in fact I ran into exactly this problem. I wanted to restore the original MBR as needed to run the Window recovery which is in the first partition on the hard drive.

Fortunately, a relative of mine has an identical netbook, which I had setup dual booting Windows and Puppy, but in that case I had used the traditional GRUB -- which made a backup of the original MBR when it modified the MBR.

This is very easy to do in a script, just get the first 512 bytes off the hard drive (I presume it is still 512 bytes for big hard drives):

dd if=/dev/sda of=orig_mbr bs=1 count=512

To restore the original MBR:

dd if=orig_mbr of=/dev/sda bs=1 count=512

Posted: **Tue 16 Nov 2010, 23:44**

Barry, does that mean that my MBR are destroyed then on the Acer D250.

I first used jolicloud to install itself using Wubi to make a dual boot and both program worked and then I used Shinobar's grub4dosconfig to install itself to make a trippel boot and as far as I know all three boots but unfortunately I have forgotten the password for Windows7starter.

How does one check if one have a backup of the original OEM MBR?

Posted: **Wed 17 Nov 2010, 00:31**

Thak you Barry, and nooby
As for the MBR issue, the grub4dosconfig v1.6.x has 2 progress.

One, the grub4dosconfig v1.6.x leaves the backup file of the old MBR, like /mnt/sda1/sda_mbr.bak, 32kB size(not 512 bytes).
Keep the file at the safe place. To recover the MBR, type the next command:

Code: Select all

cat sda_mbr.bak > /dev/sda

I do not provide automatic restore because i think it is not always safe. We cannot check the sanity of the backup file.

Two, the grub4dosconfig v1.6.1 and later makes menu entries for the multiple Windows.
You can select the usual Windows or the recover Windows from the boot menu.

As for the latter, i have not tested yet because i have not such a PC with recovery Windows in the HDD.
You can test it with making a rescue floppy or USB drive with the grub4dosconfig v1.6.1.
Awaiting your feed back.

Posted: **Wed 17 Nov 2010, 06:59**

sc0ttman wrote:I have tried
Code: Select all
pfix=ram,nox
and
Code: Select all
pfix=ram pfix=nox
The no X option always works, but LupQ still loads a save file in safe mode...

Code: Select all

title Puppy LupQ-511 in safe mode
  find --set-root --ignore-floppies /lupq/initrd.gz
  kernel /lupq/vmlinuz pfix=ram pfix=nox acpi=off apm=off nosmp noapic nodma nopcmcia i915.modeset=1 video=800x600
  initrd /lupq/initrd.gz

I tried 'pfix=ram pfix=nox' options and found the 'pfix=ram' option doesn't work in this case.
But 'pfix=ram,nox' seems working as expected.

Code: Select all

title lupq-511 (sda3/puppy5) Safe mode
  find --set-root --ignore-floppies /puppy5/initrd.gz
  kernel /puppy5/vmlinuz pfix=ram,nox acpi=off apm=off nosmp noapic nodma nopcmcia i915.modeset=1 video=800x600
  initrd /puppy5/initrd.gz

Posted: **Wed 17 Nov 2010, 07:48**

Shinobar, now when you remind me I do remember that the program did say that it made such a back up file. Thanks.

i915.modeset=1

Should that one be used for Acer D250 too.

Could that explain why I fail booting at times. I should ad that one to the kernel line?

Posted: **Wed 17 Nov 2010, 07:52**

I have a need that I think GRUB4DOS can address.

Need
I need a bootable diskette that will boot a Windows machine and will boot my QuickSET or my PUP5.2 LiveCD.

Reason
I have couple of older systems that I need to boot which require me to use a floppy to start the systems. Hardware wise, either the BIOS is faulty or the CDrom is faulty and will not boot from CDs. But the systems will start from floppy or HDD.

Request
I have 2 systems running from LiveCD; one is QuickSET and the other is PUP5.2. Using either of these LiveCDs, what do you recommend as the path to take to build a floppy that will boot the CDrom or the HDD?

Thoughts
My thoughts were to install a GRUB4DOS PET and without rebooting, build a bootable floppy? But, I am not sure if GRUB4DOS has a utility to do something like this?

Anyway, what would you do?

Posted: **Wed 17 Nov 2010, 09:03**

gcmartin wrote:Need
I need a bootable diskette that will boot a Windows machine and will boot my QuickSET or my PUP5.2 LiveCD.

Reason
I have couple of older systems that I need to boot which require me to use a floppy to start the systems. Hardware wise, either the BIOS is faulty or the CDrom is faulty and will not boot from CDs. But the systems will start from floppy or HDD.

OK, assume you have 2 or more PC's.
One has CD drive but cannot boot off from CD nor from USB, But can boot off form floppy. Let us call it 'target PC'.
The target PC is running Windows or any other OS.
Another PC can boot off from CD and have FDD. Call it 'mother PC'.

I recommend to install Puppy frugall on the mother PC.
If you do not like to touch the HDD at all, you can use USB drives.
Of course the mother PC needs USB interface if you like to use USB, but need not it can boot off from USB if you can boot off from the live CD.

The target PC needs to install Puppy on its HDD because the live CD nor USB does not work on these PC even with boot floppy.
At the boot stage grub4dos tries to access the media via BIOS, but the BIOS on these PC cannot handle the CD nor USB.

The Puppy Live CD can be any version of Puppy-4.x/5.x. But choose stable ones and what may fit for the target PC.
But i recommend Puppy-5.x with the reason of the file name issue on CD i will menssion later.

OK, then follow the next steps:

Run Puppy Live CD on the mother PC.
Make a directory at the top layer of any partition or USB, say '/mnt/sdb1/puppy'.
Copy all the contents of the live CD into the directory, say '/mnt/sdb1/puppy'.
Install most recent version of Grun4DosConfig.
Insert a floppy. Remind all the files in the floppy will be cleared.
Run the Grun4DosConfig. Menu > System > Grun4Dos config.
Select 'Floppy(fd0)' as the target. All the checkbox options are ignored in this case.
Press OK for all dialog.
Unmount the floppy after success, and remove it.
Shutdown the mother PC. You need not make savefile.
Run the target PC with Windows or any other OS from the HDD.
Make a directory with same name of the mother PC, say 'C:puppy'.
Insert the Puppy live CD and copy all the contents into the directory, say 'C:puppy'.
Depending on the Puppy version, the file names can change the case or odd names.
Puppy-5.x maybe OK. I know Quickset LupQ-511 is OK.
If you can use USB, no problem with any version of Puppy as for the file names.
Just copy the whole holder 'puppy' in the USB to the HDD.
Insert the boot floppy in the target PC and reboot.
After you confirm the floppy can boot off the Puppy in the target PC,
test if the same floppy can also boot off the Windows in the target PC.
If not, follow next step.
Run the Puppy on the target PC from the boot floppy.
Install most recent version of Grun4DosConfig.
Make new boot floppy on the target PC with same procedure as before.

Of course there are another strategies:
One with PLOP as steve_s succeeded.
http://www.murga-linux.com/puppy/viewtopic.php?t=62010
Another, we have the Lucid-Puppy-Quickset-edition-511-Installer.exe supports all Windows except Windows Me.
http://www.murga-linux.com/puppy/viewtopic.php?t=61404

Posted: **Thu 18 Nov 2010, 02:13**

@Shinobar, Thanks for your reply. I see the steps 1-19 and understand them.

One question:
Does this mean that if I have QuickPET/PUP5.2 LiveCD in cdrom at diskette boot time, I will not be able to select an option to start the LiveCD to boot?

Thanks in advance...

(old)Puppy Linux Discussion Forum

Grub4DosConfig

jolicloud

SuperOS, Jolicloud

SuperOS and Joicloud

Bugfix: v1.6.1 available

PUPPYOPTIONS

Re: Grub4DosConfig v1.6.1

How to recover the MBR

pfix=ram pfix=nox

Is GRUB$DOS good for this problem

Boot floppy for non CD bootable PC's