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 [ 02 | April | 2005 ]

<< Previous Message << >> Next Message >>


Date: Sat, 2 Apr 2005 12:26:06 PST8
From: Peter Skye <pskye@peterskye.com >
Reply-To: scoug-help@scoug.com
To: scoug-help@scoug.com
Subject: SCOUG-Help: do your INI maintenance

Content Type: text/plain

The following post on today's Weasel mail list was written by developer
Peter Moylan. Separately I've heard that the INI cache space is only 4
MB or 5 MB, and one other developer (Jim Read at UniMaint) has also told
me of this problem. So, if you've been lax in cleaning up your INI
files here's an incentive . . .
_____

>From Weasel author Peter Moylan on that list:

One thing that occurs to me - and I've often had trouble
with this - is a shortage of shared memory, leading to
WEASEL.INI not being read correctly. Unfortunately INI
files are cached inside a fixed memory area which is
dangerously small, and there's no way to tell the system
to use a different memory area because this is OS code
that's doing it. (Such problems are becoming so common
that I'm starting to wonder whether I should continue to
use the OS/2 INI mechanism - but I'm reluctant to drop it
because it's such an efficient way of handling the data,
far better than the text configuration files used in other
operating systems.) The way to check this would be to see
whether the problem goes away after a run of CLEANINI or
CHECKINI.
_____

I run CleanIni every day and my system seems more stable. UniMaint
Repair and CheckIni seldom find anything fixable so I only run them
twice a month. I also got rid of Theseus which turned out to have
something to do with half my bootups ending in traps -- not a single
trap since I removed it.

What I'd really like to have is a tiny program that monitors the small
shared memory area so I can see how much is in use. I would put its
display next to my two memory monitors, all my POP3 monitors, my pulse
cpu monitor, my IP Speed monitor, my three hard drive monitors, my
SmartBar process monitor, my PSPM process tree monitor, . . . geez!,
you'd think I was paranoid or something.

- 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
"postmaster@scoug.com".

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


<< Previous Message << >> Next Message >>

Return to [ 02 | April | 2005 ]



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.