ASUS A8V PROMISE CONTROLLER DRIVER DOWNLOAD

Originally Posted by Tumbleweed36 If the bios sees the drive but windows does not, that normally indicates the drive has not been partitioned and formatted. Or do they have to be literally identical drives in order for it to work? All works well now- and I am stuffing the drive full of odds and ends and such. Of course you would need to setup the OS and the data according to the needs e. I had been using the wrong driver all along and there was no possible way to get it to work!

Uploader: Akishura
Date Added: 14 March 2007
File Size: 10.65 Mb
Operating Systems: Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X
Downloads: 71821
Price: Free* [*Free Regsitration Required]

Originally Posted by tuskenraider. Joined Dec Age 70 Posts 64, Yes, and the fact that the two drives are mismatched in several areas as well, differing make and model, capacity, firmware, cache size. Or do they have to be literally identical drives in order for it to work? I tried connecting an additional sata drive to sata1, but the MBFastBuild utility still only saw the original 3 drives, so that did me no good. Here is what I assume but it’s merely an assumption because I did NOT try it out and thus it’s mainly based on theoretical level, knowing that in IT matters there is only one truth: After I flashed the bios from I’ve tried using the promise ports oromise a non-RAID configuration and never got it to asuss.

I had been using the wrong driver all along and there was no possible way to get it to work! I use the promise controller for RAID-1 in my rig but not as a boot array so I don’t have any hands-on experience with your problem.

  3D PROPHET II GTS PRO 64MB DRIVER DOWNLOAD

Asus A8v Deluxe Promise RAID Controller Options?

The performance isn’t as good anyway so unless you need 3 or more SATA ports, avoid it. Let me provide some more details in order for you to get a clearer picture. Everything seemed to be ok apart from the memory dividers not working correctly.

Subsequent to upgrading the cpu a couple of days ago, I have experienced an issue namely that after the Promise Sata bios screen comes up the system does not boot but says something to the effect that ‘no disk can be found’ I have already noted several posts relating to problems regarding the Promise Sata being sometimes problematic.

If so, you have to reformat it to get it to work properly. Of course you would need to setup the OS and the data according to the needs e.

Either way, the risk of data loss in RAID-0 is higher than with a single drive. I did notice something that now makes me wonder if i have the right driver installed tho. Went back into the bios and repopulated with the same format. Thread Tools Show Printable Version. Along with this problem, I also have the issue with my OS reading said drives, as I gave up on having both raid options, and set them up for raid0 performance and tried to install OS, I installed drivers as said from floppy, but XP still says cannot install it says it cannot find harddrive.

Once I had ascertained that all seemed ok, I cleared the cmos and changed the cpu over to the SD It will serve your purpose well enough, provided you understand that the risk of data loss with such a mismatched array will likely be higher than if the two drives were matched.

  FLEXSCAN SX3031W DRIVER

Here is a free trial program that might assist you: Originally Posted by gallowsroad. Of course if you do not want to boot from the array then you may install the drivers later if needed. Copyright -Tech Support Forum. Joined Dec Age 70 Posts 64, Let it detect the controller, install the drivers, reboot after shutting down and attaching promisr. Originally Posted by Tang69 My God!

Suspicious Activity Detected

I wonder if someone can help me please. Please report if possible how it worked for you Have you unplugged the drive and booted up in effect removing the drivethen shut down and rebotted the computer to see how the drive behaves?

My problem is that I cannot seem to be able to properly install the Promise Fastrack drivers so that I can switch to promisse mode in the bios.

Practically this means that a HDD which is not recognised on BIOS level will definitely not be recognised by windows whereas the opposite may be true e. Originally Posted by BWM.