Thank you very much for the instruction.
My apologies if I was off-topic.
I will reread the start post as you request.
Thank you for your time.
Regards,
Hello Dieter,
Great work here, to say the least.
I have a question for you, about an old motherboard based on the ICH9 (without R), namely the Abit IP35-E : there is a bios mod which enables the AHCI, but none of the modded drivers appear to work. In IDE mode the hardware IDâs are DEV_2921 and DEV_2926. As soon as AHCI is switched in BIOS I get a blue screen (XP SP3). I tried Dev_2922 and DEV_2923 by Fernando but I guess those were ICH9R drivers modded to work with later versions of the Intel Software. (got blue screen with them as well)
Can you tell me which device should be selected from your modified drivers? Thanks a lot, Adrian
@Adrian1 :
Welcome to the Wi -RAID Forum!
It Ăs clear, that you get a BSOD, when you simply switch from IDE to AHCI mode within the BIOS without having forced the installation of the correct Intel AHCI driver before doing the rebooting, entering the BIOS and switching the SATA mode to "AHCI".
Here are the original Controller names:
DEV_2922&CC_0106 = "Intel(R) ICH9R/DO/DH SATA AHCI Controller"
DEV_2923&CC_0106 = "Intel(R) ICH9 Family 4 Port SATA AHCI Controller"
Regards
Dieter (alias Fernando)
Hi and thank you for the quick answer.
Thatâs not the problem, before changing from IDE to AHCI I tried to force first the Dev_2923 and after that I also tried the DEV_2922. Both gave me blue screen after rebooting and changing to AHCI.
In IDE mode the controllers are identified as Dev_2921 and Dev_2926. Perhaps Dev_2923 is not the corresponding AHCI id for this particular controller?
@Adrian1 : The third Intel ICH9 AHCI Controller I know is DEV_2929&CC_0106 = "Intel(R) ICH9M-E/M SATA AHCI Controller"
I think we can rule that out, I made another partition on the SSD and install Win 7 in AHCI mode (using the defalt AHCI driver in Win 7) and the hardware ID for the AHCI controller is seen as Dev_2923.
Iâm not sure which driver file 2923 I chose when I forced the moded driver on XP, maybe I picked the one with AHCI in the name and I should have picked the iastore one? (or the other way around?) Iâll give it a try and let you know
@Adrian1 :
Since there is only 1 Controller listed with the DeviceID DEV_2923 (the AHCI one), you cannot mix them.
Make sure, that you just choose the listed "Intel(R) SATA AHCI Controller DEV_2923 added by Fernando" and nothing else.
Dieter, I finally done it 
The catch was that this particular controller was NOT requiring to be pointed to iastore.inf but to iaAHCI.inf. By the time I was trying it the system was rebooting before finishing the forceful installation of the drive on the first instance of standard IDEr, so I had to select the second instance of the standard IDE present in my device manager (didnât took a screenshot but I hope it makes sense).
And behold, it worked.
Now in my Device manager it appears like this (the PCI IDe controller is some Jmicron SATA to IDE):
Hopefully this will help others who find themselves in my situation. No registry editing was required.
Thanks a lot.
@Adrian1 :
It is fine, that you finally succeeded!
Who gave you the advice to hit onto the iaStor.inf file, which is only relevant for RAID users?
Itâs actually all over the internet when you google for âswitch win xp to ahci ICH9â or something similar. People usually donât take the time to explain in detail how they did it and what were the system specs (in this case the exact MoBo model). Now I know that those who got it working using iaStor.inf had ICH9r.
Anyway, it all ended well
@Adrian1 :
This is not correct.
Users with an Intel ICH9R Southbridge system, who want to run their on-board Intel SATA Controller in "AHCI" mode, have to use the same iaAHCI.inf file as you, but have to choose the "Intel(R) SATA AHCI Controller DEV_2922 added by Fernando".
Only Intel RAID users can use the file iaStor.inf, but the related DEV_2822 Intel SATA RAID Controller is identical for Intel ICH9R and ICH9 Southbridges.
I see, thought the R in ICH9r was for raid.
In any case, now the relevant info is spelled out as clear as it gets, if I could find something similar last Saturday it would have saved me a few good hours of toggling between AHCI and IDE.
Hi there! I use the enWin7x64_Pro_SP2.10 file iso from Fernando trying to install on my HYSTOU computer which came with WIN 10.
The USB is working but both NVMe and SATA SSD donât show up.
I tried to understand how I can find out the chip set and dismantled the computer to look at the mobo to no avail.
Device manager: " Standard SATA AHCJ Controller:
PCI\VEN_8086&DEV_9DD3&SUBSYS_72708086&REV_30
PCI\VEN_8086&DEV_9DD3&SUBSYS_72708086
PCI\VEN_8086&DEV_9DD3&CC_010601
PCI\VEN_8086&DEV_9DD3&CC_0106
Processor the i7-8565U is a âWhiskey Lakeâ 8th Gen
Is this enough information?
So itâs about the signed driver I can point to during install.
(I previous installed an desktop computer Z390 with said iso which worked like a charm, many thanks again!)
@Z390 :
Here are my answers to your requests:
-
AHCI Support of Win7:
Win7 has an in-box generic AHCI driver, which should support your on-board Intel SATA AHCI Controller from scratch. If you want to use any of my mod+signed Intel AHCI drivers, you should install them after having completed the OS installation.
All my currently offered mod+signed Intel AHCI drivers do support your posted HardwareIDs, but these drivers usually cannot be used during the installation of the OS. Since the OS Setup cannot verify the trustworthiness of the signing Company, only WHQL certified third party storage drivers are accepted during the OS installation. Once the OS is up and runnng, you can install the desired mod+signed Intel AHCI driver, but donât forget to import the Win-RAID CA Certificate before starting the installation. -
NVMe Support of Win7:
Win7 has natively no NVMe in-box NVMe driver. If you want to get NVMe support from scratch, you should boot off a Win7 ISO, where the MS NVMe Hotfixes had been integrated into the BOOT.wim and INSTALL.wim. >Here< you can find the download links to the required MS NVMe Hotfixes.
@ Fernando: Thank you for your answer.
I added a SATA SSD because I thought that would allow me to install WIN7.
From what I read the two options are:
1) Fiddle with bios settings and trying to install on de SATA disk anyway if possible
2) Trying to get the NVMe driver to work and install on NVMe disk
I used an ISO from you with an NVMe driver so perhaps that wouldnât work anyway?
@Z390 :
Since the best solution will be to use the NVMe SSD as system drive (having the OS and the boot sector on it), I recommend to temporarily unplug the SATA HDD/SSD and to install Win7 in UEFI mode onto the NVMe SSD.
If the Win7 Setup shouldnât detect the NVMe SSD, when it asks you where to install the OS, you will have to insert the NVMe Hotfixes into the Win7 Images and to redo the installation thereafter.
I donât know it, because I have never offered any Win7 ISO. Maybe the ISO you got from anyone else contains 1 or more drivers, which had been modified and signed by me, but the creation and hosting of the ISO was not done by me.
@Fernando : Sorry, the ISO " 2.1 ISO win 64 bit English " was from the user PatrickK.
Second sorry: It just dawned on me that the internal SSD, although it looks like it, is isnât a NVMe SSD. (I should have known by the Crystal Disk bench under WIN 10.)
I will try to figure out a way to get it all going. At the moment I think that I should try perhaps a ISO with only an USB driver slipped in and not an NMVe driver also like the one I used.
This all is one step beyond my level of knowledge but I want the small power efficient computer on my boat, and especially in that circumstance WIN10 is for me a 100% no go for perhaps obvious reasons. (I have to be absolutely in charge of network traffic)
@Kwstas :
Welcome to the Win-RAID Forum!
The mod+signed Intel AHCI drivers, which I am offering within the start post, should support the on-board Intel SATA AHCI Controllers of all Intel chipset systems from 6-Series up (inclusive X79) and all Win10 versions.
Another question is, whether the replacement of the much newer (donât believe the shown date) generic Win10 in-box MS AHCI driver named STORAHCI by an older Intel driver is useful for the specific system or not.
Regards
Dieter (alias Fernando)