![]() |
|
|
|
#1
|
|||
|
|||
|
Experienced system software developer in my opinion has no need in such a library. But for a newbie in driver development maybe it could somehow help to lay down from um to km...
It is like to develop drivers with help of Jungo/WinDriver/etc. or DriverStudio. However the last one could be used as a test/debug suite... P.S. It is all my IMHO
|
|
#2
|
|||
|
|||
|
Experience has nothing to do with this -- practicality has everything to do with it. Rapid prototyping is rapid prototyping -- getting the semantics of a ZwCreateFile right _once_ and writing an interface to it guarantees avoidance of any development issues, etc.
Jungo, etc. are absolutely not the same. This is an exceedingly thin layer of code, where as Jungo etc are rather nasty and bring about more problems than they solve. Implementing my solution requires knowledge of the low-level system, they do not. This is coming from someone with about 12 years of low-level software design and development, not to mention a lot of experieince in rapid development and deployment of various solutions. |
|
#3
|
|||
|
|||
|
I don't disagree with what you said thewhiz, but why do you need to write a driver if the code runs in user-mode ? I don't think you can test a wide range of functionality by doing that. There are a lot of driver-only issues (the hard ones, too), that simply do not exist in user-mode (the entire IRQL issue for instance).
|
|
#4
|
|||
|
|||
|
Infinite number of reasons. Algorithm testing in user-mode for instance. There are definitely kernel-mode issues that must be addressed, but given I am doing a finite number of wrappers and a lot of what I am concerned with are pure algorithms, it is not a big deal. IRQL issues come with I/O in my case and as such those are finite issues.
|
|
#5
|
|||
|
|||
|
Msvcrt wrapper
@thewhiz
Probably this is what you want regards. |
|
#6
|
|||
|
|||
|
I don't think that's what thewhizz wants, he needs a wrapper library to wrap the DDK (Driver Development Kit) libraries so as to be able to use standard C library function.
@thewhizz, good idea to do this, I think it's a good way to first detect the bugs related to the algorithm before having to deal with the bugs specific to driver development. Unfortunately, I do not have such a wrapper library but I would be very interested in one. Sorry that I can't be of much help |
![]() |
| Thread Tools | |
| Display Modes | |
|
|