Windows System Software -- Consulting, Training, Development -- Unique Expertise, Guaranteed Results

Home NTDEV

More Info on Driver Writing and Debugging


The free OSR Learning Library has more than 50 articles on a wide variety of topics about writing and debugging device drivers and Minifilters. From introductory level to advanced. All the articles have been recently reviewed and updated, and are written using the clear and definitive style you've come to expect from OSR over the years.


Check out The OSR Learning Library at: https://www.osr.com/osr-learning-library/


Before Posting...

Please check out the Community Guidelines in the Announcements and Administration Category.

RE: [Q] What does DRVO_LEGACY_DRIVER mean?

OSR_Community_UserOSR_Community_User Member Posts: 110,217
From: "Jamey Kirby" <[email protected]>
Sent: Friday, April 07, 2000 12:00 AM


> If you do not create a device object during AddDevice, this flag will get
> set so that the driver does not unload.

But my AddDevice() routine is called (only once, BTW) and I *do* create a
device -- my FDO of course -- and then return STATUS_SUCCESS. The FDO then
layers over the PDO and receives all the expected Plug and Play IRPs, all
the way up to IRP_MJ_REMOVE_DEVICE.

If what you say is correct, why after removal is my driver unloaded as
expected, despite having the DRVO_LEGACY_DRIVER flag?

Another curious detail is that the DRVO_LEGACY_DRIVER flag is present even
*before* AddDevice() is called. It's already set by the time my
DriverEntry() routine is called.

Any other idea what's going on or what this flag means?

- Matt
Sign In or Register to comment.

Howdy, Stranger!

It looks like you're new here. Sign in or register to get started.

Upcoming OSR Seminars
OSR has suspended in-person seminars due to the Covid-19 outbreak. But, don't miss your training! Attend via the internet instead!
Internals & Software Drivers 15 November 2021 Live, Online
Writing WDF Drivers 24 January 2022 Live, Online
Developing Minifilters 7 February 2022 Live, Online
Kernel Debugging 21 March 2022 Live, Online