Date: Mon, 08 Sep 1997 14:45:17 +0200 From: Helmut Wirth <wirth@zerberus.hai.siemens.co.at> To: emulation@freebsd.org Subject: Doscmd news Message-ID: <3413F35D.167EB0E7@zerberus.hai.siemens.co.at>
next in thread | raw e-mail | index | archive | help
Hello, the EMS emulation seems to work, the LIM EMS 3.0 function subset is tested, the rest of the functions is written, but largely untested. I am now working on two things: First test the rest of the functions and commit the code. I have to do this by hand, because there seems to be no real test software for EMS 4.0 (I have a small test program for the EMS 3.0 subset). Second, I am trying to get some test- and benchmark tools to run under doscmd. (I.e. Norton utilities´ 8.0 sysinfo.exe and ndiags.exe and QEMM 8.0 manifest (mft.exe)). This reveals a *lot* of problems with the doscmd code. I now have a nearly complete emulation of the timer chip; a DOS app can program and read the system timer (ports 0x40-0x43) This works fairly well, but it needs at least a minimal emulation of the Interrupt controller (PIC) too, because many programs use this for timing purposes. I only have a rather crude hack for testing, but I plan to do a minimal emulation of the PIC (at least a program should be able to send EOI, and to read the ISR and the IRR). This in turn enabled the benchmark programs mentioned above to start to run, but I now have a rather nasty problem with mingling signals (I think). Hence my question to gdb, (see another mail). Regards -- Helmut F. Wirth --------------- E-mail: hfwirth@ping.at E-mail (at work): wirth@zerberus.hai.siemens.co.at Tel. : +43-1-1707-37610 (at work) FAX : +43-1-1707-57602 (at work)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3413F35D.167EB0E7>