Grant the account you are logging on with the "Log On Locally" right in the Local Security Policy of the server you are logging onto. If it is a Domain Controller, you may also need to do the same thing in the Domain Controller Security Policy snap-in on the server you are logging onto.
It is not so much WinXP recognising the new processor as your machine's BIOS recognising the new processor. WinXP will get its information from the BIOS.
For example, I recently upgraded my system (ASUS A7A266 M/b) from an Athlon 1400 to a 2400XP... To get my system to recognise the new CPU...
Are there any more details on the error that mentions that file?
Try this from the Run command in the start menu:
"regsvr32.exe systools.dll" without the quotes and then click ok.
You should see a box advising that the dll was registered successfully.
Try installing the...
This problem in fact has been fixed in Outlook 2003. Now instead of rushing out and buying Office 2003, :D , try the following as it may fix the problem:
1. Uninstall Outlook
2. Search for any file that is named: mapixxx.xxx (the "x's" are wildcards).
3. Rename any of these files found...
Please see this article regarding the problem:
Firewall Stopping Windows Update From working
That article mentions Zone Alarm as being the problem but I am sure that any other firewall could possibly be blocking Windows update.
Also, this article has been known to solve the problem too...
From this website - Internet Explorer Homepage fixes
Some ISP's provide a customized version of IE. Some Web pages will also reset your home page and do this. One of the customizations they might make is to disable the ability to change the home page, so that you are forced to use their...
Delete them both as they are both in the temp folder under Local Settings. They may possibly be spyware files or virus files or even temporary files created by another program. It would be totally safe to delete them however.
Just a wild guess here but whatever Service Pack you have installed, I would reinstall it on the system again and then visit Windows Update.
For example, lets say you have Windows XP with Service Pack 1 applied. Reinstall Service Pack 1 (dont install SP2) and then visit Windowsupdate...
Have a look at this Microsoft article regarding that error:
expand cd-rom:\i386\ntoskrnl.ex_ drive:\Windows\system32 ---- From the Recovery Console.
From looking through the logs there, I have 2 possible solutions:
Follow these steps:
1. Click Start, and then click Run.
2. In the Run dialog box, type regedit, and then click OK.
3. In Registry Editor, locate and then click the following registry key...
I've seen this problem when the Journal Viewer has been downloaded and installed on Windows XP. It is one of the "recommended" updates, not critical, from Windows Update. Have you downloaded and installed this update?