SCOUG-HELP Mailing List Archives

>> Next Message >>

Date:	Sat, 9 Feb 2002 06:32:42 PST7
From:	Harry Chris Motin <hmotin@attglobal.net >
Reply-To:	scoug-help@scoug.com
To:	scoug-help@scoug.com
Subject:	SCOUG-Help: Access violation with Unimaint

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

Peter Skye wrote:

> I can't do that. The UniMaint folder freezes the entire system (and
> always has). I *have* to run UNIMAINT.EXE from a command line.

That fact in itself probably has to do with all the corruption on your
*.INI files. And with that said, trying to fix them by running UniMaint
at the commandline with the "Execute" option is sure to fail (corrupt
them to such a degree that they become unusable).

I'm not experienced using UniMaint from the commandline. Can you run it
with a "Report Only" option? Can you run it with selective fixes of your
*.INI files, using perhaps wildcards in your selection (for example fix
all references to files in a particular folder)?

If you can, I would do that. That is, you could (basically) use process
I outlined before to slowly fix your *.INI files (save a copy of the 2
OS2*.INI files; run UniMaint from the commandline and selectively fix
portions of the files; reset the desktop (or reboot); save the resulting
*.INI files, if everything is OK; then repeat the above). Somewhere
along the line in this process you will get to a set of *.INI files that
will allow you to open and use UniMaint from the Workplace Shell.

Steven's suggestion of E-mailing Jim Read is also good.
HCM
_______________________________________________________________________________________________

Peter Skye wrote:
>
> =====================================================
> 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.
> =====================================================
>
> Harry Chris Motin wrote:
> >
> > 1. Do not run UniMaint from the commandline
> > a tell it to execute an *.INI cleanup. That's especially
> > hazzardous, when you've got a lot to clean.
>
> Hi Harry,
>
> I can't do that. The UniMaint folder freezes the entire system (and
> always has). I *have* to run UNIMAINT.EXE from a command line.
>
> - 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".
>
> =====================================================

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

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 [ 09 | February | 2002 ]

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.