K9A2 Platinum & Promise T3 Windows 7 Raid Drivers

Hello,
I first want to thank everyone for taking the time to read my post. Hopefully together we can make this work. I am currently running Vista 64BIT and purchased a Windows 7 64 BIT to upgrade. I need helping finding a stable driver for the installation.
Current Specs:
K9A2 Platinum (BIOS 1.0B LATEST VERSION)
Windows Vista 64BIT
4GB DDR2 RAM
Phenom 9500 2.2GHZ Quad Core
2X 250GB Sata hard drives (currently RAID 0) on Sata ports 5&6 Promise T3.
850WATT Antec Power Supply.
I already have the two 250GB hard drives in Raid 0 on sata ports 5 & 6 (Promise T3) which works perfect in Vista. MSI doesn't have Windows 7 drivers on their website. I did however find that Promise has on their website the FastTrak TX2650 Driver which supports Windows 2008/7 which I believe will work. I believe the model number is promise_PDC42819.
If anyone has any information on this that would be wonderful. I need to know which drivers to load up with Windows 7 when installing.
Thanks again for all the support everyone!

It looks to me that the fastTrak 2650 is for an installed internal card to run a RAID config so I see that as a NO.
You are right, that promise T3 Raid driver is tough to find.
Have you tried contacting MSI tech support?
http://www.msi.com/service/download/driver-2702.html
This is the only definite RAID I see at MSI's site, the one you found for ports 1-4.
Is One controller better than the other?
IDK.
If you don't get a reply here, again, contact MSI tech support.
I also, like you, found old threads here that never answered that question.

Similar Messages

  • K9a2 platinum help installing windows xp with raid

    so the situation is this i am installing windows on my computer trying to set up raid 0. i am using the sb600 raid set up i have set  everything up in the bios and set fast trak works great till it comes time to install, after formating drive. the moment it begins it tries to copy the files from the disk and says the "ahcix86" cannot be copied and if i try it with promise *moving the drives to the right sata slots* i get the same issue, but this time its the "FTT3" file that cannot be copied. tried 3 different windows xp disks sp1/2/3 I am stuck with the same error. I have tried about every option in the bios and even changed floppy drives and floppy disks multiple times. downloading newer/older drivers as well. i cant even get it to install on one drive.
    amd socket am2 4200x2
    msi k9a2 paltinum bios 1.4
    patriot pc2-5300 667mhz ram
    Msi radeon 3850 oc edition
    samsung spin point 160gbx2
    coolmax 550watt power supply
    extra items cdrom drive and floppy
    sorry about not posting much before just frustrated.

    www.Nliteos.com great program copy your windows CD to a Directory then run Nlite select different options you want, like slipstream service packs and hotfixes, drivers, tweaks, remove stuff from install like MSN, outlook express, do a true unattended intsall (input your key and all that) its pretty powerful then put in a blank CD and hit burn and out spits a new XP disc thats custom for you.
    i dont recommend putting ALL your drivers IE video card, sound and all that just the basics then use the proper installers for the big drivers.
    check out the forums on the site lots of great info

  • MOVED: K9A2 platinum and Vista x64 unsigned drivers

    This topic has been moved to Vista problems.
    https://forum-en.msi.com/index.php?topic=114418.0

    Quote from: Fredrik Åsenius on 06-April-08, 02:55:35
    No, that is not what I said. VistaX64 supports a lot of memory. Remember you have also a lot of memory on the video card. Your configuration might not, if the combination of the four sticks - of two different models - makes the system freeze.
    Mixing memory is never good because it makes things harder for the processor (and it's memory controller).
    You could still try reducing the speed of the memory, and/or increase the memory voltage a little bit.
    I have 4 same memory moduls. I didn't mix modules. I just say, that same happens with my OLD 4 memory moduls(worked fine in my old motherboard Asus m2n-e sli), and with my new 4(exact same) modules.
    Memory is on default speed....btw. These memory modules are DDR2-1066, but running on 800. Where should I lower speed more?

  • 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.

  • How to Setup RAID 0 on K9A2 Platinum using SATA 5&6 Promise Controller

    Setup:
    MSI K9A2 Platinum
    2 x Sapphire 3870 HD in Crossfire Mode
    2 x 500 GB WD Caviar Hard drives ( I want to put these in RAID 0)
    Pioneer 115DBK DVD Burner
    LITEON BD/DVD Player SATA
    Phenom 9850
    GSKILL 4 GB 1066
    Antec P182 Case
    Rosewill 850 W Power Supply
    Windows Vista 64 bit
    I am trying to set the RAID up on the PROMISE SATA ports 5&6.  I have enabled the additional RAID controller in the BIOS and set the SATA controller to RAID.  One drive shows up as JBOD and I can set the other to RAID 0 in the Fast Track utility.  What do I need to do to change the JBOD to RAID?  I'm sure its showing that I am a newbie at this and first RAID attempt.  It's a new setup so I don't mind having to re-load VISTA.
    Additionally - I cannot get the IDE DVD burner to work.  If there is any obvious fix for this I'd appreciate input.  The SATA BD Player works just fine.
    Thanks for any advice!

    Sorry, my explanation seems to be too short... some remarks:
    - Yes, you need to go to the Promnise Setup prgram like you say;
    - Yes, you have to delete the JBOD-array, but you also need to delete the RAID-0 array. Both drives  become available now to setup RAID.
    - Make a new striping (0) array and select both drives to use -> make array and reboot.
    - go into bios and select the RAID-0 array as second boot device and your DVD/CD as first boot device (for now);
    - reboot and boot off the Vista Setup CD/DVD.
    - Wait until Vista asks to select the drive to install to. It will show you the RAID-array or it will show you nothing. If it shows you noting (and I bet it won't ), then choose to manually install a driver. Now, you can select the Promise driver to use. Vista will load it and recognize your RAID array. Select the array and tell Vista to install.
    - Now start hoping that it will work out!
    Good luck!!

  • OpenGL games fps going down after install Windows on RAID 0 on K9A2 Platinum

    Hello .
    Description of problem :
    The problem was showed right after installations Windows on RAID 0.
    When I had one HDD, the problem was not.
    The problem was showed on both integrated RAID controllers (both on SB600 and on Promise T3).
    When I play games (just games in OpenGL!!! for example conter-strike 1.6, Quake3, on Direct3D such problem is not present), and simultaneously I copy (or other users on FTP:)) a plenty of small files, game frames per second going down.
    If to stop copying in current of minute, frames per seconds goung up.
    If in 2-3 minutes, will help only restart game.
    Processor type: "AMD Athlon 64 X2 4000+ (Brisbane)"
    Motherboard: "MSI K9A2 Platinum, AMD® 790FX and SB600 (+ Promise T3) Chipset,  AMI BIOS v1.3"
    RAM: "Samsung 1GB 800MHz DDR2 Non-ECC"
    HDD: 2x in RAID 0: "Samsung HD501LJ 500GB 7200rpm 16MB with NCQ Serial ATA II-300"
    Video: "XpertVision NVidia 8800GT 512Mb"
    Power supply: "FSP ATX-400PNR 400W ATX 12V v 2.01 20+4 pin passive PFC 12cm fan Noise Killer"
    Operating System:
    Windows 2003 server 32bit
    Windows Vista Ultimate 32bit 
    I have established last version Dual Core Optimizer.
    Tried to clean in boot.ini a key /usepmtimer and reboot has helped nothing.
    The similar problem was on absolutely another motherboard (Biostar nForce570SLI) and hdd (Hitachi 80GB) with the same processor and Windows. But , installation Dual Сore Optimizer and a key/userpmtimer has helped.
    What reasons of a problem? 
    How to eliminate a problem?
    In advance thanks for the answer.

    Oops, missed the PSU....
    Quote
    But why when copying to stop in 3-4 minutes, game fps not going up.
    In fact after copying files system resources are not used, also reading and writing from a disk does not occur.
    I understand that at copying Soft-RAID use some system resources. But when system resources not use game fps not going up.
    Will help only restart game!!!
    Quote
    The problem was showed right after installations Windows on RAID 0.
    When I had one HDD, the problem was not.
    See that? You went from single disk to RAID and then the problem started...... I guess it's not very hard to conclude that one is related to the other. Just try to use single disk again an and see what happens.
    Then: did you have two disks installed before going to RAID-0? Or did you add one disk for that? If so, then your PSU may be the troublemaker, not providing enough juice to feed all devices.
    About your English: it is fine, don't worry. We do not mind, as long as it looks like English and we can understand it and as long as there's no MSN-crap in it... so, you are doing fine. 

  • K9A2 *V1* Bios 1.8 - No drivers for Promise RAID controller.

    Does anyone know which set of Promise Raid drivers work with the updated Promise firmware that is part of the 1.8 bios update?
    Version 1.2 of the bios includes Promise version 28.1030.0021 which works with at least 1.1.1030.27 of the promise drivers.
    Version 1.8 of the bios includes Promise version 28.1030.0032 for which I cannot find any working drivers; do they exist? (Vista cannot see the controller and is unable to locate a suitable driver. Trying to use existing promise driver fails since it will not recognise the device)
    Just had a brainwave. On the MSI site, there is an updated driver pack for the Promise controller (this is a V1 board); this version is
    Vista32/64 Ver.: 1.1.1030.47
    Is this the version that is compatible with v1.8 of the bios (and hence 28.1030.0032)?

    Give them a try, they if they work will show soon enough.

  • Problem RAID K9A2 platinum /vista X64

    hello all,
    i have install driver promise raid for K9A2 platinum on vista x64 but when i reboot vista say me raid not install... my bios is 1.4
    please help me

    hello and thanks,
    i installing drivers raid which I downloaded from the site msi, I install and when I reboot vista x64, I have a window that tells me that vista has detected new hardware and if I want him to research driver on the web but they did not find.
    if I go in the device manager I see raid controller with an exclamation point ( dont install).
    my config:
    Amd phenom 9600 BE
    MSI K9A2 platinum ( chipset amd 790fx )
    HDD samsung Sata 750 Go 32mo
    Sapphyre toxic HD3870
    2x1Go kingmax 1066
    alim 450w

  • Question about Raid set up with (SB600) K9A2 Platinum V 1.0

    I am having trouble setting up my raid.  I am using Windows XP Pro and go through the usual set up procedures using F6 command then installing the drivers etc.  Once I get everything up and running installed on Raid 0 the computer works very well for a few days.  Then later BSOD.  The first was a 0000007b stop error, then I got the system back up again only to have it a few days then another BSOD 00000024 stop error.  This time I was not able to bring it back.  I thought my problem was linked to a RAM issue as I was using OCZ PC2 6400 DDR2 OCZ2G8008GQ (2X2GB).  The reason I thought this was when I went to the motherboard site for approved ram, this ram was not there, then on OCZ site it was also not tested, then I went to newegg and used thier motherboard ram compatability screener and it did not show up either.  So I bought the Giel ram and am now trying to set it back up again though I could not get it back still.  So I finally just reformatted the drives (using another computer and a hard drive enclosure)and am getting ready to reinstall everything.  I want to make sure I am using the right SB600 drivers for my application.  I should be selecting AHCI X86 or x64.  This does pertain to the operating system (I am using Win XP 32 Bit) or the processor (I am using the Kuma Athlon X2 7750 2.7Ghz)
    I believe I should be selecting the x86 drivers when installing windows.  Am I right?  I just want to make sure I do not screw anything up so as to bring on the horrible BSODs again.  I realize this could be some driver issue as well that could have caused this.  I did everything I could to make sure it was not the hard drives.
    The last question I have is:  In order to ensure proper operation of the dual channel ram, (I have read the book, still confused a bit), I must install the ram with one stick in the first slot nearest the CPU and the other in the first slot of the opposite color?  In this case Green/Orange slots.
    Mainboard: MSI K9A2 Platinum 790FX
    CPU: Athlon X2 Kuma 7750 AM2+ 2.7Ghz Processor
    CPU-Cooler: Factory Supplied
    RAM: 4GB (2X2GB) G Skill F2-8500CL5D-4GBPI DDR2-1066 Dual Channel
    GPU: AMD790FX
    VIDEO: PowerColor HD4830 512MB GDDR3
    HDD: 2 Velociraptor 150 10000 rpm drives WD1500HLFS
    DVD: ASUS DRW-22B1LT SATA Drive
    Floppy: YES
    Power Supply: CORSAIR CMPSU-650TX 650W ATX12V / EPS12V SLI Ready CrossFire Ready
    OS: Windows XP Pro SP1 (Updated to SP3)

    I was just trying to obtain the fastest load times/install times.  When the machine was first running it was very quick with no cpu temps running beyond 34C, no abnormal performance.  This is my wifes computer though.  Things began to go astray after she updated through windows update to SP3.  I am now using a slipstreamed CD with SP3 already on it.  She said she was clicking on the internet explorer "E" icon and it just shut off.  THen when it rebooted (it was still set that way in windows recovery) it started loading windows then BSOD 0000007b error.  I fixed it by finally getting into windows recovery and running fixboot, then fixmbr, then chkdsk /r /f.  It started working fine again.  Then later maybe two days later it happend again this time wihtout the restarting.  She was working on something else this time and it shutdown again.  This time when it tried ot reload windows I was getting the ntfs.sys issue with a 00000024 stop error.  I could not do the same magic with windows recovery any longer.  When I tried it indicated it repaired the boot, the mbr, but when I tried to run the chkdsk, it gave me disk read errors, such as "this disk has unrecoverable errors".  I used Western Digital test programs on the drives by removing them and installing them into an enclosure and taking them to a good computer.  One drive I could see in windows and it reflected 140G/B, the other would pick up but not in my computer.  It also showed the drive as having the entire quantity as the RAID together had of 298G/B versus the real size of the drive 150G/B.  I just figured that was the drive that was set up as LD 1 in the RAID setup (prior to windows) and possible was the drive with he boot sector on it???  I could get another drive and include it into the array, but then just figure I will have to worry about 3 drives versus 2.  She keeps improtant backup stuff on an external drive.  I will tone down the ram to 800.  Should I set the latency in Bios though to the 5-5-5-15?  or just leave everything at auto like I hade done before?  Though this ram is new and was not in the computer when this happened.  I had replaced the other OCZ Gold stuff and put in the G Skill stuff I have now.  I had previously stated Giel, but it is G Skill, sorry about that.  I may just do what you say, guess sleep on it and decide whether to just install the drives with OS/Programs on one and data on the other. 

  • K9A2 Platinum latest drivers issue.

    I have here a K9A2 Platinum, a Phenom II 940 with default clocks, a pair of Kingston 2Gb modules running DDR2-1066 5-5-5-15 @ 2.2v, a GeForce 8800GTS 640Mb and two Seagate 7200.11 drives in AMD RAID.
    All runs ticky using the drivers from the supplied CD. However, there's an updated set of drivers (ati_system_drive_mb). Installing these results in a critical stop (BSOD) right at the start of the boot process, probably when it loads the RAID driver (dratted XP won't tell me which module is responsible). Oops!
    I note that the installed RAID driver (ahcix86) is 2.5.1540.48 and the one in the new package appears to be 3.1.1540.81
    Oddly enough, attempting to update the RAID driver manually results in XP swearing that the INF file "does not contain information about your hardware", although the INF appears identical to the earlier version bar the version numbers in there.
    Anyone else seen this behaviour?

    Quote from: Bas on 25-February-09, 22:19:57
    SMART isn't always working.
    And drives don't have to give noises and such to be broken.
    Sometimes you simply don't notice it but have BSOD's.
    Why updating the driver anyway if the older one is stable?
    Yes, I'd come to the same conclusion as that last as well. 
    However, things have now moved on. Firstly, it's definately the SMBUS driver. Installing that gives BSOD on boot, leaving "as is", everything works stably. I ran the sysinternals "loadorder" utility and found a few drivers being loaded that probably shouldn't be there , which I have removed. Exactly the same behaviour .
    The wheels really came off the other day when I put BIOS 17 on. Everything came up, but the RAID array kept "pausing" (whatever I'm running stops, waiting for I/O - the disks thrash like fury - normal service resumed after a few tens of seconds of this). Reverting to BIOS 16 fixes this. RaidXpert logs the odd timeout once in a blue moon (and not when the disks are going beserk with BIOS 17), but nothing frequent enough to be alarmed about. Going back to TCQ from NCQ cures this occasional timeout behaviour completely, but produces slightly lower I/O performance. I'm sticking with TCQ for now.
    I'm confused, somewhat cheesed off and about to give up on the SB600 RAID. My next move will be to move the disks to the Promise controller and see if that produces better results (which I'll live with, even though it scotches my plans for an eventual 0+1 setup). During this process, I'll fire the thing up with 'em as plain old SATAs and let Seatools have a play, just in case and to be 100% sure. That's the task for this weekend. If that doesn't turn things around I'll try a full, clean reinstallation of XP SP3 as a test. After that, if things are still fubar, it's new board time...... 

  • K9A2 Platinum Sata Raid Problems

    I could not get my 2 500 gb seagate 7200.11 drives to work on the sb600 raid controller, in raid 1 (set to raid mode in bios).  I'd set it up and it would remain functional until I formatted it and put stuff on it. Then when I restarted, it says critical and can't locate the second drive, but it shows up in the list of definable drives.  My older 200 gb seagates 7200.9 in the same setup do not have this problem.  I finally got my 500s working by hooking them up to the promise controller instead.  (Although no longer a current problem, I wouldn't mind knowing what would cause this for future occasions.)
    My new problem is, I had to unhook all but the drive I wanted to install Windows XP on (A separate 120 JBOD configured drive) so I could get it to be C:/.  This all went fine.  However when I hooked up the 500s again, Windows XP would not boot, the screen just stayed black, with them not hooked up, it boots just fine, with the 200s as well.  When running the Windows XP setup again, the 500s appear as C:/ instead of the 120 in the disk select screen of the install.  It's like the 500s took over the drive letter when they are hooked up and thus can't load.  Is there some way to stop it from doing this or am I completely off on this.
    My computer spec is:
    K9A2 Platinum
    AMD X2 6000
    2*2gb OCZ PC6400
    ATI Radeon 3870
    700 Watt OCZ PSU
    Update: Installing XP ignoring the fact its not C: fails.  It copies all the files onto it, then after restarting I get a black screen.
    Another Update: On a whim I tried disabling the SB600 raid and set it to AHCI instead as I read that other people were having problems with it and it all works perfectly now.  It's too bad this doesn't work, but I'll just put the 200s back in my old computer instead.

    I'm having the exact same problem you did. Same Mobo. Except I started off with Promise RAID 1 because when I tried using SB600 RAID, my SATA DVD drive would not function in Vista Ultimate x64. So I had my Raid 1 configured on Promise T3 with BIOS 2.8.1030.0021 using 2 320GB drives. One of them Seagate, one WD, both 3GB/s transfer, only difference was that Seagate has 16MB cache, while the WD has 8MB. But both drives worked fine in the array for some time, and then after doing some updates from Windows Updates now the Raid config shows that encountered a critial status, "A disk member of an array has failed or is not responding", "Problem is detected with Array : 1". And when I go to the see the Array status it shows the Seagate drive on ID channel 1, but for the 2nd drive it shows questions marks all the way through the item line. I checked the drive, it seems fine. And even when I go to define a second Array, it shows the WD available on channel ID 3. So it definitely see both drives, but how do I re-add that WD drive that it doesn't see to my earlier defined array without loosing data on my Seagate drive?

  • K9A2 Platinum SB600 RAID & SATA DVD

    Quick question for you.
    I have the K9A2 Platinum (V1) MS-7376 board.
    Original setup has 2 drives on SATA ports 1/2 in a RAID 1/Mirror config - plus an additional HDD and DVD-Writer on PATA (Cable Select).
    The original DVD-Writer has given it's all, and was removed and "buried with honor".
    I'm replacing with a BluRAY SATA.
    From what I've read, I can't fire up the PROMISE Controller (Ports 5/6) because that will conflict with the SB600 Raid.
    I don't believe I can add the BluRAY to one of the SB600 ports (3/4) because it's expecting to add it to a RAID array....is that correct ??
    If that is correct, it would appear that my only option is to backup everything, put the hard drives on the PROMISE controller in RAID (or just use software/OS raid), and set the SB600 to AHCI - and probably reinstall the OS from scratch.
    Comments/confirmation greatly appreciated.

    Unfortunately it does not appear to be as simple as plugging it in to one of the existing ports. I've tried both 3 and 4 (since the 2 hard drives are on 1 and 2).
    OS is Vista Ultimate 64.
    To make sure there is nothing else is at fault, I updated to BIOS last night to the latest. I also updated drivers. Unfortunately, using the ATI Catalyst Install Manager, I don't see a way to update the SB drivers.
    The BIOS recognizes the BD and reports it correctly. In the RAID BIOS it is also visible. VISTA boots successfully, and runs fine (I'm using it while typing this). Completely stable as it always was. Until you put any kind of disk in the BD drive. After it senses the presence of the disk, the system immediately blue screens with a 'driver irql not less or equal' showing the culprit code being in ahcix64s.sys - the SB ahci raid driver.
    PSU = Corsair HX620
    MB = K9A2 Platinum V1 (MS-7376)
    CPU = Phenom 9550 Agena AM2+ Quad Core
    Memory = 2 x 2GB OCZ Reaper PC2 8500 (DDR2 Dual Channel Kit)
    2 x Seagate Barracuda 500GB SataII in Raid 1 Mirror on SB600
    Vista Ultimate 64 fully up to date with all updates.
    I can see the AHCIx64s.sys on the latest driver package is more recent than what's installed, but can't find a way to install it (as described above).
    Any ideas greatly appreciated.

  • K9A2 Platinum Raid 0 Setup

    Setup:
    K9A2 Platinum
    Phenom 9850 BE
    4 GB GSkill 1066 4 x 1GB
    2 WD caviar SATA HD (in RAID 0 - I think??)
    LITEON BD Player
    Rosewill 850W PSU
    Sapphire 3870 HD x2 in Crossfire
    I connected the 2 HDD to the 5&6 SATA ports, set them on Promise controller both to RAID 0 and reloaded Windows Vista 64 bit.  I manually loaded the RAID driver during the Windows load from the MSI disk that came with MBO.  Everything seems ok.  Windows only sees a C drive, but on Device Manager sees both drives as a 1+0 RAID device in Raid 0 - this also shows up on Fast Build Utility as LD1 and 2 and both 1+0 RAID device RAID 0.  Don't really notice any improvement in load times.  Is the RAID setup correctly?  Is there a way to improve the speed?  When I run the Windows Vista performance test - HDD speed rating is only 5.7.
    Thanks for any help

    Why are you  starting a scond topic about all this?
    Please stick to the one you already started... this makes no sense at all.
    I'm locking this one.
    >> Here << is the other topic.

  • K9A2 Platinum Cannot Use RAID and PCI IDE card [SOLVED]

    Hello,
    I am trying to do the following set-up on my K9A2 Platinum, using a Phenom 9600 processor:
    - 2xSATA2 250GB Seagate drives on Promise T3 SATA controller (to be used as RAID 1 devices)
    - 1xSATA DVD-RW on Sb600
    - 2xIDE DVD-RW on onboard IDE
    - One PCI HiPoint RocketRAID ATA100 card (operating in IDE mode) on PCI slot 2 with 1xIDE 40GB hard disk (my Linux partition)
    On the BIOS I have enabled the Extra RAID function, in order to enable Promise to work as RAID.
    The system POSTs as follows:
    - Initial detection (CPU, RAM e.tc)
    - RocketRAID gets initialized and detects the IDE disk attached (40GB)
    - Promise RAID tries to detect the disks (the RAID array) and the whole system hangs.
    I've tried to relocate the two SATA hard disks to the SB600 controller (SATA 1&2 ports), but the same thing happens (after changing the BIOS to disable extra RAID function and enable RAID mode on onboard SATA SB600). The only way to POST the machine, is to remove the RocketRAID PCI card, but this way I can no longer boot my Linux disk.
    Using BIOS 1.2 and 1.3beta 2 (sent to me by MSI support).
    Any help is greatly appreciated.

    Thanks for the replies.
    Now, I'm going to surprise you: I managed to make both cards (the Promise and HighPoint) work together! Read how...
    Somehow, I got the impression that the problems I had were either caused by the BIOS or the hard disks (the SATA ones). I flashed the motherboard back to the official 1.2, doing a complete BIOS reset (removed the battery) and tried again without the RocketRAID card installed. This time, the Promise BIOS (which btw is an earlier version from the one the 1.3b2 BIOS had) reported that the one SATA drive was malfunctioning (and it was a sealed brand-new Seagate). Removed the drive, installed it on SB600 and SeaTools indeed reported that it was failing (it didn't manage to pass even the quick test...).
    Now I was curious: could it be that this - together with the beta BIOS - was the cause of my problems? I installed the other SATA disk to Promise T3 (the red socket) and the controller detected it, but all I could do is to set it up as a RAID 0 array (which pretty much does nothing). Next, I installed the RocketRAID also together with the IDE Linux disk and the system detected both disks; I can boot Linux fine and enter both the RocketRAID BIOS and Promise T3 BIOS. I can delete and recreate the array in Promise T3 as I please, but due to the fact that I only have one SATA disk now, I get limited options (RAID 0 and JBOD).
    Is it safe to assume that since the Promise BIOS is working with the RocketRAID installed, that my SATA RAID controller is working?
    Tomorrow, I shall return the SATA drive to the store I bought it and get a replacement, so that I can set up my RAID 1.
    The plan is to have Linux boot from the IDE (I've never managed to set up a Linux disk to boot from RAID) where Windows Server 2003 will boot from RAID.
    Will keep you posted about the progress I make.
    BTW Bas, I'm sorry I couldn't make out much of your brainstorming 
    Regarding the Promise controller: the board has a Promise chip right above the SATA ports, which has the number 42819 on it. I can also verify that both SB600 RAID and Promise T3 RAID have EXACTLY the same BIOS menu interface (the only differences are the texts "ATi SB600" and "Promise T3" on the menus, plus that the SB600 has also an option to securely erase the drives which Promise does not have). Are you suggesting that the SB600 RAID is actually the Promise T3? I do not know if it would be possible to have BOTH RAID controllers (SB600 and T3) working at the same time (I do not have enough disks to try...).

  • How to install W7 Promise driver for K9A2 Platinum

    First of all i assume no responsability for any loss of data ,everything described here is done on your own risk.BACK-UP data before doing this.
    Any K9A2 Platinum v1 user was disapointed when looking on the product page seeing no W7 driver.As a MSI tech recommended a driver from Promise i said to myself to try it and of course , it did not installed the normal way.You could force it tru HAve Disk from within Windows 7 only when running form the SB 600 .Also Windows updates installs an update for the cip.
    The procedure is simple ,practically you only need to edit one or 2 INF files depending on the W7 version.
    FTTX4650-2650 controllers are both compatible with Windows 7 as the Microsoft website shows.
    Download driver from Promise website the driver for FTTX4650-2650 Win7 Win2008R2 WHQL V 1.3.0.4 -> file name FTTX4650-2650_Win7_Win2008R2_WHQL_V_1.3.0.4
    Unzip the archive and navigate to the i386 or/and amd64 folders locate <FTT3s.inf> file/s ,open with Notepad.For the .inf extension to be visible go to File & Folder Options and enable extensions to be visible.
    Under the [Promise] section add the folowing lines ,this ID s were harvested from within Windows 7 Promise properties ,when no driver was installed
    %FastTrak PDC42819_Desc%=Napa_Inst,PCI\VEN_105A&DEV_3F20&SUBSYS_37161462&REV_00
    %FastTrak PDC42819_Desc%=Napa_Inst,PCI\VEN_105A&DEV_3F20&SUBSYS_37161462
    %FastTrak PDC42819_Desc%=Napa_Inst,PCI\VEN_105A&DEV_3F20&CC_010400
    %FastTrak PDC42819_Desc%=Napa_Inst,PCI\VEN_105A&DEV_3F20&CC_0104
    After the copy/paste that [Promise] section will look like this
    [Promise]
    %SATA_TX2650_Desc%=Napa_Inst,PCI\VEN_105A&DEV_3F19&SUBSYS_3F29105A
    %SATA_TX4650_Desc%=Napa_Inst,PCI\VEN_105A&DEV_3F19&SUBSYS_3F2A105A
    %SATA_TX4652_Desc%=Napa_Inst,PCI\VEN_105A&DEV_3F19&SUBSYS_3F2B105A
    %FastTrak TX2650_Desc%=Napa_Inst,PCI\VEN_105A&DEV_3F20&SUBSYS_3F21105A
    %FastTrak TX4650_Desc%=Napa_Inst,PCI\VEN_105A&DEV_3F20&SUBSYS_3F22105A
    %FastTrak PDC42819_Desc%=Napa_Inst,PCI\VEN_105A&DEV_3F20&SUBSYS_3716105A
    %FastTrak TX4652_Desc%=Napa_Inst,PCI\VEN_105A&DEV_3F20&SUBSYS_3F24105A
    %FastTrak T2_Desc%=Napa_Inst,PCI\VEN_105A&DEV_377d&SUBSYS_3772105A
    %FastTrak PDC42819_Desc%=Napa_Inst,PCI\VEN_105A&DEV_3F20&SUBSYS_37161462&REV_00
    %FastTrak PDC42819_Desc%=Napa_Inst,PCI\VEN_105A&DEV_3F20&SUBSYS_37161462
    %FastTrak PDC42819_Desc%=Napa_Inst,PCI\VEN_105A&DEV_3F20&CC_010400
    %FastTrak PDC42819_Desc%=Napa_Inst,PCI\VEN_105A&DEV_3F20&CC_0104
    %Promise_Raid_ControllerDesc%=NODRV,SCSI\ProcessorPromise_
    If it looks like this save the file.
    Go and Install it.
    A warning message for the driver will appear as with any beta or unsigned driver ,ignore it.
    When in W7 update the Promise as offered by Windows update.
    I will not be held resposable for any damage or data loss.You are doing this on your own risk.Back-up your data and test the driver for yourselves before long term usage.
    If it works for you post feedback.

    Quote from: wlahdone on 21-February-11, 21:51:07
    First of all i assume no responsability for any loss of data ,everything described here is done on your own risk.BACK-UP data before doing this.
    Any K9A2 Platinum v1 user was disapointed when looking on the product page seeing no W7 driver.As a MSI tech recommended a driver from Promise i said to myself to try it and of course , it did not installed the normal way.You could force it tru HAve Disk from within Windows 7 only when running form the SB 600 .Also Windows updates installs an update for the cip.
    The procedure is simple ,practically you only need to edit one or 2 INF files depending on the W7 version.
    FTTX4650-2650 controllers are both compatible with Windows 7 as the Microsoft website shows.
    Download driver from Promise website the driver for FTTX4650-2650 Win7 Win2008R2 WHQL V 1.3.0.4 -> file name FTTX4650-2650_Win7_Win2008R2_WHQL_V_1.3.0.4
    Unzip the archive and navigate to the i386 or/and amd64 folders locate <FTT3s.inf> file/s ,open with Notepad.For the .inf extension to be visible go to File & Folder Options and enable extensions to be visible.
    Under the [Promise] section add the folowing lines ,this ID s were harvested from within Windows 7 Promise properties ,when no driver was installed
    %FastTrak PDC42819_Desc%=Napa_Inst,PCI\VEN_105A&DEV_3F20&SUBSYS_37161462&REV_00
    %FastTrak PDC42819_Desc%=Napa_Inst,PCI\VEN_105A&DEV_3F20&SUBSYS_37161462
    %FastTrak PDC42819_Desc%=Napa_Inst,PCI\VEN_105A&DEV_3F20&CC_010400
    %FastTrak PDC42819_Desc%=Napa_Inst,PCI\VEN_105A&DEV_3F20&CC_0104
    After the copy/paste that [Promise] section will look like this
    [Promise]
    %SATA_TX2650_Desc%=Napa_Inst,PCI\VEN_105A&DEV_3F19&SUBSYS_3F29105A
    %SATA_TX4650_Desc%=Napa_Inst,PCI\VEN_105A&DEV_3F19&SUBSYS_3F2A105A
    %SATA_TX4652_Desc%=Napa_Inst,PCI\VEN_105A&DEV_3F19&SUBSYS_3F2B105A
    %FastTrak TX2650_Desc%=Napa_Inst,PCI\VEN_105A&DEV_3F20&SUBSYS_3F21105A
    %FastTrak TX4650_Desc%=Napa_Inst,PCI\VEN_105A&DEV_3F20&SUBSYS_3F22105A
    %FastTrak PDC42819_Desc%=Napa_Inst,PCI\VEN_105A&DEV_3F20&SUBSYS_3716105A
    %FastTrak TX4652_Desc%=Napa_Inst,PCI\VEN_105A&DEV_3F20&SUBSYS_3F24105A
    %FastTrak T2_Desc%=Napa_Inst,PCI\VEN_105A&DEV_377d&SUBSYS_3772105A
    %FastTrak PDC42819_Desc%=Napa_Inst,PCI\VEN_105A&DEV_3F20&SUBSYS_37161462&REV_00
    %FastTrak PDC42819_Desc%=Napa_Inst,PCI\VEN_105A&DEV_3F20&SUBSYS_37161462
    %FastTrak PDC42819_Desc%=Napa_Inst,PCI\VEN_105A&DEV_3F20&CC_010400
    %FastTrak PDC42819_Desc%=Napa_Inst,PCI\VEN_105A&DEV_3F20&CC_0104
    %Promise_Raid_ControllerDesc%=NODRV,SCSI\ProcessorPromise_
    If it looks like this save the file.
    Go and Install it.
    A warning message for the driver will appear as with any beta or unsigned driver ,ignore it.
    When in W7 update the Promise as offered by Windows update.
    I will not be held resposable for any damage or data loss.You are doing this on your own risk.Back-up your data and test the driver for yourselves before long term usage.
    If it works for you post feedback.
    I made the changes specified above. How do I install the driver ?

Maybe you are looking for