Newsgroups: comp.windows.ms
Path: utzoo!utgpu!watserv1!daemon
From: tom@mims-iris.waterloo.edu (Tom Haapanen)
Subject: Re: QEMM386/Windows config question
Message-ID: <1990Aug29.114402.7527@watserv1.waterloo.edu>
Sender: daemon@watserv1.waterloo.edu
Organization: University of Waterloo, WATMIMS Research Group
References: <18950003@hpfinote.HP.COM> <331@news.nd.edu> <1990Aug13.171459.13839@mccc.uucp> <9131@uhccux.uhcc.Hawaii.Edu>
Date: Wed, 29 Aug 90 11:44:02 GMT
Lines: 23

Eric Pilger <pilger@uhunix1.uhcc.Hawaii.Edu> writes in a nice, objective manner:
> The only thing you loose is Enhanced Mode (ie. Multitasking.) YOU DO
> NOT BREAK THE 640K BARRIER WITH ENHANCED MODE.  The problem is not in
> the thing the thing the runs the software.  The problem is in the
> software itself.  The majority of software written does not recognize
> the existence of more than 640K, hence the 640K barrier.  The ONLY
> thing that can break the 640K barrier is protected mode software.  A
> lot of this WON'T RUN under Windows 3.0 Enhanced Mode.

In fact, much of the software (soon to be a vast majority) that breaks the
640K barrier will ONLY run under Windows 3.0 (these are known as "Windows
applications").  Most of the rest will work with Windows, and only those
using the older VCPI extended memory interface will refuse to work with
Windows.

Get a clue, Eric.  You're bitching at Microsoft because Windows 3.0 doesn't
work well with QEMM/386 without understanding *WHY* Microsoft uses DPMI
instead of VCPI.  Windows is also primarily an operating environment for
Windows apps, *NOT* a multitasker for DOS apps -- and the Windows apps *CAN*
break the 640K barrier.

[ \tom haapanen --- university of waterloo --- tom@mims-iris.waterloo.edu ]
[ "i don't even know what street canada is on"               -- al capone ]
