anyway, let's ask wiki about it
as you can see, if someone wants to protect a technological advantage, there's an implicit contradiction in releasing (too much) details about the device.purpose...A device driver simplifies programming by acting as a translator between a device and the applications or operating systems that use it...
developement... Writing a device driver requires an in-depth understanding of how the hardware and the software of a given platform function.
like it or leave it - noone stops you to build your own hardware (prototype) and write your own code to 'drive' it.
just don't tell others how to handle their stuff, pretending there'd be an advantage for everyone - there isn't
as there's always this Scope Driver thingy adressed all over the place in a myriad of contexts:
there is no such thing as 'a' or 'the' Scope driver
in fact there's about 2 dozen different libraries dealing with anything from control signals to GUI elements
and due to the complex nature of the Scope environment those libraries are heavily interconnected and refer to each other.
as it has been mentioned countless times:
this is one piece of software, structured in a modular way, but that doesn't mean you can pick out arbitrary parts of it and (say) build a virtual recorder by just using scope_asio.dll
if you can't resist, open you Scope folder and add the amount of data for everything that ends with a .dll or .vxd .
Let's assume you end with some 10MBytes or so (no idea how close that is to the true figure, but it does't matter in this context)
What does matter is that it's equivalent to at least a million lines of sourcecode, not something you will just mod on a sunday afternoon...
Porting it to whatever is a serious task, and if there is a fee for it, then for sure not to squeeze a few extra bucks from the audience. There are more effective ways to make money...
cheers, Tom
