Why you should not be using MSconfig to control startups!! http://forums.majorgeeks.com/showthread.php?t=149804 Many people frequently use MSconfig as a long term solution to control startup processes and services. You will also see many websites condoning use of MSconfig and teaching you how to use it for controlling startups. This is a very bad idea for many reasons. 1. MSconfig was designed to be used only as a temporary debugging/troubleshooting tool. It was not meant to be used for long term solutions. 2. MSconfig does not show all startups anyway. 3. If you uninstall programs while they are being disabled with MSconfig, they will not be uninstall properly and you will have to resort to manual registry editing to properly get everything removed. MSconfig will leave orphan entries if/when installed software is uninstalled while under the control of MSconfig . When/if MSconfig is turned back to normal startup, it will give errors on boot due to those orphan entries. 4. MSconfig and Services: o If you uninstall programs while you have some of the programs services being controlled with MSconfig, the programs will not be uninstall properly and you will have to resort to manual registry editing to get everything properly removed. o When you uncheck a service in msconfig, you completely disable it. If you uncheck the wrong one, you may not be able to restart your computer. o It is safer to control services by using Control Panel, Administrative Tools, Services (this runs services.msc). 5. You can lock malware items into your registry that you may not see anymore until some point in time where you switch back to Normal Startup mode and now you can cause total reinfection of your PC with the malware. You need to remove the malware not mask it. If you still don't understand why not to use MSconfig, see what Microsoft writes here: The key point is stated as such: http://support.microsoft.com/kb/310560

In firefox if you click tools at the top then add/ons you will see a list of add/ons installed one of those apparently is causing a problem if your not using any add/ons then uninstall them you will see the uninstall option there. I just want to make sure your not running fiefox in safe mode all the time.

I surprisingly ran into this same issue. I've called HP before, the first time being when i took my new Pavilion Slimline out of the box and the hard drive was not being recognised. I called and was immediately told that it was no longer under warranty. I said i had just bought it about 4 hours ago at a major retailer. I was told it didn't matter, apparently it was an older model that was on the store shelves for some time now. Four calls and three hours later my computer was working, sort of. I had a few calls in the past 9 months, usually for not booting properly or at all. I'm still waiting for recovery discs from about 9 months ago. Last night i came home and my computer was frozen. I had to reboot it. It ran the CHKDSK (again) and afterwards i was missing about 100GB of data. I called HP today. After he said his greeting i opened with "pending hard drive failure". There was no talk of recovery discs. He had me run the hardware diagnostics. Surface scan : HD535-2W. The fun lies in finding a service location in Calgary. He said they had service centres & partners EVERYWHERE. Their server was offline so we couldn't get it from their website. He gave me businesses to call. In a city of over 1000000 people you'd think there would be SOMEWHERE i could go to have the hard drive replaced. He was very helpful. I just wish their computers were too. It would save me all of these calls, from which i am taking a break. This would be the first time i got someone who really listened to me too. It's really nice when that happens.

Here's the issue with firefox, FF - user.js: extensions.BabylonToolbar_i.babTrack - affID=109936&tt=100512_2_ FF - user.js: extensions.BabylonToolbar_i.babExt - FF - user.js: extensions.BabylonToolbar_i.srcExt - ss FF - user.js: extensions.BabylonToolbar_i.id - b8457168000000000000bc7737387210 FF - user.js: extensions.BabylonToolbar_i.hardId - b8457168000000000000bc7737387210 FF - user.js: extensions.BabylonToolbar_i.instlDay - 15473 FF - user.js: extensions.BabylonToolbar_i.vrsn - 1.5.3.17 FF - user.js: extensions.BabylonToolbar_i.vrsni - 1.5.3.17 FF - user.js: extensions.BabylonToolbar_i.vrsnTs - 1.5.3.1715:35:37 FF - user.js: extensions.BabylonToolbar_i.prtnrId - babylon FF - user.js: extensions.BabylonToolbar_i.prdct - BabylonToolbar FF - user.js: extensions.BabylonToolbar_i.aflt - babsst FF - user.js: extensions.BabylonToolbar_i.smplGrp - none FF - user.js: extensions.BabylonToolbar_i.tlbrId - tb9 FF - user.js: extensions.BabylonToolbar_i.instlRef - sst FF - user.js: network.protocol-handler.warn-external.dnupdate - false FF - user.js: browser.sessionstore.resume_from_crash - false We will be getting rid of that, by running the tools above.