SCOUG-HELP Mailing List Archives

>> Next Message >>

Date:	Fri, 8 Feb 2002 12:57:06 PST7
From:	Peter Skye <pskye@peterskye.com >
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.
=====================================================

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=00870000 StackLimit=0089C000 Ebp=0089BFD4 Eip=00092E5A
���������������������������������������������������������������������������
� List of currently accessed modules (DLLs) object addresses �
���������������������������������������������������������������������������
� Handle 00004799 NmeMod H:\MAINTENANCE\UNIMAINT\UNIMAINT.EXE �
� NmeEip INIMAINT �
� EIP EBP Address �
� 00092E5A 0089BFD4 0001:00082E5A |
���������������������������������������������������������������������������
� Handle 00000248 NmeMod G:\OS2\DLL\DOSCALL1.DLL �
� NmeEip DOSCALL1 �
� EIP EBP Address �
� 1BFBC088 0089BFF4 0004:0000C088 |
���������������������������������������������������������������������������

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=5000 DosErr=0 SysDosErr=0 SysOS2Err=0 SysErrno=0 HelpErr=0 PMErr=0/0 PMTest=1304/4 WPSErr=0 ErrRtn=90 SysErrRtn=287
Supplemental Error Text=24EA20/Routine=287 Access Violation in Thread Repair at Location 92E5A
habMain=660001 hwndFrame=80000138 hwndMain=8000025F hwndObject=0 hwndHelp=80000260 hwndHelpAssoc=80000138 hmqMain=17BDC870 pfnwpMLE=1FA2E06C FileType=1
Current Directory H:\Maintenance\UNIMAINT
Current File=244630/G:\OS2\OS2.INI
MainVisible=True hiniCurrent=FFFFFFFF AskDel=True AskChg=True fIniUpdate=No MLELength=54 hwndDataMLE=80000277 pfnwpMainFrame=0
Safe=No groupcount=0 hwndMainMenu=800001F1 DispSize=True DispCopy=True DispLoad=False DispFind=False hwndMainTitle=800001ED
Threads=1 OldPtr=17BFC138 WaitPtr=17BFC0EC CurPtr=17BFC138 OldMLEPtr=17BFC138 CurMLEPtr=17BFC138 Corporate=No
...(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

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

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.