Hello.
We have a product supporting plugins. Plugin SDK and examples will be distributes together with the product. Example plugins (user mode DLLs) use both SDK & DDK headers. In order to allow including of “windows.h” and DDK headers to the same file we created own version of ntdef.h. The questions are:
- Is it allowed to redistribute DDK headers along with our SDK?
- Is it allowed to redistribute our version of ntdef.h which has several declarations copy-pasted from the original ntdef.h?
If the both answers are NO how would you solve this situation?
Thanks,
Alexey.
Well you need to check with Microsoft but as far as I know you cannot
redistribute files from the DDK. Now, on your use of a custom ntdef.h,
please think about if you really need this. I have sufferred through a
project that made a custom include from a standard include. I got the
project a few years after it had been developed and the original developers
had moved on, in the end we decided to junk the several man years of work by
the idiots who had made the custom include, since the OS had moved on, and
the effort to resolve things was more than the cost of rewriting the whole
project correctly.
–
Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting
“Alexey Pakhunov” wrote in message news:xxxxx@ntdev…
Hello.
We have a product supporting plugins. Plugin SDK and examples will be
distributes together with the product. Example plugins (user mode DLLs) use
both SDK & DDK headers. In order to allow including of “windows.h” and DDK
headers to the same file we created own version of ntdef.h. The questions
are:
1. Is it allowed to redistribute DDK headers along with our SDK?
2. Is it allowed to redistribute our version of ntdef.h which has several
declarations copy-pasted from the original ntdef.h?
If the both answers are NO how would you solve this situation?
Thanks,
Alexey.
Operative word in Don’s post is IDIOTS. Underline it highlight it and make
it flash in bold bright orange.As soon as you do that foolishness the next
release is guaranteed to break what you just did (Murphy’s Primary Law).
The DDK costs shipping and handling of a CD, and is downloadable if you have
an MSDN subscription.
–
Gary G. Little
Seagate Technologies, LLC
“Don Burn” wrote in message news:xxxxx@ntdev…
> Well you need to check with Microsoft but as far as I know you cannot
> redistribute files from the DDK. Now, on your use of a custom ntdef.h,
> please think about if you really need this. I have sufferred through a
> project that made a custom include from a standard include. I got the
> project a few years after it had been developed and the original
developers
> had moved on, in the end we decided to junk the several man years of work
by
> the idiots who had made the custom include, since the OS had moved on, and
> the effort to resolve things was more than the cost of rewriting the whole
> project correctly.
>
>
>
> –
> Don Burn (MVP, Windows DDK)
> Windows 2k/XP/2k3 Filesystem and Driver Consulting
>
> “Alexey Pakhunov” wrote in message news:xxxxx@ntdev…
> Hello.
>
> We have a product supporting plugins. Plugin SDK and examples will be
> distributes together with the product. Example plugins (user mode DLLs)
use
> both SDK & DDK headers. In order to allow including of “windows.h” and DDK
> headers to the same file we created own version of ntdef.h. The questions
> are:
>
> 1. Is it allowed to redistribute DDK headers along with our SDK?
> 2. Is it allowed to redistribute our version of ntdef.h which has several
> declarations copy-pasted from the original ntdef.h?
>
> If the both answers are NO how would you solve this situation?
>
> Thanks,
> Alexey.
>
>
>
I suspect the answer to #1 is no, and #2 is a bad idea (too easy to get
out of sync). I don’t think it’s unreasonable to expect your plugin
developers to be responsible for getting their own copy of the DDK.
It’s not hard to get (I paid something like $10 and MS mailed me a CD)
and avoid redistributing DDK headers or maintaining your own
version/subset.
On 15-Jul-04, at 2:03 AM, Alexey Pakhunov wrote:
Hello.
?
We have a product supporting plugins. Plugin SDK and examples will be
distributes together with the product. Example plugins (user mode
DLLs) use both SDK & DDK headers. In order to allow including of
“windows.h” and DDK headers to the same file we created own version of
ntdef.h. The questions are:
?
- Is it allowed to redistribute DDK headers along with our SDK?
- Is it allowed to redistribute our version of ntdef.h which has
several declarations copy-pasted from the original ntdef.h?
?
If the both answers are NO how would you solve this situation?
?
Thanks,
? Alexey.
Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256
You are currently subscribed to ntdev as: xxxxx@telus.net
To unsubscribe send a blank email to xxxxx@lists.osr.com
–
Cliff Russell
Software Engineer
e-mail: xxxxx@atimi.com
ichat: xxxxx@mac.com
phone: 250 818 5711
Atimi Software: Software Development - On Time.
http://www.atimi.com
> out of sync). I don’t think it’s unreasonable to expect your plugin
developers to be responsible for getting their own copy of the DDK.
Exactly.
StorageCraft sells some toolkit libraries, and no DDK/IFS headers are included
to the package. The purchaser is expected to have these MS’s kits.
Maxim Shatskih, Windows DDK MVP
StorageCraft Corporation
xxxxx@storagecraft.com
http://www.storagecraft.com