Win XP oddities

speedlever

Senior member
Oct 27, 2000
277
0
0
Here are a few oddities I've noticed since I installed a fresh copy of XP/home/sp1 on a new HD.
Hardware:
-Asus A7V with latest BIOS (1011)
-1 Gig Athlon processor
-512 Mb Mushkin PC133 SDRAM

After installing the FAX component, logging off a user account becomes a 95+ second wait for the blue logging off screen to appear. And then it may hang there, or not. Or may even go to a black screen with a white underscore in the top left corner. Reset to fix. sigh. Fast switching between users appears to be unaffected.

If I uninstall FAX, the normal time to logoff returns. Sometimes I have to manually shut down explorer to initiate the logoff.. or wait for the windows countdown timer to do it for me.

Occasionally, I see a narrow black vertical line that starts at the bottom of the screen about 4 inches from the left that runs up 6 or 7 inches vertically. Nothing covers it up. It's always in the forefront. Although just a line, it is still annoying. I've seen it pop up on different user accounts.. and on 2 separate installs of XP on this PC. Never saw it on W2k/sp3.

I have one account that OE will not initiate unless the account is an administrator. I've deleted the account, rebooted the PC and recreated the account but continue to get the same error msg every time (the first pop-up msg tells me my HD is full or out of space, the second pop-up says MSOE.dll will not intiate). I retained the admin account and set up 4 other accounts as limited access. All work under limited access except for one. My wife's! So the easy fix is to make her account an admin as well. It works.. but this is not clean yet.

Question: is it time for a new subsystem (mobo and processor)? Or is XP just that flaky?

I like being able to connect my digicam to XP and being able to get my pics without other soft/hardware. OTOH, W2k/sp3 seemed a bit more stable (until I blew it up loading digicam software!)

And those darn pop-up balloons are just annoying the heck outta me! (yeah, I know.. there's a registry hack to fix this).

Anyone else seen any of the above?

 

LiLithTecH

Diamond Member
Jul 28, 2002
3,105
0
0
Are there any Device conflicts present in DEVICE MANAGER?

Have you checked the EVENT LOG to see what the offending application might be?
 

speedlever

Senior member
Oct 27, 2000
277
0
0
No device conflicts shown in DM.

A typical msg in the event viewer when I have such an event (the extended delay to logoff):

>>Windows saved user RICK1\Rick registry while an application or service was still using the registry during log off. The memory used by the user's registry has not been freed. The registry will be unloaded when it is no longer in use.

This is often caused by services running as a user account, try configuring the services to run in either the LocalService or NetworkService account.<<

And here's another with the same time stamp:

>>Windows cannot unload your classes registry file - it is still in use by other applications or services. The file will be unloaded when it is no longer in use. <<

Is that helpful?