• We should now be fully online following an overnight outage. Apologies for any inconvenience, we do not expect there to be any further issues.

System Lag for 1-2minutes after Windows starts?

4x4expy

Senior member
Mar 15, 2003
398
0
0
Using Windows xp Pro with sp1 and all on a recent install, system in sig.

My boot time into windows is still good, ~35sec or so, but once to the desktop for the 1st 1-2 min apps are slow to open and some apps simply will not open. After this period is up, everything is whipcrack quick. It is just very frustrating. I have run regscrub, disabled all startup apps without any change. I keep thinking that it is something with my Omega ATI drivers, because I have noticed that after I have been at my desktop for a couple mins, there is a hint of a screen flicker, and this is my cue that the system is at full speed, before the flash I have the lag. I find it also curious that if immediately after bootup I try to open Aida32, as aida is initializing, it hangs on the "Loading Drivers" message for this lag period.... After being hung there for the 1-2minutes, it flashes through the rest of the initialization and all is fine. I have uninstalled my display drivers and even used the Driver Cleaner/Cab Cleaner software according to recommendations, and reinstalled the Omegas, and also done the same uninstall followed by install of latest Cats. None of this seems to have helped. Does this sound familiar to anyone?
 

MrYogi

Platinum Member
Mar 15, 2003
2,680
0
0
try typing msconfig from start>Run and disable all the startup services.
I have never used regscrub, I tried downloading it but i think it is not available anymore
 

4x4expy

Senior member
Mar 15, 2003
398
0
0
I've done that without any change. I got regscrub from the Utilities section of the Maximum PC disk.

Thanks though, Anyone else? I might take this thread to the OS forum.
 

J1600B

Senior member
Nov 15, 2002
246
0
0
Run a trace with bootvis. I think you get it from M$ website. It will tell you what, if any, driver or (service too i think) is slowing you down.

I tried to get you a link from M$ but it says its unavailable. Maybe try a google search to find a different location. Be wary of using the option to speed up your boot if you are already hapy with it.
 

MysticWar

Member
Oct 12, 1999
116
0
0
Sounds like its trying to assign itself an IP. I'm pretty sure you have a network card on your system. What you can do is assign the IP yourself. Under network connections, choose LOCAL CONNECTION properties. Then choose PROPERTIES of INTERNET PROTOCOL (TCP/IP) Select USE THE FOLLOWING IP ADDRESS: and type in 192.168.0.101 you can use other IP too but this what I use. For SUBNET mask: type in 255.255.255.0 You can leave the DNS info blank. OK then reboot.

I hope that will fix your problem.
 

4x4expy

Senior member
Mar 15, 2003
398
0
0
Originally posted by: MysticWar
Sounds like its trying to assign itself an IP. I'm pretty sure you have a network card on your system. What you can do is assign the IP yourself. Under network connections, choose LOCAL CONNECTION properties. Then choose PROPERTIES of INTERNET PROTOCOL (TCP/IP) Select USE THE FOLLOWING IP ADDRESS: and type in 192.168.0.101 you can use other IP too but this what I use. For SUBNET mask: type in 255.255.255.0 You can leave the DNS info blank. OK then reboot.

I hope that will fix your problem.

Damn you guys are good! I actually got it fixed last night, and was checking by here to tell my solution. I didn't mention that I had a second NIC installed to connect a single workstation. It installed fine and was working fine before the system lag started. After several days of frustration, I was messing with the workstation and realized that for some reason it was unable to access internet, but access was fine on my main system(connected directly to modem). After checking the connection properties of each computer, there was obviously no communication. I just clicked the repair connection buttons on both sides. Windows reassigned IP's and after rebooting.... ZERO LAG! Thanks for your responses though, because I was hung up on the fact that it must be due to the vid drivers that I had been screwing with. Had I not literally stumbled upon the problem, I would be fixing it right now on your recommendations.