Re: How Do I Get Rid Of A Raid Controller I Do Not Have



On Tue, 23 Dec 2008 18:27:18 -0600, VanguardLH wrote:

BobN wrote:

On Mon, 22 Dec 2008 23:53:05 -0600, VanguardLH wrote:

BobN wrote:

On Tue, 23 Dec 2008 02:01:32 +0000, Adrian C wrote:

BobN wrote:
I am running the retail Windows XP Home SP2.

I replaced my CPU HS/F when my original fan died. Ever since, when I boot
I receive the message that windows has found a new raid controller. It is
listed in yellow in device manager. I uninstall and it pops up again. I
do not have a raid controller. I have never had a raid controller on my
machine.

Well you do now, probably part of the motherboard chipset. Perhaps you
may have accidently enabled it in BIOS?

I have a single EIDE drive. How do I get rid of that which I do
not have?

Either ignore it, or find the drivers. Either the manufacturer of the PC
or the motherboard will have it available for download.

I changed nothing except the HS/F. Why would I want drivers for that which
is not on my machine? Do you think installing drivers for that which is
not there is an improvement?

It *is* on your machine. The controller is on your motherboard.
Windows detected its presence and wants you to install a driver for it.
Alternatively, instead of uninstalling the device (which only results in
Windows scanning the hardware and finding it again on the next reboot),
just disable it. Or you could go get the drivers for that device from
whomever is your motherboard maker (or the computer vendor if you bought
a pre-built). Hard to tell what you have since you never identified
either the motherboard brand and model or the pre-built computer's brand
and model. Go look at their specs. You'll see they mention a RAID
controller.

There is no raid controller on MY motherboard. Maybe on yours, but not on
mine.

And you continue to keep secret the make and model of the motherboard
why?

I built the computer. It is not "pre-built." You are missing the
point.

Since you built it, you surely know the make and model of the
motherboard.

Since I did not have a raid controller for three years, why do I
have one after changing a HS/F?

Perhaps you installed a chipset driver that includes the RAID support.
For example, on old Abit mobos, you got a chipset driver package with no
RAID support (although there was a RAID controller on the mobo) so you
wouldn't get any RAID support, or you got the chipset package with the
SATA driver that included RAID support so then you would get RAID
devices detected.

The BIOS doesn't change. It's burned into EEPROMs (so you'd have to
flash the BIOS to change its contents). Normal operation has the BIOS
EEPROMs copied into the CMOS table copy of the BIOS and it is the CMOS
copy that gets used during the bootup. If there was a change in the
CMOS table then perhaps now the SATA device setup in the BIOS has RAID
support enabled. That change may have been accidental, due to a weak
battery and the CMOS losing its settings (which means they have to be
reloaded from the fixed defaults recorded in the EEPROMs), or the CMOS
table somehow got corrupted with the result that RAID support is now
enabled. Have you checked your BIOS settings to see if RAID support is
listed anywhere? If listed, is it enabled?

How do you have the Automatic Update service configured in Windows (for
Windows Updates)? Do you have it set to only notify you of updates or
do you let it download and install updates without ever prompting you?
When you visit the Windows Update site, have you ever downloaded and
installed suggest hard driver updates from there? NEVER get hardware
updates from the Windows Update site. Just use that as a prompt to go
look at the hardware maker's web site to see what is the latest drivers
for your particular hardware. The Windows Update site has been known to
be wrong in its detection of hardware and gotten a mismatch on the
driver (so you are presented with the wrong driver). Also, it can take
a long time to get a defective driver off the Windows Update database.
A hardware maker may decide a new version is unstable or causes problems
and withdraw that version, but it's still listed at the Windows Update
site. Many hardware makers incur consternations in trying to get their
bad drivers off the Windows Update site before impacting their users.
Promise had a bad driver that took almost 3 months to get off the
Windows Update site.

See my final post below.
.



Relevant Pages

  • Re: How Do I Get Rid Of A Raid Controller I Do Not Have
    ... I receive the message that windows has found a new raid controller. ... Windows detected its presence and wants you to install a driver for it. ... updates from the Windows Update site. ...
    (microsoft.public.windowsxp.hardware)
  • Re: How Do I Get Rid Of A Raid Controller I Do Not Have
    ... I receive the message that windows has found a new raid controller. ... Windows detected its presence and wants you to install a driver for it. ...
    (microsoft.public.windowsxp.hardware)
  • Re: FreeBSD 7 load hangs on boot
    ... I've tried turning off all RAID ... I even tried Windows Vista ... It didn't hang, but it found no storage devices. ... the board's manual that to load Windows XP or Vista, a special driver ...
    (freebsd-questions)
  • Re: W9xNT MCA Adapters - RAID-207
    ... SCSI port ... MDAC206 supports the following DAC960 based SCSI RAID Controllers in high ... performance busmastering mode with 32-bit addressing on Windows NT and 9x: ... Two versions of the driver are provided, ...
    (comp.sys.ibm.ps2.hardware)
  • Re: Updated computer - now it runs like crap
    ... >I recently did a Windows Update for my laptop for Windows Professional 2000, ... then the Processor driver is not the cause of your slowdown. ... Click the "Roll Back Driver" button and roll it back. ...
    (microsoft.public.windowsupdate)

Quantcast