MSAS W/MS Office

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

MS Antispyware Real Time protection is the culprit. I am running the latest
updates, and there has never been a difference for me between updates
regarding this problem.

Everytime that I open an MS Office 2000 document with anyone of the office
applications, the time it takes for the document to open is slow, and not
acceptible to me.

I have just finished testing it with all three of the real time protections
turned on. I then turned them off one by one rebooted and tested. There
does not seem to be a
recognizible difference unless all 3 are off. There really is a drastic
difference with them all off.
 
I am running Office 2000 with MSAS latest updates installed on my laptop and
I have not noticed any lag in performance in any of the Office applications
and I use Word and Outlook almost everyday. Are you the culprit isn't your
AntiVirus installed? Do you have Norton AV installed? If so, check the
options and you have an option to uncheck the Microsoft Office applications
scanning.
--
Andre
Extended64 | http://www.extended64.com
Blog | http://www.extended64.com/blogs/andre
http://spaces.msn.com/members/adacosta
FAQ for MS AntiSpy http://www.geocities.com/marfer_mvp/FAQ_MSantispy.htm
 
Andre Da Costa said:
I am running Office 2000 with MSAS latest updates installed on my
laptop and I have not noticed any lag in performance in any of the
Office applications and I use Word and Outlook almost everyday. Are
you the culprit isn't your AntiVirus installed? Do you have Norton AV
installed? If so, check the options and you have an option to uncheck
the Microsoft Office applications scanning.
Click to expand...

I have not only read this comment before, but I also experience it. If I
were to estimate, it's maybe taking ten seonds longer to load.

--
Frank Saunders, MS-MVP OE
Please respond in Newsgroup. Do not send email
http://www.fjsmjs.com
Protect your PC
http://www.microsoft.com/security/protect/
 
I'd check Andre's detail, but I don't think your observations are mistaken.

This issue has come up throughout the beta.

I don't know, however, how broad the issue is:

1) certainly not everybody sees this, given the 18,000,000 installs, or we'd
be swamped here.
2) This could be an issue specific to your machine--a driver or hardware
interaction. If this is the case, uninstalling, deleting the installation
folder (\program files\microsoft antispyware) and reinstalling should make
no difference. (You would lose access to anything in quarantine, history,
and saved settings.)
3) This could be an issue specific to a given install--basically, something
isn't really installed quite right. If this were the case, the regime in 2
could fix the problem. I'd try it.
 
I am running the latest version of Nod32 with its updates. Shutting it off
does nothing. The only thing that has fixed the problem is what I stated
above, but I appreciate the input.
Thanks you
 
Thanks Bill,
I will go through the step you suggested and see what happens and report back.
 
Just to finish this up..I uninstalled and reinstalled and there is no
difference. Guess that I have to wait until beta 2 comes out.
 
Amount of memory, CPU-speed, disk space, swap size, hyperthreading?
Or on-access virus scan?

OldBoy
 
Amount of memory=1Gb
CPU-speed= AMD XP2600 running at 2.150
Disk space= 60Gig with 45% free
On-access virus scan=Nod32, but it makes no difference if its on or off.
Swap size 1536mb
Hyperthreading?

Thanks
 
I think you are stuck until beta2 comes out.

If you want to leave the program installed, but with real-time protection
disabled, the way to do this is to use the "workaround" paragraph of this KB
article. This would allow you to continue to receive automated definition
updates (and probably automated distribution of beta2...)--and scheduled
scans:

http://support.microsoft.com/kb/892375 End users may be prompted to allow or
block administrative actions that originate from a central management tool
after they install Windows AntiSpyware (Beta) on a computer that is managed
by Systems Management Server 2003


--
 
Thanks Bill,
I think that you are correct. I will follow your instructions, and await
the upgrade.
 
One other interpretation of the facts:

This delay may be caused by a software conflict among drivers on your
system.

So--if you had lots of free time and wanted to experiment, you could try
setting up a clean boot via MSCONFIG--get down to the minimum third-party
stuff that you can, and see whether this lag still occurs.

If it does not occur, then add things back in, trying to spot where the lag
becomes an issue--where the conflict lies.

Basically--a triage process with the drivers and other contstantly running
software on your machine might gain some light on this.

This can be time consuming, and I don't know whether it'll yield a clear
result--it'd be interesting to see whether a clean boot does do away with
the lag, however.

--
 
So--if you had lots of free time and wanted to experiment, you could try
setting up a clean boot via MSCONFIG--get down to the minimum third-party
stuff that you can, and see whether this lag still occurs.
Can you tell me how to do the clean boot?
 
Irv said:
So--if you had lots of free time and wanted to experiment, you could try
setting up a clean boot via MSCONFIG--get down to the minimum third-party
stuff that you can, and see whether this lag still occurs.
Can you tell me how to do the clean boot?
Click to expand...

Sure--the below is from Microsoft MVP Jim Byrd's blog:

http://defendingyourmachine.blogspot.com/

Clean Boot - General Win2k/XP procedure, but see below for links for other
OS's (This for Win2k w/msconfig - you can obtain msconfig for Win2k here:
http://www.3feetunder.com/files/win2K_msconfig_setup.exe ):

1. StartRun enter msconfig.

2. On the General tab, click Selective Startup, and then clear the 'Process
System.ini File', 'Process Win.ini File', and 'Load Startup Items' check
boxes. Leave the 'boot.ini' boxes however they are currently set.

3. In the Services tab, check the "Hide All Microsoft Services" checkbox,
and then click the "Disable All" button. If you use a third party firewall
then re-check (enable) it. For example, if you use Zone Alarm, re-check the
True Vector Internet Monitor service (and you may also want to re-check
(enable) the zlclient on the Startup tab.) Equivalent services exist for
other third party firewalls. An alternative to this for XP users is to
enable at this time the XP native firewall (Internet Connection Firewall -
ICF). Be sure to turn it back off when you re-enable your non-MS services
and Startup tab programs and restore your normal msconfig configuration
after cleaning your machine.

4. Click OK and then reboot.

For additional information about how to clean boot your operating system,
click the following article links to view the articles in the Microsoft
Knowledge Base:

310353 How to Perform a Clean Boot in Windows XP
http://support.microsoft.com/kb/310353
281770 How to Perform Clean-Boot Troubleshooting for Windows 2000
http://support.microsoft.com/kb/281770/EN-US/
 
Hi Bill,
Well I did a clean boot following the instructions given. Learn something
new every day.
The problem remains.
Irv
 
Thanks very much!

So--either beta1 doesn't like your hardware somehow--not sure what the
remaining possibilities are.

At any rate, retesting when beta2 is available seems like the next step.

Sorry for the bad results, and thanks for bearing with us and testing.

--
 
Back
Top