Thanks for the feedback Paul this is an unusual situation that can be
remedied by a new build and doing right from the start. I have tried the
".inf" install and it does nothing as far as I can see. There is no
Promise
in device manager so that option is out at this point. I have done the
BIOS
as outlined and still nothing.
I like all things have spent too much time on this whenever I get into a
situation like this it is easier to "fdisk" and start over. I can also
install the PCI card that came with the Raptors and go that way if I don't
want the clean build but the clean build is the way to go.
I have used Everest and the original AIDA32 for a long time I tried to
find
out what you were talking about but didn't see it.
As far as your last paragraph, LOL, I won't even go there, been there done
that, and it just takes too many brain cells to get it done, clean install
is more fun!
Again, thanks for the input.
--
Don Carlson {371653}
"Don" said:
I have this MB and was going to use more drives and don't have the
Promise
Controller in Device Manager. I went into the BIOS(1018) and enabled it.
I
know that loading this driver is usually done on a fresh build but is
there
a way to do this after the fact. I have downloaded the new drivers from
ASUS
but can't figure out how to get these loaded. It states that you can
update
drivers from Device Manager but I don't have the SCSI icon in there to do
this.
Suggestions please!
I have a copy of 378ata_100104528.zip and it looks like an INF style
install. I think if you go to the WinXP folder, after the file is
unzipped, then double click the "UlSata.inf" file, that would attempt
to install it. Similarly, if you had the Promise device in the
Device Manager, with a ? on it, you could try offering the INF
in this folder for the purpose of updating the driver.
If you want to have a look at the devices in your system, get
a copy of Everest Home Edition from lavalys.com . You can get
PCI Device/Vendor information from there. If there is a Vendor 105A
Device 3373 entry, then updating with that UlSata.inf file should
work. This is the string in the INF file:
PCI\VEN_105A&DEV_3373.DeviceDesc="WinXP Promise SATA378 (tm) IDE
Controller"
The "makedisk" utility and the floppy route, are what you use
if you are installing the OS on the Promise SATA in ATA mode.
Pressing F6 and using the floppy is what you do, so that the
install can boot from the newly installed hard drive. If these
are just data disks, all you need to do is install the driver any
time after the OS is installed, assuming the Promise chip is
actually visible to the OS and ready to run.
BIOS settings:
Onboard Promise Controller [Enabled]
Operating Mode [IDE]
I vaguely remember someone posting about having difficulty with
the ATA driver, after having installed the RAID driver. If I
was stuck in a mess like that, I would start by reading the
INF file used by the RAID driver, to get an idea as to exactly
what the RAID install has messed with (registry, adding services,
etc), and attempt to undo it. Just removing the driver files is
only the tip of the iceberg, and if you don't know what you are
doing (like me
), trouble awaits...
Paul
