Those included tarballs were residue left in my install bin when a kindletool (old version) had a temp file failure with the "." tempdir kludge. If I forgot to delete them, the next build (even with a good kindletool) snarfed them up as part of the package (what happened with the first mediafire upload).
However, I just looked in my scrollback buffer, and the intermittent fail I just mentioned was preceded by a "dir" which showed ONLY install.sh in my install folder. The only thing I did to make it work on the next attempt was to delete the destination Update.bin files of the same name.
Regarding slashes, mingw kindletool fails with a backslash in the path argument.
Interestingly, at one job I worked at back in the day, we had the source code for MS-DOS 1.0 (which I read front to back), and it supported BOTH forward slashes and backslashes in file paths (at least in the source code, but I never tried it because we were adding DOS API support to a unix-ish system. For some reason Microsoft REMOVED forward slash path support in later versions (perhaps to discourage Unix fans?). Back in the day I had a shelf of AT&T unix books, and I wrote a kernel driver for our custom hardware. My main development system (early rare expensive laptop) had a small (first gen) LCD with medium greenish-grey background and slightly darker bluish-grey squashed (not pixel doubled) characters (not backlit, and highly dependent on bright lighting and viewing angle, some of which were unreadable altogether). My eyes hurt just remembering the late night coding binges sessions in those days... I cannot even remember how many device drivers (and bare-metal embedded firmware from total scratch, including cutting and jumpering mistakes I found on prototype hardware) I wrote in my lifetime. Typically most device drivers began life as diagnostics, and grew sideways from there... Probably why I still enjoy native programs and I am looking and writing kernel mode drivers (for "rootkit/hiding hacks from amazon" support?)...
