Home Page Forums MAME MAME NCR Decision Mate V (DMV)

Give a guy a finger, and he'll take the whole hand ...

... now that the demo5 is working in CP/M-80 and in colour ...

I've done some more tests

Demo5 is not running in CP/M-86 and MS-DOS ... and neither is DR DRAW in CP/M-86 and colour, but it is working in mono. Looks like the graphics emulation doesn't play nicely with the 8088 boards.

You need to run graphics.cmd and then draw.cmd from 8DRMO-M.td0 (mono) resp. 86DRDRAW.tdo (colour) from this archive. The mono version displays the splash screen and menu, the colour version just stalls.

https://dl.dropboxusercontent.com/u/55419307/NCR%20DMV/DMV%20advanced%20graphics%20%231.rar







On the third disk in above archive there is 80TGRAF.td0, another graphics library, this time again for CP/M-80, running CGDEMO shows some remaining alignment issues for the 7220

The color does the same as the mono if you load the mouse in slot 3.


The alignment issue is because it's drawing a slanted char which we don't yet support.

@crazyc thanks for all the work, I really appreciate that.

Adding the line


to the Floppy slot interface enables the selection of 96tpi disk drives. These were available as an option.

In this archive, there is a disk image with CP/M-86 that expects drive A to be 48tpi and drive B to be 96 tpi, the other disk image is a from a 96tpi disk and contains the GSX-86 test suite.

https://dl.dropboxusercontent.com/u/55419307/NCR%20DMV/DMV_CPM86_4896tpi.rar

MS-DOS can work with two 96tpi drives:

https://dl.dropboxusercontent.com/u/55419307/NCR%20DMV/DMV_DOS_96tpi.rar

Be careful to select the 96tpi drives before you drop in 96tpi images though, otherwise you'll get kicked out of emulation:



There is evidence on a 48tpi CP/M-80 disk that CP/M-80 was modified to work with 96tpi drives, but I have yet to discover a bootable disk for it - all I have is the HCOPY.com program on this disk that has a 96 tpi option.

https://dl.dropboxusercontent.com/u/55419307/NCR%20DMV/5-80-ORI.rar

The GSX-86 test suite provides further test cases for the display emulation. It is also available on

http://www.cpm.z80.de/binary.html

This archive

http://www.cpm.z80.de/download/screen.zip

contains a text file (actually WordStar) that describes what the test programs should show.

Sandro added the RTC module K803 and connected the mouse to K806.
I won't be home for a few days, so I can only test this on my Ultrabook ... if you select K803, MESS dies and complains about "Required I/O port 'DWS' not found"



This is on Windows 8.1 64bit with the new set of tools.

Another thing that puzzles me:

Calling MESS from the command line works without a hitch, but if you call the DMV driver from the internal UI, e.g. coming from another driver, you get the message "The selected game is missing one or more ROM or CHD images. Please select a different game." All my BIOS ROMs are in ../mess/roms , I've kept the default paths.

The first problem should be just a typo:
go to line 56 of emu/bus/dmv/kb803.c and substitute "DWS" with "DSW". Should work then.

typo fixed. thanks for catching.




it works here. might you have roms of the clones or of the devices inside the parent zipfile? internal UI is a bit pickier (or more limited, if you prefer) about the location of your roms than command line

I ran the GSX-86 test suite on the 96tpi disk image from post #96692 and juxtaposed the descriptions and the screenshots in this table ... this allows for easier re-testing when things change in the 7220 or DMV driver.

https://dl.dropboxusercontent.com/u/55419307/NCR%20DMV/CP-M-86%20GSX%20Test.pdf

I think it's awesome how much is already running! Some tests are not working because the functions have not been implemented in the DMV GSX driver. The blue line of garbage at the bottom of many screens is an indicator that something's not quite right yet.

Here are two disk images with software concerning the K803 Real Time Clock - both are bootable.

https://dl.dropboxusercontent.com/u/55419307/NCR%20DMV/DMV%20RTC.rar

The 5XTEST.td0 image contains a version of the DMV hardware tests that can check the K803 and find it working. It's curious though that the values that are displayed are different from using the RTC.COM on the other disk, dmv_rtc.mfi which is contained in the RTC directory.

To get the RTC working intially, you have to run CONFIG on dmv_rtc.mfi and choose to initialize the RTC on system boot. This creates a config.sys file with the correct parameters for TIMDRIVE.sys to import the time into DOS.

Two other utilities, rtc_n and set_rtc don't see the emulated K803.

Currently, on each boot of the DOS disk, the RTC is reset to the same starting point - I don't know if this is due to MESS RTC handling, the K803 driver or the internal DMV RTC driver.

Anyway,

MESS auto-syncs RTCs to the current real-world date and time each time you (re)start a driver.

It would be nice to have an "epoch delta" that is applied (via command line switch) when you start MESS.

This way you could easily "fake" your system running in the 1980s, for example