NetNews Usenet Archive 1992 #27/NN_1992_27.iso/spool/comp/os/mswindo/programm/misc/3604

Internet Message Format | 1992-11-22 | 1.7 KB

Path: sparky!uunet!pmafire!news.dell.com!swrinde!sdd.hp.com!cs.utexas.edu!sun-barr!ames!agate!stanford.edu!snorkelwacker.mit.edu!ai-lab!zurich.ai.mit.edu!pshuang
From: [e-mail] (Ping Huang)
Newsgroups: comp.os.ms-windows.programmer.misc
Subject: Re: when my windows app croaks, should I re-boot DOS too?
Date: 22 Nov 92 08:14:53
Organization: M.I.T. Artificial Intelligence Lab.
Lines: 21
Message-ID: <[e-mail]>
References: <[e-mail]>
NNTP-Posting-Host: freeside.ai.mit.edu
In-reply-to: [e-mail]'s message of Sat, 21 Nov 1992 00:04:52 GMT

In article <[e-mail]> [e-mail] (John Grant) writes:

 > While developing my Windows apps with Borland C++ 3.1, occasionally I
 > get UAEs (or whatever they're called now) [...] The question is - should
 > I also re-boot DOS when this happens?  Does Windows have any sort of
 > barriers between my app and DOS?  I'm using Windows 3.1 and DOS 5.0.

Windows 3.x makes it possible for your Windows program to corrupt the
internals of DOS, but whether you really need to reboot the machine
probably depends on what kind of bugs are causing your UAE's. I usually
have to exit and re-enter Windows when my application goes haywire
because then it doesn't deallocate unique system resources (VDMA
memory), but usually my application won't actually clobber DOS. However,
it would not be a bad idea, IMO, to warm boot at least once a day and
maybe more often than that, for your sanity's sake. :(

--
| Ping Huang (INTERNET: [e-mail]) speaking for himself.
| "One Thing to name them all, One Thing to define them,
|  One Thing to place them in environments and bind them..."