SCOUG-HELP Mailing List Archives

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

Date:	Sun, 13 Apr 2003 21:01:01 PDT
From:	Peter Skye <pskye@peterskye.com >
Reply-To:	scoug-help@scoug.com
To:	scoug-help@scoug.com
Subject:	SCOUG-Help: Manual repair of CheckINI errors ?

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

Steven Levine wrote:
>
> >I do not have Opera installed.
>
> Well, you did or someone else hase been hacking
> into your systems.

I did install it. It was awful. I deleted it.

> >A PMSEEK search on "OPERA52_" shows
> >these entries are in the OS2.INI file.
>
> Makes sense. That's where checkini found them
> before you did.

How would a mere mortal, such as I, know that? Besides, PMSEEK gives
me a chance to go do something else since it ties up the system pretty
good.

> >Looking in OS2.INI, the PM_Abstract:Objects and
> >PM_Abstract:FldrContent keys do not have any
> >5-character keys. Thus, the 5-character Object
> >i.d.'s above apparently aren't key values.
>
> Sure they are. Do you really think Henk's code could
> be this wrong given the number of folks that rely on it?

Wrong about what? I don't yet know what they are. Henk's checkini.txt
has neither a description nor a reference where somebody could find out.

> FWIW, the numbers are object handles, not object ids.

Those of us who are mere mortals don't know that. :))

> The lower four digits (in hex) are the 16-bit key.
> The 5th digit is a code that indicates the object type
> (1=transient, 2=abstract, 3=persistent). Also, keep in
> mind the handles may be stored in hex or decimal and
> may or may not include the object type code. No one
> ever said the WPS implementation was all that clean.

Thanks. I've added this info to my CheckINI startup .cmd so I'll see it
on each run.

> >How do I manually repair the above errors?
>
> checkini /c
> resetwps

That doesn't fix them. I've run CheckINI a number of times over the
past few months and the errors are still there. (UniMaint Repair
doesn't show them.) I can fix these errors by manually deleting these
four Object Handles, yes?

Besides, as of last week I can't run CheckINI any more. "checkini /c"
hangs the entire system. I had this problem before after deleting a
copy (but not the original) of the Templates\ folder. I don't know how
I finally got CheckINI to work -- I think a UniMaint Repair finally
fixed it, but that doesn't have any effect right now. Until I installed
UniMaint and ran a Repair, for about a year I couldn't run checkini.
When I tested my system file zipper-upper a week ago by restoring the
files (including the Templates\ subdirectory) to my test partition and
then deleting the unzipped files, I apparently did something to OS2.INI
and checkini now gives me "the big hang" (the clock stops) while
processing my boot drive.

- Peter

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

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 [ 13 | April | 2003 ]

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.