
This is just additional information in case you ever needed to use Grub2. I recommend just sticking to Grub4Dos since that is what works well for you. coyote Try to download a bootable cd ISO (not img) Google MS-DOS.

Also, if you ever do want to use Grub2 with frugal installations of Puppy, it is pretty easy to configure. A large file to download, but the CD you will create will be much. Your solution of backing up your menu.lst and reinstalling the bootloader is exactly what I would have recommended. Sorry, I never noticed this thread until now. I briefly looked into using Grub and Grub Legacy 2013 as they are also both on Puppy, found that they have been superseded by Grub2, and wasn't sure if the ''standard version'' of Grub2 would detect frugal installations of Puppy as the bootloaders that come with Puppy do, so decided just to stick with Grub4Dos in the meantime since I know how to use it and it does the job. The grub4dos for UEFI EFIBootBOOTX64.EFI (renamed to g4e圆4.efi) is located on MBR (hd1, 0) which has a FAT-32 0C Primary partition where the EFI files/folders reside, of course during UEFI booting the HDs order is swap and becomes (hd0,0) as it is the only UEFI capable (seen then as first HD).

I backed up the menu.lst file first of all, then deleted the new one that was created when I ran Grub4Dos and replaced it with the back up, and I now have the menu back just as it was before.
