Unsupported Executable New Crc

[Beverly Zielonko]

13Invalid or unsupported executable format

This error is returned if the kernel image being loaded is not recognized as Multiboot or one of the supported native formats (Linux zImage or bzImage, FreeBSD, or NetBSD).

That is the case. My main distro is Arch_gnome, and I created an Arch_enlightenment on a separate partition, because enlightenment is my second favorite desktop. Arch_gnome grub installed in MBR end supposed to handle all the other installs. Chainloader +1 never failed me before. And it still boots ubuntu without problem.

Just curious, why did you do it that way? There is no reason one cannot install several 'desktops' and choose the one you want at run time. You can even log in multiple times and use different environments with each log in.

Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday

Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing

---

How to Ask Questions the Smart Way

Suddenly this method stopped working and I keep getting "Error 13: invalid or unsupported executable format" after I press return in the boot menue. I have tried using GParted and Grub4Dos on different versions of Puppy, but it makes no difference.

In Gparted.

showing the contents of the USB.

Are there any error icon tags on any of the partitions?

Right click on the ext3 formatted partition.

Select check.

See if that finds any problems.

Ext3 partition is flagged boot?

The next set of USBs were created using GParted to create a main partition and a swap partition. The entire content of the .iso file was then copied from the USBs created in the first step to the main partition of the new USBs. Until this point, there was only one Puppy per USB and no dedicated directory on the main partition. The files were copied directly to the main partition.

In the third step, I created another USB just like in the second step with the intention to try out several more Puppies using a common USB. This time I created a directory for each of the Puppies I wanted to try out. I downloaded the .iso files one by one, dragged them to the folder, clicked the .iso file to access the content, copied the content from the window that appeared and removed the .iso file. When all the Puppies were installed, I ran Grub4Dos. This was all done using Slacko Puppy 6.3.2. At least, this is how I remember it.

Now when I do the same way, I get "Error 13". Since I can get things to work if I use the downloaded .iso files from the first step, I suspect that the reason I get "Error 13" has something to do with how I access and copy the files. If I'm right, I don't really understand how it worked the first time.

The first way you did it.

The installer programs designed to do USB installs, make sure the USB is setup to boot, using the boot loaders files, that are in the Puppy iso.

This is a live install to a USB.

A frugal install is placing all the Puppy iso files in a named directory on the USB.

No Puppy files are just on the USB. They are all in specific directories for each Puppy version.

Then installing a boot loader on the USB to boot it.

You are trying to use Grub4dos boot loader.

One issue is what directory names Grub4dos Config looks for, to make a boot menu entry.

Best if you use the name of the Puppy version, to name the directory, you put the files in, for a frugal install.

To put more frugal installs on the same USB stick.

Do the complete Frugalpup Installer process again, for the new Puppy version.

When you run the boot loader install.

It will make entries, for all installs it finds, on the USB drive.

(Mind you, what you see above is part of the way I always add Puppies. Create a directory, copy the contents of the ISO across, then edit the 'menu.lst' file to add another boot entry. Commonly known as a 'quick'n'dirty' install. I'm sure I annoy certain individuals on here simply because I don't use the 'official' installers, into which they put a lot of work. Fact of the matter is, for the first couple of years I did.....after which I rapidly discovered the 'quick'n'dirty' method takes a fraction of the time once you have enough Puppy experience to know what you're doing.

If you only intend to have one single Puppy on the stick, a dedicated directory isn't necessary. However, it makes absolutely no difference at all whether files are copied to a dedicated directory OR to the partition itself.....they are treated no differently.

Frugal & live installs work pretty much the same in Puppyland. Both load Puppy into RAM, where able to do so, then give you the option to save your session at the end should you wish to do so. A frugal is usually installed to a 'permanent' home - an HDD partition, or a USB flash drive; the save is usually located in the same place as the Puppy install, though it doesn't have to be.

Generally speaking, it's only called a 'Live' install when used purely for testing purposes. However, as stated above, in Puppyland a traditional Linux 'Live' install works almost identically to the way a Puppy 'frugal' does.

I think I may have figured out what causes the problem, but I'm not sure I understand why. Looking at Mike's illustration I noticed that the .iso file that he klicked to open was located in a dedicated directory. I dragged the downloaded .iso file directly from the Firefox download library to the main partition. Here I klicked the .iso file to open it. It opened into a new window. From this window i copied all the files to the main partition. This method caused "Error 13".

I was under the impression that programs like Balena Etcher and Rufus cloned the .iso file to the USB. What difference, if any, is there to what happens when i open the .iso file in a folder in Puppy Linux by just klicking on it?

The thing is, not all drives have the exact same abilities, to perform read/write processes.

What built in controller, the drive has, and it's abilities.

So, hard to say 100%, all drives work exactly like this.

sure, they can all read/write, but exactly how does the drive do it.

Think on this.

If you have the iso on the same partition as the one you want to install the files on.

Everything is being done on that single partition and drive at the same time.

Got to read from it, and write to it.

Can only do one thing at a time.

So the reads have to be stored in memory and when it stops having to read, then it can do writes.

Also, a ISO is not actually accessed like a directory or folder. It is mounted or unmounted.

Example:

.

I wonder if you released the iso and unmounted it ,when you completed copying the files from it?

That can affect being able to do a clean unmount of the USB drive, when you shutdown the computer.

Luckily, Puppy shutdown or reboot process, is suppose to handle properly unmounting all drives, before completely power off computer.

.

If the iso is in a different location, a different drive is even better.

In fact, having the read data, on one drive, and the write location, on a different drive, always works best.

You can read and write at the same time.

No conflict on drive read write process.

The programs specifically for doing USB live installs.

Also have code to run checks on the drive for proper setup.

That when complete, it did make a working live install.

Most, by default, want the drive partition format to be fat32.

Why?

Because USB drives are already that format, by the manufacture, and all computers, have no problems, with fat32 format.

Some computers, only see a drive partition formatted fat32, as a proper boot partition, if containing a boot loader, to use to boot the computer.

I have a computer this affects. (has latest UEFI firmware)

If the usb has one partition, formatted fat32, a Live Puppy install, it has no problem booting.

If the partition is formatted a ext 2, 3, or 4 format, flagged boot, and has a Live Puppy install (same Puppy files).

The drive is not seen by the computer, as a boot-able device.

But, I can make a small first partition, formatted fat32, flagged boot, with bootloader files on this partition.

A second partition (any format), with the live Puppy install or a frugal install.

This setup boots with no problem.

Think on this.

If you have the iso on the same partition as the one you want to install the files on.

Everything is being done on that single partition and drive at the same time.

Got to read from it, and write to it.

Can only do one thing at a time.

So the reads have to be stored in memory and when it stops having to read, then it can do writes.

Yeah, that all makes sense when I think about it, actually. As I've said before, I'm perhaps not the best person to be helping folks out with much of this basic stuff; I don't use many of the built-in utilities that others have put lots of work into getting functional for beginners. I do SO much stuff in a totally manual, non-standard way, because it's simply quicker & easier for me to do so....

Small update, I've managed to get my hands ASRock W790 for a week or so and here are the results.

The motherboard comes with x2APIC (Extended APIC) enabled by default and there is NO way to disable it, replaced and dropped the APIC tables from the ASUS one and managed to get pass the Kernel Load and got stuck on AppleACPICPU. I'm guessing APIC issues need to be fixed, another problem is that the ASRock board doesn't have the COM port so its a blind test.

Attaching the Clover ACPI Dumps, Clover (Can't boot Clover yet, it's stuck on loading Kernel) and OC Bootlogs. and the ACPI SSDT I've replaced.

Any Suggestions? Is there a way to replace x2APIC in OC? I'm really in dark in here.

Thanks guys.

3a8082e126