xp load-up

Hi there, my xp home, checked for spyware, malware, trojans, etc very slowly boot to final screen. checked the drivers, got all updates fm MS, still same problem. (winxp, 512Mb, Toshiba Satellite/HD 40/ best

Hello bikbok01 and welcome to WTT!

Slow starting windows can be caused by a number of things. The first things we should do are get rid of the temp files and defragment the hard drive. Defragmenting the hard drive will put all the files fragments that belong to a particular file in sequential order so it is faster to pull each individual file. It will work better this way because the operating system will not have to search as much to find all the fragments it needs.

Run the Disk Cleanup utility:
Go to Start | Run, type cleanmgr, and press Enter. Go through the prompts and select which items you'd like to clean up.

Next, Run the Disk Defragmenter utility:
Go to Start | Run, type dfrg.msc, and press Enter. Choose the drive to defragment and click Defragment. Let it run through and it will give you a report at the end. If you can post this, it will help us know if there is anything else that needs to be defragmented.

Regards,

Ax

Thanks Ax238 defragment every week, never over 4-5%, however system log shows the same errors for last few weeks: 1. Source MSDTC, event ID 4197, service MS DTC XA 2. Source: Service Control Manager, event ID 7024, RemoteAccess terminated; specific error 2147500037 (0x80004005). 3.Source: Service Control Manager, event ID 7024; Distributed Transaction Coordinator terminated; wspecific erroor 3221229627 (0xC000103B). 4.Source: Service Control Manager, event ID 7023; file not found by the way, name is Jack

Hey Jack,

Great, glad to hear you keep your computer defragmented. It's probably in pretty good shape as far as that goes then. Let's try to resolve the first event error you listed.

Check out the following MS KB article:
You may receive error code -1073737712 when you try to start the Distributed Transaction Coordinator service in Windows XP or in Windows Server 2003

If the instructions here don't help you resolve the issue, try the following:

• Go to Start | Run, type cmd, and press Enter
• Copy and run the following commands:

  MSDTC -uninstall

  MSDTC -install

  (Run the commands by clicking the [external image: Posted Image] image button in the upper left portion of the command prompt window title bar and choosing Edit | Paste, then pressing Enter.)

Failing this, try rebuilding the TCP/IP stack.

Let me know how it goes,

Ax

Hi Ax, Done both, seems a bit better, let you know whta the admintool report show on nxt boot Thnks v much Jack

Sounds good, I'll await your response.

And again, the next boot produced similarlly looking problems: a. Service controll manager, event id 7024, remote access terminated, specific error 2147500037 (0x80004005). b. Service controll manager, event id 7023, aplication manager terminated, file not found c. warning: MRxSmb, event ID 3032, not registered NetBT_Tcpip_{A5E70808-190B-498A-801C-A37E0 for reason: transport is in off-line mode Jack

Jack, do you have Netbios over TCP/IP installed in Local Area Connection Properties? If so, uninstall/remove it, see if that resolves the SCM problem.

For your slow boot problem, does it also happen in Safe Mode? If not, physically disconnect from the Internet to prevent a malware infection while your Anti-virus and/or Firewall are disabled in the following steps, then do a normal boot:

Click on Start then Run, type msconfig and press Enter.
Click on the Startup tab and disable everything (remember what is enabled so you can put it back).
Do a regular boot, see if it runs normal.
If yes then use msconfig to enable several items at a time till you find the culprit.

If no, re-enable then click on the Services tab. Check the Hide All Microsoft Services box then disable what's left.
Again, do a regular boot, see if it runs normal.
If yes then use msconfig to enable services till you find the culprit.

Reconnect to the Internet when done.

Once you've found the culprit, uninstall it or find out how to eliminate it from your system. Simply disabling it in msconfig is a temporary fix at best.