After a quick look I came to the conclusion that it would take a lot of work, problem is the 'windows forms base' of the program as it is now.
Also converting to UWP or WPF would't be a solution.
Checked Mono as a possibility but there are many snags with that I'm afraid.
So I'm not porting the...
Indeed it is the question of what a simulator is.
In this case it just simulates the input/output of the SDK-85 in the form of a display and keyboard.
So nothing with the timing (which is considerably slower with this program for the purpose of examining the assembler code running on it).
It emulates the SDK-85 in the way that is displays what is send to memory address 1800H and it reads the keyboard (if you click with the mouse on a button) by filling that value in 1800H.
But only if interrupt 5.5 is enabled (not masked) because that is the interrupt the SDK-85 uses for the...
Now at version 1.3 of the simulator, fixed some bugs.
Thinking about adding a second display/keyboard form for debugging other homemade (single board) systems, maybe based on a multiplexed system (port for digit, data for segments).
Any thoughts ?
Just my 2cents:
Recently acquired an SDK-85, so busy on a simulator for it last few months.
Just uploaded the first version to GitHub for those interested:
I recently bought me an IBM 5160 that I was able to put to use after a low-level format of the harddisk and installing MS-DOS 3.3 on it.
However, I noticed an 'Internal Stack Overflow' after operations for some time.
At first I suspected the keyboard (interrupt) because of the...