Date: Wed, 26 Feb 1997 11:45:33 +1030 (CST) From: Michael Smith <msmith@atrad.adelaide.edu.au> To: jlemon@americantv.com (Jonathan Lemon) Cc: msmith@atrad.adelaide.edu.au, sef@kithrup.com, emulation@FreeBSD.org Subject: Re: Status report of vm86/dos emulation Message-ID: <199702260115.LAA20104@genesis.atrad.adelaide.edu.au> In-Reply-To: <Mutt.19970225102827.jlemon@right.PCS> from Jonathan Lemon at "Feb 25, 97 10:28:27 am"
next in thread | previous in thread | raw e-mail | index | archive | help
Jonathan Lemon stands accused of saying: > > The version of doscmd that I have is doscmd_fbsd-960923; I don't know if > this is the latest version or not. It was, however it has some serious problems with the redirector that I was talking about. Fortunately, my comments about 'big changes' were off the mark because I was looking at the 960920 release. If you want to tinker with the 'current' state of things, try ftp://gsoft.com.au/pub/doscmd/doscmd_fbsd-970225.tar.gz , this _should_ work, but I haven't been able to test it yet. (Waiting on Sean's 2.2 diffs and some time.) Note that the redirector bugs will affect any drives mapped in your .doscmdrc file using the syntax assign X: <path> and they are _serious_. > Sean mentioned something about using > ^T to display more information, I haven't been able to find anything to > make it do that. The new doscmd catches SIGINFO, you can use 'stty status ^T' to have the tty driver send SIGINFO. The default SIGINFO handler prints some useful details which you may prefer to the brusque output from the emulator. > With -current as of 2/4, and the last patch set I sent out, everything seems > stable (although tracing with '-t' does not work, my fault). If you are able to fix this (fairly tough, I know), that would be _extremely_ helpful in debugging future problems. > It seems that doscmd is lacking in some areas, at least wrt to OpenDOS. To > wit, I have the following problems: > > - I can't boot OD off an emulated hard drive, but it will happily > boot off of a real floppy or an emulated floppy (floppy image). Emulated in which sense (mapped like above, or using an assign to an image file)? > - if I pause for a long time, then hit a key, OD attempts to do > an "OUTSB xa60", and then quits with an illegal instruction. :-( Erk. That looks like someone trying to be smart and resetting the keyboard. > I'm definitely not a DOS hacker, so I really don't know what to look at. I > just bought the van Gilluwe book (Undocumented PC) but it only seems to cover > some BIOS calls - is there a better book to look at? If I can get a box here ticking with the patches, I can champion the hardware emulation stuff; what would be most helpful from you would be looking at using the VME stuff on Pentium systems (if you have access to one), and other cpu-emulation stuff. You've proven that you're a lot better at it than either of us 8) 8) 8) Finding bugs (like the ones above) is also a great thing 8) If you get a chance, have a look at Bochs; http://world.std.com/~bochs/ , and hit their FTP site for the latest version. This is IMHO the best of the soft PC emulators - it even runs W95. It would be most extremely cool if we could manage this 8) You could also look at the Linux 'dosemu', which does some good things with protected-mode programs. > Jonathan -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199702260115.LAA20104>