Driverpacks does not use txtsetup.oem files... most of our drivers do not include this file (because we neither need it nor do we use it).
Try deleteing the txtsetup.oem file and see if opsi can properly deal with the driver files without it
. I assume it will because (again) most of the included driver folders do not contain this file anyway and opsi seems to deal with them just fine.
Yes, that fixed it. I've adapted our packaging mechanism so that this file is renamed to "txtsetup.oem.faulty" when the driverpacks are installed on our production machines to work around this.
I guess that the txtsetup.oem file would be required if the driver was required to be loaded during the Windows setup, but our test machine runs fine without it. Probably it would only be required if we would be using the BIOS fakeraid support, but I'm certain that none of our clients are using this, so it's not really a problem 
PS This is the DriverPacks support forum ... um... your not useing DriverPacks / DriverPacks BASE. What you're doing is technically not supported, but well see if we can help
I am removing the "BUG" tag from your title because you absolutely do not have a bug... You are not useing a supported method of implementing the DriverPacks. If you use them in an unsupported manner then you can't run over here and cry bug.
Sorry, that was not the intention 
I just wanted to notify you that I believed this to be a bug, namely a file that seems to contain an invalid path. If this isn't relevant to the DriverPacks project and you therefore close it, it's perfectly fine with me.
