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

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


Date: Fri, 19 Jul 2002 23:07:09 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:
>
> When you reset the Desktop, you effectively throw
> away the changes that the WPS has been caching in
> OS2.!!!. What the reset is supposed to accomplish
> is to prevent these cached changes from reversing
> the changes made by Unimaint or checkini.
>
> ... The longer you take to run checkini, the
> more chance that the WPS will decide to flush
> its internal buffers and overwrite a change.

Hmm.

-- 1. Okay, the OS2*.INI files are very simple key|subkey|datastring
databases.

-- 2. There appear to be two ways to modify these files:

------ a. Call the appropriate OS/2 routine with the key and subkey
values and add/delete/change the datastring, or
------ b. Read the file into memory, modify it using your own code, and
write it back out. And hope that the WPS hasn't done anything to it in
the interim.

Am I right so far?

Now then, my impression is that UniMaint uses 2a above and CheckIni uses
2b above. Is this correct? (I don't know which method CleanIni uses --
I don't use it any more because it kept zapping my INI files.)

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

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


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

Return to [ 19 | 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.