Q: about ZwLoadDriver()

device driver

    Sponsored Links

    Next

  • 1. What is the equivalent of NDIS_GET_PACKET_MEDIA_SPECIFIC_INFO in NDIS 6.0
    Hi, can anyone help me in finding out the equivalent function of NDIS_GET_PACKET_MEDIA_SPECIFIC_INFO for NDIS 6.0. I need to get the MediaSpecificInformation from the NET_BUFFER_LIST. i was using NET_BUFFER_LIST_INFO(pNetBufferList ,MediaSpecificInformation); but unfortunately it returns NULL. can anyone help me in this regards, Thanks and Regards, Neo
  • 2. Windows 64 INF-Section to register 32-bit components
    Hi, I have a problem with figuring out how to (self-)register 32-bit components under Windows 64 OSes. I've come up with : [DEV_AddReg_Filter_SysWoW64] HKLM,%RunOnce%,"AddReg_SysWoW64_Filter",,"%10%\SysWow64\regsvr32.exe /s 10%\SysWow64\%FilterFilename_x86%" HKLM,%RunOnce%,"AddReg_SysWoW64_PropPage",,"%10%\SysWow64\regsvr32.exe /s %10%\SysWow64\%PropertyPagesFilename_x86%" which works fine, but is deprecated by Microsoft and fails DTM tests. Is there an official way, to do this? Or do I have to bypass the self-registering part and just hard code the according registry entries? thanks Christopher
  • 3. How to share a section between Driver and User Mode Applicatio
    Thanks Don. I know this is bad- and I am sure code reviewers will complain. But the problem is I am trying to get data that is available from a source that does not provide kernel mode API. The supplied API works only on Win32. I need a single application that provides the data- not multiple application. Other applications will not use this method, use normal procedure to read and write data - means the application here is private to driver. Even worse there is some existing usermode application (with source code) to supply data to the driver. I can not replace that application easily because of its size- for time limitation. Only thing I can try is to fix that thing. So, I am making a separate dummy driver and fixing problems one by one and comparing the result with main driver to fix that. I think I am almost done with this process. I wish I build next from scratch. Thanks - without all your help in news groups I could not work so easily.
  • 4. Replacement of LayoutFile in Inf file
    Hello, What is the substitute of LayoutFile=layout.inf in the inf file for Vista ?. I try to install automatically the driver usbser.sys but the directive LayoutFile not work, because the layout.inf is not present in Vista. I have seen that the driver usbser.sys is present in directory "C:\Windows\sytem32\DriverStore\FileRepository\mdmcpq.inf\", can I add in my inf file this directory, and is it recommanded ? Best regards
  • 5. DDKLocalMon Port Monitor
    Can anyone explain how I can compile the sample Port Monitor Provided in the DDK for windows 2000? I want to use this monitor for Windows 2000, Windows XP and Windows 2003 Server. Thank you, Shreyash B. Patel

Q: about ZwLoadDriver()

Postby Aleksey Rechinsky » Thu, 02 Oct 2003 02:12:03 GMT

Hello!

Can somebody confirm or contradict these three statements:

1) ZwLoadDriver() interface remains unchanged from Win2000 to a latest
Win2003 (or to which version as you know?)

2) It's prototype is
NTSYSAPI NTSTATUS NTAPI ZwLoadDriver( IN PUNICODE_STRING
DriverServiceName );
where DriverServiceName is the name of driver under "Services" key in
registry. For example,
L"Registry\\Machine\\System\\CurrentControlSet\\Services\\Tcpip".

3) DriverEntry() routine of the driver to be loaded is always execute in
system thread context, no matter, where was the ZwLoadDriver() executed.

Any info would be very appreciated.
Thanks, Aleksey.





Similar Threads:

1.about ZwLoadDriver()

> 1) ZwLoadDriver() interface remains unchanged from Win2000 to a latest
> Win2003 (or to which version as you know?)

Yes, since FS recognizers depend on it.

> 3) DriverEntry() routine of the driver to be loaded is always execute in
> system thread context, no matter, where was the ZwLoadDriver() executed.

Yes.


2.Q: about ZwLoadDriver()

Hello!

Can somebody confirm or contradict these three statements:

1) ZwLoadDriver() interface remains unchanged from Win2000 to a latest
Win2003 (or to which version as you know?)

2) It's prototype is
NTSYSAPI NTSTATUS NTAPI ZwLoadDriver( IN PUNICODE_STRING
DriverServiceName );
where DriverServiceName is the name of driver under "Services" key in
registry. For example,
L"Registry\\Machine\\System\\CurrentControlSet\\Services\\Tcpip".

3) DriverEntry() routine of the driver to be loaded is always execute in
system thread context, no matter, where was the ZwLoadDriver() executed.

Any info would be very appreciated.
Thanks, Aleksey.



3.about ZwLoadDriver()

"Aleksey Rechinsky" <ar_(dont_spam) XXXX@XXXXX.COM > wrote in message
news: XXXX@XXXXX.COM ...
> Hello!
>
> Can somebody confirm or contradict these three statements:
>
> 1) ZwLoadDriver() interface remains unchanged from Win2000 to a latest
> Win2003 (or to which version as you know?)

Right. From at least NT 3.51 [perhaps even the very first NT release] up to
the very latest version, at the time writing.

> 2) It's prototype is
> NTSYSAPI NTSTATUS NTAPI ZwLoadDriver( IN PUNICODE_STRING
> DriverServiceName );
> where DriverServiceName is the name of driver under "Services" key in
> registry. For example,
> L"Registry\\Machine\\System\\CurrentControlSet\\Services\\Tcpip".

Right.

> 3) DriverEntry() routine of the driver to be loaded is always execute in
> system thread context, no matter, where was the ZwLoadDriver() executed.

I have some evidence that it is so. But I always call it from a dedicated
thread, just in case.

S


4.Q: about ZwLoadDriver()

Hello!

Can somebody confirm or contradict these three statements:

1) ZwLoadDriver() interface remains unchanged from Win2000 to a latest
Win2003 (or to which version as you know?)

2) It's prototype is
NTSYSAPI NTSTATUS NTAPI ZwLoadDriver( IN PUNICODE_STRING
DriverServiceName );
where DriverServiceName is the name of driver under "Services" key in
registry. For example,
L"Registry\\Machine\\System\\CurrentControlSet\\Services\\Tcpip".

3) DriverEntry() routine of the driver to be loaded is always execute in
system thread context, no matter, where was the ZwLoadDriver() executed.

Any info would be very appreciated.
Thanks, Aleksey.





Return to device driver

 

Who is online

Users browsing this forum: No registered users and 41 guest