[comp.windows.ms.programmer] Get more than 570KB in a DOS window under WIN 3.0?

ndeng@EULER.BERKELEY.EDU (12/21/90)

Thanks to all who responded my question of getting 570K+ memory for a WIN 3.0
DOS window. All the responses I got seem to give one solution: Get QEMM 5.11
memory manager, though one person mentioned there is a possibility that the
upcoming DOS 5.0 will include most of the features of QEMM.

It appears to me that I really need to invest another $80 to get this useful
piece of program. Solutations for QEMM. And I feel sorry that I cannot solve 
this problem within Windows. I hope the Windows gurus in Microsoft (Anyone
else can claim to be more proficient than them? :-) will come with a solution
and include it in the next release of this really useful GUI environment.

Mike
ndeng@euler.berkeley.edu

wayne@teemc.UUCP (Michael R. Wayne) (12/22/90)

In article <9012210822.AA09659@euler.Berkeley.EDU> ndeng@EULER.BERKELEY.EDU writes:
>Thanks to all who responded my question of getting 570K+ memory for a WIN 3.0
>DOS window. All the responses I got seem to give one solution: Get QEMM 5.11
>memory manager, though one person mentioned there is a possibility that the
>upcoming DOS 5.0 will include most of the features of QEMM.

	Just a warning here.  Watch out if you have a SCSI drive and you
install QEMM.  It walked all over my 660 MB drive (Adaptec 1542A controller).
After waiting on hold for >30 min, Quarterdeck tech support told me to try
EXACTLY the sequence that trashed my disk in the first place (it's clearly
documented in the manual).  After I explained that this was not an acceptable
workaround (once was more than enough, thank you), they told me that I should
get a driver from Adaptec.  I'm undecided whether to track down this driver or
just toss QEMM into the circular file.

/\/\ \/\/
-- 
Michael R. Wayne      ---     TMC & Associates      --- wayne@teemc.tmc.mi.org
         Operator of the only 240 Horsepower UNIX machine in Michigan 

poffen@sj.ate.slb.com (Russ Poffenberger) (12/27/90)

In article <196033@teemc.UUCP> wayne@teemc.UUCP (Michael R. Wayne) writes:
>In article <9012210822.AA09659@euler.Berkeley.EDU> ndeng@EULER.BERKELEY.EDU writes:
>>Thanks to all who responded my question of getting 570K+ memory for a WIN 3.0
>>DOS window. All the responses I got seem to give one solution: Get QEMM 5.11
>>memory manager, though one person mentioned there is a possibility that the
>>upcoming DOS 5.0 will include most of the features of QEMM.
>
>	Just a warning here.  Watch out if you have a SCSI drive and you
>install QEMM.  It walked all over my 660 MB drive (Adaptec 1542A controller).
>After waiting on hold for >30 min, Quarterdeck tech support told me to try
>EXACTLY the sequence that trashed my disk in the first place (it's clearly
>documented in the manual).  After I explained that this was not an acceptable
>workaround (once was more than enough, thank you), they told me that I should
>get a driver from Adaptec.  I'm undecided whether to track down this driver or
>just toss QEMM into the circular file.
>


I have no problem with Win 3, QEMM 5.11 and my CDC Wren IV (327Mb) on an
Adaptec AHA1542B controller.

Is it related to a DOS version? I am using 3.30, with many partitions (D-N).

I have a permanent Swap file on N:.


Russ Poffenberger               DOMAIN: poffen@sj.ate.slb.com
Schlumberger Technologies       UUCP:   {uunet,decwrl,amdahl}!sjsca4!poffen
1601 Technology Drive		CIS:	72401,276
San Jose, Ca. 95110             (408)437-5254

zack@bosslog.UUCP (Zacharias Beckman) (01/03/91)

In article <196033@teemc.UUCP> wayne@teemc.UUCP (Michael R. Wayne) writes:
>documented in the manual).  After I explained that this was not an acceptable
>workaround (once was more than enough, thank you), they told me that I should
>get a driver from Adaptec.  I'm undecided whether to track down this driver or
>just toss QEMM into the circular file.

I've been using QEMM 5.1 with my 170MB and 330MB SCSI's for quite a while now.
I'm also using the Adaptek 1542A controllers.

While you do have the option of using the driver, you can also simply lock out
the region of memory used by the Adaptek controller.  If you can't locate what
this region is, write back (email).  I'll have to take a look next time I'm at
home.  Works just as well as having the driver, as far as I can tell...
-- 
Zacharias J. Beckman  |  To be "matter of fact" about the world is to
Lower Code Dweller    |  blunder into fantasy -- and dull fantasy at that,
Boss Logic Inc.       |  as the real world is strange and wonderful.
zack@bosslogic.com    |  --- Lazarus Long, by R. A. Heinlen