Compact messages

Something screwy is going with OE after installing XP SP3 with some
people. Most people don't seem to be affected but a few are.

Several other programs have been implicated, but even then, not everyone
with those programs are affected.

--

Mike - http://pages.prodigy.net/michael_santovec/techhelp.htm



"Opinicus" <gezgin DeleteThis @spamcop.net> wrote in message
news:eUfk#ZA2IHA.2068@TK2MSFTNGP05.phx.gbl...
> "Michael Santovec" <michael_santovec DeleteThis @prodigy.net> wrote
>
>>>> That it keeps coming up indicates that something on your system is
>>>> repeatedly opening and closing OE (MSIMN.EXE). To solve the
>>>> problem,
>>>> you need to determine what is causing that.
>
> 8<!
>
>> But since XP SP3, we've been seeing some issues where various other
>> programs are triggering the problem.
>
> Just curious but what other programs would open and close OE and why?
>
> --
> Bob
> http://www.kanyak.com
>
>
>

Are you sure OE isn't getting opened/closed? Just having the count go
over 100 won't trigger the compact prompt until MSIMN.EXE is closed
again.

And one person who renamed MSIMN.EXE found that it was automatically
restored the next time the prompt came up.

--

Mike - http://pages.prodigy.net/michael_santovec/techhelp.htm



"PA Bear [MS MVP]" <PABearMVP.DeleteThis@gmail.com> wrote in message
news:eMTRQyB2IHA.548@TK2MSFTNGP06.phx.gbl...
> Opinicus wrote:
>>>>> That it keeps coming up indicates that something on your system is
>>>>> repeatedly opening and closing OE (MSIMN.EXE). To solve the
>>>>> problem,
>>>>> you need to determine what is causing that.
>>
>>> But since XP SP3, we've been seeing some issues where various other
>>> programs are triggering the problem.
>>
>> Just curious but what other programs would open and close OE and why?
>
> The applications in question aren't opening/closing OE. In some
> cases, OE has been Removed from the install of Windows XP.
>
> See this recent discussion about the problem:
> http://groups.google.com/group/microsoft.public.outlookexpress.general...owse_fr
>
> For reference, here's a list of things which are known to cause this
> behavior (so far):
>
> • Various & sundry anti-virus applications (including Norton)
> • Various & sundry anti-spyware applications
> • Various & sundry third-party firewalls
> • Any/all of the above running when SP3 was installed
> • IBM Rapid Access keyboard (driver) RAKDLL.DLL
> • Nero plug-in(s)
> • Windows Desktop Search
> • Windows Live Mail
> • Disk defragmentation
> • MailWasher
> --
> ~PA Bear
>

"Robert Aldwinckle" <robald RemoveThis @techemail.com> a écrit dans le message de groupe
de discussion : e4uX9ew1IHA.1772 RemoveThis @TK2MSFTNGP03.phx.gbl...
> "wabarron" <wabarron RemoveThis @discussions.microsoft.com> wrote in message
> news:ECE510DE-FA02-4647-B9C0-826CA764E39E@microsoft.com...
>>
>>
>> Dear Robert~~
>>
>> Thanks.
>>
>> I tried the command .. which promptly dumped 69MB of
>> junk into the Recycle bin.. almost shutting down the pC...
>> as it tried to perform the task on both my c and slave-e
>> hard drives.
>
>
> Good. So you're set for another week then.
>
>
>>
>> Is there a way to just turn OFF this notification and
>> NOT compact everything?
>
>
> Michael showed you a way to zap the registry.
>
>
> ---
>
>

Invoking OE (MSIMN.EXE) and opening it are 2 different things in my book,
Michael.

MSIMN.EXE is a default & protected file; if deleted, it would be replaced on
reboot by default.


Michael Santovec wrote:
> Are you sure OE isn't getting opened/closed? Just having the count go
> over 100 won't trigger the compact prompt until MSIMN.EXE is closed
> again.
>
> And one person who renamed MSIMN.EXE found that it was automatically
> restored the next time the prompt came up.
>
>
> "PA Bear [MS MVP]" <PABearMVP.TakeThisOut@gmail.com> wrote in message
> news:eMTRQyB2IHA.548@TK2MSFTNGP06.phx.gbl...
>> Opinicus wrote:
>>>>>> That it keeps coming up indicates that something on your system is
>>>>>> repeatedly opening and closing OE (MSIMN.EXE). To solve the
>>>>>> problem,
>>>>>> you need to determine what is causing that.
>>>
>>>> But since XP SP3, we've been seeing some issues where various other
>>>> programs are triggering the problem.
>>>
>>> Just curious but what other programs would open and close OE and why?
>>
>> The applications in question aren't opening/closing OE. In some
>> cases, OE has been Removed from the install of Windows XP.
>>
>> See this recent discussion about the problem:
>> http://groups.google.com/group/microsoft.public.outlookexpress.general...owse_fr
>>
>> For reference, here's a list of things which are known to cause this
>> behavior (so far):
>>
>> • Various & sundry anti-virus applications (including Norton)
>> • Various & sundry anti-spyware applications
>> • Various & sundry third-party firewalls
>> • Any/all of the above running when SP3 was installed
>> • IBM Rapid Access keyboard (driver) RAKDLL.DLL
>> • Nero plug-in(s)
>> • Windows Desktop Search
>> • Windows Live Mail
>> • Disk defragmentation
>> • MailWasher
>> --
>> ~PA Bear

Michael

I read the thread posted by Bear concerning OE and Mailwasher. It was
quite interesting to see the diagnostic process at work.


--
Regards.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~



Michael Santovec wrote:
> Under ordinary circumstances, it is the user.
>
> But since XP SP3, we've been seeing some issues where various other
> programs are triggering the problem.
>
>
> "Gerry" <gerry.DeleteThis@nospam.com> wrote in message
> news:##o8#K71IHA.5140@TK2MSFTNGP02.phx.gbl...
>> The User perhaps Michael <G>?
>>
>>
>> --
>> Regards.
>>
>> Gerry
>> ~~~~
>> FCA
>> Stourport, England
>> Enquire, plan and execute
>> ~~~~~~~~~~~~~~~~~~~
>> Michael Santovec wrote:
>> .
>>>
>>> That it keeps coming up indicates that something on your system is
>>> repeatedly opening and closing OE (MSIMN.EXE). To solve the
>>> problem, you need to determine what is causing that.

> Something screwy is going with OE after installing XP SP3 with some
> people. Most people don't seem to be affected but a few are.

I use a Visual Basic program to insert emails into Outlook Express using
DoCmd.SendObject and every time that command is executed, OE *now* ups the
compaction count, rendering this feature a pain as after 100 emails, it wants
to compact the registry. I send out about 500 emails a day using VB, and now
sit on the ESC key for 400 emails. After reading threads here it's clear that
MS is not going to do anything about it, so I guess it's time to get dump
SP3.

It would be helpful if MS just LEFT this program alone. If they ARE going to
have a programmer make changes, then rewrite this application to use a proper
database that doesn't require this nonsense of compaction. Compaction was
done in the 1970's because few programmers then knew how to structure
databases that did not require compaction, but in the 1980's most learnt how
to do that. That was 25 years ago