UMDF Skeleton copyright
-
So, I've managed to put my UMDF driver together and it actually works like a charm. Now I'm wondering about the legal issues and the copyright for the source code. The UMDF Skeleton sample is supposed to be some kind of a boiler plate for writing new UMDF drivers. I haven't found any advise on how the files are supposed to be treated regarding copyright issues in the documentation/help. My customer naturally wants to put their copyright notice in all files, but nearly all source files for the driver contains the Microsoft copyright notice. Someone been there before? Any ideas?
"It's supposed to be hard, otherwise anybody could do it!" - selfquote
"High speed never compensates for wrong direction!" - unknown -
So, I've managed to put my UMDF driver together and it actually works like a charm. Now I'm wondering about the legal issues and the copyright for the source code. The UMDF Skeleton sample is supposed to be some kind of a boiler plate for writing new UMDF drivers. I haven't found any advise on how the files are supposed to be treated regarding copyright issues in the documentation/help. My customer naturally wants to put their copyright notice in all files, but nearly all source files for the driver contains the Microsoft copyright notice. Someone been there before? Any ideas?
"It's supposed to be hard, otherwise anybody could do it!" - selfquote
"High speed never compensates for wrong direction!" - unknown -
re-write the microsft source files so they are sufficiently different.
Morality is indistinguishable from social proscription
fat_boy wrote:
re-write the microsft source files so they are sufficiently different.
:laugh: No prior post on CodeProject has made me laugh spontaneously such as this one! Seriously, I was hoping you would answer my post, but I was also hoping somebody had stumbled on some kind of Microsoft statement that explicitly granted the use of those source files and how the copyright issues should be handled. I mean, the documentation clearly says the Skeleton sample should be used as starting point when developing new drivers and that can be interpreted as we are free to use these files. It is also described step by step how the source of the Skeleton sample should be modified in order to created a new driver. Any other idea, beside writing to "the author"?
"It's supposed to be hard, otherwise anybody could do it!" - selfquote
"High speed never compensates for wrong direction!" - unknown -
fat_boy wrote:
re-write the microsft source files so they are sufficiently different.
:laugh: No prior post on CodeProject has made me laugh spontaneously such as this one! Seriously, I was hoping you would answer my post, but I was also hoping somebody had stumbled on some kind of Microsoft statement that explicitly granted the use of those source files and how the copyright issues should be handled. I mean, the documentation clearly says the Skeleton sample should be used as starting point when developing new drivers and that can be interpreted as we are free to use these files. It is also described step by step how the source of the Skeleton sample should be modified in order to created a new driver. Any other idea, beside writing to "the author"?
"It's supposed to be hard, otherwise anybody could do it!" - selfquote
"High speed never compensates for wrong direction!" - unknowna heck of a lot of code is copied off the Microsfdt samples. Why? Because the documentation is so bad for a lot of stuff you have no choice. So jut copy it, change the code structure a bit, and no court in the world could say it is the same, and therefore protected.
Morality is indistinguishable from social proscription
-
a heck of a lot of code is copied off the Microsfdt samples. Why? Because the documentation is so bad for a lot of stuff you have no choice. So jut copy it, change the code structure a bit, and no court in the world could say it is the same, and therefore protected.
Morality is indistinguishable from social proscription
fat_boy wrote:
a heck of a lot of code is copied off the Microsfdt samples. Why? Because the documentation is so bad for a lot of stuff you have no choice.
Well, can't argue with that.... :-\ Good point, thanks.
"It's supposed to be hard, otherwise anybody could do it!" - selfquote
"High speed never compensates for wrong direction!" - unknown -
fat_boy wrote:
a heck of a lot of code is copied off the Microsfdt samples. Why? Because the documentation is so bad for a lot of stuff you have no choice.
Well, can't argue with that.... :-\ Good point, thanks.
"It's supposed to be hard, otherwise anybody could do it!" - selfquote
"High speed never compensates for wrong direction!" - unknown