If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.
acheyenne[/size]]
I'd be interested to know if this is normal startup, because it is sometimes annoying to have to wait if something can be tweaked to avoid it.
It most definately isn't normal as both the K6-3+ and Athlon here boot very quickly into XP. :?:
<center> </center>
It does boot very quickly to the desktop, and I can immediately run Netscape, for example, and go happily to the internet or my email. But Windows Explorer, for example, will not start for a minute or so, until XP gets done doing whatever it's up to. Same with getting to the Start menu, so I can't run services.msc to see what the heck is holding it up.
Is yours fully functional as soon as the desktop comes up?
By chance, have you disabled MS Messenger from running at start up? I had a similar experiece when I first loaded XP Pro. XP knows I have a NIC and creates a LAN connection. I'm just guessing, but if Messenger is started up and XP thinks the PC has a LAN connection already, then it might be trying to use your network connection (which may not exist yet, so this is going to cause some wait states) to set up your Messenger service.
As soon as I went to the messenger icon in the System Tray and selected don't start Messenger on start up, then on my next restart, it came right up.
Yay!!! Thanks, you guys are on the right track! I disabled Messenger in XP services, (and also had to actually rename the folder as per wuntvor's link). I also set SNMP services to manual. Something in this combination has reduced the time for full boot by at least 30 seconds. After the desktop appears, there's still about 8 or 10 seconds of thrashing around before the start menu becomes available, but it's a huge improvement.
Comment