shorterxp Posted February 19, 2019 Share Posted February 19, 2019 (edited) 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 February 20, 2019 by shorterxp Link to comment Share on other sites More sharing options...
Tripredacus Posted February 20, 2019 Share Posted February 20, 2019 It seems like BootVis is capable of this, but I have not used it before. https://www.majorgeeks.com/files/details/bootvis.html Link to comment Share on other sites More sharing options...
shorterxp Posted February 20, 2019 Author Share Posted February 20, 2019 Thankyou Link to comment Share on other sites More sharing options...
Destro Posted February 21, 2019 Share Posted February 21, 2019 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. Link to comment Share on other sites More sharing options...
luweitest Posted February 22, 2019 Share Posted February 22, 2019 (edited) 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 February 22, 2019 by luweitest 2 Link to comment Share on other sites More sharing options...
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now