SCOUG-HELP Mailing List Archives

>> Next Message >>

Date:	Sat, 23 Jun 2001 08:00:52 PDT
From:	Harry Chris Motin <hmotin@attglobal.net >
Reply-To:	scoug-help@scoug.com
To:	scoug-help@scoug.com
Subject:	SCOUG-Help: Re: The big slow down

Content Type: text/plain

=====================================================
If you are responding to someone asking for help who
may not be a member of this list, be sure to use the
REPLY TO ALL feature of your email program.
=====================================================

I guess I am going to add my 2 cents to all of this. Until yesterday I
was using the OS/2 > 64 MB setting on my motherboard. I worked OK. I
have Warp 4 and FixPak 15. I have an AZZA motherboard with an Award BIOS
(09/2000 and then updated to 02/2001).

Yesterday (after reading "The big slow down" issues and responses) I
switched my BIOS to the non-OS/2 setting and booted up. I did this as a
test in case I ever change the motherboard and BIOS to one that does not
support the OS/2 > 64MB setting. So far so good. I've booted
successfully for almost 2 days now. My System Information application
reports the correct amount of RAM on my system. Everything seems to be
running fine just as before.

I guess the bottom line is that the OS/2 > 64MB setting will work
successfully depending on the motherboard and BIOS that you have.
Alternately, if you use an updated kernel that uses the MS standard for
> 64MB memory management, that works too.

I hope this helps.

H. C. Motin
________________________________________________________________________

Steve Carter wrote:
>
> =====================================================
> If you are responding to someone asking for help who
> may not be a member of this list, be sure to use the
> REPLY TO ALL feature of your email program.
> =====================================================
>
> Daniela's PATCHLDR is probably what you need.
>
> Daniela's PATCHLDR made it possible for my machine (W4, FP12)
> to see ALL the memory installed. Previously, using
> Theseus, it reported either 16MB or 64MB, depending
> on how the setting "OS Select for DRAM>64MB" in the
> AWARD BIOS (dated 4/2000) was set. Sadly, the OS/2
> setting was generally useless with Warp 4 and, iirc,
> was actually WORSE than the "non OS/2" setting.
>
> I think I recall being told that the OS/2 setting was
> intended for really old versions of OS/2 (pre-v2?).
> Award's tech support was clueless, although they did
> eventually respond. But by that time I had it working,
> with a little help from my friends.
>
> You will have to re-run her patch EVERY time you upgrade
> certain core parts of OS/2 (kernel, etc.). It's in
> the documentation, which is interesting reading.
>
> +++++++++++
> On 6/22/01, Peter Skye wrote, in part:
> >
> >Steven Levine wrote:
> >> Daniela Engert created a patch to make the
> >> Warp4 kernel work with the new [Microsoft] way.
> >
> >My notes say it's on Hobbes as PATCHLDR and that it fixes the OS/2 >64MB
> >memory detection defect in some late-1999 BIOS's which use
> >Int 15 Fn E820 instead of Int 15 Fn E801 to report memory size.
> >Definitely worth a try. >- Peter
>
>
> -+-+-+-+-+-+-+-+-+-+-+-+-+-+-
>
>
> =====================================================
>
> To unsubscribe from this list, send an email message
> to "steward@scoug.com". In the body of the message,
> put the command "unsubscribe scoug-help".
>
> For problems, contact the list owner at
> "rollin@scoug.com".
>
> =====================================================

=====================================================

To unsubscribe from this list, send an email message
to "steward@scoug.com". In the body of the message,
put the command "unsubscribe scoug-help".

For problems, contact the list owner at
"rollin@scoug.com".

=====================================================

Return to [ 23 | June | 2001 ]

SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group. OS/2, Workplace Shell, and IBM are registered trademarks of International Business Machines Corporation. All other trademarks remain the property of their respective owners.