Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!foxhound.dsto.gov.au!fang.dsto.gov.au!myall.awadi.com.au!myall!blymn From: blymn@awadi.com.au (Brett Lymn) Newsgroups: comp.os.386bsd.questions Subject: Re: DOS/Windows under 386bsd (is there such?) Date: 29 May 93 23:14:29 Organization: AWA Defence Industries Lines: 26 Message-ID: <BLYMN.93May29231429@mallee.awadi.com.au> References: <1tgme7$n0q@urmel.informatik.rwth-aachen.de> <1993May20.234750.5815@fcom.cc.utah.edu> <1tmn92INN6el@hrd769.brooks.af.mil> <1993May24.182422.7719@gmd.de> <1993May25.082233.22564@cnplss5.cnps.philips.nl> NNTP-Posting-Host: mallee.awadi.com.au In-reply-to: rooij@mozart.cft.philips.nl's message of Tue, 25 May 1993 08:22:33 GMT >>>>> On Tue, 25 May 1993 08:22:33 GMT, rooij@mozart.cft.philips.nl (Guido van Rooij) said: Guido> veit@mururoa.gmd.de (Holger Veit) writes: [tacky mechanics of a dos emulator deleted...] Guido> I think, when trying to make a dos emulator for 386bsd, you can better wait till Guido> 0.2 comes out because it should have a per process IO bitmap. It makes Guido> things more easy. I think that allowing the dos emulator to perform direct i/o is an ugly cop-out and unnecessary to boot. I have worked with dos emulators that do not require direct i/o the result of which I was able to experience the joys of using Microsoft word on a vt220 terminal simply because the programmers had not made the blithe assumption that they could take control of the display adapter. This is what I want to aim for. Guido> Btw: whta happened to all ppl working on a dos emulator? I saw somepostings long time ago about someone porting the mach stuff. What happened to him/her? I am still here. I have decided to dump my work on the Mach DOS emulator and switch to the Linux one due mainly to the problem I experienced trying to duplicate all the multi-threading capabilities the Mach kernel has. -- Brett Lymn