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

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.

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 for the report.
I tried BootFlash on a USB flash to emulate ZIP drive.
Used the Grub4DosConfig-1.6.3 on Luci-241 and got success to boot.
It may depend on the hardware and BIOS?

"What generates the sdb4?" fdisk will do that -when you press 'n' to add a partition it gives you the option of specifying the number.
I've just been reading the bootflash script and noticed that it creates both 1 and 4 partitions, but my understanding has always been that for real ZIP drives to work there should be only the fourth partition, but maybe I am wrong -that happened once before, IIRC. LOL

the older version of your program placed the menu.lst on Sda1 instead of Sda3 where mnt/home is and all the pup folders and other programs.
How can I move them from Sda1 to Sda3? Drag and drop or do I need to do something more involved? The sda_mbr.bak should that one still be in Sda1 then?
What about bootmgr and grldr where should they be?

The bootmgr is of Windows, you cannot move it.

The grldr and menu.lst can be on any partition.
But notice that they are searched from the first partition and then next.

There is a trap. If there is a ext4 partition in the grldr search process, it hungs up.
One of the reason the grub4dosconfig put grldr on the first partition is escaping this trap.

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