K9A Platinum Raid Drivers = Information

Just figured I would let everyone know that for some reason MSI has two Raid Drivers listed for this. The "IDE" Raid Drivers are the actual ATI Raid Drivers.
Why they have SI Drivers, the "SATA" raid drivers, listed is beyond me. I grabbed them first thinking they were what I needed only to discover "after" I was home from my Fiance's w/ a Laptop with no floppy that they were the wrong drivers.....

Does anyone know where I can get working drivers? Because without them, I can't get the Windows installation to detect my hard drives.

Similar Messages

K9A Platinum Raid Drivers, Windows Install Issue

I unzipped the "ATI IDE RAID" driver to a floppy, but I can't get the windows install to recognize it. It just goes to the "Please insert the disk labeled 'Manufacturer-supplied hardware suppor disk' into Drive A: and press ENTER" screen. I'm not sure what's wrong, as everything is connected, am I doing something wrong making the disk?

Yeah, I've used two different ones, and they both work fine on the computer I'm writing them with, I was wondering if you had to mess with the files, like put them all in the same folder or somesuch (I've tried that), or if you just unzipped to the diskette (tried that too). Is there cause to suspect the drive itself at this point?

K9A Platinum RAID - Be careful if you're considering this MB

Unbeknownst to me when I purchased this board to replace my ASUS P4S8X which had a Promise FastTrak 376 SATA RAID controller, when you create a mirrorset on the K9A Platinum you *cannot* preserve data. In my wildest dreams I didn't think that would be that way so I never thought to ask before I bought it. A RAID controller that can't preserve that data on one of its members?? Mind boggling to say the least.
Yes folks and it's true, confirmed by MSI support:
"ATI Raid Controller does not support this feature which is the chipset limitation which you will need to create the raid array and have a fresh install."
That's real nice eh? Completely re-install everything from scratch? <<Removed>> I just did that a week and an a half ago when I lost the MBR after a failed disk and Windoze fixmbr clobbered the partition table. That took 16 hours not including the Windoze install time. Don't want to do that again.
Plan B: Boot a knoppix CD and use dd_rescue to duplicate the disks then create the mirrorset, sync them and cross my fingers.
But that's only the half of it. In playing around with changing the IDE setting from Native IDE to raid, XP blue screens after the Logo with a 7b error. Haven't looked into that yet but I suspect it's because it doesn't have the drivers for the now raid controller. I'll worry about that once I have a sync'd mirrorset created.
When the IDE chipset is set to RAID in the BOIS I tried booting Windoze install disk and adding in the drivers for the now RAID chipset, it fails every time. I think I'm using the right drivers, need to confirm that, ahci8086, but every time it tries to load the driver it tells me that ahci8086.sys is corrupt. I've downloaded it numerous times with the same result. Same thing with the one off the included CD. The ahci8086.sys file is dated 5/18/2006 and I've got the latest which is dated 7/27/2006 which I don't think I tried yet but plan too. If I'm using the wrong driver for when the IDE BOIS is in RAID mode, please let me know but that's what is delivered in the ATI SB600 IDE RAID download so I assume that would be correct. Or maybe I'm supposed to be using one of the Silicon Image driver sets, I couldn't find any information anywhere on what is the correct driver.

I got censored?!?! I don't know where this Forum is headquartered or based, but here in the United States of America we have a thing called "Free Speech" that protects the citizens of our Country from exactly what has just occurred here.
What was censored wasn't really that bad, no profane language or anything, just a reference to the shortsightedness of some engineers. I hope this isn't a Forum where you're only Welcome if you post "MSI is GREAT!" and are not allowed to even whisper anything even slightly negative about them...
As a background I've been in IT support roles for around 25 years. Managed Digital Equipment Corp. VAX's and Alpha's (VMS, ULTIRX, and Tru64 UNIX, started using VAX's in 1978), Sun's Enterprise large servers and assortment of other SPARC boxes (Solaris), IBM 6x0's, and a host of smaller systems running both UNIX and Linux. I cut my teeth on DEC's ULTRIX.
That said, to come across a RAID controller in the year 2006 that will not allow you to preserve the data on one of its members when creating a mirrorset is just unconscionable. So I made reference to the shortsightedness of the engineers by referring that they might be something, and that got censored. I was hoping that might be a wakeup call to these engineers, sort of like a 2x4 upside the head, so they don't make a mistake like this again.
And I learned something else about the ATI SB600 South Bridge RAID controller which once again is just unconscionable. If you take a disk with a filesystem on it, with data, and have the SB600 present it to the OS as a JBOD, it clears the partition table. What!?!? Yes. There is no warning that this is going to occur. Promise's FastTrak controllers *do not* wipe out the partition table. They just present any disk that is not part of a mirrorset to the OS. That seems like a really good idea, ya think? But the SB600 don't do that, it doesn't present the disk to the OS unless it is part of and LD so you have to assign it to one as a JBOD. Poof! Partition table gone!
I just cannot fathom the mindset of the engineers that created the ATI SB600 South Bridge RAID functionality. They just do not seem to be aware of what is expected of a RAID controller in this day and age. They must live their life very sheltered and not have any idea of what other vendors are doing and what the users of their products expect.
Bottom line: The MSI K9A Platinum seems to be a decent MB, but better suited for an full install from scratch then as a replacement MB for an existing, running, seasoned system, if the objective is to use the SB600 RAID controller and preserve existing data on existing disks. I know there's multiple ways to get around this, but that's jumping through hoops that I never had to jump through before.
If anyone is interested I was able to use my existing disk's mirrorset and preserve the OS and data on them.
The steps:
1. Know which is the disk you want to use and duplicate the data from, like Port 1 Master (this is related to SATA drives connected to the MB).
2. Using the FastBuild BIOS Utility create a mirrorset using the two drives. Set Gigabyte Boundary to OFF, set Fast Init to OFF. DO NOT SET Fast Init TO ON, YOU WILL LOSE YOUR MBR!
NOTE! NOTE! NOTE! If you're so inclined to use the ATI SATA RAID Utility that you can get from MSI's website to initially create the mirrorset that comes along with WebPAM which you put and use on a bootable floppy, DO NOT "Initialize Array", DO NOT "Synchronize Array", NO, NO, NO!
3. Boot the OS if it will boot but I doubt it BUT DON'T LET IT BOOT INTO THE OS. With the OS only really on one of the disks I don't know what would happened and if the RAID controller uses the "Read Least Busy" algorithm who knows what will happened.
4. Power down the system and unplug the SATA drive that DOES NOT have the OS on it.
5. See if the system will boot. If so great, proceed to step 7.
6. Do what you have to do to get the system to boot with only the one, original drive connected and in the mirrorset. Ignore for now the FastBuild warnings on boot that mirrorset is CRITICAL. In my case I had to use the Windows XP install CD and Repair an existing installation.
7. Install from MSI ATI's WebPAM utility.
8. Power down the system.
9. Connect the SATA drive that is to be the second member of the mirrorset that you disconnected in step 4. Power up the system. When you get FastBuild's warning that your mirrorset is CRITICAL ignore it. DO NOT GO INTO THE FASTBUILD BIOS AND DO A REBUILD THERE. NO! NO! NO! I tried that once on a 500GB mirrorset and after 8 hours with the drive activity light blinking sort of dimly it's progress was still at 0%.
10. Once the OS is running (Windows I presume, XP Pro in my case), start WebPAM. if all went well you will see that WebPAM knew the mirrorset was missing a member, found the FREE drive you reconnected in step 9, and is already in the process of rebuilding the mirrorset. If not, you can manually start the rebuilding process in WebPAM.
Of note, WebPAM only took somewhere in the neighborhood of 2 to 3 hours to rebuild the 500GB mirrorset as opposed to the BIOS rebuild running for 8 hours and accomplishing nothing. (This wasn't a one time anomaly, I had tried it before letting it run a few hours and saw no progress. The 8 hour run was just to be sure.) While the WebPAM rebuild is running you are in Windows and it is running and you could do other things. I didn't though, I left it run until it finished.
There ya go, a rather unorthodox way to make a mirrorset on a MSI K9A Platinum preserving your OS and data and getting around the shortcomings of the ATI SB600 South Bridge RAID implementation.
And I know I could have used Ghost. But that is in hindsight. I would have had to know I needed to do that *before* removing and replacing the MB. But I didn't do that, because I didn't know I was dealing with a brain dead RAID controller.
<Added some more info in the steps.>

K9a Platinum MOBO Drivers or Sapphire?

Hello,
I am set up on a k9a Platinum and am also running two Sapphire Radeon 1950 Pro (w/crossfire). My question is simple and ask forgiveness if its already been addressed. When I am installing from anew, MSI provides the AMD Chipset driver, which is just a bundled AMD/ATI Catylyst Control Center (w/display, c++ Vis basic, etc.) Do I also install/update with the package from Sapphire Tech?

Yes, the MSI driver is for Chipset (although it seems to install CCC) but not Graphics drivers (unless you have integrated video).

K9A Platinum audio drivers won't install

I am trying to install the audio drivers for my K9A Platinum off of the cd that came with it and it gets about halfway through and the it says "Install Realtek HD Audio Driver Failure !!" Does anyone know what I could do?

Well, check all things already mentioned...
- Bios: onboard sound enabled?
- clean Windows install;
- also, you can try the native drivers (not from MSI-website, but from Realtek's)
@Fredrik: I'm not going to spend time trying to understand Windows. XP is pretty good, but it still can be as stupid as possible... No use digging up the causes, there are too many possibilities that can cause the problems. Also, keep in mind that far most of the people don't get these problems. It looks like everyone has this problem, but that is because this is a tech support forum... people don't get in here to tell us that soemthing is working all right.

K9a platinum raid setup options?

few quick questions.
for raid 0 what do the following options mean?
gigabyte boundary? default is on. should it be?
next is fast write default is off but i turned it on?
stripe/block size? is smaller better or bigger better?
lastly, can i partition a raid 0 array? or is it a bad idea?
thanx.
p.s. i already set mine up but maybe when i upgrade to vista later i would like to have a better understanding of it.
i set my boundary to on, my fast write to on and my stripe/block size to 64k since it matches the block size for my NTFS. drives are 2 wd 150 gb raptors.

Quote from: msiguy on 26-September-07, 08:31:02
few quick questions.
for raid 0 what do the following options mean?
gigabyte boundary? default is on. should it be?
It means that the raid-size is in GB's only and not parts of them. Just leave it like it is. No reason to mess around with it.
Quote
next is fast write default is off but i turned it on?
I don't know what it does exactly, but I suppose it has to do with the way data is written to the array. I'd leave it at the default value for now.
Quote
stripe/block size? is smaller better or bigger better?
There is no good answer to that. You need to understand first how a striped array works. For example: if you have a raid 0 with two disks, the following situation exists. When the blocksize is set to 64kB and you write a 128kB file, the file is split in two 64kB parts. Those parts are written to both disks at the same time. So, disk A receives one part and disk B receives the other part at the same time. Now, the smaller the blocksize is set, the more files will be split. (You see, a 64kB file cannot be split in smaller pieces, since it is equal to the block size of the RAID-0).
So, the answer is something like this: if you use many small files, setting a small blocksize is better (for example, when you install Windows on the RAID). When you use it for data storage (many large files), larger blocksizes are better. If you are not sure, set it to 64 or Auto.
Quote
lastly, can i partition a raid 0 array? or is it a bad idea?
Yes, you can. No problem.
Quote
thanx.
You're welcome!
Quote
p.s. i already set mine up but maybe when i upgrade to vista later i would like to have a better understanding of it.
[/size]
I hope you will wait a bit with that ....
Quote
i set my boundary to on, my fast write to on and my stripe/block size to 64k since it matches the block size for my NTFS. drives are 2 wd 150 gb raptors.
If it is working fine now, just leave it alone.
Note this: if one of your disks gets damaged, or when data is lost from it, you will lose the whole RAID array and all the data on it. So, it is important to backup everything regularly.

MSI K9A Platinum and VIA drivers issue? XP 0x0000007B stop error.

I get a Windows Stop error when trying to boot into Windows XP with new components. The SATA hard drive (and Windows XP installation) is from the old computer.
The new computer components are:
MB: MSI K9A Platinum, chipset: RD580 (North Bridge), SB600 (South Bridge)
CPU: AMD Athlon 64 x2 5600+, boxed (the cooler and fan came with the CPU).
Video: MSI Radeon 1950 XTX
The old (and working) computer setup is:
OS: XP Professional
MB: Abit AV8-3rd Eye, chipset: VIA K8T800Pro + VT8237
CPU: AMD Athlon 64 3500+
Video: Sapphire Radeon 9800Pro All-in-Wonder, videodriver: atidvag.dll version 6.14.10.6542
HD: Maxtor 6B200M0 SCSI Disk Device
BIOS: Phoenix 6.00PG 20.04.2005
System drivers with "via" in the name: VIAAGP1.SYS, viaide.sys, viasride.sys
VIA 4in1 (Hyperion) version: 4.55 (that can be found at HKEY_Local_Machine\Software\Via4in1Driver).
VIA 2.20e SATA/RAID driver was used when installing this computer setup.
The precise stop error is:
0x0000007B (0xba4c3528, 0xc0000034, 0x00000000, 0x00000000)
From many sites I have gathered that the error is related to Windows XP not being able to access a critical system drive. Most probably the SATA hard drive issue.
The problem probably is the VIA drivers of the old motherboard and/or the SATA driver.
First I should mention, that MSI K9A Platinum does not have a hard disk SATA driver. If it does, I have been unable to find one. Certainly no such floppy disk included, and no such driver in the MSI's Web page for this motherboard.
Second important point: I never used RAID. I did use VIA 2.20e SATA/RAID driver disk when installing Windows XP to the old computer.
Strange that the hard drive model is reported as a "SCSI Disk Device". It's not a SCSI drive however: it's a SATA disk.
I have tried to uninstal the motherboard chipset drivers (Hyperion v4.55), but there seems to be a bug here: the drivers should be uninstalled using the installation program, and select the uninstall option. However, I do not get the uninstallation option to choose at all! Yes, I'm using the normal installation mode, not the quick installation (although tried that, too). The Hyperion setup program just installs, and asks to reboot the computer. After rebooting and trying again, it still does not offer me an uninstallation choise.
I know how to install hard drive VIA SATA driver, but I have no idea how to uninstall it. And I'm afraid to do that without certainty that it IS the solution, since I could not access the hard drive any more in the old computer setup (and return to read this forum). Also, I do not have a floppy drive any more. Anyone know if there is an issue with K9A and XP having VIA SATA driver installed?
When I tried the new computer setup, I first tried the simplest possible hardware combination: there were no CD/DVD-drives, no (parallel)IDE hard drives, and no PCI cards, except the MSI video adapter.
My BIOS Setup experiments. None of these helped: got the same stop error each time.
1) I didn't much touch the BIOS setting first. Just tried to boot with the settings BIOS came with.
2) Next I disabled the integrated audio, LAN and IEE1394 devices and floppy drive and disabled all other choises except the SATA drive as a boot device.
3) Next I tried with the fail-safe BIOS defaults.
4) Cleared CMOS.
5) Changed OnChip SATA type from Native IDE to Legacy IDE. (Only one boot attempt with the setting as Legacy.)
6) Disabled PCI IDE BusMaster.
7) Never touched anything in the Cell Menu: so the settings are in minimum.
A step I have taken after the last attempt: run Windows XP hard drive error-checking tool to every logical drive with the fix option selected, and the system drive also with scan the bad sectors option selected.
My plans next are:
1) to install a newer Hyperion driver. If that would correct the no-unistallation-choice-bug,
2) to disable USB-devices in the BIOS (desperate),
3) to choose the Windows general video display driver (although I seriously doubt this is a display driver problem!).
4) to uninstall the Anti-Virus software (Avira Antivir).
I've read a numerous Web pages so far about the 0x0000007B stop error. Here are some links:
Quote
http://www.seagate.com/www/en-us/support/knowledge_base/
Stop 0x0000007B or INACCESSIBLE_BOOT_DEVICE
This Stop message, also known as Stop 0x7B, indicates that Windows XP Professional lost access to the system volume or boot volume during the startup process. This error always occurs while the system is starting and is often caused by one of the following:
* Hardware problems
* Corrupted or incompatible storage drivers
* File system problems
* Boot sector viruses
* Outdated firmware
During I/O system initialization, this error can occur when:
* The controller or driver for the startup device (typically the hard disk) failed to initialize the necessary hardware.
* File system initialization failed because the system did not recognize the data on the boot device.
Quote
http://support.microsoft.com/kb/314082
You receive a Stop 0x0000007B error after you move the Windows XP system disk to another computer
SYMPTOMS
After you move the Microsoft Windows XP system (boot) disk to a backup computer, you may receive the following Stop error when you try to start the Windows XP-based backup computer:
STOP: 0x0000007B (0xF741B84C,0xC0000034,0x00000000,0x00000000)
CAUSE
This error may occur if the registry entries and the drivers for the mass storage controller hardware in the backup computer are not installed in Windows XP.
RESOLUTION
To resolve this error, use the same hardware for the backup computer.
Heh, heh! Very nice Microsoft, but I plan to update my computer, so I NEED to use different components
Quote
http://support.microsoft.com/kb/324103
Device Driver Issues
You may receive a "Stop 0x0000007B" error message in the following scenarios:
•   A device driver that the computer boot controller needs is not configured to start during the startup process.
•   A device driver that the computer boot controller needs is corrupted.
•   Information in the Windows XP registry (information related to how the device drivers load during startup) is corrupted.
Hardware Issues
You may receive a "Stop 0x0000007B" error message if there is a resource conflict between the boot controller and another controller or between SCSI devices. You may also receive this Stop error message if drive translation is not being performed or if drive translation was changed. To troubleshoot this issue:
1.   If an IRQ or I/O port address conflict exists between the boot controller and another controller, Windows XP either stops responding (hangs) or displays a "Stop 0x0000007B" error message. If you recently added new hardware, remove the new hardware or reconfigure it so that it does not conflict with the resources of any other installed controllers.
2.   If you are using a SCSI hard disk, check the SCSI chain for correct termination. Remove any unused SCSI devices or make sure that each SCSI ID is unique.
3.   Make sure that drive translation is turned on (if it is required) and that it has not been changed. For example, if you recently switched controllers, this issue may occur. For additional information about this issue, click the following article number to view the article in the Microsoft Knowledge Base: 314082.
Quote
http://support.microsoft.com/kb/316401/
SYMPTOMS
When you start your Microsoft Windows XP-based computer after you replace the motherboard on the computer, you may receive a Stop error message that is similar to the following:
STOP 0x0000007B INACCESSABLE_BOOT_DEVICE
CAUSE
This issue may occur if the new motherboard contains an embedded IDE controller that has a different chipset than the original motherboard.
RESOLUTION
Method 1: Perform an in-place upgrade of Windows XP [<- That means repair installation of Windows XP]
•   Do not use a repair or in-place upgrade if you suspect disk problems.
Method 2: Repartition and format your hard disk and reinstall Windows XP

Alright I got the situation over.
Quote from: Roskaposti on 19-May-07, 04:44:59
My plans next are:
1) to install a newer Hyperion driver. If that would correct the no-unistallation-choice-bug,
2) to disable USB-devices in the BIOS (desperate),
3) to choose the Windows general video display driver (although I seriously doubt this is a display driver problem!).
4) to uninstall the Anti-Virus software (Avira Antivir).
I did try all all the above, and none of them helped.
And by the way: after installing the new Hyperion (VIA chipset drivers), I was finally able to also uninstall. It also uninstalled the IDE SATA (I think) and PATA drivers.
But what I had to do, was to make a REPAIR installation of Windows XP.
So, I was wondering now afterwards: this is really, really silly. Why the hell we need to re-install Windows if we move the SYSTEM SATA drive to another computer? We don't have similar problem with parallel IDE drives. Whom should we thank here??
The issue is to insert the driver files and the information of the ide drivers Windows should use with the next boot. How can it be this difficult?
What you basically need is..
- the information about the new chipset's PCIIDE.SYS/[VENDOR_PROVIDED_FILE].SYS and ATAPIIDE.SYS inserted into the values in HKEY_LOCAL_MACHINE\SYSTEM\ControlSetXXX\Control\CriticalDeviceDatabase
- and the vendor's IDE drivers to the %SYSTEMROOT%/System32/drivers folder.
Maybe something else, I don't know. But the problem was, Windows didn't know how, or what drivers to use. That can't be so big problem you need to install the whole OS anew!

K9A Platinum - Not seeing RAID Array on restart...

Hello again guys...
Here's the deal...
The computer will not recognize the RAID array when I choose to restart from inside Windows. If I press the reset on the computer or I do a shutdown then reboot, it works fine. Also, this morning I finished a clean install of Vista 64 and forgot to turn off sleep mode like I normally do, and when I came back home I got a tasty blue screen. When I tired to restart I got a message stating that the RAID driver was corrupt or missing. I reloaded Vista again, but I still have the issue of the machine not seeing the RAID array upon restart, and I have tried this about 10 times with the same results.
Restart = No Recognized RAID Array.
Cold Boot, Reset Switch or CTRL+ALT+DEL = No problems.
My system specs are in my sig below.
There was one other tidbit, I had a problem with this motherboard failing to load Windows with 4GB of RAM installed when I first got her, and thru this forum and the MSI help center, it was suggested I update my BIOS to a beta version that was out at the time. I see now that the version is now a standard release v1.6, should I go to the release BIOS or just stay with the current one?
Thanks for your time!

Yes I can. I first installed XP Pro since I was testing system stability with my new 6000+. Every soft reboot results in the array being undefined. I have to wait until the controller scans and says there is no array, then I can reset it to make it see the arrays. If I reset before the controller scans, it still shows no arrays.
Vista 64 Ultimate will only install on my K9A platinum if the following is true:
1) The SATA controller is in RAID mode, I have 4 SATA HD's, none are striped, and my DVD is external
2) The desired HD/array must be the first boot device, if the DVD is first it will refuse to recognize the partition as valid to use
If I use Native IDE or AHCI mode, Vista doesn't see any partitions. If I use Legacy IDE mode, Vista will start the install, but on reboot the motherboard pauses for 5 minutes and tells me the HD has an error and I have to hit F1 to continue.
I only recently got Vista 64 Ultimate stable again. I was having a problem where the system would power off instantly when it reached the desktop. I replaced the power supply. I then had trouble getting the drivers installed without crashing the OS. One thing I noticed while reinstalling Vista is that Microsoft automatically updates the driver for the RAID Controller. The driver version is 2.5.1540.41 and the version that the ATI 7.6. and 7.7 want to install in 2.5.1540.36. That would put it out of sync with the ATI RAID Console driver. The next reboot would result in crashing. Can't prove that is why though.

K9A Platinum Low Raid 0 Performance?

hi i just build this pc a few days ago and i did some tests on my raid using HD Tach (and on a website called pcpitstop.com)
both of these seem to be reporting my hard drives are doing no more than 80MB/s ... even though i have setup RAID 0 for 3 drives on the utility with the motherboard,
a friend of mine (who uses 4 drives in raid 0 of EXACTLY the same type of hard drive) gets more than 320MB/s on his drives ....
i fail to see how 3 of my drives = 80 MB/s, whilst 4 of his = 320MB/s
I installed the driver and took off the jumper at the back of the drive (to make them SATA II)
I checked the RAID config utility and all the settings seem to be perfect, however the drives seem to be failing to deliver the transfer speed i am looking for ...
My IDE drive is comparable to this setup, which kind of defies the point of me paying so much money for a RAID setup that's giving me the performance of only one of my drives
Windows recognises one drive, and says RAID 0 so i guess the RAID is working it's just not performing properly
Any help or suggestions would be greatly appreciated,
thanks

Quote from: Hans on 14-June-07, 03:56:02
Hi!
Please read Moan Guide first.
In general: RAID-0 performance is often exaggerated, although your speed seems to be too low. RAID-0 speeds depend on many things: the way the RAID has been set up (block/chunk size, driver, disks, controller, etc). Furthermore, different bench tools will show you different speeds, so don't depend too much on what a tool tells you.
*Edit: don't confuse burst speed with average read/write speeds! The burst speed can exceed the read/write speeds by a factor more than 2!
Some tips you may want to try:
- enable/disable NCQ (Device Manager -> SCSI/RAID-devices);
- try a different block size;
- try a different/newer driver or try the driver that came with the board;
- use the manufacturer's disk tool to have all disks checked for any errors. You may need to connect them as if they are IDE's to make them being recognized properly.
Then this: As far as I'm aware, Windows will not show RAID-0, unless you set up the RAID through Windows disk manager (system tools). If you did setup through Windows disk manager, please setup RAID again using the RAID bios on you board.
hey thanks for the reply, i'll try and give you some more info on what's going on;
firstly some more computer specs:
CPU: AMD Athlon 64 bit dual core 5000+
Graphics: ATI x1950XT-X Crossfire Edition (Single card at the moment)
Mobo: K9A Platinum (havent updated bios yet)
PSU: OCZ GameXStream 700W
RAM: Corsair 2GB DDR2 XMS2 Dominator DHX PC2-6400C4 TwinX (2x1GB)
HDD: 3xSeagate Barracuda 7200.10 320GB ST3320620AS SATA-II 16MB Cache - (Took the jumpers off the back to make them SATA II)
The motherboard uses the ATI XPRESS 3200 chipset, which supports up to 4x SATA II Drives, this is what i have used to connect the hard drives to. The Motherboard also offers a RAID utility for 0,1, and 0+1 RAID - i have used raid 0 with block size 128KB (it offered 64 or 128), FastInit was ON, and the other 2 settings i couldnt change, i activated all drives to the array and setup (in the BIOS) for the SATA's to be seen as a RAID configuration.
The latest drivers i used was catalyst 7.5 available from ATI website, the drivers on the CD dont work because i use Vista 64, and the CD says it doesnt support my OS, so i downloaded them.
In response to windows seeing the RAID .... i meant it see's one normal hard drive but the disk comes up as a RAID SCSI device in Propeties -> Hardware, that is the name the RAID utility (straight after POST) gives to the array i think, and so windows recognises it as one.

K9A2 Platinum not loading raid drivers sb600 or promise for raid 0

I am tired of trying by myself, hopefully you guys can help me out Ive been fighting this thing for 2days now and i hate this computer I'm on that feels like 28k dial up.
i know theres the promise plugs and the sb600, and i know they have different drivers. i also know that you have to disable the sb600 raid to get the promise working and vise versa *read the manual for that*. i set up the raid in raid configure *<alt-f>* and set it to raid 0 and assign the raid, and its fully functional.
the problem is when it comes to boot windows i hit f6 and then use the drivers i got off the cd...or website *two floppy's* and pick the i86 raid configuration *windows xp not 64, 64bit one is corrupted on both disks as well* it gets through that part, i format the drive *it sees in in raid in fast configure and in windows format, not in bios* and then go to install. it begins to install and stops on the first file FTT.inf, it apparently cannot read it, which is the same file on the disk if i am not mistaken. i have tried to install about 100times,if not more with different configurations in the bios.
the settings i have now for raid set up in the bios are:
integrated peripherals
extra raid controller enabled
in I/O devices on chip sata controller disabled *tried both enabled and disabled same problem*
it does not show drives in the sata ports but i figured that since it only shows 1-4 and the internal promise are the 5/6 ports.
i have formated and re-installed the drivers on the disks multiple times ive also tried the sb600 drivers disabling the extra raid controller in bios setting raid *it finds it in the 1/2 slots then 1 as raid* configured it in the raid set up as well but the same problem arises except its not FTT.inf its ahcix86.inf that errors. skipping the files *which is obvious but i tried it just to see what would happen * causes blue screen on reboot and another error of the same type at 99% but .sys file this time.
i have installed windows on one drive and booted up using the same drivers was able to configure everything was slightly inclined to just say screw it 1 drive it is. but it was a shame since i bought them both to raid 0 em from the start. loaded windows up and even installed drivers.
i also heard that u need to do full format sometimes to get the raid to work if you have tried both raid drivers so i did slow fat format... no avail did it twice. and fast the rest. if you guys know of any boot-able type formating program that i could throw on a floppy disk that would be great too, if thats the case.
i am at a wall and frustrated as all hell with what Ive done so far hope u guys can help me out, tried to be as detailed as possible but i bet i missed something .
rig specs*dont know if this will help but w/e*
msi K9A2 platinum
amd 4200 duel core socket am2
1gig of patriot 667 ram 512x2
ati x1900gt video card
Samsung spin point 160gb sata drive x2 *praying to god to put it in raid 0 once again*
THX FOR READING :D

Quote from: asd9000 on 17-May-08, 08:51:19
did all those settings. and have the newest and the disk version of the drivers.
do u guys really think that it not being able to find the driver file a power issue? either way i ll do anything at this point i rewired some stuff where the video card has its own rail and the hard drives have theirs with the cd-rom drive. took out my fan controler and really power hungry after market video card fan replaced with an old 60mm fan.
Error once again... ??? DAMN FTT3.inf file
edited: cause i sounded like an angry a$$hole with that first line :P
Stop swearing here! It's NOT allowed.
As for the floppy, goto the command prompt of a Windows machine, then type "format a:" and let the floppy format, if your floppy shows any error throw it away and try another.
It's not uncommon floppies fail.

K9A Platinum 64x Edition drivers?

I have the K9A Platinum with windows professional 64x.My problem is that I can not install the 64x realtek gigabit ethernet drivers. And I can't use the CD to install the drivers.

http://www.msi.com.tw/program/support/driver/dvr/spt_dvr_detail.php?UID=737&kind=1
The drivers page for your MB is a great resource to get the most current drivers. You may want to see if that driver works any better from the link above.

P965 Platinum SATA RAID drivers to slipstream

Hey guys,
Once in a while I slipstream SATA and SATA RAID drivers into my WinXP Pro setup cd, so I will not need a floppy on any system. My setup cd now contains drivers for VIA VT8237, nForce3, Promise 20378 and Promise 20579 controllers. I would like to add Intel ICH8R drivers...
I know how to do it, that's not the issue. But on MSI's download section for my P965 Platinum I can find two drivers:
Which one is to be used to setup RAID arrays on the ICH8R? Both contain contents for a floppy, both folders and files look the same. It's just that they differ in size, so I'm not sure which one I need. Do I need to slipstream both drivers to setup a RAID 0, 1 or 5 array?
Thnx in advance...

Quote from: Quadrifoglio Verde on 03-March-07, 23:47:11
Alright, thanks. Why the first one and not the second one? Is there a difference between the two? I can not slipstream both, as they are both named "iastor.sys"...
"I can not slipstream both, as they are both named "iastor.sys"..."
you no need to put them both, only one of them.
they are the same version, all files match except iastor.sys size (in same time both iastor.sys are "same version" too.. 6.0.0.1022)
"Why the first one and not the second one?"
just guess, because MSI put them as ICH8R SATA RAID Driver as primary. if you have any problems you can try drivers from second achieve.

Help with GeForce 8400 GS on K9A Platinum

Hello,
I changed my video card to PNY GeForce 8400 GS, the machine boots up fine but doesn't look like the video card is being recognized properly. I get only 800x600 and the colors are all messed up. In Device Manager, when I click on the video card it says "Your computer's system firmware does not include enough information to properly configure and use this device. ... (Code 35)". I have the latest drivers from NVIDIA, I just updated my BIOS to the latest version (1.9), but still the same problem.
Machine Specs:
MSI K9A Platinum (MS-7280)
AMD Athlon 64 X2 3800+ 2GHz
Corsair 2GB DDR2
Samsung DVD RW Drive
Antec Truepower Trio PSU 550W
Windows 7 x64
Old video card:
Sapphire Radeon X1900 GT 256MB
New video card:
PNY GeForce 8400 GS 512MB
Can someone please help?
Thanks,
Sunil.

Sounds like there could be a conflict with the old driver fragments from the X1900 GT. Uninstall all graphics drivers, run >>Driver Sweeper<< and this time install the graphics drivers supplied by MSI.

K9A Platinum Won't load XP PRO 64

I have a K9A Platinum board, Athlon 64 x2 4800+, 4 x 1 GB OCZ Gold ram. The system boots up, recognizes the raid drive, starts to install Windows, I specify the driver for the raid controller, it loads it, finishes loading all the rest of the drivers, and then sits there with a blank blue screen with the text "Starting Windows" at the bottom.
It will not go past this point. Any ideas?

It has nothing to do with the board!
But everything with the CPU and number of memory banks.
The CPU only supports 4 banks at full speed, this is:
2 sticks double sided (=4 banks)
4 sticks single sided (=4 banks)
This is a CPU limitation, not board.
Normaly you can get it running with more then 4 banks by reducing the memory speed.

K9A Platinum with 2 Sapphire X1650XT crossfired but CCC will not see them?

A Newbie here, so sorry if I sound thick. I have a K9A Platinum with 2 X1650XT DDR3 installed and windows see's them both but ATI Catalyst Control Centre tells me the interconnect cable are not attached?? Both the cables are connected (ATI Genuine). I have installed all the latest drivers and checked that my bios is up to date, I only built/purchased the parts 4 days ago.
Hope you guys can help??
My Specs:
Windows XP-pro 64bit
AMD 6000+ X2 AM2
MSI K9A Platinum
Zalman CNPS9500 AM2
Corsair DDR2 800MHz 2gig (2X1024MB matched pair)
Sapphire X1650XT DDR3 (x2)
Western Digital Raptor 37gig Sata
Seagate Baracuda 250gig Sata (x2)
Samsung DVD-R Sata
Corsair 520watt PSU (only using 3 rails)

HI AaronYuri, thanks for the response but I have tried the cards switched and the cables swapped/reversed, I have tested the cards on there own in the board, I have just noticed that when I do system information it can see the both cards on the board but it only give me the memory information for one of the cards, not sure if this is relevant but assume that because I am using the main card for my display the others is not being used.
Jonnyt

K9A Platinum Raid Drivers = Information

Similar Messages

Maybe you are looking for