-----Original Message-----
From: G. Roderick Singleton [mailto:[EMAIL PROTECTED]
Sent: Friday, February 18, 2005 7:33 AM
To: [email protected]
Cc: Gyaltsabje Buddhist Centre
Subject: Re: [users] error message after registry fix
On Tue, 2005-02-15 at 01:49 +0000, Gyaltsabje Buddhist Centre wrote:
> Our charity has been a grateful user of the OpenOffice suite for over
> a
> year now. However, in order to tidy up the inner workings of our
> computer, we recently performed a couple of registry tasks that we
fear
> may have interfered with OpenOffice. In MS-DOS mode, we executed
> "scanreg/fix" and "scanreg/opt", unfortunately without backing up the
> registry. Since then, whenever we've booted up or tried to open
> OpenOffice, it has failed to start, giving this error message:
>
> SOFFICE caused an exception e06d7363H in module MSVCRT.DLL at
> 0167:7800a6ff.
> Registers:
> EAX=0093f8c0 CS=0167 EIP=7800a6ff EFLGS=00000206
> EBX=00000000 SS=016f ESP=0093f8a4 EBP=0093f8cc
> ECX=00000000 DS=016f ESI=78031e00 FS=40c7
> EDX=0093f924 ES=016f EDI=0093f8cc GS=0000
> Bytes at CS:EIP:
> 5f 5e c9 c2 08 00 55 8b ec 51 53 56 57 8b 45 0c
> Stack dump:
> 00a7be04 00a86310 e06d7363 00000001 00000000 00000000 00000003
> 19930520 0093f924 006e3288 0093f95c 006b3d2c 0093f924 006e3288
> 00a7be04 00a9d3d0
>
> We've tried:
> 1) Scandisk
> 2) repairing OpenOffice with its setup.exe file
> 3) Uninstalling then reinstalling OpenOffice
> but the error message still occurs.
> Our computer operates on Windows 98 with a LiteStep shell and 128MB
> RAM.
>
> If you can help us at all it would be most appreciated.
>
Looking at that error makes me think that maybe you have bad memory. Try
swapping the sticks and see if doing so causes other errors.
--
Documentation Co-Lead
PLEASE - keep list traffic on the list. Email sent directly to me may
be ignored utterly.
1) I don't understand why a registry fix would damage memory.
2) I used to have frequent problems with MSVCRT.DLL when using another
program. In that case, it usually involved conflicting versions of the
file installed by different programs. (I have not experienced this with
Ooo.)
-These two things lead me to believe the problem may be that the
Registry fix made changes either to MSVCRT.DLL or to its references to
the file, causing the error message. Can you roll back your OS to a
restore point prior to the Registry "fix"? Absent that, I have no idea
how to fix the problem without a registry backup.
HTH,
MM
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
