Path: utzoo!attcan!uunet!samsung!munnari.oz.au!uhccux!todd
From: todd@uhccux.uhcc.Hawaii.Edu (Todd Ogasawara)
Newsgroups: comp.windows.ms
Subject: Re: QEMM Obsolete? was: Windows 3.0 and QEMM
Message-ID: <7937@uhccux.uhcc.Hawaii.Edu>
Date: 29 May 90 08:08:19 GMT
References: <443@latvax8.lat.oz> <1990May25.152712.18579@cbnewsl.att.com>
Reply-To: todd@uhccux.UUCP (Todd Ogasawara)
Organization: University of Hawaii
Lines: 25

From article <443@latvax8.lat.oz>, by CCMK@latvax8.lat.oz (Mark Kosten - Computer Centre, La Trobe Uni.):
> I installed v3.0 on my IBM model 70 with QEMM-simulated 4MB expanded
> memory and it worked fine during install and even showed the expected
> amount of expanded memory in the about... box.
> 
> On restarting it, with either win /2 or win /3, the program says
> something like 'Other protected mode programs working - abort'.

Umm.. Correct me if I am mistaken... But I never expected Windows 3.0 to
work with QEMM on a 386. Windows 3.0 is supposed to handle protected mode
memory. This means that it would collide with any software that also
attempts to directly manipulate protected mode memory (like QEMM does).
This is also the case for Windows 386 2.11 which tries to deal with
protected memory directly (though less effectively than Windows 3.0). I
haven't received my update yet, but I am expected that I will have to have
different CONFIG.SYS and AUTOEXEC.BAT files in order to deal with Windows
3.0 and non-Windows (i.e., plain DOS) software. My guess is a lot of us
will be rebooting a lot when we move between Window 3.0 and DOS
configurations... todd

-- 
Todd Ogasawara, U. of Hawaii
UUCP:		{uunet,ucbvax,dcdwest}!ucsd!nosc!uhccux!todd
ARPA:		uhccux!todd@nosc.MIL		BITNET: todd@uhccux
INTERNET:	todd@uhccux.UHCC.HAWAII.EDU