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 ]

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


Date: Thu, 29 Jul 2004 05:31:53 PDT7
From: "Harry Motin" <hmotin@sbcglobal.net >
Reply-To: scoug-help@scoug.com
To: < "scoug-help@scoug.com" > 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.
=====================================================

On Wed, 28 Jul 2004 22:46:38 PDT7, Gary Granat wrote:

>IIRC, the recommended procedure is to make necessary repairs followed ASAP by a
>restart.

That's correct, a full system restart will also do the trick. Or, just as I use to do, wait until
the updates are written in to the OS2*.INI files.

> The reason for this is to ensure that your updates are written to the
>permanent INI files. I suspect that the reason that updates are written to the
>!!! files is because of a great likelihood of losing your updates if they are
>written directly to the INI files (i.e., the updates being overwritten from the
>!!! on the next restart).

OK! OS2 uses the OS2*!!! to temporarily hold all changes to the OS2.INI files. the OS2*.!!!
function like buffers. If your OS did not do that, but instead wrote to the OS2*.INI files,
these files would be under constant/continual write. They would quickly become
corrupted.

The OS2*.!!! files are supposed to disappear, when you close down the OS, unless you
have installed something like XWorkplace. The XWorkplace enhancement somehow
keeps the OS2*.!!! files after shutdown. At a minimum your system must ALWAYS turn off
the "read only" attribute on the OS2*.INI files during shutdown. If that does not happen,
then the system cannot re-create the OS2*.!!! files during bootup. Then, the system will
not have anything to temporarily hold the changes to your desktop and system.
Updates to the OS2*.INI will then NOT occur. You have the so-called "non-write"
OS2*.INI file situation.
HCM

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

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