Re: Are some DDK Header files allowed to be distributed?
From: Tom (noname_at_noprovider.nodomain)
Date: 11/16/04
- Next message: Ray Trent: "Re: Keyboard filter (to work with a Card Reader)"
- Previous message: Stephan Wolf [MVP]: "Re: NdisMRegisterUnloadHandler"
- In reply to: Bill McKenzie: "Re: Are some DDK Header files allowed to be distributed?"
- Next in thread: Don Burn: "Re: Are some DDK Header files allowed to be distributed?"
- Reply: Don Burn: "Re: Are some DDK Header files allowed to be distributed?"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 16 Nov 2004 16:07:15 -0600
Thanks, Bill. I see no other practical way besides your suggestion C.
I see mention of the DDK for $30 but whenever I search the MS website,
I can only find it for $199, so I suspect those who may want to compile
the code run into the same obstacle. Guess it's time to learn DLL's !
-- Tom
"Bill McKenzie" <bill.mckenzie@nospam.conexant.com> wrote in message
news:uM9fey6yEHA.3408@tk2msftngp13.phx.gbl...
> Either:
>
> A) Morph the structures into your own structures for use in your app
>
> B) Require the DDK to build your app
>
> C) Isolate all of the DDK dependent code in a prebuilt binary such as a
> DLL,
> or lib.
>
> or
>
> D) Come up with something equally or more creative
>
> The license agreement for the DDK ships with the DDK. You agreed to it if
> you installed a DDK. It would not matter what MS said anywhere else. You
> need to read the agreement that shipped with the DDK(s) you installed.
>
> --
> Bill McKenzie
> Software Engineer - Prism 802.11 Wireless Solutions
> Conexant Systems, Inc.
>
>
> "TOM" <noname@noprovider.nodomain> wrote in message
> news:O$7U0y3yEHA.3624@TK2MSFTNGP09.phx.gbl...
>> Well - I had read somewhere that some MS had a policy on some of the
> header
>> files,
>> but I am not able to find it anywhere by searching the website. That's
>> why
> I
>> asked.
>>
>>
>>
>> "nospam@cristalink.com" <cristalink@nospam.nospam> wrote in message
>> news:%23FHhIl3yEHA.2788@TK2MSFTNGP15.phx.gbl...
>> > You've got some files you want to distribute. And these files are
>> > copyrighted and not yours. And you obtained them legally. Then you must
>> > have a License Agreement or a copyright notice related to the files.
> Read
>> > it. If you've got questions after reading, contact the copyright holder
>> > and ask them in an official way. Nobody here can give you a legal
> advice,
>> > rather their own opinion. Who knows on what terms you acquired those
>> > files.
>> >
>> > --
>> > http://www.firestreamer.com - NTBACKUP to DVD and DV
>> >
>> >
>> > "TOM" <noname@noprovider.nodomain> wrote in message
>> > news:uZhACY3yEHA.1192@tk2msftngp13.phx.gbl...
>> >>I did not write a driver - only the application. The 3rd party driver
>> >>(Cypress EZUSB.SYS)
>> >> requires that my application fill out the low-level USB data
>> >> structures
>> >> and pass a pointer
>> >> to it to the driver. The structures are complicated enough that they
> use
>> >> several DDK include files
>> >> (which in turn use other DDK include files) amounting to perhaps a
>> >> thousand lines or more of
>> >> header.
>> >>
>> >> So it does not seem practical to cobble together my own include file,
> and
>> >> I can't just make
>> >> simple ones for an API - because to write that API would require those
>> >> same DDK header
>> >> files.
>> >>
>> >> Has MS stated any policy?
>> >>
>> >> -- Tom
>> >>
>> >>
>> >>
>> >>
>> >> "Doron Holan [MS]" <doronh@nospam.microsoft.com> wrote in message
>> >> news:%23Sl3hYqyEHA.1392@TK2MSFTNGP14.phx.gbl...
>> >>> if your customers are going to be writing drivers, wouldn't they need
>> >>> the ddk to do that?
>> >>>
>> >>> --
>> >>> Please do not send e-mail directly to this alias. this alias is for
>> >>> newsgroup purposes only.
>> >>> This posting is provided "AS IS" with no warranties, and confers no
>> >>> rights.
>> >>>
>> >>>
>> >>> "nospam@cristalink.com" <cristalink@nospam.nospam> wrote in message
>> >>> news:O4UfBWpyEHA.3024@TK2MSFTNGP14.phx.gbl...
>> >>>> You should read the End User License Agreement. As far as I
>> >>>> remember,
>> >>>> it doesn't allow redistribution of the headers.
>> >>>>
>> >>>> Can't you supply your own headers?
>> >>>> Can't your customers afford DDK for $30?
>> >>>>
>> >>>> --
>> >>>> http://www.firestreamer.com - NTBACKUP to DVD and DV
>> >>>>
>> >>>>
>> >>>> "Tom" <noname@noprovider.nodomain> wrote in message
>> >>>> news:ebuiCBpyEHA.4044@TK2MSFTNGP10.phx.gbl...
>> >>>>> I've developed some USB devices that use a 3rd party device driver
>> >>>>> for low-level USB calls. In order to call that driver, I use some
> of
>> >>>>> the
>> >>>>> DDK headers pertaining to low-level USB structure definitions.
>> >>>>>
>> >>>>> Now that the DDK is no longer available on the MS website, is
>> >>>>> there a policy regarding which ones can be distributed? Are there
>> >>>>> some DDK headers that can be distributed, or are all of them
>> >>>>> off-limits?
>> >>>>>
>> >>>>> If none can be distributed, then it's impossible for others to
> compile
>> >>>>> my application (not driver) code unless they have purchased the
>> >>>>> DDK.
>> >>>>>
>> >>>>> -- Tom
>> >>>>>
>> >>>>>
>> >>>>>
>> >>>>
>> >>>>
>> >>>
>> >>>
>> >>
>> >>
>> >
>> >
>>
>>
>
>
- Next message: Ray Trent: "Re: Keyboard filter (to work with a Card Reader)"
- Previous message: Stephan Wolf [MVP]: "Re: NdisMRegisterUnloadHandler"
- In reply to: Bill McKenzie: "Re: Are some DDK Header files allowed to be distributed?"
- Next in thread: Don Burn: "Re: Are some DDK Header files allowed to be distributed?"
- Reply: Don Burn: "Re: Are some DDK Header files allowed to be distributed?"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
