Zitat von Fernando im Beitrag #15

---

@XPLives:
ASRock is offering Intel's drivers and not ASRock's drivers.
Why do you insist claiming, that ASRock has modified Intel's drivers? From whom do you know, that the modification hasn't been done by Intel?

---

A driver really only consists of binary components, the .sys file, an .inf guide, and possibly helper items like dynamic link libraries (with the main driver in the .sys file.) This "OEM" file sounds like some extra metadata file included in ASRocks's driver bundle, and as the .sys file is identical to that provided by Intel, ASRock did *not* modify the driver regardless of whatever they did to the OEM file.

This would be like saying they modified the driver by changing a word in the provided readme.txt.

I've never heard of anything aside from the .sys file having a provided certificate .cat file either, the OEM file would not need to be resigned as it wasn't hashed/verified to begin with as it is not part of the driver binary.

You only use the drivers for parts of the motherboard, things like the chipset, USB controller, and so forth - you could feasibly have multiple "motherboard IDs" which use the same set of drivers, and the IDs provided in this OEM file are probably intended as a guide to see if the driver set for the drivers themselves to see if they need to even be installed.

@Omicron:

When using the Device Manager manual driver installation method the TXTSETUP.OEM will not be required because you are already inside the OS. All you will need is the .INF and the .SYS and whatever files the .INF lists required for the device. Modifying the .INF will break the certification but in some ways this is the only way to compact the drivers list needed to be installed for the device to work. Often times they add files that are not required. I was able to reduce a couple hundred MBs of files of space used by an nVidia driver down to less than 20MBs compressed for driver installation. So there was tremendous bloat in nVidia installer packages.

I don't think you have a firm enough grasp of 2000/XP/2003 F6 installation methods regarding the TXTSETUP.OEM as it used to load drivers during the initial OS installation stage using a Floppy Disk Drive. Fernando may not even be familiar with using this method either as I doubt he uses floppy disk drive equipped systems which is why nLite is the easier solution for beginners.

The TXTSETUP.OEM is not a simple readme.txt file. If it were it would have no effect on the F6 driver installation process and you could remove it. If you attempt this it will error if not present.

Nlite performs a similar automated method of this but it does some unnecessary modifications of certain OS files and is why it's usually used by beginners. More advanced skills are required to use the TXTSETUP.OEM method. I had to perform close to a hundred different test installs to get a better sense of how it works during Unattended install experiments.

The TXTSETUP.OEM file is needed during the F6 stage to install a driver through a Floppy disk drive or a USB Floppy disk drive.

The TXTSETUP.OEM offers a selection menu of devices which can be customized. But without it you could not install the driver using the F6 method or could also be used to perform an Unattended Installation with the drivers detected during the OS install process. If you only had the .INF and the .SYS files it would not be enough as it will continue to request the TXTSETUP.OEM file.

I never said AsRock modified the actual device driver as AsRock would never modify the actual driver or it would break the certification and add more work for Intel or MS to recertify it and highly doubtful Intel would "EVER" release the source code of their Intel SATA driver to other companies unless they had a NDA. I said AsRock modified the driver package that differed from the Intel one which you clearly are not understanding. The packages are different regarding the TXTSETUP.OEM files and the layout of the files inside it as well. My point was AsRock modified this TXTSETUP.OEM and not Intel which Fernando either disagrees with or doesn't understand and thinks Intel did it. So I'll have to clearly spell it out further as the proof is already provided and maybe unaware.

If you examine the two TXTSETUP.OEM files:

The AsRock one will show these items to choose from during the F6 setup process.

[Actual ASROCK List First Seen]
Intel(R) Desktop Express Chipset SATA AHCI Controller - Windows XP <--- DEFAULT SELECTION (aAHCI32_DesktopWorkstationServer)
Intel(R) Desktop Express Chipset SATA AHCI Controller - Windows XP64
Intel(R) Desktop Express Chipset SATA RAID Controller - Windows XP
Intel(R) Desktop Express Chipset SATA RAID Controller - Windows XP64

[Defaults]
scsi = iaAHCI32_DesktopWorkstationServer <--- This line in the AsRock TXTSETUP.OEM determines what default device is if first selected in the F6 Setup Menu once the Floppy Disk has read the driver info.

The AsRock default refers to: Intel(R) Desktop Express Chipset SATA AHCI Controller - Windows XP
PCI\VEN_8086&DEV_1C02&CC_0106

The Intel default refers to: Intel(R) Mobile Express Chipset SATA RAID Controller
PCI\VEN_8086&DEV_282A&CC_0104

The Intel match to Asrocks calls it Intel(R) Desktop/Workstation/Server Express Chipset SATA AHCI Controller

---Lining them up---------------------------------------------------------------------------------------------------------------
You can now compare the two:
Intel(R) Desktop Express Chipset SATA AHCI Controller - Windows XP <--- AsRock description
Intel(R) Desktop/Workstation/Server Express Chipset SATA AHCI Controller <--- Intel description
-----------------------------------------------------------------------------------------------------------------------------------

Intel would never add the words "- Windows XP" or "- Windows XP64" to their device description for the items in the TXTSETUP.OEM found on Intel's website.
And you can see in the AsRock version the words "/Workstation/Server" have been removed.
This clearly shows you that the Asrock version is different from the Intel version. The Hardware IDs are also completely different for the default selection settings.


The reason why you see this in my opinion it was modified specifically by AsRock for their internal floppy drive F6 installation. They purposely filtered down 15 items found in the Intel's original version and parsed it down to just these 4 or if they had access to the driver earlier on 5 months prior then they only added their motherboards 4 listed options and Intel added the rest to their own TXTSETUP.OEM later to support more:
1 for XP 32-Bit AHCI
1 for XP 64-Bit AHCI

1 for XP 32-Bit RAID
1 for XP 64-Bit RAID

During the F6 stage driver installation you will only see these four items listed to choose from listed above and the rest are not selectable or shown.

On the Intel's original Floppy setup it will be different and will have 15 options total.

[Defaults]
scsi = iaStor_Mobile <--- This line in the Intel TXTSETUP.OEM determines what default device is if first selected in the F6 Setup Menu once the Floppy Disk has read the driver info.

[THIS IS THE MENU LIST BELOW]
Intel(R) ICH7R/DH SATA AHCI Controller
Intel(R) ICH7M/MDH SATA AHCI Controller
Intel(R) ICH9R/DO/DH SATA AHCI Controller
Intel(R) ICH9M-E/M SATA AHCI Controller
Intel(R) ICH10D/DO SATA AHCI Controller
Intel(R) ICH10R SATA AHCI Controller
Intel(R) 5 Series 4 Port SATA AHCI Controller
Intel(R) 5 Series 6 Port SATA AHCI Controller
Intel(R) 5 Series/3400 Series SATA AHCI Controller
Intel(R) Desktop/Workstation/Server Express Chipset SATA AHCI Controller
Intel(R) Mobile Express Chipset SATA AHCI Controller
Intel(R) ICH7R/DH SATA RAID Controller
Intel(R) ICH7MDH SATA RAID Controller
Intel(R) Desktop/Workstation/Server Express Chipset SATA RAID Controller"
iaStor_Mobile = "Intel(R) Mobile Express Chipset SATA RAID Controller" <--- DEFAULT SELECTION
Since the DEFAULT item is located at the very bottom of the file you should see these four items listed initially and would have to scroll up to see the rest.


[Actual INTEL List First Seen]
Intel(R) ICH7R/DH SATA RAID Controller
Intel(R) ICH7MDH SATA RAID Controller
Intel(R) Desktop/Workstation/Server Express Chipset SATA RAID Controller
"Intel(R) Mobile Express Chipset SATA RAID Controller" <--- DEFAULT SELECTION (iaStor_Mobile)


Since the Default for the Intel version is iaStor_Mobile is for "Intel(R) Mobile Express Chipset SATA RAID Controller".
If the user was using this on the AsRock Z68 Desktop Hardware ID and the user were to hit ENTER and select this item the installation would fail with the BSOD 7B early on.

This is why the AsRock version appears modified by AsRock for the intent of selecting the correct matching Hardware ID by default for a Windows XP 32-Bit SATA AHCI driver installation for their Z68 series motherboard. This filtering down of other Hardware devices from being shown was by "intent" from AsRock. Intel would never customize the TXTSETUP.OEM in this manner for a Floppy disk installation. If you observe all other Intel Floppy Based SATA driver packages they would never add "- Windows XP" or "- Windows XP64" to any of their items and the default highlighted initial item would most likely will be iaStor_Mobile which would highlight "Intel(R) Mobile Express Chipset SATA RAID Controller".

Since I've done numerous F6 Floppy disk installations over the years and even modified the TXTSETUP.OEM there is no other reasonable conclusion as to why the Asrock version vs the Intel Floppy driver packages are different.

If you are still not convinced you could try installing the Intel SATA driver package yourself and use a USB floppy on a Sandy Bridge Z68 system during the F6 stage and use the default Intel(R) Mobile Express Chipset SATA RAID Controller and it will give you a BSOD 7B.

Now if you had a matching Z68 Hardware Id motherboard which hopefully it should be the same for another Z68 motherboard and repeated the process with the AsRock Floppy SATA driver it should work without a BSOD 7B.

If you can list any Intel Floppy based SATA storage driver off Intel's own site that shows Intel doing this same exact kind of TXTSETUP.OEM modification adding - Windows XP and - Windows XP64 to the device description I'd like to see it. Intel would never add the OS to the name of the device in this manner and I found another case of this happening in another AsRock MB chipset Floppy SATA driver package. There might be other Floppy packages from Asus and Asrock with modified TXTSETUP.OEM files like this since they are related companies but not on Intel's own site.

Also one other difference I noticed was the Intel 64-Bit Driver package is isolated just like the Intel 32-Bit Driver package with their own individual TXTSETUP.OEM file and not shared. Only the AsRock package combines both the XP 32-Bit and XP 64-Bit driver selectable options into one convenient TXTSETUP.OEM file. Only AsRock could have modified it this way. I could not find any Intel XP 32-Bit and XP 64-Bit TXTSETUP.OEM integrated together like this on Intel's site.

By using this TXTSETUP.OEM method of Unattended installation it also allowed me to get Intel USB 3.0 controllers working in XP for the first time never done by anyone else. Sometimes the hardest way turns out is the best way...



[BREAKDOWN OF THE ASROCK VS INTEL TXTSETUP.OEM FILES]
http://asrock.pc.cdn.bitgravity.com/Driv...0.8.0.1003).zip
[Asrock] TXTSETUP.OEM v10.8.0.1003
Monday, May 09, 2011, 4:18:10 PM
2.43 KB (2,493 bytes)

Ah, I think we just have a case of people being on different pages here.

No, I'm not highly familiar with the old driver install process of the "PE" text mode environment of Windows XP/2003 (5.1/5.2) other than using it *once* to load an AHCI driver. I pretty much ditched 2003 when Windows 7 came out as there was finally a reason to upgrade - the 5.X kernel series became antiquated to me.

I was just saying to Windows 7, something like that OEM file is comparable to a text file as it isn't even touched to my knowledge - and that my discussion comes from a higher familiarity with newer 6.X drivers.

Now, if a manufacturer managed to actually modify a .sys binary driver file, that would be "modification of the driver" per my experience.

I'm actually sort of curious, there are xHCI/USB 3.0 drivers that actually work on XP? I had no idea anyone did/tried that.