Hello,

I need to embed a security parameter in the export driver binary (Win2K/XP)
after compilation.

I have defined an array in data segment which is initailized with a unique
string. An external application then parses the driver sys file and modifies
it to the value I want.

When I use the export driver sys file, it does not load. Why does the export
driver not load?

Can I modify the driver file and still execute? I have done this for
application exe and it works.

Is there any other way I can perform the same task?

Thanks,

...Ram

If I understand you, you have in essence "patched" the binary SYS, wrote it
back out to dics, and then expect to load that file. Did you at the same
time re-compute the CRC for that file? If that is the case, I suspect you
will find Device Manager has your driver yellow banged and you will find an
event error concerning CRC not agreeing.

--
The personal opinion of
Gary G. Little

"Ram Nayak" <test@test.com> wrote in message
news:%23bjLWPmsGHA.4608@TK2MSFTNGP04.phx.gbl...

I think the proper way to this would be to go throuh WHQL and get a
certificate for the driver.

--
The personal opinion of
Gary G. Little

"Ram Nayak" <test@test.com> wrote in message
news:%23bjLWPmsGHA.4608@TK2MSFTNGP04.phx.gbl...

You must recompute the image checksum in the header, it is really checked for
drivers (and for KnownDLLs). To do this, run "editbin /release" or "link -edit
release".

In the good old NT4 days, I changed the Blue Screen of Death to the Gray Screen
of Death this way just patching a byte in hal!HalAcquireDisplayOwnership and
in hal!HalDisplayString, and then "editbin /release" on hal.dll

:-)

--
Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
maxim@storagecraft.com
http://www.storagecraft.com