Hi @dj_groovin ,
I did use the virgin driver.
About the modded BIOS, please can you send me a private mail so that I can offer you all the stuff I had archived for modding the original ASUS v4101. Rgds.
Hello 100PIER,
thank you very much for your instant reply and help!
Did you install the original driver manually the normal way from within the Device Manager or did you force the installation by pressing the āHave Diskā button and navigating to the matching *.INF file?
I did the have disk method and pointed to the iastor driver. it ends after a few minutes with a message that the driver installed but encountered problems. In device manager it then shows the driver version is v14, however all the disk drives attached to it end up with exclaimations in device manager.
Trying to just install the software ends up with it spinning endlessly around 60 percent and nothing happens beyond that
Trying to uninstall the inbox driver results in a lock up as well.
Its strange as x99 is technically supposed to be supported by asus for windows 10 so you would think that the virgin driver and software pack would install without too many issues.
Is there any chance uaing the ntlite method still works? I can open the iso and remove.the in box driver and try and then do the have disk method on install? Or is v14 completely unable to function with the latest.builds of windows 10
@dj_groovin
Did you follow 100PIERās offer and have sent him an eMail?
He knows much more about the best storage drivers for Intel X99 chipsets than me.
Yes we have been trading messagesā¦
I may have had a slight break through, albeit its been only in testingā¦after getting the v14 driver in, i disabled jmit in device manager and rebooted. Now the system didnt shut down and hung so i had to hold the power buttonā¦however i re enabled the driver on the boot up and the driver now says its working properly, even more surprisingā¦the exclaimation marks on the drives went awayā¦ i tried installing rst software and it hung and i neeeed to hold the power button again and restartā¦i managed to install rst using command line, āsetuprst -nodrvā. It seems to be installed and its allowing me tk make changes on the raid configuration.
Im wondering how i should test it, its not like stress testing an overcloxkā¦lol. i need to check performance.
My.os drive is a samsung nvme so its not affected but i have a 3 drive raid 5, a 2 drive raid 1, and a single 2 tb sata ssd connected to the 6 ports.
I wonder if i can replicate this without having to powercycle live windows os so i dont have to worry about corrupted system files and what notā¦i guess i can run integrity checks on that laterā¦but this is a step forward for now i thinkā¦
Hello gents, @Fernando and @100PIER
So it seems microsoft drop support officially for v14 drivers as of windows 10 build 1903 based on the research i have done. No matter how i try, windows 10 now refuses to accept and properly work with the v14 driver and the inbox driver does not seem tomfunction correctly either.
However, the rst enterprise driver v5 is not mentioned at all in any of the information i have found. I believe this might still be supported in windows 10.
With the x99 board its been said we can use the rste v14 or the rst enterprise v5 driver for the primary raid controller.
Does anyone know how i could install the enterprise edition driver for my raid setup on the primary sata controller?
Im assuming i would need to change the orom from the rste v14 to the rst enterprise v5 version. Or is incorrect?
Im very curious if this work around may keep the board officially relevant at least until microsoft drops windows 10 all together.
hello dj_groovin,
Here are some HWINFO64 screenshots from my old ASUS Sabertooth configured with 2 SATA RAID0 matrices. I do use W11 23H2. Why you donāt use W11 instead of W10 ?
I have tried to download my modded BIOS X99ST stuff (zipped), but I getan error message athe end of the upload 'ā¦ try again". But after several download attempts of this zipped this does not work (zipped file is about 47Mo, is it the problem ?).
However, hope these infos help you. 100PIER
Hi iām trying to install XP on a machine, but i canāt find the right AHCI driver, my hardware id from device maneger are as following,
PCI\VEN_8086&DEV_5AE3&SUBSYS_72708086&REV_0D
PCI\VEN_8086&DEV_5AE3&SUBSYS_72708086
PCI\VEN_8086&DEV_5AE3&CC_010601
PCI\VEN_8086&DEV_5AE3&CC_0106
I hope that someone can help.
@bach1223
Welcome to the Win-Raid Forum!
I recommend to take the āGeneric 32bit Intel RST AHCI driver v11.2.0.1006 mod+signed by meā. It should work with your system.
Good luck!
Thanks for the quick replay.
I have already tried that one, but i still ran into the stop error 0x0000007b when installing.
the machine Iām trying to install windows on is a eBOX626-311-FL ( eBOX626-311-FL Fanless Embedded System - Axiomtek | Mouser )
I hope you have an idea that can help me.
@bach1223
Although I seriously doubt, that it was the modded generic Intel RST AHCI driver v11.2.0.1006, which has caused the 0x0000007b BSOD, you may try the attached non-generic RST AHCI driver v11.2.0.1006 (the real driver of both driverpack is identical).
Universal 32bit Intel RST AHCI driver v11.2.0.1006 mod+signed by Fernando.rar (249.4 KB)
@Fernando
What do you think did it then? I will try the driver you just provided tomorrow, as the pc are at my work.
Another loaded or integrated textmode driver.
That is why I strongly recommend to use an original (untouched) OS Image as source.
The one i used today was found on the internet, but i have found my original copy here at home, so i will try and make a new one from that one tomorrow, but thanks for the help.
@Fernando
I finally had a chance to test this, i have made a new bootable usb using the original windows XP cd i have, then i have used nLite to slipstream the driver into the iso that i have made the usb from. How ever, i still keep getting BSOD both 7B and A5. not sure if Iām doing something wrong, what i have done:
If i donāt press anything when the F6 appears, then i get A5
If i press either F5 or F7 when F6 appears, then i get 7B
Am i inserting the driver the wrong way?
The 7B BSOD indicates a wrong/not matching textmode driver (maybe it is the in-use USB 3.0/3.1 driver), whereas the A5 BSOD indicates a wrong/not matching ACPI driver named acpi.sys.
>Here< is my Guide about how to do it.
@Fernando
I have used the same method as in your guide, so that should be good.
Iām using usb 2.0 ports on the device.
I hope you have any ideas on how I can resolve this issue
Hello @Fernando
How are you ?
I need your help because i want install Windows XP Integral Edition 2023 in CD. I have burn the iso but after i have error 07 or 05.
I have try use your universal AHCI + Raid 32 bits with iso x86 Professionnal Windows XP. with NLITE and i have selectionned my drivers AHCI
Hisānt not working can you help me please 
.
My laptop itās MSI GL75 Leopard 10SER
@yaceur
Welcome to the Win-Raid Forum!
If you want to get Windws XP installed, you have to use a āclassicalā Intel RST driver (without the additional iaStorF.sys driver). I recommend to use the āGeneric 32bit Intel RST AHCI driver v11.2.0.1006 mod+signed by Fernandoā.
To prevent the error code 05 I recommend to press F5 or F7 and to change the computer type while prompted to press F6.
Good luck!
Hello @Fernando ,
I have boot with CD and integrated the universal 32 bits ahci intel without the additional iastorf.sys. In my bios AHCI, i trying F5 in first and i click on āother computerā but install don"t detect the next step.
I have trying F7 to spam before menu F6 appaired in down text.
I go tell you the come back test