Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!ucsd!helios.ee.lbl.gov!nosc!logicon.com!trantor.harris-atd.com!trantor!dsampson From: dsampson@x102a.harris-atd.com (sampson david 58163) Newsgroups: comp.windows.ms Subject: Re: Windows 3.0 Message-ID: Date: 25 May 90 12:37:00 GMT References: <6564@umd5.umd.edu> Sender: news@trantor.harris-atd.com Organization: Harris Gov't Aerospace Systems Division Lines: 32 X-Local-Date: 25 May 90 05:37:00 PDT In-reply-to: brianf@umd5.umd.edu's message of 23 May 90 14:29:51 GMT In article <6564@umd5.umd.edu> brianf@umd5.umd.edu (Brian Farmer) writes: >Many people been have complaining about how 3.0 protected mode won't >allow many old apps to run. This is giving a FALSE! impression and may scare some users into thinking that their old (windows ver 2.xx) applications will not run at all. When you try to execute a program that was designed for ver 2.xx, a message box pops up and warns you about a POSSIBLE incompatability that MAY result in errors or a loss of data (only in memory. Windows won't scrog your disk files). It tells you to re-start windows like this --> win /R The /R tells windows to start in real mode (i.e. 286 mode), which maintains compatability for older programs. The downside of the /R paramater is that in forcing 286 compatability, you are limited to the 640K barrier. In standard mode, that barrier is removed. David -- ------------------------------------------------------------------------------- David Sampson Harris Corporation dsampson@x102a.ess.harris.com Gov't Aerospace Systems Divison uunet!x102a!dsampson Melbourne, Florida -------------------------------------------------------------------------------