Vitaly, thanks. I was just kind of fishing for educational purposes here anyway. I was really just trying to get into the mechanics of the $OEM$ install process. On second thought, without choosing the TEXTSETUP.OEM, your program might not pick it up correctly, and thereÂ’s no reason to mess around with unneeded manual labor. It might want to see it as a PnP driver that would defeat the purpose.
I think your comments that “it runs problem-free” (and it does), and that your method mirrors the same one used by Microsoft are key comments.
No problem on the language. IÂ’m on a German board, and I appreciate your efforts. Thanks again.
On May 23, Intel updated their (TEXTMODE) RAID and SATA drivers (and their PnP chipset INF drivers). The RAID and SATA drivers are still contained within the executable program called
iata57_enu.exe at the same location.
You no longer have to extract the iaStor drivers from the executable in the manner described above. Intel has simplified the process.
All you have to do is use a program like Winzip, Winrar, or 7-Zip to extract all files to wherever – iata57_enu would be the default. When you extract the files from the iata57_enu.exe, there is now a
Winall folder that is created. Within the
Winall folder there is a
Driver folder and a
Driver64 folder that contains the latest mass storage drivers.
if you intergrate textmode drivers and then use a sysprep do they get added to build mass storage section of sysprep.ini ? i currently am having trouble adding textmode drivers and this tool may be my answer.
I don't know. May be it is enough to copy folow rows from winnt.sif to sysprep.ini:
Code:
[OemInfFiles]
OemDriverFlags=1
OemDriverPathName="%SystemRoot%\OEMDIR"
OemInfName="abc.inf","xyz.inf"
May be it isn't enough. I don't know how work sysprep.exe !
thank you for your quike reply. i just test and see if it works.