I am writing a protocol driver and in my stack I need to update some system provided driver, but WFP keeps reverting that back.
I have to delete from all other places and then copy, muck registry/restart etc.
I hread there is a key for every driver in registry which has the loaction of the drier wher eit is picked from.
Can somebody let me know where I can find that registry key for any given .sys file, so that I can change that to point my debug dir instead of system32\driver default dir?
----- Original Message ----- From: To: “Windows System Software Devs Interest List” Sent: Wednesday, November 28, 2007 7:32 PM Subject: [ntdev] Disabling WFP
> All > > I am writing a protocol driver and in my stack I need to update some > system provided driver, but WFP keeps reverting that back. > I have to delete from all other places and then copy, muck > registry/restart etc. > > I hread there is a key for every driver in registry which has the loaction > of the drier wher eit is picked from. > Can somebody let me know where I can find that registry key for any given > .sys file, so that I can change that to point my debug dir instead of > system32\driver default dir? > > thanks, > > — > NTDEV is sponsored by OSR > > For our schedule of WDF, WDM, debugging and other seminars visit: > http://www.osr.com/seminars > > To unsubscribe, visit the List Server section of OSR Online at > http://www.osronline.com/page.cfm?name=ListServer
If your goal is really what you state, disabling WFP or changing the Windows directory or whatever is like shooting a fly with an elephant gun.
Dude… You want to load the debug version of a system-supplied driver, or a replacement for a driver under WFP? Use KDFILES in WinDbg. Read this: http://www.osronline.com/article.cfm?article=238
Peter
I need to replace a system provided .sys with the newest one that has not yet made to service pack etc.
They could modify or manually delete from dllcache, replace or muck registry etc (prepping test machines etc when no debug setup is yet there).
Definietely .kdfiles for my own stack .sys’es during debug!
Are you trying todo this on customer machines? Or just during debug? You are not allowed to ship OS binaries that are prerelease, the only way you can replace a system driver is with a MSFT provided QFE
Peter
I need to replace a system provided .sys with the newest one that has not yet made to service pack etc.
They could modify or manually delete from dllcache, replace or muck registry etc (prepping test machines etc when no debug setup is yet there).
Definietely .kdfiles for my own stack .sys’es during debug!
You can’t use the kdfiles technique for boot start drivers. There is another
similar mechanism documented for boot drivers, but as far as I can tell,
that mechanism has never worked. You can of course eradicate all traces of
storport.sys from your test system and then brute force copy over your test
storport.sys. That works pre-vista.
On Nov 29, 2007 1:50 AM, wrote:
> Just during internal debug/test for storport.sys (2k3) > > — > NTDEV is sponsored by OSR > > For our schedule of WDF, WDM, debugging and other seminars visit: > http://www.osr.com/seminars > > To unsubscribe, visit the List Server section of OSR Online at > http://www.osronline.com/page.cfm?name=ListServer >
If I recall correctly, I’ve gotten it to work for boot drivers, but it
was most particular about order, particular directory path (considering
aliases) and perhaps case. That being said, I would also just wipe it
out and replace it, as it sounds like you won’t be doing this commonly.
Good luck,
mm
Mark Roddy wrote:
You can’t use the kdfiles technique for boot start drivers. There is
another similar mechanism documented for boot drivers, but as far as I
can tell, that mechanism has never worked. You can of course eradicate
all traces of storport.sys from your test system and then brute force
copy over your test storport.sys. That works pre-vista.
On Nov 29, 2007 1:50 AM, > mailto:xxxxx> wrote: > > Just during internal debug/test for storport.sys (2k3) > > — > NTDEV is sponsored by OSR > > For our schedule of WDF, WDM, debugging and other seminars visit: > http://www.osr.com/seminars > > To unsubscribe, visit the List Server section of OSR Online at > http://www.osronline.com/page.cfm?name=ListServer > > > > > – > Mark Roddy</mailto:xxxxx>
Mark
For storport.sys yes I will just replace it etc.
For other drivers in my stack - virtual bus driver, ndis protocol driver and storage miniport driver can I use .kdfiles with 1394 or should I have to go serial only?
–thanks
For your own drivers you are faced with the same boot start issue. If they
are boot start you either have to figure out how to get the windbg boot
driver replacement thing working, or replace them manually before rebooting
the test system. If they are not boot start then .kdfiles works great.
On Nov 29, 2007 11:22 PM, wrote:
> Mark > For storport.sys yes I will just replace it etc. > For other drivers in my stack - virtual bus driver, ndis protocol driver > and storage miniport driver can I use .kdfiles with 1394 or should I have to > go serial only? > --thanks > > — > NTDEV is sponsored by OSR > > For our schedule of WDF, WDM, debugging and other seminars visit: > http://www.osr.com/seminars > > To unsubscribe, visit the List Server section of OSR Online at > http://www.osronline.com/page.cfm?name=ListServer >