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 [ 29 | July | 2004 ]

>> Next Message >>


Date: Thu, 29 Jul 2004 03:46:56 PDT7
From: Peter Skye <pskye@peterskye.com >
Reply-To: scoug-help@scoug.com
To: scoug-help@scoug.com
Subject: SCOUG-Help: UniMaint help needed

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

Gary Granat wrote:
>
> Peter,
> IIRC, the recommended procedure is to make necessary repairs
> followed ASAP by a restart. The reason for this is to ensure
> that your updates are written to the permanent INI files.

Yeah, but for some reason that doesn't work. I did a big-time test of
this a few weeks ago before contacting Jim Reed, and UniMaint wouldn't
save the changes. That's when Jim told me about the buffer problem.

The weirdest part is that if I run UniMaint Repair and then exit the
program and immediately run it again, everything looks fine. But if I
wait a while and run it, or if I reboot, the "fixed" stuff has returned.

There are three places where the OS2*.INI info is kept: 1) in memory,
2) in OS2*.!!!, 3) in OS2*.INI. Changes are made to the memory info,
which is occasionally written to OS2*.!!!, which is occasionally renamed
as OS2*.INI. I think. Where the failure occurs is unknown.

Since an immediate rerun of UniMaint shows that the fixes have "stuck",
the info in memory apparently has been fixed. For some reason the
changes aren't making their way to OS2*.INI.

- 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 [ 29 | July | 2004 ]



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.