Thanks Jason! I have tried it. Strip all ahcix64 from txtsetup.oem file: [Disks] disk1 = "AMD AHCI Compatible RAID Controller Driver Diskette", ahcix86, \
[Defaults] SCSI = Napa_i386_ahci8086 [SCSI] Napa_i386_ahci8086 = "AMD AHCI Compatible RAID Controller-x86 platform", ahcix86 [Files.SCSI.Napa_i386_ahci8086] inf = disk1, ahcix86.inf driver = disk1, ahcix86.sys, ahcix86 catalog = disk1, ahcix86.cat [HardwareIds.SCSI.Napa_i386_ahci8086] id = "PCI\VEN_1002&DEV_4380&SUBSYS_280A103C", "ahcix86" . [Config.ahcix86] value = "", Tag, REG_DWORD, 1 But after checking the disk, and under copy files it sad that could not copy ahcix86.inf, ahcix86.cat and ahcix86.sys :( As a last chance I have try install from CD and floppy with "stripped" driver disk. It's again complain that it could not copy ahcix86.inf file - as a prompt idea, I have pull the floppy and copy the \x86 folder and drivers - wow, it's found drivers and proceed with installation. I have tried the cleaned (no $OEM$ folder at all) XP sp3 install using unattended with prepared driver floppy. It couldn't copy the driver from floppy which is worked some minutes ago with "original" install disk (it's not really original because of the slipstreamed sp3). Next I have retry install from CD - for sure - it's working as before, the disk is good for sure. txtsetup.oem does not contain anything points to other folder. Is it possible that from point of copy it lookup inf file? What is going on. Any more ideas? May be strip all unneeded vendor/device pci IDs? Sincerely tovis > I ran into the same problem some time ago, and got it working quickly enough. As I recall, the problem is in the [Disks] section. Windows does not like looking in subdirectories for textmode drivers. Go figure. > > Attached my own TXTSETUP.OEM file. Note that I don't use 64-bit Windows, so I manually stripped all references to the 64-bit drivers, and deleted the relevant files. In my case, I have the following files: > > ahcix86.cat, ahcix86.inf, ahcix86.sys > > ... just sitting in the i386\$oem$\textmode\ directory, alongside TXTSETUP.OEM. And [Disks] simply points to ahcix86.sys in the root [textmode] directory. > > If you need the 64-bit driver, you should probably drop it into > amd64\$oem$\textmode\ ;) > > Also note that I deploy to machines that require the Intel AHCI/RAID textmode drivers as well, and they are in the same TXTSETUP.OEM file, just using disk1 and disk2. The driver files also share the textmode directory. I've stripped all of the information from the attached TXTSETUP.OEM file, just to keep it concise. But it's definitely possible to include as many textmode drivers as needed. Well, within reason, I guess. I'm not about to comment on the scalability of the Windows textmode installation... :P > > > On 12/15/2010 08:41 AM, tovis wrote: >> Dear list! >> I've got run to problem with text mode (F6 mode) driver installation. I've >> a main board GA-MA74-S2H with the next type of AHCI controller on it (excerpt from "#lspci -vnn" output): >> 00:11.0 SATA controller [0106]: ATI Technologies Inc SB700/SB800 SATA Controller [AHCI mode] [1002:4391] (prog-if 01 [AHCI 1.0]) >> Subsystem: Giga-byte Technology Device [1458:b002] >> Flags: bus master, 66MHz, medium devsel, latency 32, IRQ 22 >> I/O ports at ff00 [size=8] >> I/O ports at fe00 [size=4] >> I/O ports at fd00 [size=8] >> I/O ports at fc00 [size=4] >> I/O ports at fb00 [size=16] >> Memory at fe02f000 (32-bit, non-prefetchable) [size=1K] >> Capabilities: [60] Power Management version 2 >> Capabilities: [70] SATA HBA v1.0 >> Kernel driver in use: ahci >> I've get the driver from Gigabyte WEB site, but this look like a little bit unusual: >> │ readme.txt >> │ ahcix86 .. contain only 10 bytes : fastsx >> │ ahcix64 .. contain only 10 bytes : fastsx >> │ txtsetup.oem >> │ >> ├───x64 >> │ ahcix64.inf >> │ ahcix64.cat >> │ ahcix64.sys >> │ >> └───x86 >> ahcix86.sys >> ahcix86.inf >> ahcix86.cat >> Excerpt from "txtsetup.oem" : >> [Disks] >> disk0 = "AMD AHCI Compatible RAID Controller Driver Diskette", \ahcix86, >> \ >> disk1 = "AMD AHCI Compatible RAID Controller Driver Diskette", \ahcix86, >> \x86 >> disk2 = "AMD AHCI Compatible RAID Controller Driver Diskette", \ahcix64, >> \x64 >> [Defaults] >> SCSI = Napa_i386_ahci8086 >> [SCSI] >> Napa_i386_ahci8086 = "AMD AHCI Compatible RAID Controller-x86 platform", >> ahcix86 >> Napa_amd64_ahci = "AMD AHCI Compatible RAID Controller-x64 platform", >> ahcix64 >> [Files.SCSI.Napa_i386_ahci8086] >> inf = disk1, ahcix86.inf >> driver = disk1, ahcix86.sys, ahcix86 >> catalog = disk1, ahcix86.cat >> [Files.SCSI.Napa_amd64_ahci] >> inf = disk2, ahcix64.inf >> driver = disk2, ahcix64.sys, ahcix64 >> catalog = disk2, ahcix64.cat >> [HardwareIds.SCSI.Napa_i386_ahci8086] >> id = "PCI\VEN_1002&DEV_4380&SUBSYS_280A103C", "ahcix86" >> .. >> [HardwareIds.SCSI.Napa_amd64_ahci] >> id = "PCI\VEN_1002&DEV_4380&SUBSYS_280A103C", "ahcix64" >> .. >> [Config.ahcix86] >> value = "", Tag, REG_DWORD, 1 >> [Config.ahcix64] >> value = "", Tag, REG_DWORD, 1 >> First time I was simply copy whole thing under >> xpsp3/I386/$OEM$/TEXTMODE/ >> folder. The installer, when copying drivers sad that it's skip folders x86 >> and x64 - of course windows installer stuck with error code 18 "can not load "\$WIN_NT$.~BT\$OEM$\x64\ahcix64.sys" file. >> OK I have using RIP Linux and copy files to appropriate places >> (\$WIN_NT$.~BT\$OEM$\x64\ and \$\$1\TEXTMODE\ for sure). Restart, process >> goes further - start "windows system", check disks and before start copying files stuck, that it can not copy ahcix64.inf, ahcix64.sys and ahcix64.cat >> (for testing I have skip them, and after reboot it's hang as suspected). >> The next what I have tried copy all drivers under one folder, and edit the >> "txtsetup.oem" : >> [Disks] >> disk0 = "AMD AHCI Compatible RAID Controller Driver Diskette", ahcix86, \ >> disk1 = "AMD AHCI Compatible RAID Controller Driver Diskette", ahcix86, \ >> disk2 = "AMD AHCI Compatible RAID Controller Driver Diskette", ahcix64, \ >> The result was different, start system was OK (check disk is OK) but on copy it doesn't found any parts (inf, cat, sys) of driver. >> I've clean whole x86 part, left only x64 (for now it would be enough), "move" everything into disk1 and "\" but I've get error in parser .c code >> on line xxxx. >> At last I have copy whole thing on a floppy, using F6 functionality - again doesn't work ... It can not load the ahcix64.sys file :( >> For now I will be happy with x64 AHCI driver to use. Would be so kind some >> one and give me a hand? First time i have seen multi folder driver disk for F6. >> Sincerely >> tovis >> ------------------------------------------------------------------------------ Lotusphere 2011 >> Register now for Lotusphere 2011 and learn how >> to connect the dots, take your collaborative environment >> to the next level, and enter the era of Social Business. >> http://p.sf.net/sfu/lotusphere-d2d >> _______________________________________________ >> unattended-info mailing list >> unattended-info@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/unattended-info > ------------------------------------------------------------------------------ Lotusphere 2011 > Register now for Lotusphere 2011 and learn how > to connect the dots, take your collaborative environment > to the next level, and enter the era of Social Business. > http://p.sf.net/sfu/lotusphere-d2d_______________________________________________ unattended-info mailing list > unattended-info@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/unattended-info > ------------------------------------------------------------------------------ Lotusphere 2011 Register now for Lotusphere 2011 and learn how to connect the dots, take your collaborative environment to the next level, and enter the era of Social Business. http://p.sf.net/sfu/lotusphere-d2d _______________________________________________ unattended-info mailing list unattended-info@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/unattended-info
