Windows System Software -- Consulting, Training, Development -- Unique Expertise, Guaranteed Results
Before Posting...
Please check out the Community Guidelines in the Announcements and Administration Category.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/
RE: [Q] What does DRVO_LEGACY_DRIVER mean?
OSR_Community_User
Member Posts: 110,217
in NTDEV
To: "NT Developers Interest List" <[email protected]>
Sent: Tuesday, April 11, 2000 6:33 PM
> Damn straight. Life's already complicated enough without trying to paddle
> upstream....
>
> What are the _benefits_ to using the Borland compiler ?
Well, for me, the benefits are...
1) I'm already completely proficient with it and use it for other projects
besides WDM drivers.
2) I don't have to learn another sets of tools.
3) I build drivers from an IDE, instead of a command-prompt.
4) I know exactly how my drivers are being built.
I use Borland C++ to compile all my Win16, Win32, VxD and WDM code, often
with related targets of any and all of the aforementioned types in the same
project.
> Do you think
> Microsoft care one iota that you're taking a stand against using their
tools
> ?
I didn't say I was taking a stand against Microsoft and I couldn't care less
what they think. I simply prefer Borland C++.
> I think your customers are much more likely to be annoyed when _they_
> discover that the C runtime for the Borland compiler doesn't work
correctly
> in kernel-mode....
Neither does Visual C++'s. Anyway, I'm not using Borland's RTL either. My
drivers function properly (and, having done the work to get there, I know
*why* they function properly).
Sent: Tuesday, April 11, 2000 6:33 PM
> Damn straight. Life's already complicated enough without trying to paddle
> upstream....
>
> What are the _benefits_ to using the Borland compiler ?
Well, for me, the benefits are...
1) I'm already completely proficient with it and use it for other projects
besides WDM drivers.
2) I don't have to learn another sets of tools.
3) I build drivers from an IDE, instead of a command-prompt.
4) I know exactly how my drivers are being built.
I use Borland C++ to compile all my Win16, Win32, VxD and WDM code, often
with related targets of any and all of the aforementioned types in the same
project.
> Do you think
> Microsoft care one iota that you're taking a stand against using their
tools
> ?
I didn't say I was taking a stand against Microsoft and I couldn't care less
what they think. I simply prefer Borland C++.
> I think your customers are much more likely to be annoyed when _they_
> discover that the C runtime for the Borland compiler doesn't work
correctly
> in kernel-mode....
Neither does Visual C++'s. Anyway, I'm not using Borland's RTL either. My
drivers function properly (and, having done the work to get there, I know
*why* they function properly).
Howdy, Stranger!
| 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! | ||
| Kernel Debugging | 13-17 May 2024 | Live, Online |
| Developing Minifilters | 1-5 Apr 2024 | Live, Online |
| Internals & Software Drivers | 11-15 Mar 2024 | Live, Online |
| Writing WDF Drivers | 26 Feb - 1 Mar 2024 | Live, Online |