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]" wrote in message
...
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/micro...d35fbfa457fd6f

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

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]" wrote in message
...
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/micro...d35fbfa457fd6f

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" wrote in message
...
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

CESDewar wrote:
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...

Thanks for this feedback.

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

Care to guess when OE was written? eg

hola que tal ahi
"CESDewar" escribió en el mensaje
...
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

Is OE open when you do that? If not, open it and leave it minimized in
the background. That might prevent the problem.

--

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



"CESDewar" wrote in message
...
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

"CESDewar" escribió en el mensaje
...
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

Well, now I can't find who had suggested to install Registry Monitor from
Sysinternals.com, but in my case - WinXP, SP3, regular use of Outlook Express
- I clearly see that each 2o secs the NMIndexStoreSvr (service?) queries the
value: "Compact Check Count', and sets a new value here, incrementing by one.
When the value reaches 100 (decimal), the annoying message prompt re-appears.
I have one crucial question he what side effects are to be expected by
stopping the service which triggers the counter update in background, causing
that after a little longer than half an hour after compacting we see the
message again? What is the service name to look for in computer management? I
am aware that this is not solving the root cause, but it is obvious that
though SP3 is one thing in common of these problems, they are triggered by
co-incidental influence of many other codes...

"Michael Santovec" wrote:

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" wrote in message
...
"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.

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

NMIndexStoreSvr is a Nero plug-in and is one known cause for this behavior:

• Various & sundry anti-virus applications (including Norton);
• Various & sundry anti-spyware applications;
• Various & sundry third-party firewalls;
• Any/all of the above running when WinXP SP3 was installed;
• IBM Rapid Access keyboard (driver) RAKDLL.DLL;
• Nero plug-in(s);
• Windows Desktop Search is installed;
• Windows Live Mail is or had been installed;
• Disk defragmentation, need for;
• Using Visual Basic DoCmd.SendObject command to create an email;
• Using any number third-party applications (e.g., accounting software) to
send emails by via Outlook Express;
• MailWasher; and/or
• Programatically opening EML files while OE is closed (e.g., creating a
New Message via Address Book).

See this recent discussion about the problem:
http://groups.google.com/group/micro...d35fbfa457fd6f
--
~Robear Dyer (PA Bear)
MS MVP-IE, Mail, Security, Windows Desktop Experience - since 2002
AumHa VSOP & Admin http://aumha.net
DTS-L http://dts-l.net/


Dachshound wrote:
Well, now I can't find who had suggested to install Registry Monitor from
Sysinternals.com, but in my case - WinXP, SP3, regular use of Outlook
Express - I clearly see that each 2o secs the NMIndexStoreSvr (service?)
queries the value: "Compact Check Count', and sets a new value here,
incrementing by one. When the value reaches 100 (decimal), the annoying
message prompt re-appears. I have one crucial question he what side
effects are to be expected by stopping the service which triggers the
counter update in background, causing that after a little longer than half
an hour after compacting we see the message again? What is the service
name
to look for in computer management? I am aware that this is not solving
the
root cause, but it is obvious that though SP3 is one thing in common of
these problems, they are triggered by co-incidental influence of many
other
codes...

"Michael Santovec" wrote:

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" wrote in message
...
"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.

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