(old)Puppy Linux Discussion Forum

Hi sc0ttman

Heres my grub4dos entry;

title 214-X5 (sda2/puppy214)
find --set-root --ignore-floppies /puppy214/initrd.gz
kernel /puppy214/vmlinuz pmedia=atahd psubdir=puppy214 root=/dev/ram0
initrd /puppy214/initrd.gz

Hope this helps
Stripe

Thanks bigpup, sc0tman and stripe.

Stripe wrote:title 214-X5 (sda2/puppy214)
find --set-root --ignore-floppies /puppy214/initrd.gz
kernel /puppy214/vmlinuz pmedia=atahd psubdir=puppy214 root=/dev/ram0
initrd /puppy214/initrd.gz

I will write about 'root=/dev/ram0' option on the document regarding the classic pup.

Updated Grub4DosConfig v1.6.3. See the top of this topic.
CHANGES:

• Manage the issue USB flash devices treated by the 'BootFlash' corrupts with Grub4DosConfig. (Thanks to smokey01)
  But anyway, re-format the USB device using gparted before using Grub4DosConfig (back up the data before).
  1. Delete all the partition
  2. Rewrite the partition table (Device >> Create Partition Table)
  3. Create partitions and format.
• Chainload PBR.
  Grub4DosConfig v1.6.3 gives menu items chainload the Partition Boot Records, like '(sda2:PBR)'.
  It does not always mean you can boot up from the partiton.
  There may be cases boot flag is on but the boot loader is not there.
  These items may be redundant because the OS is already listed up on the leading items.
  You can remove it from the menu after you are sure you can boot up the OS with another entry.
• New Puppy simple filename support.(Thanks to artifus and ICPUG)
• Classic Pup support, maybe not perfect.(Thanks to Stripe)
• Tool tips.(Thanks to sc0ttman)
• New icon. (Thanks to big_bass)

Thanks to all, and awaiting your report.

shinobar wrote:Manage the issue USB flash devices treated by the 'BootFlash' corrupts with Grub4DosConfig. (Thanks to smokey01)

Th Grub4DosConfig v1.6.3 checks the sector size, and gives error message like this:


It occures only when you once treat the USB by the 'BootFlash' and then you re-format it with ext4 partition.
Because fat32 case, the Grub4DosConfig v1.6.3 escapes the issue by using smaller boot loader.

Anyway, I recommend to re-format the USB device using gparted before using Grub4DosConfig (back up the data before).
1. Delete all the partition
2. Rewrite the partition table (Device >> Create Partition Table)
3. Create partitions and format.

Can you change "after escaping all the data" to "after backing up all the data"?

noryb009 wrote:Can you change "after escaping all the data" to "after backing up all the data"?

Thanks. Maybe next release

Shinobar, have patience with a perennial Newbie now.

I want to have a USB mem stick that I can use as a rescue thing on my and others computers.

But when I make the usb then it look for OS on the particular machine one make it on.

Suppose I make it on the Acer D250 then it list all the puppies I have on that one and it makes a menu.lst to be able to boot on that one.

All good but then I want to rescue the Packard Bell or the HP/Compaq computer.

So one would need some kind of script that would give a choice to include the new computer under its name and brand? A kind of menu.lst that was changed the order of the entries so the older entries for AcerD250 was pushed further down and those for the current Packard Bell that one use at the moment comes fist choices and then when one use it on the next computer then the OS for that one comes up first?

Maybe very unrealistic request for further versions update?

Maybe one could start all over with grub4dosconfig on each computer and create nested menu.lst files that had names or numbers for each computer one test it on?

nooby wrote:Maybe one could start all over with grub4dosconfig on each computer and create nested menu.lst files that had names or numbers for each computer one test it on?

Nice idea, nooby You can do it manually editing the menu.lst.

1. You make a menu.lst for the 1st computer running grub4dosconfig on the 1st computer.
2. You go to the 2nd computer and run grub4dosconfig on the 2nd computer.
   Made new menu.lst for the 2nd PC. This time, the menu list for the old 1st PC is automatically backed up with a name menu-xxxx-xx-xx-xxxxxx.lst. (you can rename it, say 'menu-1st.lst'.
3. Add next entry in the menu.lst of the new 2nd:

   Code: Select all

   title Next menu for the 1st PC
   configfile /menu-xxxx-xx-xx-xxxxxx.lst
   commandline 

For Classic Pup support, i add 'root=/dev/ram0' option in the grub4dosconfig v1.6.3.
But it may not proper...
What version of Puppy require 'root=/dev/ram0' option to boot up?
I am confused seeing the Barry's document:
http://www.puppylinux.com/hard-puppy.htm

Cool and when one boot how does the one chose among them?

I guess one have to manually go into geany or some other editor and add entries from each back upped menu.lst then?

Could not the script notice that one are on a new computer by knowing this is another MAC address.

Then it ask. Do you want me to add the OS on this new machine to the menu.lst or do you want me to back up the old menu.lst by giving it a back up number and treat this new machine as the one you exclusively want to use from now on?

Does that add too much to the simplicity?

Shinobar I know nothign about such but puppy search I found this one.

root=/dev/ram0

http://www.murga-linux.com/puppy/viewto ... 550#165550

You don't need 'root=/dev/ram0 ramdisk_size=16384' -- the kernel in Dingo will just ignore the root=/dev/ram0

Thread title is "Boot Puppy on the Asus eeepc"

in case that explain something?

when are that ram= used then?

shinobar wrote:What version of Puppy require 'root=/dev/ram0' option to boot up?

Only Puppy 2.xx. Starting with Puppy 3, that option was eliminated.

Hi shinobar

Grub4dos is working with frugal installs of 214 on hard drive and on usb stick as well

Cheers
Stripe

rcrsn51 wrote:Only Puppy 2.xx. Starting with Puppy 3, that option was eliminated.

Thanks nooby, rcrsn51 and Stripe.
I had a mistake. add the root=/dev/ram0 to both Puppy 2.x and 3.x.

@ Puppy 3.x users:
Remove the root=/dev/ram0 opton from the menu.lst entry.

shinobar wrote:For Classic Pup support, i add 'root=/dev/ram0' option in the grub4dosconfig v1.6.3.
But it may not proper...
What version of Puppy require 'root=/dev/ram0' option to boot up?
I am confused seeing the Barry's document:
http://www.puppylinux.com/hard-puppy.htm

Puppies prior to 3.0 used a ramdisk at bootup, from 3.0 onwards they used a "initramfs" -- a ramfs (ram filesystem) in memory to hold the initrd.gz contents.

Note, a ramdisk is a simulated disk drive in RAM, with a normal filesystem in it -- Puppy created a ext2 f.s.

From 3.0 onwards, if you do have "root=/dev/ram0" it just gets ignored. But, better not to have it as it will confuse people wondering why it is there.

BarryK wrote:From 3.0 onwards, if you do have "root=/dev/ram0" it just gets ignored. But, better not to have it as it will confuse people wondering why it is there.

Thanks Barry. I understand the "root=/dev/ram0" option is harmless but better to be removed as for the Puppy-3.x and later.

I just figured out what this was. Wow! Thank you so much!

jemimah wrote:I just figured out what this was. Wow!

Thanks jemimahf for your interest.

Please take a look on 'How to Install Puppy on Windows PC':
http://www.murga-linux.com/puppy/viewtopic.php?t=61796

Also consider the Windows Installer:
http://www.murga-linux.com/puppy/viewtopic.php?t=61404
The Windows Installer does not support Windows Me,
some problem reported with Windows 7(64bit) at this point of time,
Windows 7(32bit) is OK.

Just a word of thanks. I had an issue with my eeepc after fiddling with the partitions grub2 installed by ubuntu decided it would just give me an error message, with no solution. After much googling, it seems there is no working solution for grub2. Never did like it. I have no idea why ubuntu decided grub2 was better. Its a p.o.s. in my opinion anyway.

So back on topic, I had a usb drive with quirkynop on it, that included both a grub installer, and this grub4dos. Having only used grub before, I was happy to install it, but it insisted that my ext4 and ext3 partitions were both not linux partitions. Grrr-ub. So I tried grub4dos with the gui config. Wow. Awesome. Two clicks and it told me that there was puppeee, ubuntu and windows installed on the machine; and also that quirky was running via usb. Quick few name changes, and it installed everything perfectly. Beautiful. I didn't even have to argue with it like I have always had to with grub.

The only issue was that it put in an entry for the quirky usb that I had used to rescue the eeepc. So downloaded and installed grub4dosconfig to the puppeee install, ran the gui again. Absolutely perfect. And, also with a puppeee pfix=ram option. Fantastic. Even shows me my old grub2, which still doesn't work properly, but who cares.

I spent an entire day searching google and fiddling with ubuntu and repartitioning and generally messing around to get grub2 fixed, and in the end, grub4dos fixed it in under ten minutes. Brilliant.

Love puppy.

Love grub4dos.

Love simplicity.

I used Grub4Dos bootloader config to configure a USB Zip drive to boot puppy in a subdirectory on my harddisk.

My pc finds the zip drive and starts to boot from it however I got messages to say that grldr could not be found even though it had been successfully installed on the zip drive.

So I copied both grldr and menu.lst onto my harddisk and now after a few error messages the system boots into puppy as I wanted it to....

So why if I'm booting off the zip drive are the files on the zip drive not being found I wonder.....

Thanks
Peter