very unresponsive w2k/xp after startup

[Alexei A. Frounze]

Hello folks,

I was wondering what can be wrong with my computer or windows
configuration...
The prob is as follows.

I do a clean install of w2k pro or wxp pro, install only something like gfx
card driver and nothing else, I mean there's basically no other software but
windows itself.

I start up windows and log on to it. Windows shows the desktop, loads all
what it needs by default.

Then I try to open the settings->control panel (another scenario: launch
outlook express and receive mail). Here the windows kinda stops, the control
panel doesn't open (in the other scenario: dialup window doesn't show up).
At this moment no disk activity is done, I can move the mouse pointer, but
whenever I want to open or run anything by clicking, nothing happens. The
windows gets utterly unresposive to any of my commands.
This lasts for as long as about half a minute, then something happens, and
things continue to work where they stopped. E.g. the requested windows open
and show up, programs run, etc.
And if I just start up windows (it gives me the log on dialog window) but I
wait this half a minute before logging in, everything is OK after log in.
E.g. it doesn't matter whether I log in or not. Windows does some work of
its own, yet it's unclear what it does or waits for. All the installed
devices are properly configured and working (drivers installed for gfx card,
modem, sound card, network card, no question marks shown in control panel ->
.... -> system -> ... -> device manager).

Here comes the question. What can be deadly wrong with windows configuration
or my computer? I have never seen such a behaviour on any other PC running
w2k or wxp before. But this is really irritating.

For your info:
PC is a Celeron 600 MHz (MB is 6VIA90A1 with VIA 694X chipset), 256 MB RAM,
20 GB HDD, NVidia GeForce2 MX 400 (64 MB RAM) gfx.
W2k Pro can be either raw or with SP4 installed, doesn't seem to make any
difference. Both W2k and WXP have identical behavior.

Thanks in advance,
Alex

 

[Guest]

Please see my previous thread entitled "Slow Right Click Response and Slow Opening of Office Docs" which explains the source of this problem in more detail. Also, following is an excerpt from another email that I sent regarding this issue:

We encountered a serious problem involving extremely slow response on all of our computer systems starting sometime yesterday (Wednesday, January 8, 2004). Upon further investigation via newsgroups and after a couple of calls to Symantec (publisher of Norton System Works and Norton AntiVirus), we have found that the same problem is affecting thousands and perhaps millions of other users who are using Norton AntiVirus.

The problem is triggered by allowing Norton's LiveUpdate module to download the latest virus definitions update. Apparantly this virus definitions update contains an expired Verisign security certificate, which is the root cause of the problem. Symantec representatives indicated they are working to resolve this problem, and that additional information and/or a fix will be provided through their web site as soon as possible. In the meantime, their suggested work-around is to open Internet Explorer, select Tools->Internet Options from the menu, click on the Advanced tab, then scroll down the list and uncheck the "Check for publisher's certificate revocation" option. Obviously, this is a less than desirable and only temporary workaround, since unchecking the aforementioned option will open a potential security loophole.

While attempting to research this problem, I tried to reach Symantec via their 800 number, and was unable to get through after multiple attempts over an hour. I made 2 subsequent calls via Symantec's 900 toll call support line, and also requested a refund of my phone charges since this problem obviously resulted from flawed Symantec software and not any fault of my own. The rep that I initiallly spoke with indicated that Symantec could not issue any refund for calls on the 900 line. I requested to speak with a supervisor, and they said they would call back within three days to discuss my complaint further.

In my mind, the appearance of this problem raises serious questions regarding Symantec's credibility as a vendor of computer security products. There should have been absolutely NO way that one of their virus updates could have made it out the door with an expired security certificate. That seems like an *obvious* problem which ought to have been detected before sending out the update by any competent security software provider.

 

[Pegasus \(MVP\)]

This could be an NAV issue. Check existing posts in this
newsgroup that have the words "Right" or "Norton" in the
Subject line.