Slow Interaction with Word and Excel

  • Thread starter Thread starter Steve
  • Start date Start date
S

Steve

I am running Office 2000 Professional SP3 on Windows 2000P
SP4. Athlon 2700+ 512meg 333DDR Abit NFS-7 v2. All updates
current.

Cold boot computer. Logon as a user with full admin rights.
After the computer is fully up and running with loading of
all services and programs complete, open a local Excel or
Word document by clicking on the actual document file.
There will be an annoying hesitation of up to 5 to 8
seconds dependant upon computer speed.

Close the document and do it again. At this point the
document and application should still be in memory so the
document should open immediately. Instead it will hesitate
5 to 8 seconds again.

Now close the Beta version of Microsoft anti-spyware. Open
the document. The Word or Excel document will open at
normal speed.

Note: If Word or Excel is launched from the program icon
(start - run - Progam ...) it will open normally. If the
document is then opened through the menubar "file -
open..." it will open at normal speed. There appears to be
some difference in how the beta program processes opening
an Office document. It is as if it is checking a document
launched application against a list each time it opens.
This is a cumbersome and time consuming process and if
unfixed, it would keep me from using or recomending this
product except as a service tool to clean up an existing
infection.
 
I had the same problem ( see my message a few below this
one).
Bill Sanderson implied that he would be looking into it
but never saw any fix.
I have uninstalled the AntiSpyware for now - I was getting
too nervous seeing all the problems.
Hey Bill - do you have an answer for this ???
 
Dave - all that I can say is that multiple users have observed this
issue--some people see it others don't, and I don't have a fix on any
commonality between those sets of installations.

I believe that Microsoft is aware of this issue, but I don't know whether
they have been able to reproduce it themselves.

So--I don't have a fix for you, and I think you've taken the right course of
action.

They've said that another beta build will be released, and I'd urge you to
re-test upon that release, and see whether this issue is still present or
not with the new build.
 
Back
Top