On 10/3/06, <b class="gmail_sendername">Robert Lunnon</b> <<a href="mailto:bobl@optushome.com.au">bobl@optushome.com.au</a>> wrote:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On Tuesday 03 October 2006 02:18, James Courtier-Dutton wrote:<br>> Martin Owens wrote:<br>> >> Re Copy Protection.<br>> >><br>> >> be quite hard to make this work I think?<br>> ><br>> > It would be quite dangerous to make this work.
<br>> ><br>> > What about creating a file say with a fake data map, wine thinks it's<br>> > the direct access to the hard drive where all this information is<br>> > held. all we do is add the place where the data starts and the data
<br>> > thats stored. it would be slower but it would get around the dangers<br>> > while keeping the interface the same.<br>><br>> The easiest way round this is to simply recognise the executable with<br>
> the copy protection, and simply install a hook to catch the appropriate<br>> file system or registry calls and divert them to a special handling<br>> routine to satisfy the application. The difficulty would come from
<br>> actually implementing the "copy protection" part. I.e. Preventing the<br>> wine user from copying the software.<br>><br>> James<br><br>Why not just use a sparse database, IE when the write happens, record the
<br>program name, offset, length and data and on a read to that offset and<br>length, return the same data. Using the program name and offset as the lookup<br>key means you can even support multiple programs writing to the same space
<br>and you don't then need to handle space management (Can emulate an empty<br>disk). You could even use the registry.<br><br>Bob<br><br><br><br></blockquote></div><br>I'm by no means an expert on copyright law or copy protection, but I think that using any method other than writing directly to the MBR with those copy protection measures would be illegal because writing to a file (registry, wine-only proprietary db or any other type of file) as opposed to writing to the mbr like the copy protection is supposed to could potentially reveal data that the copy protection companies don't want being revealed, and therefore that would end up making wine a possible target for aiding circumvention. Sure there are tools out there that crackers use that read the mbr and store it in a file, so that they can circumvent the copy protection, but that has nothing to do with wine.
<br clear="all"><br>-- <br>Thanks<br><br>Tom<br><br>Check out this new 3D Instant Messenger called IMVU. It's the best I have seen yet!<br><br><a href="http://www.imvu.com/catalog/web_registration.php?userId=1547373">http://www.imvu.com/catalog/web_registration.php?userId=1547373
</a>