I would like to know why my freshly installed slipstreamed xp w/ service pack 2 takes so much time to load up when i turn the computer on.

Firstly, it comes up with this white loading bar which takes about 3/4 of a minute, then it comes up with the regular xp loading screen which takes another minute or so.

I've just formatted as well, and my computer has 1 gb of ram and a 1.7ghz processor. Every other time i formatted with service pack one saw very rapid boot ups, about 20 seconds - now its just unacceptably slow.

Must be something to do with your system configuration. I've found that the Systems I have here with SP2 installed actually boot quicker than those without it.

I know what you mean greasywog87. Have the same problem. I've heard really bad things about SP2 for XP. One of my relatives works at Boeing and she heard from some of the tech agents that XP's Service Pack 2 may even have glitches that could harm some system files and screw up your firewall. I suggest you don't install SP2 on any other XP OS until windows can fix this problem. Also, when windows comes out with a new Service Pack, DO NOT download it right away. Sometimes, such as SP2, they may come out with one that contains glitches, may work good for some people, and screw all the other people. So wait before installing a new service pack until windows can fix the little problems. ;)

cargenius, i think u mean when microsoft fixes the problems, not windows. Anyway, generally system performance is faster, its just that it takes ages to boot.

My system configuration is as good as I can get. I don't know what else to do.

I've come across a couple of other situations where people have experienced problems after preparing a slipstreamed installation of SP2. I've not come across such problems where the installation hasn't been slipstreamed.

Damned if I know just where problems might lie, though.

But there definitely is NOT an inherent problem in SP2 which leads to such problems as slow startup or the issues described by cargenious. What you CAN get are problems where software is installed which makes illegal calls and thus does not adhere to the standards checked for by SP2s security features. For such software exceptions need to be set to security restrictions for the programs which breach such standards, and that is a fault of the programs themselves, not of Windows ;)

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.