On 3/8/26 01:48, B 9 wrote:
On Sat, Mar 7, 2026 at 1:41 AM Brian K. White <[email protected]
<mailto:[email protected]>> wrote:
Adopted your idea to just flip the high bit instead of
adding/subtracting. I still don't encode 255 by default because it
makes
the file larger, but added an option that adds 255 to the unsafe list.
It's 127 (DEL) that gets dropped by EDIT. I use !255 to encode delete
just to be safe, even though the BASIC tokenizer handles it okay. This
is just in case someone wants to EDIT the file loader before running it.
ahh
That's more likely for my co2do program since it currently doesn't have
a SAVEM option; it always runs CALL/EXEC.
Added an option to generate a "poor man's trigger file" instead of
either call or savem.
A "trigger file" sounds like a good idea, if it means what I think it
means. It's just a little BASIC program that uses CALL to a machine
language routine, right? What is a "poor man's" version?
The "poor man's" version is a one-line basic that does clear & call.
Or clear & runm if you want to have multiple .co files that all need to
run from the same address range, but the real point is not to have any
.co file, just the single actually runnable copy in highmem, and just a
short basic to launch it by calling to the exe address.
The user has to type 2 commands manually from screen prompts, but one
nice thing, the final command in the loader is a LOAD that loads the
temp ascii file (which the user then has to save), and that LOAD wipes
out all the space taken by the loader & data just like NEW, so that's nice.
The not-poor-mans version is a tiny specially crafted fake co file
that's just a header with no payload, and ideally also with the filename
edited to remove the .CO
I don't know how to make one or how it actually works.
There is a recipe to make one in the Teeny manual, but for the life of
me I can not follow Ron's baroque writing. Plus, it's not really an
explanation of how trigger files work in general anyway, it's more just
a sequence of steps to perform like a monkey without knowing why you are
doing them, but if you just pretend you are a computer that Ron has
programmed, then at the end you have a trigger file for teeny, maybe.
The "program" does even include error handling and cleanup branches so
at the end you might not have a trigger file.
"In mother Russia, document write you!"
https://bitchin100.com/wiki/index.php?title=TEENY.CO_MANUAL#Invocation_via_Trigger_File
or
https://github.com/bkw777/dl2/blob/36cb387f40dfb6ec9c28992b0831118020e0dbe3/clients/teeny/teenydoc.txt#L675
--
bkw
