Path: utzoo!utgpu!watserv1!watmath!att!att!emory!wuarchive!julius.cs.uiuc.edu!apple!vsi1!hsv3!jls
From: jls@hsv3.UUCP (James Seidman)
Newsgroups: comp.windows.ms
Subject: Re: Flight simulator and WINDOWS
Message-ID: <5534@hsv3.UUCP>
Date: 29 Oct 90 23:07:35 GMT
References: <85057@lll-winken.LLNL.GOV>
Reply-To: jls@hsv3.UUCP (James Seidman)
Organization: Video Seven / Headland Technology
Lines: 28

In article <85057@lll-winken.LLNL.GOV> rhodes@rogue.llnl.gov writes:
>Flight simulators are very processor intensive and so is WINDOWS. The two
>together are a bad mix. Just for fun I tried running FALCON AT under 
>WIN3 with some very amusing (and unusable results). So far, I think
>windows is great for things like DTP and drawing programs like DESIGNER and
>little else.

You might try running in Standard mode, which is much faster than 386
Enhanced mode for running DOS apps.  If you want to run it in 386 mode,
you should adjust the PIF to (a) make it run in exclusive mode, and
(b) set the "Monitor Ports" in the advanced section to "Text."

Part (b) alone will make a tremendous performance difference.
Any graphics-intensive application will perform terribly if
the PIF has "Monitor Ports" set to "High Graphics."  That setting
will add quite a bit of overhead to the graphics functions.

If you're not doing something else processor intensive in the background,
the speed of calculation itself shouldn't be too much of a problem.  When
not running other programs, you should suffer less than a 15% performance
hit.  Assuming you're running in 386Enh mode, try this and see what a
difference it makes.

-- 
Jim Seidman (Drax), the accidental engineer.
"It doesn't have to work... they'll be paralyzed just from laughing at me."
							- Dr. Who, _Shada_
UUCP: ames!vsi1!hsv3!jls	         INTERNET: hsv3.UUCP!jls@apple.com