Gigatron Hackers

Update:

- Removed 6502 emulation from ROMvX0.
- Removed WozMon from ROMvX0.
- Removed Apple-1 from ROMvX0.
- Removed Racer from ROMvX0.
- Added an interim version of Delpozzo's VideoPoker to ROMvX0, (update coming).
- Updated SDCard Browser to look more spiffy and to use 32 char file and path names.

I've updated the link in the first post to the new ROM and added a link to the new corresponding BabelFish.

Update:

- Updated VideoPoker thank you Delpozzo!
- Updated SDCARD Browser, can use up to 38 char filenames now.
- Updated clock.
- Updated executables gtemuAT67 and gtBASIC.
- The full source code for the ROMvX0 aware gtemuAT67 and gtBASIC are now available at https://github.com/at67/gigatron-rom/tr ... ntrib/at67, build them as you have done in the past. Tested on a couple of flavours of Linux and a big thanks to Delpozzo for helping remove the last of the Linux compiler warnings.

I've updated the link in the first post to the new ROM and added a link to the new corresponding BabelFish.

Any time at67, always happy to help! A huge thank you for including VideoPoker in ROMvX0, it's truly an honor

Hi, I have made in past several C-language programs and I wonder to what ROM version should I compile them?
Assuming I install ROMvX0 to machine and want best compatiblity. GLCC probably doesn't have ROMvX0 support. Would compiling to ROMv5a work?
I am not jumping to basic programming yet, because I tend to use the same codes with Linux-PC.

Edit. I was able to test with gtemua67 that my ROMv5a compiled programs dont start

GLCC 2.0 generates ROMvX0 compatible binaries by using the option "-rom=vx0 -cpu=5" or "-rom=v6--" depending on the exact version of the compiler.

Thx. I got it working with "-rom=vx0", but it seems its very slooow on my laptop. My desktop-pc is much better but not always the normal speed.

Hi.

How can I make ROMvX0 available in gtemuAT67 1.0.9R under Mac OS?
I found in loader_config.ini:
; an example of how to use external ROMS, (no limit until out of memory)
[ROMS]
RomName0 = ROMv3y.rom
RomType0 = 0x28
;RomName1 = dev.rom
;RomType1 = 0xf8

I copied ROMvX0.rom to the same place as Romx3y.rom is located.
So I entered RomName1 = ROMvX0.rom in the above loader_config.ini
But RomType1 = 0x?? ?

What needs to be given there? Is this some value at a specific file location?

thx, Peter

That INI file section is no longer needed, create a 'roms' folder wherever your executable is, (case sensitive for Linux and MacOS), and copy your ROM's into the folder.

Hmm..?
I did that and moved ROMv3y.rom also togehter with ROMvX0.rom in this new 'roms' directory.

Result:
This error message in console: Cpu::initialise() : failed to open ROM file : ROMv3y.rom <-- (did not change loader_control.ini)
And no extra roms (ROMv3y and RomvX0) visible with Ctrl+R.

Before, when I inserted RomvX0,rom in loader_config.ini, both were visible:
; an example of how to use external ROMS, (no limit until out of memory)
[ROMS]
RomName0 = ROMv3y.rom
RomType0 = 0x28
RomName1 = ROMvX0.rom
RomType1 = 0x28

and when clicking on ROMvX0, gtemuAT67 crashed with following console message:
Cpu::setRomType() : Unknown EPROM Type = 0x80 : exiting...
Press ENTER to continue . . .

Same behavior, when I change RomType1 = 0x80 in loader_control.ini

best, Peter

You're not using the latest version of gtemuAT67, the latest version is always here:
https://github.com/at67/gigatron-rom/tr ... ntrib/at67

P.S. That's not a crash, it's a clean exit handling an unknown ROM