AnsweredAssumed Answered


Question asked by VRFuser on Aug 17, 1997
Thanx Greg - - >

We have come up with an approach that allows us to use seperate files
with different instrument configurations for each program that we
distribute.  It isn't rocket science, it is actually simple.  We use to/from
file objects to over-write the existing file (which is backed up)
with a file of our choosing.  We zip the "personalized" files
with each of our applications so that the program that is launched
over-writes the stock 'buffer' file with its own local copy of the io
file that the program needs.  This eliminates the need for users to go
through an automatically included developers io file that might contain
dozens of Instruments.  We developed this approach when several of our users
complained about naming conventions, addresing issues and such.  We only
allow the users to run one instance of VEE at a time, so they cannot corrupt
the existing 'real-time' i/o file with an additional instance of VEE.  This
whole concept will probably not mean much unless you are writing programs
that many different users are going to be running, which is what we
do..........Parting shot:  We use 'Install Shield Express" to create
Installation "setup" programs for our .vxe applications.  It works really
good for this and allows you create icons and program group associations
with Win 95.  Check out there website, you can download a fully operational
copy of this program that will work for 19 days,

Jeff Davis
Motorola SSTG
Scottsdale AZ
>Subject: VRf-VXE_VEE.IO
>Date: Sunday, August 17, 1997 11:00PM
>send q VRf-VXE_VEE.IO ww vrf
>from: Greg Goebel / HP-MXD
> / 970-679-3030 / FAX 970-679-5971
>      website:
>to:   VRf-Jeff Davis
>date: Sunday, 17 August 1997 1148 MDT
>> Date: Fri, 1 Aug 1997 9:04:32 -0500
>> From: JeffTEF Davis-P25691 <>
>> Subject: VRF - vee command line options
>> To:
>> I have been attempting to use the command line option <-veeio> to cause
>> to use an io config file other than the normal (original) one.
>> I have been successful doing this with the development copy of vee but
>> I try doing the same thing with the .vxe file, the normal veeio file is
>> accessed and not the custom one that was created. Is this functionality
>> possible with the executable files?
>> Let us know?
>Sorry I'm running late ... here's what I think the answer is:
>--------------------------------- cut here
>* With VEE 4.X, a new runtime scheme was introduced to make a VEE program
>look as much like an executable program as possible.  The user can save
>secured VEE programs with a .VXE (VEE eXEcutable) extension; when these
>programs are selected under Windows, they are automatically executed -- by
>way of an "association" to the "veerun.exe" file set up when VEE is
>This arrangement can be a little confusing.  A VEE user wanted to use a
>command-line option -- the "-veeio <filename>" option, which allows the
>to specify an alternate VEE I/O configuration file -- and found out that it
>worked for the original .VEE file but not for the run-time .VXE file.
>This turned out to be a somewhat confusing configuration issue.  For
>development, a user invokes the "vee.exe" file through the Windows start
>or a shortcut; it is simple to modify either to add the "-veeio <filename>"
>option, and this works fine for program development.
>Once saved as a .VXE file, however, the program is then executed by
>"veerun.exe" automatically through the file association ... and so the same
>option has to be applied to "veerun.exe".
>The appropriate changes can be made through either Windows Explorer or
>Windows MyComputer ... just select:
>   View -> Options -> File Types
>-- then find "HP VEE Executable" and "Edit" that entry ... you will get a
>list of selections with "open" as the only entry, so "Edit" that in turn.
>This gives an invocation of "veerun.exe" that can be modified to add the
>"-veeio <filename>" option.  From that point on, all invocations of .VXE
>files from Windows will use that VEE I/O configuration file.