Can't get there from here.

I made room to put Linux on my net-failing WinXP system and made a wrong choice. All the drive got wiped for Ubuntu.

The Ubuntu boot USB I have is old, 10.10. It installed great but the path up without a burner is make a USB boot. I get the 32 bit iso(s) and use the boot maker but the boot(s) give an error about a config file with few details and then it tries to boot over and over with "gfxboot.c32:not a COM32R image" message.

My WAG is that my Ubuntu 10.10 isn't dealing with those isos (tried Ubuntu 14 and 16 and Linux Mint) right, they all fail the same way at least.

So I have an Ubuntu install/rescue CD otw for Monday.

One bright feature: Arduino latest stable ver copied over and installed, tested, working just fine. Serial 2000000 baud!

Seriously, 1 byte per 5 microseconds, per 80 cycles, 200000 cps. Default SPI is 500000 (clk/4 div 8 bits per byte).

I need to find an archive of my serial keyword matcher to see if it chokes at 2000000 baud! It handled 250000 baud.

Try Puppy Linux - it can boot and run from a USB stick and you can then fix things on your hard disk. I suggest you use the Tahrpup 6.0 CE version of Puppy as they don't seem to have been successful making the change to the latest version of Ubuntu and Tahrpup should be fine to get you out of a hole. I used that as my principal OS for a considerable time but I am now using Mint 18 Mate

To be honest I can't see any value for the Puppy folks upgrading beyond Ubuntu 14 because all modern PCs have tons of RAM and disk space.

...R

My Puppy boot was also old and without the Winblows I have only one way to make a boot from an iso which isn't working.

I made a mistake in not preparing an up to support version, thinking what I had working would do the job.

BTW, the word matcher can't keep up past 250000 baud. There is an input buffer though, it didn't start to lose chars until about 80 where the output turned to garbage.