<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: copy protection in LabVIEW</title>
    <link>https://ni.lithium.com/t5/LabVIEW/copy-protection/m-p/13481#M9727</link>
    <description>LabVIEW has a palette of VI's that allow you to open, create, read, write, and delete registry keys.  With this functionality, you could find some unique machine information in the Windows registry and verify this in your program.&lt;BR /&gt;&lt;BR /&gt;These VI's can be found from the Advanced function palette. However, I would warn you that making changes to the Windows registry can be very dangerous if you don't know exactly what you are doing.  I would advise only using the "read" functionality. &lt;BR /&gt;</description>
    <pubDate>Thu, 19 Apr 2001 20:08:44 GMT</pubDate>
    <dc:creator>Matt_R</dc:creator>
    <dc:date>2001-04-19T20:08:44Z</dc:date>
    <item>
      <title>copy protection</title>
      <link>https://ni.lithium.com/t5/LabVIEW/copy-protection/m-p/13476#M9722</link>
      <description>i want to protect my application against illegal copies by allowing installation on only one machine. i want to do this by reading some machine specific information, for example disk drive serial number or network card serial number or operating system serial number. can anyone please tell me how to read any of these or something similar (maybe from the registry?). otherwise do you have any suggestions regarding copy protection.&lt;BR /&gt;i am running NT/win 2000 and i do not have any NI hardware installed. many thanks. &lt;BR /&gt;</description>
      <pubDate>Thu, 19 Apr 2001 18:32:29 GMT</pubDate>
      <guid>https://ni.lithium.com/t5/LabVIEW/copy-protection/m-p/13476#M9722</guid>
      <dc:creator>jimstew</dc:creator>
      <dc:date>2001-04-19T18:32:29Z</dc:date>
    </item>
    <item>
      <title>Re: copy protection</title>
      <link>https://ni.lithium.com/t5/LabVIEW/copy-protection/m-p/13477#M9723</link>
      <description>I use a couple VI's I found on the 'net called "GetComputerName.vi" and &lt;BR /&gt;GetVolumeInformation.vi" to discover the users hard drive id # and computer&lt;BR /&gt;name.&lt;BR /&gt;&lt;BR /&gt;From these two inputs I create a hex value using a one-time pad encryption&lt;BR /&gt;algorithm.  The user sends me this value and I create an unlock, based on another&lt;BR /&gt;one-time pad. I now have the users computer name and hard drive ID in my database&lt;BR /&gt;for future reference.&lt;BR /&gt;I create an unlock code and return this value to the user and he/she installs it into the Registry&lt;BR /&gt;via a LabVIEW vi I wrote specifically to do this. &lt;BR /&gt;&lt;BR /&gt;When my application fires up, it searches the Registry for the unlock value, if it matches the&lt;BR /&gt;value generated by the users computer name and hard drive ID, I start my app.&lt;BR /&gt;&lt;BR /&gt;The system could be hacked, I imagine,&lt;BR /&gt; by using a hex editor and discovering the one-time&lt;BR /&gt;pad and then guessing what I'm using to create the code, but I figure if they want to go&lt;BR /&gt;to that much work, they can have it. If you really wanted to be secure I guess you could&lt;BR /&gt;add current time as an input, and then there would never be anything the same from the output &lt;BR /&gt;of the one-time pad.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;&lt;BR /&gt;Alan&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;"jimstew" &lt;X&gt; wrote in message news:5065000000080000000E1B0000-986697009000@quiq.com...&lt;BR /&gt;&amp;gt; i want to protect my application against illegal copies by allowing&lt;BR /&gt;&amp;gt; installation on only one machine. i want to do this by reading some&lt;BR /&gt;&amp;gt; machine specific information, for example disk drive serial number or&lt;BR /&gt;&amp;gt; network card serial number or operating system serial number. can&lt;BR /&gt;&amp;gt; anyone please tell me how to read any of these or something similar&lt;BR /&gt;&amp;gt; (maybe from the registry?). otherwise do you have any suggestions&lt;BR /&gt;&amp;gt; regarding copy protection.&lt;BR /&gt;&amp;gt; i am running NT/win 2000 and i do not have any NI hardware installed.&lt;BR /&gt;&amp;gt; many thanks. &lt;BR /&gt;&lt;/X&gt;</description>
      <pubDate>Thu, 19 Apr 2001 20:00:51 GMT</pubDate>
      <guid>https://ni.lithium.com/t5/LabVIEW/copy-protection/m-p/13477#M9723</guid>
      <dc:creator>abrause</dc:creator>
      <dc:date>2001-04-19T20:00:51Z</dc:date>
    </item>
    <item>
      <title>Re: copy protection</title>
      <link>https://ni.lithium.com/t5/LabVIEW/copy-protection/m-p/13478#M9724</link>
      <description>thanks, this is just the information i need. where can i find the vis you described (getcomputername and getvolumeinformation) ? &lt;BR /&gt;</description>
      <pubDate>Thu, 19 Apr 2001 20:22:00 GMT</pubDate>
      <guid>https://ni.lithium.com/t5/LabVIEW/copy-protection/m-p/13478#M9724</guid>
      <dc:creator>jimstew</dc:creator>
      <dc:date>2001-04-19T20:22:00Z</dc:date>
    </item>
    <item>
      <title>Re: copy protection</title>
      <link>https://ni.lithium.com/t5/LabVIEW/copy-protection/m-p/13479#M9725</link>
      <description>I was afraid you would ask me that, I don't have a link to the .llb and the author&lt;BR /&gt;did not provide info inside the library.  It's called driveinfo.llb.&lt;BR /&gt;&lt;BR /&gt;Maybe check this site, http://www.mooregoodideas.com/&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;"jimstew" &lt;X&gt; wrote in message news:506500000005000000DF230000-986697009000@quiq.com...&lt;BR /&gt;&amp;gt; thanks, this is just the information i need. where can i find the vis&lt;BR /&gt;&amp;gt; you described (getcomputername and getvolumeinformation) ? &lt;BR /&gt;&lt;/X&gt;</description>
      <pubDate>Thu, 19 Apr 2001 21:00:53 GMT</pubDate>
      <guid>https://ni.lithium.com/t5/LabVIEW/copy-protection/m-p/13479#M9725</guid>
      <dc:creator>abrause</dc:creator>
      <dc:date>2001-04-19T21:00:53Z</dc:date>
    </item>
    <item>
      <title>Re: copy protection</title>
      <link>https://ni.lithium.com/t5/LabVIEW/copy-protection/m-p/13480#M9726</link>
      <description>thanks alan, i'll go look. &lt;BR /&gt;</description>
      <pubDate>Thu, 19 Apr 2001 21:09:15 GMT</pubDate>
      <guid>https://ni.lithium.com/t5/LabVIEW/copy-protection/m-p/13480#M9726</guid>
      <dc:creator>jimstew</dc:creator>
      <dc:date>2001-04-19T21:09:15Z</dc:date>
    </item>
    <item>
      <title>Re: copy protection</title>
      <link>https://ni.lithium.com/t5/LabVIEW/copy-protection/m-p/13481#M9727</link>
      <description>LabVIEW has a palette of VI's that allow you to open, create, read, write, and delete registry keys.  With this functionality, you could find some unique machine information in the Windows registry and verify this in your program.&lt;BR /&gt;&lt;BR /&gt;These VI's can be found from the Advanced function palette. However, I would warn you that making changes to the Windows registry can be very dangerous if you don't know exactly what you are doing.  I would advise only using the "read" functionality. &lt;BR /&gt;</description>
      <pubDate>Thu, 19 Apr 2001 20:08:44 GMT</pubDate>
      <guid>https://ni.lithium.com/t5/LabVIEW/copy-protection/m-p/13481#M9727</guid>
      <dc:creator>Matt_R</dc:creator>
      <dc:date>2001-04-19T20:08:44Z</dc:date>
    </item>
    <item>
      <title>Re: copy protection</title>
      <link>https://ni.lithium.com/t5/LabVIEW/copy-protection/m-p/13482#M9728</link>
      <description>Hi Jimstew,&lt;BR /&gt;&lt;BR /&gt;another very secure way is hardware key.&lt;BR /&gt;I use to protect my software a hardware key called SentinelSuperPro from Rainbow Technologies    www.rainbow.com&lt;BR /&gt;It is available both for parallel port and USB.&lt;BR /&gt;It is a quite inexpensive and versatile method for protection, further and most important, its software package included some example in LabVIEW that show how to manage the security codes.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;&lt;BR /&gt;Alberto Locatelli &lt;BR /&gt;</description>
      <pubDate>Fri, 20 Apr 2001 07:50:33 GMT</pubDate>
      <guid>https://ni.lithium.com/t5/LabVIEW/copy-protection/m-p/13482#M9728</guid>
      <dc:creator>Alberto</dc:creator>
      <dc:date>2001-04-20T07:50:33Z</dc:date>
    </item>
  </channel>
</rss>

