Slow WinXP start-up

[lankia]

What might be a good program to examine what's going on during startup?? I used to run Bootlog Examiner when I was on WinME. But Bootlog is not compatible with WinNT/XP ... any suggestion?

My problem is that my computer used to boot up so much faster than it is now. I got to the desktop screen really fast, but I can't do anything for the next few minutes because something is running at the background and it's waiting to be completed. I looked at task manager, but it wasn't informative. In case it matters, I am running Norton AntiVirus and Norton INternet Security 2002 and both programs start up with windows.

Any help would be much appreciated.

-lankia

[edit] One more thing is that I can't bring up my IIS management window anymore. Is it possible that this is a virus/trojan problem? [/edit]

 

[Miramonti]

have you tried bootvis?

(click on "downloads")

 

[lankia]

Thanks for the suggestion on BootViz, but didn't see anything suspicious on the Boot Viz trace ...

Perhaps, I should just say write down what I am going through and hopefully someone can help me out here.

When the computer reboots, it only takes a short while to get to the log-in screen and then to desktop. But once in desktop, I can see that my Norton AntiVirus 2002 (NAV) is trying to load and usually it takes 3-5 mins to complete the loading up process. During this time, if I try to bring up the system properties (right-click on my computer and click on properties) or run any applications for that matter, Windows will only display it after my NAV has fully loaded up.

When my computer is fully loaded, there are the following items on the systray:
1. NAV
2. Norton Internet Security (NIS)
3. AdWatch (for ad-ware detection)
4. PopUp Killer
5. Microsoft ActiveSync
6. Plus a variety of services including IIS

Devices attached are as follow:
1. Digital Camcorder to a StarTech firewire adapter
2. Compaq all-in-one machine (USB)
3. Compaq IPAQ Craddle (USB)
4. Logitech Cordless Keyboard & Mouse combo (USB & PS2)

In the past, NAV did take an extra few seconds to load up after the desktop screen has shown up, but never more than 30 seconds. I have tried uninstallng and reinstalling, but that apparently didn't work.

I have also used msconfig to NOT load all the items in the STARTUP tab, but no avail as well. My compie still took as long a time before I can really run any applications. I ran full virus scan on all my harddrives and no virus was detected. Haven't tried trojan scanner, though. Can anyone suggest a good trojan scanner? By the way, I only installed NIS a few weeks after I installed IIS, which definitely make my system susceptible to trojans.

A funny thing happened tonight .. I couldn't bring up the IIS management console, nor could I uninstall it through "Add/Remove Windows Component." I am wondering if that, in any ways, suggests a trojan(s) lurking in my system. Oh, there wasn't any error message when I tried to pop up the IIS management console or to uninstall it. The requested process just sit there.

I am not sure what else can I should do at this time, so I would extremely grateful if someone can help me out or perhaps suggest a few other things I can try to solve my problem.

Thanks in advance.


-lankia

 

[YBS1]

Do you have a network card installed in your pc? If so assign it an IP address, Windows looking for one will cause a wait of about 30-45 seconds after your desktop comes up.

 

[lankia]

YBS1, you are right!! assigning an IP to my network card definitely makes my system response faster after desktop shows up.

the problems i am facing now are:
1. I am on a dsl (using PPoE method to connect) with floating IP address. when I do a ipconfig on a command prompt, i got two adapters: LAN and PPoE, even though there is only one adapter. If I assign LAN and IP address then my system definitely boot up a lot faster, BUT i can't dial to verizon (my DSL provider). Is there a way to get around this?

2. Also I have a Firewire card that shows up as "1394 Connection" under "LAN or High Speed Internet" in my Network Connections control panel. Should I assign it a fixed IP as well?

Thanks in advance for any help.

-lankia

 

[YBS1]

I'm on PPPoE dsl also, Sprint however. You should be able to assign a random IP to your network card (192.x.x.x) and subnet mask (I used 255.255.0.0), leave the default gateway and DNS server entries blank and it work ok as long as you leave the PPPoE properties alone. If it doesn't, you may want to contact verizon to see if you need any specific entries to make a connection (sometimes the provider will have recommended settings for those using routers, hardware firewalls, etc.).

Actually, try this. Connect in a normal way to verizon, once your connected open you network card's properties and look at the values it has been assigned. Make note of them, disconnect, apply those manually to the card and reboot. You should be ok if not, contact verizon for any settings you may need.

 

[btvillarin]

<< I'm on PPPoE dsl also, Sprint however. You should be able to assign a random IP to your network card (192.x.x.x) and subnet mask (I used 255.255.0.0), leave the default gateway and DNS server entries blank and it work ok as long as you leave the PPPoE properties alone. If it doesn't, you may want to contact verizon to see if you need any specific entries to make a connection (sometimes the provider will have recommended settings for those using routers, hardware firewalls, etc.).

Actually, try this. Connect in a normal way to verizon, once your connected open you network card's properties and look at the values it has been assigned. Make note of them, disconnect, apply those manually to the card and reboot. You should be ok if not, contact verizon for any settings you may need. >>



If in your situation, you're not connected to a LAN, and you have a dynamic IP address, this should not work. Your first paragraph explaining what to do is right (for the NIC connected to the DSL modem), but don't set a fixed IP address. lankia uses a dynamic IP address. You'll have to look more into your other NIC connected to the LAN. I'm not sure what settings you'd use there. But, at least for the DSL NIC, you can set a bogus IP address and subnet mask, leaving the default gateway and DNS cells blank.

I did explain all this here.

I hope you work this out...

 

[lankia]

jjsole, thanks for the bootviz program!!

YBS1 & btvillarin, thanks for helping me out with my slow bootup. I finally fixed it by assigning a bogus IP (192.168.0.1) and subnet mask (255.255.255.0)!!!

-lankia

[edit] I forgot to add the fact that I called Verizon Tech Support only to be told I needed to upgrade to a more expensive package in order to solve my problem!!! I told the rep that I didn't need any static IP, but just a bogus IP for the DSL NIC and he said it's NOT possible because of the way the Verizon network is set up!! I thought to myself that if that's the case, everyone who signs up for Verizon's Choice Pack (instead of the more expensive Ultra Pack) subjects him/herself to startup distress. And was wondering if it can be filed as a complaint. [/edit]