Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!cbmvax!brim
From: brim@cbmvax.commodore.com (Mike Brim - Product Assurance)
Newsgroups: comp.windows.ms
Subject: Re: qemm/windows crash
Keywords: qemm, page frame
Message-ID: <21272@cbmvax.commodore.com>
Date: 6 May 91 12:06:50 GMT
References: <19727@cs.utexas.edu>
Reply-To: brim@cbmvax.commodore.com (Mike Brim - Product Assurance)
Organization: Commodore, West Chester, PA
Lines: 22

In article <19727@cs.utexas.edu> colaluca@cs.utexas.edu (Mark Colaluca) writes
> I have encountered a problem with QEMM and Windows.  If I want to load my
> Stacker.com device driver (39K) into high memory, I have to use space in
> either D000-DFFF or E000-EFFF.  As some of you might know, the page frame
> for QEMM must take up 64K of contiguous high memory, usually at E000-EFFF.
> Windows, however, seems to crash when the page frame is placed here.  Adding
> X=E000-EFFF to my QEMM device line cures this problem, but then there is no
> room for the stacker device driver.  Does anyone know why Windows does not
> like an E000-EFFF page frame,....

 Qemm and Windows(386 mode) do work while Qemm uses E000H-EFFFH for page frame.
I suspect your problem lies with another program other then Qemm that may be
conflicting with Qemm at that location.  Use MFT to search through your memory.
    
-- 
********************************************************************************
Disclaimer: I don't speak for my company or myself.

Mike Brim			     |	Commodore Electronics Limited
PC Analyst - System Evaluation Group | 	West Chester, PA 19380
Product Assurance		     |	InterNet: brim@cbmvax.commodore.com
********************************************************************************