Article View: aus.computers.os2
Article #6916Re: Examining RAM Allocation
From: Tony Coates
Date: Fri, 01 Jul 1994 09:04
Date: Fri, 01 Jul 1994 09:04
36 lines
2873 bytes
2873 bytes
In article <Cs7vIF.Lqz@Cadence.COM> daled@cds9172.Cadence.COM (Dale DePriest) writes:
In article <2uqk01$eab@goanna.cs.rmit.oz.au>, s932562@yallara.cs.rmit.OZ.AU (Adam Frey) writes:
|> gcw@cougar.multiline.com.au (Gavin White) writes:
|>
|> >Try a program called 21memu.zip (or 20memu.zip for os/2 2.0) from the
|> >IBM/ews (employee written software) section on cdrom.com (or the Hobbes CD)
|> >That gives a pretty good rundown of memory usage. Requires a device
|> >driver to be installed before running, so installation requires reboot.
|>
|> Tried that. Couldn't get it to work. Even after installing the device
|> driver. I suspect because it says something about only be applicable
|> for some cdrom pre release version of 2.1
The way that this is delivered requires that you get a modified driver
that is in a separate zip file. There are/were 2.0, 2.1, 2.11 drivers
available. Find the right driver and you will be ok.
There is some confusion over using os20memu, due to the fact that when
OS/2 2.1 first came out, a program called os21memu was released.
However, the *current* program, for both OS/2 2.0 and 2.1, is
os20memu, which come in 20memu.zip. Do *not* use 21memu.zip. I use
os20memu under OS/2 2.1, and it works perfectly well (I have no
experience with 2.11 though).
Cheers,
Tony.
--
_____________________________________________________________________________
A.B.Coates, Dept. of Physics,
The University of Queensland QLD 4072 Australia.
Email: coates@physics.uq.oz.au
Phone: (07/+617) 365-3424 Fax: (07/+617) 365-1242
Disclaimer: The University is ignorant of my
opinions, let alone guilty ...
_____________________________________________________________________________
Technical Details
Message-ID:
<COATES.94Jul1090424@kelvin.physics.uq.oz.au>Path:
arc1-ca.pugleaf.net!bga.com!news.sprintlink.net!hookup!swrinde!gatech!europa.eng.gtefsd.com!newsxfer.itd.umich.edu!isclient.merit.edu!msuinfo!harbinger.cc.monash.edu.au!bunyip.cc.uq.oz.au!dingo.cc.uq.oz.au!coatesReferences:
<2uit1i$34b@goanna.cs.rmit.oz.au> <2umqvo$188@cougar.multiline.com.au> <2uqk01$eab@goanna.cs.rmit.oz.au> <Cs7vIF.Lqz@Cadence.COM>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 1044c2,cb78351743d02da0 X-Google-Attributes: gid1044c2,public X-Google-Thread: 10a752,cb78351743d02da0 X-Google-Attributes: gid10a752,public X-Google-ArrivalTime: 1994-06-30 16:16:58 PST Path: arc1-ca.pugleaf.net!bga.com!news.sprintlink.net!hookup!swrinde!gatech!europa.eng.gtefsd.com!newsxfer.itd.umich.edu!isclient.merit.edu!msuinfo!harbinger.cc.monash.edu.au!bunyip.cc.uq.oz.au!dingo.cc.uq.oz.au!coates From: coates@kelvin.physics.uq.oz.au (Tony Coates) Newsgroups: aus.computers.os2,comp.os.os2.misc Subject: Re: Examining RAM Allocation Date: 1 Jul 94 09:04:24 Organization: Department of Physics, The University of Queensland Lines: 36 Message-ID: <COATES.94Jul1090424@kelvin.physics.uq.oz.au> References: <2uit1i$34b@goanna.cs.rmit.oz.au> <2umqvo$188@cougar.multiline.com.au> <2uqk01$eab@goanna.cs.rmit.oz.au> <Cs7vIF.Lqz@Cadence.COM> Reply-To: coates@physics.uq.oz.au NNTP-Posting-Host: kelvin.physics.uq.oz.au In-reply-to: daled@cds9172.Cadence.COM's message of Thu, 30 Jun 1994 15:39:51 GMT