SCOUG-HELP Mailing List Archives

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

Date:	Wed, 28 Jul 2004 18:42:20 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.
=====================================================

Hi Peter,

Let me see, if I can help with some of these problems:

>I now use UniMaint's "Repair" first, which seems to help. I have
>trouble with all three of the above, but in fairness they have a lot of
>trouble with my OS2*.INI files due to all the "fiddling" I do.
>
>-- UniMaint has a habit of making repairs and saying it has deleted
>stuff but the stuff shows back up a few minutes later. Really weird.
>(Jim Reeves says I might be hitting some kind of maximum buffer size on
>the OS2*.INI files).

First, hope you are using version 5.10.23 or later (I think Jim made a limited distribution
of a version after 5.10.23). On my previous OS/2 machine I had to use the following
technique to retain cleaned OS2*.INI after UniMaint worked:

1. Clean them, using UniMaint ("Report Only", then "Do Repairs")
2. Wait a few minutes after UniMaint completed the repairs (DO
ABSOLUTELY NOTHING)
3. Wait until OS/2 writes the repaired information to the OS2*.INI files from
the OS2*.!!! (you actually made the repairs to the opened OS2*.!!! files and not the
OS2*.INI files).
4. Reset the WPS
5. Run Checkini
6. Run Cleanini
7. Save that generation of OS2.INI, OS2SYS.INI and CONFIG.SYS files

If I did not wait for OS/2 to write to the OS2*.INI files (started doing work on the computer),
the UniMain cleaning would not take affect. Instead of waiting, I could reboot my system.
That would work, too.

>-- CheckINI simply hangs every so often when I run it; I've never
>figured out why but I can usually get it to complete by doing a Ctrl-C
>part way through while it's running (so the files are "partially" fixed)
>and then running it again (if that doesn't work I simply skip it and go
>to CleanINI).

I'm betting that after you get the UniMaint repairs to stick, you will have a lot less
problems with Checkini. I use the following parameters with Checkini:

/C /S /Y:2 /T

Write the corrections to the ini-files with confirmations for every change

Run 'silent' and only write to the errors to the logfile (program runs faster)

Auto answer ...., with a 'YES' and also no confirmation for any individual tests

Enable the disk scan function (do not use, if more than 1 OS/2 version installed)

>-- CleanINI used to totally zap my OS2*.INI files but I might have been
>using one of the /Del* parameters when I first started using it (I don't
>use any of the /Del* parameters now and it seems to work okay). Do you
>use any of the /Del* parameters?
>
>/DelFldPos enable delete of PM_Workplace:FolderPos
>/DelFldCont enable delete of PM_Abstract:FldrContent
>/DelMisc enable delete of PMWP_ASSOC_TYPE, PMWP_ASSOC_FILTER,
> PMWP_ASSOC_CHECKSUM and PM_Workplace:Startup
>/DelAll parameters /DelFldPos, /DelFldCont and /DelMisc

I run Cleanini with the following parameters:

/C /R /D:A /M /RFD

Make a backup of OS2.INI. Then, write the required corrections to OS2.INI

Restart the WorkPlace Shell (WPS) after making corrections to OS2.INI

Delete all (equivalent to the parameters: '/D:FP /D:FC /D:MA /LOGDEL

Scan multiple times so that all unnecessary handles can be deleted

Delete handles of all remote files

Only show and log those handles that are deleted

I wrote two sets of REXX scripts (one for Checkini and one for Cleanini) to make the user
interface a little better to these two programs. Search for them on Hobbes, using
"Checkini" and "Cleanini" as search words.
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".

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

Return to [ 28 | July | 2004 ]

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.