T
Tom Hall
Actually, this problem began appearing shortly before I installed SP2
from the CD I ordered from Microsoft.
Computer:
Operating System Microsoft
Windows XP Home Edition
OS Service Pack Service Pack 2
Internet Explorer 6.0.2900.2180
Computer Name TOM-EPWIFTQ4R0S
User Name Tom
Logon Domain TOM-EPWIFTQ4R0S
Motherboard:
CPU Type AMD K6-2, 550
MHz (5.5 x 100)
Motherboard Name AOpen AX59 Pro
(2 ISA, 4 PCI, 1 AGP, 3 DIMM)
Motherboard Chipset VIA VT82C598
Apollo MVP3
System Memory 256 MB (SDRAM)
BIOS Type Award Modular
(08/07/02)
Communication Port Communications
Port (COM1)
Communication Port Communications
Port (COM2)
Communication Port Printer Port
(LPT1)
Display:
Video Adapter NVIDIA GeForce2
GTS/GeForce2 Pro (32 MB)
3D Accelerator nVIDIA GeForce2
GTS
Monitor Samsung
SyncMaster 905DF(X)/955DF(X)/MagicSyncMaster CD195A (HCCW117563)
When I restart or turn on the machine and log in, IE does not want to
create a window for about 3-5 minutes. It doesn't matter what URL I
invoke, or even if I try to bring up a blank browser window, IE will not
create a window on my desktop.
I have confirmed with Task Manager the existence of a IEXPLORE.EXE
process, using a substantial amount of memory in most cases, but the
window does not appear.
If I leave everything alone, the window eventually appears, but this is
on average after at least 3-4 minutes of uptime.
I'm not sure if there's a relationship, but it seems that for the amount
of time that IE won't put up a window, there's an instance in Task
Manager of wuauclt.exe, which I believe is the Windows Update utility.
This instance eventually goes away, I find, and it seems that as soon as
it does, IE works without a hitch.
This problem does NOT appear after a logon or logoff as when changing
users. The only other account on my computer is the Guest account, and
it is not immune from the problem if I log in as Guest immediately after
system startup. It seems that restarting the system is the only way to
reliably reproduce this phenomenon.
Once again, this problem predates my SP2 installation. In general, so,
far, I can say that SP2 has not created any new problems for me, but it
also hasn't resolved any pre-existing ones.....
The only other post-SP2 issue I have found so far is when using my
webcam (Logitech Quickcam Express). I have recently upgraded the video
card from SiS6326 to Nvidia GeForce2 and have added another 128-mb stick
of PC133 ram to the existing 128-mb stick of PC100 ram that came with
the box. The tech who installed the 2nd stick for me said that the PC133
would automatically "clock down" to the speed of the slower memory.
Since installing SP2, the cam seems quite sluggish on MSN Messenger 6.2
and on one occasion caused a complete system reset -- even though I have
Windows configured to produce a stop screen. It was as if someone had
hit the reset button. Nothing got written to the Event logs.
Fortunately, I don't do a lot of camming, but it would be nice if it
worked as well under SP2 as it did under SP1.
Prior to the hardware changes, I couldn't get more than 2 minutes into
the SP2 install without getting a blue screen. I was relieved to find
that the 2nd attempt at installing SP2 went without a hitch.
Any suggestions would be most welcome.
Tom
from the CD I ordered from Microsoft.
Computer:
Operating System Microsoft
Windows XP Home Edition
OS Service Pack Service Pack 2
Internet Explorer 6.0.2900.2180
Computer Name TOM-EPWIFTQ4R0S
User Name Tom
Logon Domain TOM-EPWIFTQ4R0S
Motherboard:
CPU Type AMD K6-2, 550
MHz (5.5 x 100)
Motherboard Name AOpen AX59 Pro
(2 ISA, 4 PCI, 1 AGP, 3 DIMM)
Motherboard Chipset VIA VT82C598
Apollo MVP3
System Memory 256 MB (SDRAM)
BIOS Type Award Modular
(08/07/02)
Communication Port Communications
Port (COM1)
Communication Port Communications
Port (COM2)
Communication Port Printer Port
(LPT1)
Display:
Video Adapter NVIDIA GeForce2
GTS/GeForce2 Pro (32 MB)
3D Accelerator nVIDIA GeForce2
GTS
Monitor Samsung
SyncMaster 905DF(X)/955DF(X)/MagicSyncMaster CD195A (HCCW117563)
When I restart or turn on the machine and log in, IE does not want to
create a window for about 3-5 minutes. It doesn't matter what URL I
invoke, or even if I try to bring up a blank browser window, IE will not
create a window on my desktop.
I have confirmed with Task Manager the existence of a IEXPLORE.EXE
process, using a substantial amount of memory in most cases, but the
window does not appear.
If I leave everything alone, the window eventually appears, but this is
on average after at least 3-4 minutes of uptime.
I'm not sure if there's a relationship, but it seems that for the amount
of time that IE won't put up a window, there's an instance in Task
Manager of wuauclt.exe, which I believe is the Windows Update utility.
This instance eventually goes away, I find, and it seems that as soon as
it does, IE works without a hitch.
This problem does NOT appear after a logon or logoff as when changing
users. The only other account on my computer is the Guest account, and
it is not immune from the problem if I log in as Guest immediately after
system startup. It seems that restarting the system is the only way to
reliably reproduce this phenomenon.
Once again, this problem predates my SP2 installation. In general, so,
far, I can say that SP2 has not created any new problems for me, but it
also hasn't resolved any pre-existing ones.....
The only other post-SP2 issue I have found so far is when using my
webcam (Logitech Quickcam Express). I have recently upgraded the video
card from SiS6326 to Nvidia GeForce2 and have added another 128-mb stick
of PC133 ram to the existing 128-mb stick of PC100 ram that came with
the box. The tech who installed the 2nd stick for me said that the PC133
would automatically "clock down" to the speed of the slower memory.
Since installing SP2, the cam seems quite sluggish on MSN Messenger 6.2
and on one occasion caused a complete system reset -- even though I have
Windows configured to produce a stop screen. It was as if someone had
hit the reset button. Nothing got written to the Event logs.
Fortunately, I don't do a lot of camming, but it would be nice if it
worked as well under SP2 as it did under SP1.
Prior to the hardware changes, I couldn't get more than 2 minutes into
the SP2 install without getting a blue screen. I was relieved to find
that the 2nd attempt at installing SP2 went without a hitch.
Any suggestions would be most welcome.
Tom