In article <(E-Mail Removed)>, "pc"
<(E-Mail Removed)> wrote:
> I am totally bewildered by the latest ASUS BIOS download for the ASUS
> A8N-SLI DELUXE.
>
> I download the BIOS. Great. What flash tool? It implies I need
> awadflash.exe v1.14, but that's not to be found. I have ASUS update
> V6.10.02 installed, I'll try that. But first....
Have a look here. The FTP directories use the same path structure as
the Support/Download page, and that can give you a few hints as to where
to look for stuff. You might also explore your motherboard CD, as there
can be some interesting files on there that may not be obvious if you use
the interface that appears when you load the CD into the drive. It is better
to access these tools from a Download page, as there can be warnings
associated with downloadable tools, and just getting them from an
FTP link means you won't see those warnings.
ftp://ftp.asus.com.tw/pub/ASUS/mb/flash/
>
> It instructs me to update chipset drivers to V6.65 or later. Great. I
> download and expand the zip file. It's got 10 files called
> MAKEDISK.EXE in it. Jesus.
Makedisk is used to make a floppy disk, for the F6 "install driver" stage
of a Windows install. If you are updating the drivers on an existing
install, the 30MB full installer might be a better choice. The 30MB
installer likely has an InstallShield to do the job for you. (In these
days of bloated universal installers, you'd be amazed how much of these
downloads simply isn't necessary. I was on a dialup modem over the
holidays and basically I couldn't repair squat on the computer I was
on, due to the "bloat" issue. Some of these installers have support for
like 20 languages, and an installer 1/20th the size, for a specific
language, would be a pleasant alternative.)
You could likely copy one of the folders from the 30MB download, onto
a floppy disk, and not use the Makedisk. That is if you needed to do
an F6 during Windows install or repair install.
I had a quick look and you're right. I cannot find docs to help you
understand what to do with a Makedisk executable. And going around
double clicking files until something happens is not exactly a clever
way to use computers - they should have included a quick note to go
with the download.
>
> So, I'm running XP 32 bit. That narrows it down to two files with
> PATARAID and SATARAID in the names. What do I nead PATARAID for? Does
> the IDE interface support RAID? News to me.
Nvidia is getting better at listing and explaining features on their
chipsets. Down at the bottom of this page, it mentions that their
RAID functions can span PATA + SATA disks. I've never read any
experiences in this group, mixing the two, so don't know whether
it works well or not.
http://www.nvidia.com/page/pg_20041015917263.html
>
> I run the programs and make floppies. The download page says the OS is
> DOS. Since the source is called MAKEDISK.exe I assume it will make a
> bootable floppy. NOT.
>
> What in the blazes am I spoda do with these things???? Put them on a
> DOS bootable disc? That's easy, but at this point I'm not comfortable
> going any further because the damn instructions are sooooo cryptic.
> What's wrong with these people?
The floppy you made, would be best if installing the OS for the first
time, or if you were doing a repair install to a disk moved from another
computer to this new motherboard.
I really recommend using the full (30MB) installer, just in case it
gives you an "Add/Remove" option for the list of installed software
on your computer. If you ever needed to back out, having InstallShield
clean up the mess is better than getting in there with a screwdriver
and trying to fix it by hand.
Generally speaking, if a folder has a .INF file in it, double clicking
on that may install whatever is in the directory. (At least I've had
that experience on one of my older Windows machines.) But some installer
directories have multiple .INF files, and figuring out what they do
is a painful way to do things. I think you can also go to Device Manager
and request to update a driver for a device in there, then point
Windows to the folder containing the .INF file. Using a proper installer
is a lot better than either of those options.
>
> Your inputs would be greatly appreciated.
>
> pc
>
<<snipped the file list>>
HTH,
Paul
Similar Threads
