PCBUILD Archives

Personal Computer Hardware discussion List

PCBUILD@LISTSERV.ICORS.ORG

Options: Use Forum View

Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Rick Glazier <[log in to unmask]>
Reply To:
PCBUILD - Personal Computer Hardware discussion List <[log in to unmask]>
Date:
Fri, 17 Aug 2001 13:12:48 -0400
Content-Type:
text/plain
Parts/Attachments:
text/plain (56 lines)
I'm answering ONLY the reply with the sender and time
as listed at the end, below.
I refer to that exact message because the quoting is way
out of hand, and I did not want to include it all (or any)...

The first thing I would do is back up the Registry, and
know how to restore the back-up.

That will allow you to recover to the "state" you are in now,
unless you change files and things on the hard drive that pertain
to your busmaster hard drive controller drivers.

This problem usually shows up for me when I damage my
Busmaster Drivers, or install the wrong version or type.
(Or even try to change them...)
Changing MotherBoards is enough to easily get you into this
situation with a VIA chipset MB.  I think that is what you did.
(This is how I get into this.)

I was actually waiting for others to give a "magic bullet" type
of answer, as this can be a real problem for me on occasion.

I read something about removing an entire section of the Registry
to force Windows to Re-Enumerate ALL your hardware.
I never used that method, and was not paying attention.
(It is not the kind of thing you try for "kicks" on a system
that is working well...)

I think what is happening is this: Windows is looking in the Registry
and installing the wrong drivers for your MB chipsets.
They are only close, but good enough to fool Windows into
trying to initialize them.

Once Windows tries to actually use them, they fail in some way,
(since they are the wrong ones), and you are forced into SafeMode.

I have no further answers or advise, other than to clone the HD if you
can, and only work on fixing the Cloned copy.
This will give you more than one attempt at solving the problem.
(And is a fool proof way to get back to at least where you are now.)

Good luck.  When you are done, make sure all your drives are
NOT running in compatibility mode.

                   Rick Glazier

----- Original Message -----
From: "joseph marty" <[log in to unmask]>
To: <[log in to unmask]>
Sent: Friday, August 17, 2001 7:08 AM
Subject: Re: [PCBUILD] Forever booting into safe mode

              The NOSPIN Group is now offering Free PC Tech
                     support at our newest website:
                          http://freepctech.com

ATOM RSS1 RSS2