Hi there,

I just have finished up my filter driver writting on 32bit WinXP and Vista.
The next thing I am currently doing is porting this filter driver to 64 bit
OSes. I have this filter driver built with "Win XP 64 bit build Envirnoment"
and it ended up these drivers neither work on XP nor Vista.

From the registry, I can tell that the filter driver service has been loaded
up but I can't see any my debug message print out from my driver.

I have been searching on net and forums but nothing useful except this thing
called "Kernel-Mode Code Signing". I start to suspect that my filter driver
does not work mostly because of this so-called "code-signing policy". Does
anyone can tell me am I on the right track?


Many thanks in advance.

Best Regards,
aze2cool

Re: Filter driver on 64 bit OSes by David

David
Mon Oct 15 22:12:12 PDT 2007

Try your 64 bit driver on an Itanium. It will load. It might even work.

"aze2cool" <aze2cool@discussions.microsoft.com> wrote in message
news:C199F2F7-007D-48AF-B382-0E7A641A6360@microsoft.com...
> Hi there,
>
> I just have finished up my filter driver writting on 32bit WinXP and
> Vista.
> The next thing I am currently doing is porting this filter driver to 64
> bit
> OSes. I have this filter driver built with "Win XP 64 bit build
> Envirnoment"
> and it ended up these drivers neither work on XP nor Vista.
>
> From the registry, I can tell that the filter driver service has been
> loaded
> up but I can't see any my debug message print out from my driver.
>
> I have been searching on net and forums but nothing useful except this
> thing
> called "Kernel-Mode Code Signing". I start to suspect that my filter
> driver
> does not work mostly because of this so-called "code-signing policy". Does
> anyone can tell me am I on the right track?
>
>
> Many thanks in advance.
>
> Best Regards,
> aze2cool
>



Re: Filter driver on 64 bit OSes by Bajamani

Bajamani
Tue Oct 16 04:27:54 PDT 2007

On Oct 16, 8:41 am, aze2cool <aze2c...@discussions.microsoft.com>
wrote:
> Hi there,
>
> I just have finished up my filter driver writting on 32bit WinXP and Vista.
> The next thing I am currently doing is porting this filter driver to 64 bit
> OSes. I have this filter driver built with "Win XP 64 bit build Envirnoment"
> and it ended up these drivers neither work on XP nor Vista.
> From the registry, I can tell that the filter driver service has been loaded
> up but I can't see any my debug message print out from my driver.

from registry you cannot tell whether your filter is loaded. In your
case it seems that the driver gets installed but it is not getting
loaded.


> I have been searching on net and forums but nothing useful except this thing
> called "Kernel-Mode Code Signing". I start to suspect that my filter driver
> does not work mostly because of this so-called "code-signing policy". Does
> anyone can tell me am I on the right track?

on Vista 64 bit drivers need to be signed, on XP64 this is not a
requirement. So if your facing same prob on XP64 then you can check
whether something is going wrong in the DriverEntry.


> Many thanks in advance.
>
> Best Regards,
> aze2cool




Re: Filter driver on 64 bit OSes by aze2cool

aze2cool
Tue Oct 16 06:04:00 PDT 2007



"Bajamani" wrote:

> On Oct 16, 8:41 am, aze2cool <aze2c...@discussions.microsoft.com>
> wrote:
> > Hi there,
> >
> > I just have finished up my filter driver writting on 32bit WinXP and Vista.
> > The next thing I am currently doing is porting this filter driver to 64 bit
> > OSes. I have this filter driver built with "Win XP 64 bit build Envirnoment"
> > and it ended up these drivers neither work on XP nor Vista.
> > From the registry, I can tell that the filter driver service has been loaded
> > up but I can't see any my debug message print out from my driver.
>
> from registry you cannot tell whether your filter is loaded. In your
> case it seems that the driver gets installed but it is not getting
> loaded.

I thought you can tell from the following registry key entry,
HKLM\System\CCS\Services\MyFilterDriver\Enum\xxx
where xxx is the index of the device. I might be wrong but this is how I
verify whether my filter service is up or not. Or is there any other way to
do that?

>
>
> > I have been searching on net and forums but nothing useful except this thing
> > called "Kernel-Mode Code Signing". I start to suspect that my filter driver
> > does not work mostly because of this so-called "code-signing policy". Does
> > anyone can tell me am I on the right track?
>
> on Vista 64 bit drivers need to be signed, on XP64 this is not a
> requirement. So if your facing same prob on XP64 then you can check
> whether something is going wrong in the DriverEntry.
>

Speaking of which, do I need to modify anything on DriverEntry when porting
to 64 bit XP/Vista? I have put some debug print message in DriverEntry
function but I don't see any of it and I would say my driver has never been
loaded up or skipped by the OS for some reason. That was why I kept thinking
it is the problem caused by "code-signing policy".

Does anyone out there has the same problem when trying to port existing 32
bit to 64 bit filter driver?

TIA.

Best Regards,
aze2cool





>
> > Many thanks in advance.
> >
> > Best Regards,
> > aze2cool
>
>
>
>

Re: Filter driver on 64 bit OSes by Don

Don
Tue Oct 16 06:21:27 PDT 2007


"aze2cool" <aze2cool@discussions.microsoft.com> wrote in message
news:BB3D5FF6-12AF-40FF-9E2B-E4D726E255EE@microsoft.com...
>
> I thought you can tell from the following registry key entry,
> HKLM\System\CCS\Services\MyFilterDriver\Enum\xxx
> where xxx is the index of the device. I might be wrong but this is how I
> verify whether my filter service is up or not. Or is there any other way
> to
> do that?
>
No there is no way to tell by the registry.

> Speaking of which, do I need to modify anything on DriverEntry when
> porting
> to 64 bit XP/Vista? I have put some debug print message in DriverEntry
> function but I don't see any of it and I would say my driver has never
> been
> loaded up or skipped by the OS for some reason. That was why I kept
> thinking
> it is the problem caused by "code-signing policy".
>

You have to enable debug prints for Vista, by default they will not show up.


--
Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting
Website: http://www.windrvr.com
Blog: http://msmvps.com/blogs/WinDrvr
Remove StopSpam to reply



Re: Filter driver on 64 bit OSes by aze2cool

aze2cool
Tue Oct 16 06:40:00 PDT 2007



"Don Burn" wrote:

>
> "aze2cool" <aze2cool@discussions.microsoft.com> wrote in message
> news:BB3D5FF6-12AF-40FF-9E2B-E4D726E255EE@microsoft.com...
> >
> > I thought you can tell from the following registry key entry,
> > HKLM\System\CCS\Services\MyFilterDriver\Enum\xxx
> > where xxx is the index of the device. I might be wrong but this is how I
> > verify whether my filter service is up or not. Or is there any other way
> > to
> > do that?
> >
> No there is no way to tell by the registry.
>
> > Speaking of which, do I need to modify anything on DriverEntry when
> > porting
> > to 64 bit XP/Vista? I have put some debug print message in DriverEntry
> > function but I don't see any of it and I would say my driver has never
> > been
> > loaded up or skipped by the OS for some reason. That was why I kept
> > thinking
> > it is the problem caused by "code-signing policy".
> >
>
> You have to enable debug prints for Vista, by default they will not show up.
>

Are you trying to tell me that the debug print I was using at 32bit Vista is
different from the 64bit?



Re: Filter driver on 64 bit OSes by Don

Don
Tue Oct 16 06:45:27 PDT 2007

No, but according to Microsoft and from what I have seen you do have to
enable registry settings to get DbgPrint's to work on the non-checked Vista.


--
Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting
Website: http://www.windrvr.com
Blog: http://msmvps.com/blogs/WinDrvr
Remove StopSpam to reply


"aze2cool" <aze2cool@discussions.microsoft.com> wrote in message
news:760FCE8C-76F4-4B49-98C8-FEBDAD70F14A@microsoft.com...
>
>
> "Don Burn" wrote:
>
>>
>> "aze2cool" <aze2cool@discussions.microsoft.com> wrote in message
>> news:BB3D5FF6-12AF-40FF-9E2B-E4D726E255EE@microsoft.com...
>> >
>> > I thought you can tell from the following registry key entry,
>> > HKLM\System\CCS\Services\MyFilterDriver\Enum\xxx
>> > where xxx is the index of the device. I might be wrong but this is how
>> > I
>> > verify whether my filter service is up or not. Or is there any other
>> > way
>> > to
>> > do that?
>> >
>> No there is no way to tell by the registry.
>>
>> > Speaking of which, do I need to modify anything on DriverEntry when
>> > porting
>> > to 64 bit XP/Vista? I have put some debug print message in DriverEntry
>> > function but I don't see any of it and I would say my driver has never
>> > been
>> > loaded up or skipped by the OS for some reason. That was why I kept
>> > thinking
>> > it is the problem caused by "code-signing policy".
>> >
>>
>> You have to enable debug prints for Vista, by default they will not show
>> up.
>>
>
> Are you trying to tell me that the debug print I was using at 32bit Vista
> is
> different from the 64bit?
>
>



Re: Filter driver on 64 bit OSes by David

David
Tue Oct 16 09:09:52 PDT 2007

Everyone seems to have missed that he built the driver with the XP 64 build
environment. Either he just provided it in quotes and didn't mean it or he
is building an Itanium driver. I chose to believe him. The XP DDK is
obsolete and anyone using it should really needs to do some research first.

"Don Burn" <burn@stopspam.windrvr.com> wrote in message
news:%23i8MPr$DIHA.4880@TK2MSFTNGP03.phx.gbl...
> No, but according to Microsoft and from what I have seen you do have to
> enable registry settings to get DbgPrint's to work on the non-checked
> Vista.
>
>
> --
> Don Burn (MVP, Windows DDK)
> Windows 2k/XP/2k3 Filesystem and Driver Consulting
> Website: http://www.windrvr.com
> Blog: http://msmvps.com/blogs/WinDrvr
> Remove StopSpam to reply
>
>
> "aze2cool" <aze2cool@discussions.microsoft.com> wrote in message
> news:760FCE8C-76F4-4B49-98C8-FEBDAD70F14A@microsoft.com...
>>
>>
>> "Don Burn" wrote:
>>
>>>
>>> "aze2cool" <aze2cool@discussions.microsoft.com> wrote in message
>>> news:BB3D5FF6-12AF-40FF-9E2B-E4D726E255EE@microsoft.com...
>>> >
>>> > I thought you can tell from the following registry key entry,
>>> > HKLM\System\CCS\Services\MyFilterDriver\Enum\xxx
>>> > where xxx is the index of the device. I might be wrong but this is how
>>> > I
>>> > verify whether my filter service is up or not. Or is there any other
>>> > way
>>> > to
>>> > do that?
>>> >
>>> No there is no way to tell by the registry.
>>>
>>> > Speaking of which, do I need to modify anything on DriverEntry when
>>> > porting
>>> > to 64 bit XP/Vista? I have put some debug print message in DriverEntry
>>> > function but I don't see any of it and I would say my driver has never
>>> > been
>>> > loaded up or skipped by the OS for some reason. That was why I kept
>>> > thinking
>>> > it is the problem caused by "code-signing policy".
>>> >
>>>
>>> You have to enable debug prints for Vista, by default they will not show
>>> up.
>>>
>>
>> Are you trying to tell me that the debug print I was using at 32bit Vista
>> is
>> different from the 64bit?
>>
>>
>
>