TSGL: Compaq Desktop With Boot Problem

[Glen Bigelow]

Don,

Thanks for the feedback...I had surmised as much...regarding the apparent
driver issue.  The strange thing is that the computer had worked since
purchased in April.  One would think that by restoring it to the build that
it supposedly started with...would eliminate any driver issues, but
apparently not.

There are no peripherals to contend with...no printers, scanners, etc.  Just
the Compaq, monitor, keyboard and mouse.

Fortunately, I contacted Compaq and they agreed it was hardware problem,
decided the computer was under warranty and are sending me shipping crate to
send to them for repair at no charge.  I don't know what they will do to it,
but I suspect that a motherboard replacement will be part of the solution.

Thanks to all for your suggestions and help.

Glen B.
Sacramento, CA

-----Original Message-----
From: list-bounces at tsgserver.com [mailto:list-bounces at tsgserver.com] On
Behalf Of Don Penlington
Sent: Tuesday, February 06, 2007 6:09 PM
To: Tech Support Guy Mailing List
Subject: Re: TSGL: Compaq Desktop With Boot Problem

At 10:40 AM 2/5/2007 -0800, you wrote:
>If you try booting into
>Safe Mode...again it gets to MUP.SYS and stops.>>


It's quite a common problem. Apparently more common on Compaqs because of 
all the proprietary junk they load at startup.

The problem is not with Mup.sys, but with whatever it's trying to load 
immediately following that.  Usually it's a driver problem, as drivers load 
immediately after mup.sys.

If you're using Compaq restore and boot disks, you're only repeating the 
same problem.

There are many reasons why Windows fails to load at this point--- there are 
100's of varied and different answers, with very few common threads and not 
much logic to it.  Try googling mup.sys for some possible leads. Very 
basically, it's usually a driver conflict.  Sometimes, removing all 
peripheral hardware helps, in case there's a printer, scanner, or whatever 
incompatible to Compaq. The problem is not unique to Compaq, but seems to 
be more common to brand names generally, with all their proprietary stuff 
which CAN be incompatible with certain hardware/software combinations.

In some cases it's an intractable problem and you'll need to reformat and 
load a clean (not proprietary) copy of XP.

Don Penlington


 From the Beach at Surfers Paradise in sunny Queensland.
Computer tutorials, local scenery,  and other things at my website:
http://users.tpg.com.au/deepend/index1.html


_______________________________________________
Tech Support Guy Mailing List
http://www.tsgserver.com/list/