Hi
@01micko and
@gyrog .
So far I have only tried booting the test eslacko64 from a USB as follows.
a) Added a directory "eslacko64-test" to the "OS" partition on a USB drive used to boot Fatdog64-811 and multiple Puppies. The setup is derived from the Fatdog64-811 usb-boot-mbr.img.
Although I would normally only copy a subset of the files in the ISO across to the directory, in this case I copied all of them.
Modified grub.cfg on the USB drive to add two entries, one eslacko-test1 (without the pdrv parameter) and eslacko-test2-pdrv (with pdrv=OS).
1st test on an AMD A4-9125 based laptop in Legacy/CSM mode:
Booting with "...-test1" resulted in "Waiting for 5 seconds for slow storage devices" coming up early in the process.
The Puppy files seemed to load, but it didn't boot to a desktop, not being able to load "X".
Booting with "...-test2-pdrv" resulted in "Waiting for partition[OS]" appearing early in the process. Again Puppy files seemed to load, but the OS was unable to proceed to a desktop.
I didn't pursue things any further in either case since I suspect the element being tested had worked as expected and this machine can be finicky (needing nomodeset at times, etc).
Edit-[I suspect it may not like the real time kernel, or I might have missed something.] [should be] Heck, I'm dense. Because it is nice and easier, I have been booting off a USB drive with Fatdog and multiple Puppies. However, they are booting with the parameters that I have put into the grub.cfg file, not the parameters and options available in their respective boot menus. They are not chainloading etc.. Hence, while it mainly works, it probably isn't the best option when trying to test something. D'oh.
2nd test on an AMD A4-9125 based laptop in UEFI only mode:
Essentially the same as above.
3rd test on an AMD Turion64x2 based laptop locked in Legacy/CSM mode:
"test1"- "Waiting for 5 seconds for slow storage devices" (as expected). Booted to desktop.
"test2-pdrv"- Odd, it seemed to go straight to loading the Puppy files (unless I missed the "waiting..." message). Again booted to a desktop.
I was almost going to try to use FrugalPup to do a test installation on this machine, but after reading the Help I bailed out.
Whilst I could be wrong, I get the impression that it might be most suitable for an install to a "fresh/clean" drive. This is only an impression of course.
The "real" problem, that finished any thoughts, was the requirement for a FAT32 partition at the beginning of the drive.
Whilst I understand that a USB drive could be set up to do the boot, this machine has Windows XP, a number of older Linux distros, Fatdog and a directory with Puppies on it.
These are booting from a Legacy Grub setup (not Grub4DOS), the files for which are on a partition following the one holding XP.
I held off since I can see myself getting into a "mess".
I thought I should post something even though I could try some other machines. I was also thinking of just "burning" a CD-RW for "clean" tests on some machines, without any other variables.
However, if I understand correctly, it seems to be working this way.
Would you prefer that I edit this post to add any later test, or a make a fresh post?
Thanks.
Edit- additional info and crud.
The ISO was successfully burnt to a CD-RW. When it booted there was a fleeting message about "No MBR magic", along with some other messages that went by too quickly for me. However it seemed to boot OK, so maybe not relevant. I presume as it was booting from optical media, there were no "Waiting..." messages.
Following this I decided to try to use FrugalPup to install eslacko64 to a USB drive. Blundering Baldronicus Bean Magoo has made a right wondrous mess of this. I think I might try again tomorrow. Between not concentrating and reading properly, together with, I now think, using a suspect USB drive, the result has not been good. The USB drive didn't boot. The BIOS just seemed to keep cycling, trying to get it to work.
Since I did make such a mess of it, there might be some things that might be of interest for later.
Although it is indicated that the partitioning needs to be set up in advance (clearly for the sub unit that I have forgotten the name of. D'oh. But not quite as clearly for FrugalPup- but I think that might just be my interpretation), there doesn't seem to be an actual size requirement given for the leading FAT32 partition on a device (I'll probably see it in bright flashing lights tomorrow). I realise that different environments might have different requirements, but it could be an area where some of us might need guidance.
When the USB drive didn't boot, I thought I would take a look at the boot directory. Being the click-happy nut that I am, I had to see what this phantom "i386-pc" file was, didn't I? Clicking this changed the screen background to black. I don't know what else might have been messed up, so I just rebooted. I have a vague idea that I have seen and done this before. I only mention it case there might be support questions later.
In the end I attempted to use "Boot" to reload the boot environment. It couldn't proceed as the partition was not FAT32, even though a couple of checks with GParted seemed to indicate it was. Hence my suspicion about the USB drive itself.
Apologies for the verbal waffle again.
Thanks.
