SCOUG-HELP Mailing List Archives

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

Date:	Fri, 8 Feb 2002 19:33:47 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,

I sounds like you've got a lot of junk to clean up, and that's the real
problem. You let it accumulate. I believe that you should do a several
of things:

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. Instead:

2. Back up your OS2.INI and OS2SYS.INI files, first, before doing
anything (use your most recent, good set of *.INI files).

3. Run UniMaint from the icon, not the commandline. Select the "Repair"
icon in the Unimaint window, when it opens up.

4. Select the opinion "Report only" (that's usually the default) in the
UniMaint repair window.

5. If you get a big report of errors, select only a few to clean at any
one time. Highlight those few errors, select the "Execute" option and
get rid of those few.

6. After cleaning/fixing those few errors, reset the desktop to make
sure you have not done anything bad to the *.INI files.

7. Redo the above steps, 1 through 6, working your way slowly to a
clean set of *.INI files.

8. Once you get a fully clean set, using UniMaint, then go back do the
same thing, this time using checkini, then finally cleanini.

It will take a while, but you've got a ton of accumulated errors in
those files (looks like)! Hope that helps!

HCM

_________________________________________________________________________=
______________________

Peter Skye wrote:
> =

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

> This was the first morning in three weeks that I haven't had
> hourly disasters, and believe me the quietude was unnerving.
> =

> So I decided to run Unimaint and clean my .ini files.
> (This has never worked, but I figured "what the heck,
> it's such a nice peaceful morning.")
> =

> Opened a command line window and switched to the Unimaint
> subdirectory, then ran
> =

> UNIMAINT -> Recover -> Repair INI Files -> Execute
> =

> Blazammo! It blew up.
> =

> Here's UNIEXCEP.LOG:
> =

> [H:\Maintenance\UNIMAINT]type UNIEXCEP.LOG
> 02/08/02 11:51:28 00000 UniMaint - Version 5.10.23
> Passed Values Stack=3D00870000 StackLimit=3D0089C000 Ebp=3D0089BFD4 E=
ip=3D00092E5A
> =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0
> =A0 List of currently accessed modules (DLLs) object addresses =
=A0
> =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0
> =A0 Handle 00004799 NmeMod H:\MAINTENANCE\UNIMAINT\UNIMAINT.EXE =
=A0
> =A0 NmeEip INIMAINT =
=A0
> =A0 EIP EBP Address =
=A0
> =A0 00092E5A 0089BFD4 0001:00082E5A =
|
> =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0
> =A0 Handle 00000248 NmeMod G:\OS2\DLL\DOSCALL1.DLL =
=A0
> =A0 NmeEip DOSCALL1 =
=A0
> =A0 EIP EBP Address =
=A0
> =A0 1BFBC088 0089BFF4 0004:0000C088 =
|
> =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0
> =

> Here's the first few lines of UNIMAINT.DMP:
> =

> [H:\Maintenance\UNIMAINT]type UNIMAINT.DMP
> 02/08/02 11:51:28 00001 UniMaint - Version 5.10.23
> Access Violation in Thread Repair at Location 92E5A
> Dump Information for UniMaint V5.10.23 OS/2 V2.40 Date/Time 2/8/2002 =
11:51:28
> Logerr=3D5000 DosErr=3D0 SysDosErr=3D0 SysOS2Err=3D0 SysErrno=3D0 Hel=
pErr=3D0 PMErr=3D0/0 PMTest=3D1304/4 WPSErr=3D0 ErrRtn=3D90 SysErrRtn=3D2=
87
> Supplemental Error Text=3D24EA20/Routine=3D287 Access Violation in Th=
read Repair at Location 92E5A
> habMain=3D660001 hwndFrame=3D80000138 hwndMain=3D8000025F hwndObject=3D=
0 hwndHelp=3D80000260 hwndHelpAssoc=3D80000138 hmqMain=3D17BDC870 pfnwpML=
E=3D1FA2E06C FileType=3D1
> Current Directory H:\Maintenance\UNIMAINT
> Current File=3D244630/G:\OS2\OS2.INI
> MainVisible=3DTrue hiniCurrent=3DFFFFFFFF AskDel=3DTrue AskChg=3DTrue=
fIniUpdate=3DNo MLELength=3D54 hwndDataMLE=3D80000277 pfnwpMainFrame=3D0=

> Safe=3DNo groupcount=3D0 hwndMainMenu=3D800001F1 DispSize=3DTrue Disp=
Copy=3DTrue DispLoad=3DFalse DispFind=3DFalse hwndMainTitle=3D800001ED
> Threads=3D1 OldPtr=3D17BFC138 WaitPtr=3D17BFC0EC CurPtr=3D17BFC138 Ol=
dMLEPtr=3D17BFC138 CurMLEPtr=3D17BFC138 Corporate=3DNo
> ...(lots more, the file is almost 180K)
> =

> I'm running Warp 4 FP 10 plus the last Unimaint update (5.10.23).
> =

> Any ideas on what caused this?
> =

> - Peter
> =

> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D
> =

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

> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D

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

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 [ 08 | 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.