AnsweredAssumed Answered

Vrf-RPC

Question asked by VRFuser on Dec 8, 1997
There is one thing you should consider about the advice below.  You may
distribute your VEE program and the VEE-Runtime at no charge.  If you
install the full development environment on a system, then you are
obligated to purchase a license to do so.  Please don't be installing
the full development bits "willy-nilly" on systems - this is in
violation of the license agreement. 

Given that, the idea of another user profile that limits ability to
actually execute said development environment version of VEE is a good
idea.

Ken Colasuonno

Ken Colasuonno (cola@lvld.hp.com)
Hewlett-Packard Company
815 14th St. SW, Loveland, CO 80537
(970) 679-2903  fax (970) 679-5952


     -----Original Message-----
     From:     ANDREW_HAMILTON@HP-SantaClara-om12.om.hp.com
[SMTP:ANDREW_HAMILTON@HP-SantaClara-om12.om.hp.com]
     Sent:     Tuesday, December 09, 1997 10:33 AM
     To:     Stefan.Westh@ffvmatteknik.ffv.se
     Cc:     hpvxd_xc@hpislsup.lvld.hp.com
     Subject:     Re: Vrf-RPC

          Dear Vee-World,
         
          I have one comment for you that may be critical to the
strategy
          mentioned in the preceeding email for using HPVee.  In
production (ie
          my customer's) PCs, I use Vee-Runtime to execute programs.
This
          prevents normal users from making modifications to files.
You should
          consider this option.  For debugging, you can have the
development
          environment installed somewhere on the PC, and you could
even create a
          new user profile (assuming you are using NT/95) and do not
give you
          normal users write access to those files, or to the HPVee
dev. version
          either.
         
          One last comment is, you may wish to have your customer run
there
          files off of a CD-ROM, ie, get a CD-ROM writer if you are
really
          concerned about people not changing your code.  This has
helped me be
          more disciplined as well.
         
          As a comment about timeouts, I assume that you are talking
about I/O
          interface timeout?  In this case, you can change the
timeout
          configuration in your instrument manager without affecting
your
          program-code.  Extend these timeouts for the time that you
are
          debugging, then don't forget to change them back again. 
         
          I HAVE NEVER USED A SECURED VERSION OF A PROGRAM.  I
PERSONALLY THINK
          THAT DOING SO IS A BIG WASTE OF YOUR TIME, FOR MANY
REASONS.  ie I
          THINK VEE RUNTIME, AND CHANGING FILE PERMISSIONS EITHER FOR
YOUR
          GENERIC USER TYPE, OR THROUGH USING VARIOUS USER-PROFILES
AND LEARNING
          TO MANAGE THEM ON NT/95 IS A BETTER SOLUTION, AS MENTIONED
ABOVE.
         
          Respectfully,
         
          Andrew Hamilton
          andrew_hamilton@hp.com


Outcomes