From: Rez Newsgroups: comp.os.msdos.djgpp Subject: Re: WARNING: DOS is about to die Date: Tue, 07 Sep 1999 20:26:05 -0700 Content-Transfer-Encoding: 7bit References: <8D53104ECD0CD211AF4000A0C9D60AE30163726C AT probe-2 DOT acclaim-euro DOT net> X-Posted-Path-Was: not-for-mail Content-Type: text/plain; charset=us-ascii X-ELN-Date: 8 Sep 1999 03:23:16 GMT X-ELN-Insert-Date: Tue Sep 7 20:25:26 1999 Organization: Offworld Press Lines: 18 Mime-Version: 1.0 NNTP-Posting-Host: 1cust57.tnt4.lancaster.ca.da.uu.net Message-ID: <37D5D74D.3BB@earthlink.net> X-Mailer: Mozilla 3.04 (Win16; I) To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com Shawn Hargreaves wrote: > things back a bit further in the right direction, I find the Linux > DOSEMU program does a much better job of running djgpp programs than > an NT dos box (it even supports SVGA VESA graphics in a window!), Question, then: I beta-test for a coder who works with DJGPP under Win95. I test our app exclusively in real DOS. About half the time when there's a bug, the program runs just fine under Win95 in a DOS box (both for the coder and my testing partner) but segviols before it even gets fully loaded under real DOS with CWSDPMI. Sometimes this happens even with trivial bugs, like a wonked menu item. I realise this is vague, but anything in particular which causes this dichotomy (bug has no effect under Win95, dies spectacularly under DOS) ??? ISTM if we knew what sort of things cause this, we (ie. our coder) could avoid 'em up front. I'm tempted to rename this thread "DOS kills escaped bugs" :) ~REZ~