Some one asked for PARSEC, so here it is...
So, for the items I've captured so far, I have been able to take a pretty lazy approach for most things.
1. If Fred Kaal wrote it, then I use his ModuleCreator program over on ti99-geek.nl, this is so easy it needs no explanation, if it works for your EA5 images.
2. If it was an EA5 with 3 or less 8K files, and the load location of the first file is A000, then I just use Classic99 to make a 379 cartridge loader, and capture the high mem address range from A000 - FFFF.
3. Use bankinvert.jar to save the file as a non-inverted image.
Now parsec looked too big at a glance, it was four files, but 2 of them were smaller than 8k. So I googled up the EA5 format, to find the description on the TI tech pages. But that had to be wrong.. the address and bytes to load are backwards in Theiry's docs.
But, since the EA5 format looks so innocently simple: It looks like it can only copy bytes into CPU ram, and the files each say where and how much...
So, the parsec EA5 files I have, had the following header information for the 4 files:
Flag | Size | Addr
FFFF | 2000 | A000
FFFF | 2000 | BFFA
FFFF | 1900 | DFF4
0000 | 117A | 268C
For the purposes of making a cart loader, ignore the flag.
The Size and Addr can be used to figure out exactly what memory needs to be captured into the cart loader.
In this case, high memory is used from A000 to F8F4. A000 because that is the lowest high memory value in the Addr field of the file headers. And F8F4 because the highest Addr value plus that files Size will be the top of that.
The odd address needs to be included, so we want to tell the cart loader to capture high memory across A000 to F8F5
Then, we have a file that is in low memory.. so we do the same thing. Add Addr and Size and capture from Addr to that sum + 1.
If you have the room, check the restore VDP registers. Give the module a menu name, 'build' it, and then test it as a user module.
once that works, use bankinvert.jar to transform to a non-inverted image, and load it up on your FlashROM 99.
Images created in this way, require the 32k expansion to run, as the cart is loading the same EA5 bytes into the same addresses in memory, and then resuming.