Error message at Start-up?

The XML Parser error comes if either the xml file is bad, or if the xml parser is corrupt or malfunctioning.

You could try first removing the related program from startup by using the MSCONFIG Utility. Start -> Run -> Type MSCONFIG and Click OK. Goto Startup Tab and look for the relevant program and uncheck it, this will disable it from running the next time you start your computer. Do remmember that every time you make a change in MSCONFIG Utility, the warning window appears on next reboot warning you about the change in configuration. Just check the checkbox in that window saying Do not show this dialog again.

If you still face xml parser errors from other applications, like opening an xml page from a website in Internet Explorer, then you might think of reinstalling the XML Parser.

Link for downloading the XML Parser:

http://www.microsoft.com/downloads/details.aspx?Fa...

In case you are unable to install the above version, try the little older version: http://www.microsoft.com/downloads/details.aspx?fa...

Caution: Always create a restore point before installing any software which is as important like an XML Parser.

All the Best!

Cheers,

Manish

If your not using Corel Office, do get rid of it! This will save some disk space for other stuff! After you un-install do a defrag. Get AVG Anti-virus, Ad-Aware, Spy-bot Search and Destroy, and Windows Defender for your friends computer. They are all free downloads and work well. Update them and run them in safe mode.

You have newdotnet trying to load on your computer from an existing or old installation. newdotnet is spyware. All you have to do is remove it from the startup. start>run>msconfig>startup tab>uncheck newdotnet Do the usual spyware removal though too. Google search for "Symantec security scan". It's free and gives you a list of infected files which you can remove by going into safe mode (press F8 repeatedly when turning on computer) If you're real good, you can put your hard drive in another computer and delete those infected files with your infected drive as a secondary drive.

If this happens on start-up... I'd first remove the references to it.

Checking MSCONFIG and the registry.

uninstall this program, and try to reinstall it again.

it probably will help.

oh that happened to me too