wrote:
> You might try cleaning up your OS2.INI and
> OS2SYS.INI files, using a combination of:
>
> UniMaint (http://www.filestar.com/)
> CheckIni (http://hobbes.nmsu.edu/)
> CleanIni (http://www.ca-arnold.de/e/index.html)
>
> I've found that whenever my system starts acting up,
> cleaning the *.INI files usually fixes
> things. You need all three (3) maintenance tools,
> above, because no one tool does a
> complete job with the *.INI files.
> HCM
Hi Harry,
At one time there was a suggested and well-tested
procedure, regarding _which_ of these should be used
in _what_ order, and with exact syntax
recommendations. (UNIMAINT, though, is operated just
fine from its GUI, in my experience.) Perhaps you
were the one responsible for this, and did a SCOUG
newsletter piece on this ? For sure, it was discussed
on the Help List. I could just do a search, but if
you still have this readily to hand, perhaps you could
drop a link or two in here, or summarize it -- even
with a quick cut & paste ? If so, I'll do what I
should have done originally, and save it as a
monograph in my reference section.
Jordan
=====================================================
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
"postmaster@scoug.com".
=====================================================
<< Previous Message <<
>> Next Message >>
Return to [ 10 |
September |
2007 ]
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.
