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.

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._________________Downloads for Puppy Linux http://shino.pos.to/linux/downloads.html

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?_________________I use Google Search on Puppy Forum
not an ideal solution though

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.

You make a menu.lst for the 1st computer running grub4dosconfig on the 1st computer.

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

Add next entry in the menu.lst of the new 2nd:

Code:

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

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?_________________I use Google Search on Puppy Forum
not an ideal solution though

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._________________http://bkhome.org/news/

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum