Posts: 9,242
Threads: 140
Joined: May 2002
Reputation:
0
i have recently been having boot up problems with XP, my version is around 2 years old. It seemed to be hanging at the MUP.SYS driver and would go no further except in safe mode. After invading numerous forums... fora?.... and listening to far more intellectual people than myself, at least where PC logic is concerned, I tried all manner of suggestions until I came across one good one. DELETE THE DRIVER.
I did this and things seem OK now. I believe the driver is for connecting to Novell, whatever that is. As previously explained I just want to press a button and it works. The Blueyonder PC Guard is working well, on it's own and has detected and deleted a large number of spyware.
Posts: 9,242
Threads: 140
Joined: May 2002
Reputation:
0
The reason why I mentioned this, I've never come across the problem before until the last week or so and I was being persuaded by some it was a feature of "Service Pack 2" that somehow or other affected the boot up. I think I can safely say I've now squashed that theory, but why should it suddenly start happening and when it did I found that lots of other people. judging by the forums had been having the same problems, and why has Microsoft not done anything about it? I was even tempted to install Linux to change completely my operating system, but for the time being I'll leave it as the system seems to have stabilised now. FOR THE MOMENT.
Posts: 3,857
Threads: 266
Joined: Mar 2003
Reputation:
0
Congrats Noel, You are the only person that I have heard of who is operating PC Guard OK. My installation gave so many conflicts and lock-ups that I decided to discard it. I have several `paid for` programs - such as adware,pop-up and anti virus programs and ALL conflicted with PC Guard.
Whilst you were tackling your boot-up problem, I wondered if you had used your `go back`,or `revert drive ` utility.
Jim
Posts: 9,242
Threads: 140
Joined: May 2002
Reputation:
0
The answer was simple Jim, I disabled the conflicting programs and allowed PC Guard to run on it's own as advised, the instructions did say that if you didn't disable all other spyware/antivirus/pop-up programs that there would be conflicts and it wouldn't work properly.
. Did you try disabling them and running PC Guard on it's own? My son also uses PC Guard on my advice, his hard drive had slowed down so much as to be virtually unusable. He installed PC Guard, disabled the conflicting programs and it cleared the drive of it's problems within minutes of installing it. He is so impressed he has cancelled his BT antivirus/spyware monthly subscription.
I don't know what you mean by "go back" do you mean "restore to previous settings"? If you do, I did that and it worked first time then second time seized up again. I actually reinstalled everything using my RELOAD CD again!!! The boot up worked first time. Second time it seized again at MUP.SYS. At this stage I went on to numerous forums and ther eit was that I found that this is a very common occurence, well common enough for others to have complained about it.
Posts: 9,242
Threads: 140
Joined: May 2002
Reputation:
0
Darn it, I've had to restore MUP.SYS.
My PC Started to do all sorts of odd things and the only way I could get back on the internet was to restore the driver.
Now I'm flummoxed. Any suggestions anybody?
Posts: 9,242
Threads: 140
Joined: May 2002
Reputation:
0
Thanks Jim, I'll have a look at that. My disc is a RELOAD disc not called Windows XP. It wipes everything off the hard drive and estores it to factory condition. I have 3 options, one is to restore everything R, the second is repair Boot sectors B and the third C Cancel. This simply seems to take me back to a drive and I haven't a clue what to do after that. It ain't half annoying I can tell you. At the moment I can't access e-mail for some odd reason but I'll keep trying . Thanks again Jim I'll have a look at that now.
Posts: 3,857
Threads: 266
Joined: Mar 2003
Reputation:
0
I know that the above help link from David was aimed at Noel, but being nosey (and having a thirst for knowledge)I had a peek.
What a different slant that artical put on the problem.
Like Noel, I thought that the file the boot-up hung on was the problem one. How enlightening to dicover that the last file to show is the last GOOD one and it`s the NEXT one that is causing the problem.
So chasing info on MUP.SYS proved to be the proverbial wild goose chase. Thanks David.
Jim
Posts: 457
Threads: 9
Joined: Oct 2004
Reputation:
0
If you have startup problems then you can hold a specific key down on your keyboard during the boot process and choose the option for "Step by Step Startup" (different key for different computers), this gives you each line of the boot process and asks if you want to run that line. If you use this procedure then you just keep pressing 'Y' until you authorise the line to run that causes the boot process to hang. You then know which driver, or which line of the startup sequence is causing the problem.
