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:17:55 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:03:21 PDT7, Peter Skye wrote:

>I wrote a little .cmd which tells me if the OS2*.INI files have been
>updated.

But the point is here, that you CANNOT use that *.cmd file. If you use it and one or both
*.INI files have not been updated, then your repairs to that file(s) will not take affect. You
have to simply WAIT WITHOUT DOING ANYTHING UNTIL THE OS WRITES THE
REPAIRS TO THE OS*.INI FILES

>Making sure they are both updated is a little tricky because
>they aren't always written at the same time -- sometimes OS2.INI is
>written but OS2SYS.INI requires waiting another minute or so.

>I don't know why UniMaint's updates aren't applied to the OS2*.INI files in all
>situations. Maybe the program isn't using the expected system calls to
>modify the files.

Because, with Warp 4 you've got to wait for the write update, before you do anything!
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.