Driver which do nothing

NTDEV
1

Hi,

Is it possible to write an empty simple driver (juste to test installation
by exemple) ?
I tried to create one whith following code:

#include <ntddk.h>
#include <ntstatus.h>

NTSTATUS DriverEntry(IN PDRIVER_OBJECT DriverObject, IN PUNICODE_STRING
RegistryPath)
{
return STATUS_SUCCESS;
}

and when the driver started I get error status 0xC0000018:
// The specified address range conflicts with the address space.
//
#define STATUS_CONFLICTING_ADDRESSES ((NTSTATUS)0xC0000018L)

what does that mean exactly ? How can I prevent it ?</ntstatus.h></ntddk.h>

2

You need to fill the pointers to your dispatch routines in the DRIVER_OBJECT
structure.

Mat

-----Original Message-----
From: Nicolas Mugnier [mailto:xxxxx@cesa.fr]
Sent: Thursday, July 31, 2003 9:32 AM
To: Windows System Software Developers Interest List
Subject: [ntdev] Driver which do nothing

Hi,

Is it possible to write an empty simple driver (juste to test installation
by exemple) ?
I tried to create one whith following code:

#include <ntddk.h>
#include <ntstatus.h>

NTSTATUS DriverEntry(IN PDRIVER_OBJECT DriverObject, IN PUNICODE_STRING
RegistryPath)
{
return STATUS_SUCCESS;
}

and when the driver started I get error status 0xC0000018:
// The specified address range conflicts with the address space.
//
#define STATUS_CONFLICTING_ADDRESSES ((NTSTATUS)0xC0000018L)

what does that mean exactly ? How can I prevent it ?

—
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

You are currently subscribed to ntdev as: xxxxx@guillemot.com
To unsubscribe send a blank email to xxxxx@lists.osr.com</ntstatus.h></ntddk.h>

3

>> You need to fill the pointers to your dispatch routines

And why exactly is this required ? By default, a create driver operation
will set the entry points for the dipsatch table to a ntoskrnl internal stub
which will return
STATUS_INVALID_DEVICE_REQUEST .

Dan

----- Original Message -----
From: “Mathieu Routhier”
To: “Windows System Software Developers Interest List”
Sent: Thursday, July 31, 2003 5:12 PM
Subject: [ntdev] RE: Driver which do nothing

> You need to fill the pointers to your dispatch routines in the
DRIVER_OBJECT
> structure.
>
> Mat
>
> -----Original Message-----
> From: Nicolas Mugnier [mailto:xxxxx@cesa.fr]
> Sent: Thursday, July 31, 2003 9:32 AM
> To: Windows System Software Developers Interest List
> Subject: [ntdev] Driver which do nothing
>
> Hi,
>
> Is it possible to write an empty simple driver (juste to test installation
> by exemple) ?
> I tried to create one whith following code:
>
> #include <ntddk.h>
> #include <ntstatus.h>
>
> NTSTATUS DriverEntry(IN PDRIVER_OBJECT DriverObject, IN PUNICODE_STRING
> RegistryPath)
> {
> return STATUS_SUCCESS;
> }
>
> and when the driver started I get error status 0xC0000018:
> // The specified address range conflicts with the address space.
> //
> #define STATUS_CONFLICTING_ADDRESSES ((NTSTATUS)0xC0000018L)
>
> what does that mean exactly ? How can I prevent it ?
>
>
>
> —
> Questions? First check the Kernel Driver FAQ at
> http://www.osronline.com/article.cfm?id=256
>
> You are currently subscribed to ntdev as: xxxxx@guillemot.com
> To unsubscribe send a blank email to xxxxx@lists.osr.com
>
>
> —
> Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
>
> You are currently subscribed to ntdev as: xxxxx@rdsor.ro
> To unsubscribe send a blank email to xxxxx@lists.osr.com
></ntstatus.h></ntddk.h>

4

I found the solution, I compiled using a bad environment. Thanks anyway.

“Nicolas Mugnier” a écrit dans le message de
news:xxxxx@ntdev…
>
> Hi,
>
> Is it possible to write an empty simple driver (juste to test installation
> by exemple) ?
> I tried to create one whith following code:
>
> #include <ntddk.h>
> #include <ntstatus.h>
>
> NTSTATUS DriverEntry(IN PDRIVER_OBJECT DriverObject, IN PUNICODE_STRING
> RegistryPath)
> {
> return STATUS_SUCCESS;
> }
>
> and when the driver started I get error status 0xC0000018:
> // The specified address range conflicts with the address space.
> //
> #define STATUS_CONFLICTING_ADDRESSES ((NTSTATUS)0xC0000018L)
>
> what does that mean exactly ? How can I prevent it ?
>
>
>
></ntstatus.h></ntddk.h>