said:
>I wrote a little .cmd which tells me if the OS2*.INI files have been
>updated. 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.
This is by design. The INI updates are done by a low priority thread. It
runs when needed or when some internal timeout expires.
>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.
Well, how could it use the standard interfaces since it is the standard
interfaces that caused the problem.
>Yes, fewer problems, but I still occasionally get a CheckINI hang (I got
>one last week and I ran UniMaint first).
This is not unexpected. Different code is going to fail different way.
If you force a process dump the next time checkini hangs, I might be able
to tell you something about the hang.
>My hangs always occur in what I'll call the "drive handles" section where
>each drive letter is displayed followed by whatever handles are removed.
That's a complex area. IIRC, these are linked data structures, so it's
easy to understand how the code might loop. It's too bad Henk did not
provide full source or some of this could be fixed.
>The drive letters seem to show up in a different sequence on each
>CheckINI run (I don't know why)
Because checkini rewrites the table.
>attempt and CheckINI found nothing to fix. Sure wish Henk had put in a
>/Debug switch (I sometimes use /w which shows every handle but it's not
>sufficient to figure out what is causing the hangs).
There's always the source code and a debugger. You have both available.
Steven
--
----------------------------------------------------------------------
"Steven Levine" MR2/ICE 2.47 #10183 Warp4/FP15/14.093c_W4
www.scoug.com irc.fyrelizard.com #scoug (Wed 7pm PST)
----------------------------------------------------------------------
=====================================================
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 [ 28 |
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.