SCOUG Logo


Next Meeting: Sat, TBD
Meeting Directions


Be a Member
Join SCOUG

Navigation:


Help with Searching

20 Most Recent Documents
Search Archives
Index by date, title, author, category.


Features:

Mr. Know-It-All
Ink
Download!










SCOUG:

Home

Email Lists

SIGs (Internet, General Interest, Programming, Network, more..)

Online Chats

Business

Past Presentations

Credits

Submissions

Contact SCOUG

Copyright SCOUG



warp expowest
Pictures from Sept. 1999

The views expressed in articles on this site are those of their authors.

warptech
SCOUG was there!


Copyright 1998-2024, Southern California OS/2 User Group. ALL RIGHTS RESERVED.

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.

The Southern California OS/2 User Group
USA

SCOUG-HELP Mailing List Archives

Return to [ 22 | June | 2001 ]

>> Next Message >>


Date: Fri, 22 Jun 2001 00:25:06 PDT
From: "Steven Levine" <steve53@earthlink.net >
Reply-To: scoug-help@scoug.com
To: scoug-help@scoug.com
Subject: SCOUG-Help: The big slow down

=====================================================
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.
=====================================================

In <200106212142.AA961151198@oco.net>, on 06/21/01
at 09:42 PM, "mrakijas" said:

>Okay, this is definitely the problem. Line 17,
>the QSV_TOTPHYSMEM line says 16M. So now, this
>is the symptom - I must figure out the cause.

Think of it as an opportunity to hone your investigative skills.

>Memory is definitely good and works the same
>with two different DIMMs. It must be the BIOS
>upgrade or the peer fixpak (8414) and of course,

The BIOS upgrade is a likely candidate. Forget the Peer FP. Peer loads
long after OS/2 has decided how much memory exists.

>I'd guess the former. I'll work it, but I can't
>imagine why - I've never been able to limit the
>memory that OS/2 sees compared to what is

There are several ways to check how much memory exists. One was the
original way. The other is the new MS enforced standard. Warp4 used the
old way with the exception of some of the most recent kernels. At one
time most BIOS's had a switch to support the old way. Newer BIOS's tend
not to have the switch. Daniela Engert created a patch to make the Warp4
kernel work with the new way. Your choices are:

- find the switch in the BIOS if it exists
- use Daniela's patch (see Hobbes)
- use a kernel that supports the new way

Steven

--
----------------------------------------------------------------
"Steven Levine" MR2/ICE 2.28a #10183 Warp4/FP11
www.scoug.com irc.webbnet.org #scoug (Wed 7pm PST)
----------------------------------------------------------------

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

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".

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


>> Next Message >>

Return to [ 22 | June | 2001 ]



The Southern California OS/2 User Group
P.O. Box 26904
Santa Ana, CA 92799-6904, USA

Copyright 2001 the Southern California OS/2 User Group. ALL RIGHTS RESERVED.

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.