Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


Sign in to follow this  
shorterxp

Tool to identify problematic service at log on?

Recommended Posts

Hi,

Is there an easy way to "track" services behaviour at log on for windows XP?

I installed a ethernet device driver, upon reboot + logon (and everyone subsequent logon) explorer loads however majority of windows stuff refuses to open (some non .net apps can). Things like Device manager, network connections, control panel, won't open for circa 2minutes. I suspect that a service which is supposed to run at startup impdes the usual logon sequence. Is there a tool out there that can monitor the sequence?

FYI: It's definately the ethernet driver that does it because upon fresh install of XP (which takes but a minute) everything works as expected until IT alone is installed. Even after uninstall, the hang persists. Trried both manual installation of the driver via device manager and the provided installshield package, both lead to the same end.

 

Cheers fellas

 

EDIT: problem goes away if I Disable the connection in Network Connections (or device in device manager). Very strange

Edited by shorterxp

Share this post


Link to post
Share on other sites

most  likely has to do with serivice and driver load order.  I recal there is a way to change that but I don't remember right now.

Share this post


Link to post
Share on other sites

I had the same problem before. Analyzing with Bootvis, there's driver delay related to *smb*, so I deleted all desktop link to remote directories (like \\host\folder\), it gets quicker, but not enough until I totally changed "workstation" service to "manual" ("computer browser" and "tcp/ip Netbios helper" have already changed to "manual" before). That reduces boot time to 30s or so, and no stuck after showing the desktop anymore.

The side effect is, if you need to visit remote folders afterwards, you should run "workstation" service manually.

Edited by luweitest
  • Like 2

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

  • Recently Browsing   0 members

    No registered users viewing this page.

×