4 ms·

One of the problems here is that this uses quite a lot of the MS source code and I'm not sure of the license & legality of it. This was in an era where MS used

One of the problems here is that this uses quite a lot of the MS source code and I'm not sure of the license & legality of it. This was in an era where MS used to release part of the actual source code of Windows for OEMs to adapt, but as there was a special deal for each particular OEM, it is not very clear what the actual licensing & redistributing terms are if you didn't had such a deal. Most probably, this is violating MS copyrights, even if the source code is easily available on the web these days. I already had to drop a customer project like this a decade or so ago (just because of this uncertainty) so it's not entirely a moot issue.

mouse_ 2y ago
Life's simply too short to worry about Windows 3.1 extensibility licensing and terms of use.
- AshamedCaptain 2y ago
  Think a video manufacturer who wants to release sources for their drivers but legal team says "no" because of this. "Life is too short to care" is the stupid argument that the lawyers will use to avoid spending any time digging on the issue. So they will just say "no it's too much a risk". As a consequence the source code for the drivers of Fancy-Historical-Hardware will never be released.