On 10/3/06, <b class="gmail_sendername">Michael [Plouj] Ploujnikov</b> <<a href="mailto:ploujj@gmail.com">ploujj@gmail.com</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;">
> I'm by no means an expert on copyright law or copy protection, but I think<br>> that using any method other than writing directly to the MBR with those copy<br>> protection measures would be illegal because writing to a file (registry,
<br>> wine-only proprietary db or any other type of file) as opposed to writing to<br>> the mbr like the copy protection is supposed to could potentially reveal<br>> data that the copy protection companies don't want being revealed, and
<br>> therefore that would end up making wine a possible target for aiding<br>> circumvention. Sure there are tools out there that crackers use that read<br>> the mbr and store it in a file, so that they can circumvent the copy
<br>> protection, but that has nothing to do with wine.<br><br>Could you not say the same thing for vmware or any other virtual<br>harddrive application?</blockquote><div><br>Technically yes, but the difference is that VMware actually writes _everything_ into that one file vs wine proposing to write just what is written to the boot sector into a file..
<br><br>The reason it is different, is because it is much more difficult (if not impossible) to tell what is boot sector and what isnt if you have a file that contains an entire drive's worth of data.<br></div><br></div><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>