Re: window386 && their WORD

Article View: comp.sys.ibm.pc

Article #42989

#42989

From: Matt Watson
Date: Sat, 24 Feb 1990 19:29

8 lines
1009 bytes

I currently have W.F.W. running on a model 70 (16 Mhz).  A couple of
things seem to help...  Make sure you run memset to configure the
maximum available memory, and then try running windows with the /n
switch.  That helped more than anything to get over the inherent
slowness of Windows/386. (stick it out, though...Wait 'till you see
windows ver. 3...zoom).

mw.

Technical Details

Message-ID: <9513@portia.Stanford.EDU>

Path: arc1-ca.pugleaf.net!utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!uwm.edu!ogicse!decwrl!shelby!portia!homerun

References:

<754@eedsp.eedsp.gatech.edu> <1779@uklirb.informatik.uni-kl.de> <542@cpqhou.UUCP> <2113@milton.acs.washington.edu> <6728@uhccux.uhcc.hawaii.edu>

Show Full Headers

Complete Article Headers

Path: arc1-ca.pugleaf.net!utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!uwm.edu!ogicse!decwrl!shelby!portia!homerun
From: homerun@portia.Stanford.EDU (Matt Watson)
Newsgroups: comp.sys.ibm.pc
Subject: Re: window386 && their WORD
Summary: try this...
Keywords: not that slow
Message-ID: <9513@portia.Stanford.EDU>
Date: 24 Feb 90 19:29:01 GMT
References: <754@eedsp.eedsp.gatech.edu> <1779@uklirb.informatik.uni-kl.de> <542@cpqhou.UUCP> <2113@milton.acs.washington.edu> <6728@uhccux.uhcc.hawaii.edu>
Sender: Matt Watson <homerun@portia.stanford.edu>
Reply-To: homerun@portia.Stanford.EDU (Matt Watson)
Organization: Stanford University
Lines: 8

Reply to Parent Message