Install path for custom device driver

N

news

Hi,

We have written a Windows device driver for a custom peripheral in our
embedded product, the peripheral is accessed via the ISA bus. We are
booting from a compact flash card partitioned into C: and D:, with EWF
enabled on C:
As there are likely to be updates to the driver after the product has
shipped, we would like to install the driver .sys on the D: partition
to avoid having to disable/enable the EWF. Currently the files are
installed to c:\windows\system32. We have tried modifying the install
script to specify D:\Drivers as the install path, this appears to work
but when the system is re-booted a 'file not found' error is displayed
and the driver doesn't load.

Has anyone tried to do this, is it possible or is the \windows
\system32 path hard-coded? The driver was built with the MS DDK, I
haven't tried to create a component for it yet until I can get this to
work on a desktop XP Pro system on the same hardware.

Thanks
 
V

valkr1e

I believe the system32 path that windows uses is the path variable, I doubt a
simple registry hack would get around this as that is ewf protected. why not
simply perform a commit on the EWF after the install?
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top