TeraByte Unlimited

Hi,

I'm trying to use the drvins_1/2.run example to come up with a way to inject the intel usb3 drivers into a windows 7 embedded 32bit image that has been restored to a PC with only USB3 ports. What looks to be the issue is a number of the files that get copied onto the system look to have strange permissions, and the drvint_2.run script running using tbosdtw.exe has a problem accessing them within windows. It usually errors on the ADD INF line with an "Access is denied." error.

I've had the OSDtool install those drivers to a point where the mouse/keyboard on USB3 work, but there are big problems with the system afterwords (specifically ewf/fbwf and user accounts).

Does anyone have any idea what could be going on here? Alternatively, does anyone have an example that does the usb3 driver upgrade to an image?

Thanks,
Jay

I would imagine you'd want to restore, boot, disable efw/fbwf, make changes,
enable again, create image?

the permissions of directly created files comes from the folder its in,
using the attribute not the metadata files.

as part of your process you could modify the scripts run to launch the
program to change acls (cacls / iacls)

Not sure what the issue of just using osdtool to inject the drivers if efw
is disabled, I'm not sure if enable/disable is simply a registry setting you
could modify or there is more to it?

"jstav" wrote in message news:[email protected]...

Hi,

I'm trying to use the drvins_1/2.run example to come up with a way to inject
the intel usb3 drivers into a windows 7 embedded 32bit image that has been
restored to a PC with only USB3 ports. What looks to be the issue is a
number of the files that get copied onto the system look to have strange
permissions, and the drvint_2.run script running using tbosdtw.exe has a
problem accessing them within windows. It usually errors on the ADD INF
line with an "Access is denied." error.

I've had the OSDtool install those drivers to a point where the
mouse/keyboard on USB3 work, but there are big problems with the system
afterwords (specifically ewf/fbwf and user accounts).

Does anyone have any idea what could be going on here? Alternatively, does
anyone have an example that does the usb3 driver upgrade to an image?

Thanks,
Jay

Hi, actually I’m looking to restore an image, disable ewf and install usb3 drivers from tbosdt and then boot into windows. The original pc is no longer available, and my target pc only has usb3 ports, so just booting the restored pc without the usb3 driver isn’t helpful as there is no mouse/keyboard control possible. Turning off ewf is just changing a registry value.

Thanks for the pointer on the permissions, I’ll see if those tools gets me there. It looks like the osdtool also suffers the same file permissions issue with the windows part of the driver installation on that pc.

Jay

Does the BIOS have an option to use the ports in USB 2 mode?

Have you tried installing those drivers from Dos or Linux (using the IFL boot disk for ex.)? So the target System does not have a drive letter and tbosdt is using its own accessing method.
Or try to remove the drive letter of the System before processing it.

Thanks to all. I needed to add the following line to the drvins_2.run file at the beginning to correct the file permissions of the driver files that drvins_1.run copies in.

The command:

icacls.exe c:\driverdirectory /grant system:F /t

Seems to have fixed the problem. Note that I also am seeing this issue when installing the driver with the osdtool.run tool, and it may be worthwhile to add a similar line to what is generated there.

Jay

Many thanks for your report. So yes, if running from Windows, it may be a good Idea to run this command

I'm wondering if we should not do this instead?
icacls.exe C:\driverdirectory /reset /T