Copying additional Files during WINNT OS Installation

hi all,
I have a SCSI Miniport Driver for Windows NT Which installs file and
works fine. I have two DLLs and one EXE that i want to Copy to a particular
location (WinNT\system32) when i install the driver. I am able to do this if
i go to Control Panel-> SCSI ADAPTERS then add my driver. I tried the same
thing during OS Installation using my Driver by modifying the txtsetup.oem
file but when i select my driver (by pressing F6 during setup) i get a error
messege :

" Unexpected Error occured at the following
location: Line 2245 H:XXX\YYY\OemDir"

The same chnaged in txtsetup.oem works fine for win2k.
Is there a possibiliy that i will be able to copy some additional files when
my .sys is being copied During OS installation on my Adapter?? How do i do
that??

Any help is highly appriciated.

Thanks
ajitabh

You have stumbled upon the same “feature” that I did some time ago, namely
that the txtsetup.oem and oemsetup.inf files used during OS installation
for Windows NT do not apparently support copying any other files besides
the driver (a DLL= line in the txtsetup.oem file causes that error).

I couldn’t find a way around this, just had to have the user run an
installation program after the OS is built.

Good luck.
Greg

did you try putting the entries into your regular device INF? I thought
GUI-mode setup should be processing the device INFs normally to get
everything configured … txtsetup.sif is simply for getting enough of
the system together to run GUI-mode setup.

-p

-----Original Message-----
From: Greg de Valois [mailto:xxxxx@yahoo.com]
Sent: Wednesday, October 30, 2002 9:58 AM
To: NT Developers Interest List
Subject: [ntdev] Copying additional Files during WINNT OS Installation

You have stumbled upon the same “feature” that I did some time ago,
namely
that the txtsetup.oem and oemsetup.inf files used during OS installation

for Windows NT do not apparently support copying any other files besides

the driver (a DLL= line in the txtsetup.oem file causes that error).

I couldn’t find a way around this, just had to have the user run an
installation program after the OS is built.

Good luck.
Greg


You are currently subscribed to ntdev as: xxxxx@microsoft.com To
unsubscribe send a blank email to %%email.unsub%%

No, putting CopyFiles entries in the oemseutp.inf file didn’t work either
for WINNT. Worked fine through Device Manager, and with Win2k, but not
during NT text setup.