Do [OemBootFiles] and the $OEM$\Textmode folder allow for subfolders?

[Gary Barrett]

I'm attempting to do unattended installations of Windows 2000 Server. I want
to have one set of binaries (i386 folder) but have a different unattend.txt
for each machine I deploy to

My problem is that the machines I deploy to can be varied types of server
each requiring different SCSI drivers for Mass Storage Devices. Windows
unattend documentation says that my scsi drivers have to be in the
$OEM$\Textmode folder. But I was thinking that it would be neat to place
each set of drivers in its own subfolder rather than lumping them all into
one

e.g. for some compaq servers the folders would be:
$OEM$\Textmode\DL360\
$OEM$\Textmode\1850R\

and then in the OemBootFiles section of the unattend.txt make reference to
the appropriate subfolder e.g:
[OemBootFiles]
DL360\cpq32fs2.sys
DL360\txtsetup.oem

But when I try to do an unattended deployment with this I get the following
error:
"Setup was unable to copy the following file:
cpq32fs2.sys"

i.e. it doesn't pick up on the subfolder even though it picks up on the
filename

The problem with lumping them all into the one subfolder is that the
txtsetup.oem files would overwrite each other and I can't be guaranteed that
the other filenames won't clash either.

Is what I'm trying to do possible? Has anyone got a solution?

Thanks,

Gary

[Nimbus]

I don't think you can use subfolders. I had two different adapters from
different vendors in my textmode folder; I combined the txtsetup.oem files into
one. If you look at them (at least in my case), it was fairly simple to figure
out.

Another possibility for you is to look into the custom PNP folders you can
specify. I suggest you check out the unattend.doc file in the Support Tools.