I'm very confident that my machine is virus/malware free, but I can't guarantee it as I am connected to the internet. Therefore I take no responsibility for anything bad that happens to your machine, everything you do with this Zip is of your own free will So please scan it before running it!

With that out of the way: I tested this on a Win32 Win7 machine and it worked fine, the only issue was that the Visual Studio runtime was not installed on that laptop and hence upon initial startup I received a "Application could not start 0xC000007B" error.

Stable ROM's are always built into the executable, so the executable you have has ROM's V1 to V4 built in, to access them you press CTRL+R, (CTRL+H displays a help screen).

When the ROM list pops up you'll see Grey ROM's and White ROM's, (the asterisk in the emulator GUI marks the currently selected ROM), Grey are internal, White are external. You can add external ROM's by editing the 'loader_config.ini' file.

Add whatever test ROM you want by copying it to the same directory as your executable, (or you can make a ROM directory, just make sure to get the paths correct), then add an entry into the INI file like so:

What sort of computer/GPU do you have? The help screen is a simple full screen quad texture with an Alpha channel that is quickly faded in and out. On every PC I have tried it on, (even 8 year old laptops), it works fine.

You shouldn't be using ALT-F5 or CTRL-F5, they are for executing code at specific addresses, (ALT talks to real hardware). The ALT functions won't work until you setup an Arduino with a COM port to your real Gigatron hardware. You also have to configure loader_config.ini

Normally what you want to do without real hardware hooked up to the emulator is just left click on a file in the Browser, (CTRL + B). This will execute it automatically in the emulator.

The emulator understands *.gt1, *.gt1x, *.asm, *.gasm, *.gbas *.gtb and *.gcl files, it will do everything it needs to do, to build and execute each type of file automatically.

But for *.gcl files and *.gtb files you must configure the path in loader_config.ini to your gigatron-rom tools, like this:

P.S. You also have to have Python 3 installed and the gigatron-rom tool suite contained within it, up and running to be able to compile and execute *.gcl and *.gtb files. You get the gigatron-rom repo from here: https://github.com/kervinck/gigatron-rom

Native:
- Native code runs from ROM.
- Native code is 8bit.
- Native code executes in a Harvard architecture.
- You use Native code when creating new ROM's or creating new SYS functions for new ROM's.
- You can build Native code in one of only two ways that I am aware of:
1) Use Marcel's Python tools to build new Native ROM's.
2) Use my assembler to build new SYS functions or ROM's.
- You can test new Native code ROM's or SYS functions in my emulator, it can load different ROM's, but it can also load and execute SYS functions to it's fake ROM for testing, (check out the *_ntv.gasm examples).

P.S. A SYS function is an extension written in Native code, (so it must live in ROM), that VCPU code can call for extra speed or low level functionality that VCPU code is unable to provide. It has limitations in it's size and and cycle count and has a calling convention that you must adhere to, once again check out the *_ntv.gasm examples.