Home Page Forums MAME MAME Requirements?

Didn't get this going as quickly as I thought, I forgot we didn't have comm or printer ports at all yet The disassemblies are definitely helpful though!

I've added COM and LPT ports and set them up to loopback properly (COM->COM, LPT->KBD, KBD->LPT). It's not working yet, so I'm diving into the ROM code to try and figure out what's actually going on.

The disassemblies unfortunately almost completely miss most of the failing diagnostic code (e.g. the interrupts test at ~F4C30) so I'm having to disassemble manually.

Yeah, the disassemblies are not perfect. Interrupt handling is especially fuzzy (though F4C30 _should_ be somehow covered).

Had hopes (in the past) that an Intel (or IDA) expert steps in and improves it.

With IDA 5 Freeware you'd be able to improve the source AND follow the execution flow more easily (-> graph feature, jump back and forth etc.)

Unfortunately, i am away this week and can't provide the most up-to-date IDB file necessary.

Not a problem. The 7201 printer port is now receiving the correct test byte sent from the keyboard 8251 but the test is showing as failed anyway so I'm trying to figure out why

We're now passing more of the tests, but MESS's existing 7201/z80dart emulation isn't lowering the interrupt line when it should, which means we get SYSTEM ERROR 2 (unsolicited interrupt). Working on it.

ETA: email sent to Curt, I don't understand what the 7201 is meant to be doing exactly

I bet that your problem is that you aren't reading the m1_r line to ack the interrupt. I think that it is a z80sio/dart thing that doesn't exist on the i8274/upd7201 but is currently required by the shared emulation.

The 8088 issues the 0x38 RETURN_FROM_INT command to the 7201 at the end of the ISR, but that causes z80_irq_reti() to hit the "Failed to find an interrupt to clear IE0 on" message and so the interrupt isn't cleared.

As far as I know, the alternate clear is only for the 8274, not the uPD7201, but I could be wrong.

The old link has been updated to include 2 binary IDB files (suitable for IDA 5).

I'd be interested which parts of the HTML output were flaky

A co-worker once advised me not to submit binary files to version control. So how can we start a collaborative effort?

I'd like to think we're actually nearing the end of needing to read disassemblies for this system, but we'll see :-)

To give something back to the community, i have delved into 'cpmtools' (LIBDISK). The original Win32 distribution was incredibly hard to use.

List, verify, empty, extract (or populate) CP/M images for VT180 and Rainbow-100 (*.img / *.td0).

https://dl.dropboxusercontent.com/u/37819653/CPMTOOLS_FOR_VT180_and_Rainbow100.7z

Comes with updated DISKDEFS. Win-32. GPL.

----------------
@R.Belmont: the "Design Maturity Test" disk contains 2 programs that could be interesting (disk boots, as does DIAG) -

CDVT CMD : PC100-B COMM DIAGNOSTIC REV 1.0 June 17 1983
XDVT CMD : Communications Diagnostic Rev 3.0 June 10 1983

Thank you very much for your patience and commitment.