jedimatt42

This concept or something like it was once upon a time implemented in something I just stumbled upon, but for GRAM devices: http://ftp.whtech.com/utilities/raggums.txt [email protected]

Dang, I would have never in a million years, thought to click on that. Regardless, I do like the index in post #1. For some reason naming the file: "TI-99/4a FlashRom99 Tunnels of Doom Non Inverted ROM EA5 Loader.bin" never caught on. I should look on my children's computers and see how they name things, or if they have been infected by emulating our past. [email protected]

http://www.ifarchive.org/indexes/if-archiveXscott-adamsXinterpretersXscottfree.html Oops, Greg beat me to this... [email protected]

There are two things that need to collide here: ScottFree, a C implementation of Scott Adam's Adventure interpreter, that is open source, GPL. And GCC for the TI... It looks like you'd just have to re-write the disk access and the screen handling. Maybe add a scroll back feature in AMS if available, and or larger database support. I was thinking 80 column adventure would be nice to have just a couple days ago. [email protected]

Here is Fred Kaal's Dsk2Pc v1.2 DSK2PCV12-8.BIN This would probably be a good test for stressing the disk gremlins. [email protected]

One of these days, I should read the manuals for these games [email protected]

I was thinking, I'm glad my soldering iron doesn't spark like that. Schmitzi has sounded hesitant to solder in the past, this must be why He's using too much power! [email protected]

Adventure works great.. Even loads data off HDX if you want! I love that the early TI stuff was compatible with full device.directory.filenames. [email protected]

Yep, my interface is very different, it is just pretending to be the same thing Don't forget about Tursi's scroll-lock option that turns the arrows keys from Fctn-E/S/X/D to just E/S/X/D. I've never been able to move and fire in parsec with the keyboard. Even on my console before I did anything too it. In fact, last July the first articles I received was a plain silver console, and parsec cartridge. And then I had to get some joysticks, cause that's how it was... hmm. I wonder what I do differently. [email protected]

So, I took a look at the good disk version of TOD I like having a good disk version of TOD... However, it's good for a reason. It uses the full 32k for itself. That doesn't leave any room for the cartridge loader code. Which needs about 300 bytes. So I have re-attached the TOD8.bin to my prior post, as indexed by Omega in post #1. [email protected]

I tested parsec, end to end just now. And with the usb keyboard it works just as well as with the TI keyboard. You can't move when you are firing. [email protected]

Yes, it does need the 32k expansion. The technique using classic 99 to create the cart image creates a cartridge that when run just loads the memory back up into expansion ram, and then executes from there. I had given this one a shot earlier, but forgot to share it! You know, this indicates another good reason to use the extended basic compiler, and put new life into those old basic programs [email protected]

Thanks! I forget that it is a dual rendered page with different info on the PC side...

A large set of TI programs never heard of initializing their variables. Cartridge software designed to work from power on state with nothing else getting to run before it was particularly guilty. At least that is my impression. Some of the conversions to EA5 from cartridge needed patches to fix up that start up state. At some point, this pursuit will probably require writing some assembly code. [email protected]

Cool! Careful with the 9.bin stuff. I was WRONG when I started naming them 9.bin, because that is not what I meant to signify. I was trying to name them so that Classic99 would recognize it as a non-inverted bank switched rom from the Cartridge-User menu. 8.bin means that. 9.bin meant nothing. I've tried to clean up my posts that had those 9.bin files in them. If you have downloaded them, take a moment to rename the file, so we don't create more confusion. [email protected]

That was all Fred's hard work, I just did the peanut butter and chocolate thing. I've been meaning to ask, in the video, it looks like you captured links that take you directly to the chat or webmail without going through the login page.. Can you describe your recipe for those links? Or have you already? [email protected]

Yes, sure! And I saw your request for Dsk2Pc. [email protected]

http://www.stuartconner.me.uk/ti/ti.htm#internet_web_browser It is a D/V80 file, that looks like it can contain any 99ml markup. The browser looks for it at DSK.BROWSER.FAVS, so by diskname. I hex-edited my browser, so it would look for HDX1.BROWSE.FAVS ... There is an example of the file in the .DSK image that Stuart makes available. [email protected]

By the way, I deleted the TOD8.bin from my earlier post, in hopes of containing it while I try again later with the good EA5 version posted by Torrax. [email protected]

Nice, I'll do a do-over. I only had the @1 @2 style files.

I'm happy to be helpful. Thanks! [email protected]

I've played this disk version quite a bit in the last year. But yesterday was the first time I tried it in classic99. The corruption on real iron is different than on classic99. The gameplay has always been fine though. [email protected]

I have to admit, I didn't try this image and the keyboard. I'll check it out after work. I played lots of the parsec that is on the xb2.7 cart, with my USB keyboard. It worked like the TI keyboard, that is problems moving and firing at the same time. [email protected]

Oh, nice, and the same process worked for TOD. Or at least the hacked up disk based loader of TOD that I have... (EDIT: I removed the attached file for now, in hopes of getting trying again with better source material) (EDIT (Again): The good disk based TOD which you can find a few posts down, is too big to pack into 32k ROM with a RAM loader, so I return to you, the slightly reduced title screen version) TOD8.BIN This TOD seems to have sacrificed the dragons face on the title screen. And as this is a GROM to expansion-ram conversion, you get to see a menu screen after you select the cart from a menu screen. It'll look less weird from the FlashROM 99. Maybe someone has a better EA5 version of the TOD module? [email protected]

Some one asked for PARSEC, so here it is... PARSEC8.BIN -- 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.