Advanced

What we want is a driver _analyser_ instead

Story: DriverLoader and NDISWrapper gift-wrap your wireless Windows devicesTotal Replies: 0
Author Content
AnonymousCoward

Nov 22, 2004
2:57 AM EST 		If you wrapped the win32 driver in a debugging layer, you could fairly swiftly deduce what it was doing without disassembling the code. This would allow you to do a clean-room implementation without having to have two teams (disassembly team in safe haven, "air gap" (specification summary document), separate reimplementation team). Hopefully, faster development would result. In principle, since you are not "circumventing" the driver (it does not work with your OS), nor disassembling it, it would be more difficult to make a DMCA claim against someone doing this.

Post a reply to this thread:

A free account is needed to post. Write your comment here first: your text is kept in this browser while you sign up or log in, and is waiting for you when you come back.

Your message:
|||||
10
Markdown: **bold**, *italic*, [text](https://link), - lists, > quotes, $x^2$ for math. Formatting help

Sign up and post (it is free)  or  Log in and post