SCOUG-HELP Mailing List Archives

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

Date:	Sat, 9 Feb 2002 17: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'm not sure. If I double-click on the UniMaint folder, the system
> freezes instantly (the folder never starts to open). I tried
> uninstalling UniMaint to "get rid of the folder" and that freezes the
> system too.

Peter,
You know, I failed to focus exactly on what you previously said, so I
might have jumped to a false conclusion. Now that I am focusing, let me
ask the question. When you say that you "cannot open the UniMaint
folder" do you truly mean the folder, the red one that is named
"UniTools" and which contains various UniMaint icon tools? Or, do you
mean you cannot run the UniMain application from the program object icon
that was created during the instalation of UniMaint? Which one?

If it is indeed the folder, I still think that problem is related (tied)
to the tremendous amount of corruption in your *.INI files (for example,
one or two folders on my desktop use to freeze on before I started
regularly cleaning the *.INI files).

If it's the folder, why don't you create a new program object for
UniMaint on your desktop (using a program object template from the
Template folder)? Then, you can run UniMaint from the newly created
program object and slowly clean up your *.INI files as previously
suggested.

If it is the UniMaint program object recreated during the install, then
you are going to have to use the commandline, at least for a while, to
begin cleaning the files. E-Mail Jim Read and ask how to do it.

Hopefully, your problem is indeed in openning the folder. If so, create
a new program object.
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.
> =====================================================
>
> > > The UniMaint folder freezes the entire system (and always has).
>
> > That fact in itself probably has to do with
> > all the corruption on your *.INI files.
>
> I'm not sure. If I double-click on the UniMaint folder, the system
> freezes instantly (the folder never starts to open). I tried
> uninstalling UniMaint to "get rid of the folder" and that freezes the
> system too.
>
> > Steven's suggestion of E-mailing Jim Read is also good.
>
> I did, and Jim got right back to me and said he was forwarding my log
> and dump files to Larry Martin. Larry then got right back to me and
> said he would take a look at the files later today. Both these guys
> gave me incredibly fast response -- I'm impressed.
>
> By the way, that's an impressive "dump file" that UniMaint generates.
> I'm going to ask Larry what tool he used to do that.
>
> > > I *have* to run UNIMAINT.EXE from a command line.
> >
> > 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.
>
> There shouldn't be any difference whether UniMaint is run from the
> command line or by clicking on its icon. The program itself is a
> Presentation Manager app and you get the GUI screen either way. I run
> it from the command line by changing to the UNIMAINT\ directory because
> I can't open the UNIMAINT folder -- this should be a transparent
> workaround. Sort of like running Netscape by changing to its directory
> and typing "netscape" at the command line.
>
> > 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
>
> Yes, that's a good idea. I'm waiting for Larry to get back to me in
> case there's something I've overlooked. If he needs more testing or if
> he doesn't have a fix I'll use your method.
>
> - 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.