Sharp MZ

Do you happen to have the MZF file?

And beware, once compressed, it is like obfuscated as you cannot decompress it and get the binary back. So when archiving MZF, always keep an uncompressed one.

Here is the Windows version (compiled with Microsoft Visual Studio C++ 2019). You may need the usual runtime dlls if not already installed.

The link I gave you has the disassembly with address label lXXXX. I don't know more about. It sounds as if it can handle Floppy Disk AND Quick Disk the same way as MZ-800. The main difference would be around dealing with specific MZ-1500 hardware (palette, pcg, etc.) So ROM is IPL (2KB) + GCROM (4KB...

The only interest was for our MZ-700 to be able to get the complete QD management. But, yeah, that replica won't fit because it would need a different address decoder and a 2732 instead (that's what my last post was saying a "BUT"). MZ-1500 has already the complete QD management in its ori...

But it looks as if those ROMs having a complete set of QD commands have an address range of $E800-$FFFF instead of $E800-$EFFF. And I would even consider they could have code between $E010-$FFFF in fact (not necessarily only for QD).

MZ-1500 has 9Z-502M. http://mail.ordoz.com/pipermail/sharpmz ... 00815.html

I know three interfaces: MZ-1E14 (MZ-700), MZ-1E18 (MZ-2000/200), MZ-1E19 (MZ-800) and MZ-1500 has already a QD ROM. I wonder if the QD part for MZ-1500 can be used since MZ-1500 is more or less an extended MZ-700. I know MZ-700 QD ROM is more limited than MZ-800's. MZ-1E19 ROM commands: - QF-Format...

You must run the RAMTEST after each chip replacement until there is no more halt with the hexadecimal faulty pattern and address. Once running, say, a minute, without halting, it means there is no faulty chip found. Then you can try again your BASIC.

Really cool! Could it be possible to use the MZ-1500 QD code as I believe it is more complete and can write programs in QD unlike the MZ-700 interface?