Just wanted to let everyone know, the tinybasic is ported to the Z8000 and working. I'll be putting the patched code up over the weekend.
The porting was relatively uneventful with two exceptions:
* zcc truncated all function names to 8 characters, causing two different globals (program_start and program_end) to appear as one.
* zcc does not handle word writes at non-word alignment, and this was causing line numbers to get corrupted.
N.Brown I would like to learn more about the Z80 emulation. I'm pretty sure the version I'm running does not have that. I wasn't even aware it existing (Ciarcia's Trump Card does mention running CP/M-80, but I figured he had written a translator)
The easiest way to check for Z80 and Intel 8080 emulation is to try out an old Utility or application for that class of microprocessor.
Normally if the system does not error out (a none program status error), crash, lock up, etc. then some sort on emulation is installed. with CP/M-8K or CP/M-68K. As fare as the OS Kernel files sizes they would change much depending how the emulation was done and if they are using kernel compression. They would only be slightly larger.
To test for 8080 emulation just run a old CP/M 2.2 utilities like the ones @
.................................................sq111.com Machine language SQueezer, very fast
.................................................uncr8080.com , uncr8080.txt 8080 uncruncher for LZW compressed files
.................................................uncr-z80.com is a Z80 uncruncher for LZW compressed files
> Of course the above listed (unarched executables) is to be tried on a junk fire on the system in question, or you could decompile the how OS to look for a emulation/translation code, but the above would be quicker to do for a test of an emulation module. (OLd school)
unfortunately our host (This message board) does not like some file extension. COM, EXE files, so I added a short link above to them.
The original OEM Emulation modules were not very large to add to add to a CP/M kernel that did not have them.
Integrated VT52 Emulation module for CP/M was around 4K in size, VT100 wasn't much bigger
Oem VT52 Graphics extension for CP/M was around another 4K to 8K in size (without using the GSX-80 extension)
Microprocessor Emulation. The objective code was from about 16K to 18K in code size for the Z80 emulation but could be up to 32K in size depending on how it was done.
I have included a short link to some 8080 emulators if you wish to try to add it to your CP/M 8000 kernel.
8080 emulation code
for dos but has source code link
Contribute to M4tthewDE/emu8080 development by creating an account on GitHub.
is a JAVA scrip version without OS kernel. A new link would have to be written.
has a A complete emulation of the Intel 8080 processor written in C99.
> Their are several others still available, but their support is questionable, Their use of undocumented function calls, instruction , shortcuts, Newer C extensions bugs with older compilers, Etc., Etc..
Two other links are : https://gitlab.com/gbrein/tnylpo/-/tree/master/mine
The big thing is the OS kernel would have to be patched at the point where the OS loads the Application or Utility or program to auto detect the microprocessor code being used and then use the Emulation code to run it. Etc. ,Etc. , The OS error kernel should also be updated.
Newer OEM version of Concurrent CP/M-86, 68K, Z8K, Concurrent DOS 86 had some sort of X80, Z80 emulation module installed if their was no real microprocessor on the system. As for Intel 8080 emulation under MC68000 microprocessor the Corvus
Concept native OS used a Intel 8080 emulation/translator module to run CP/M-80 stuff. yes, a Intel 8080 combability module for their OS.
The old Byte magazine Project - Ciarcia's Trump Card does mention running CP/M-80, they did integrate a Z80 combability module and built itin. Even with all the units that they sold - No body bothered to archive any of its software and firmware. (To bad Because I could of used a couple of them).
Their where other emulation modules for use by OEM's for the Z8000 based systems, but their data is mostly lost now days.
To keep this message short for our host - I just gave the basic outline of it.