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 [ 20 | July | 2002 ]

>> Next Message >>


Date: Sat, 20 Jul 2002 00:02:55 PST7
From: Peter Skye <pskye@peterskye.com >
Reply-To: scoug-help@scoug.com
To: scoug-help@scoug.com
Subject: SCOUG-Help: boot hang... still

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

Steven Levine wrote:
>
> For performance reasons, the WPS
> caches a lot of data in memory.

Yes. And as far as I know both of the OS2*.INI files are included in
this "data" and are kept in memory and occasionally written to disk.

> I think [both UniMaint and CheckIni] use [the appropriate
> OS/2 routines] along with the documented WPS interfaces.
> However, the problem is that neither can notify the WPS
> of the changes thay have made, in all cases.

This makes no sense. If a program uses WPS calls to modify OS2.INI then
the WPS gets these calls and updates the data. If a program uses a WPS
call then "making the change" and "notifying WPS of the change" are both
done with a single call, the same call. Yes?

> The regressions occur when the WPS has something cached
> and unimaint/checkini fixes the same item in the .INI and
> then the WPS decides to flush its cache to the .INI's.

It shouldn't make any difference if the WPS first has to shove the
update into a memory buffer and from there eventually caches it to
OS2.!!! which gets written to OS2.INI on shutdown. And if a program
makes a call to the WPS with an update while the WPS is moving the
memory buffer to the disk cache then the WPS shouldn't "lose" the
update, it should just put this new update into the memory cache for the
next buffer flush to disk.

Are you saying that somewhere along this linear data flow the WPS is
internally broken and "loses" updates?

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

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


>> Next Message >>

Return to [ 20 | July | 2002 ]



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.