I have a need to pass variables into VEE and have been able to with
little trouble in HP-UX but am a newcomer to PC's so could use
some guidance.
In short, inside VEE I need to programmatically figure out where
VEE is installed. In Unix the script that initiates VEE first
sets a variable VEEROOT to the appropriate directory and then
in VEE I use the Execute Program to access this variable and return
it to VEE. This works fine and is pretty much foolproof since
the unix call to initiate VEE is $VEEROOT/veetest, so that
VEEROOT is always valid.
Well now I'm looking at Windows and don't see how to proceed. VEE
doesn't start from a script and even if it did the Execute Program
can't return values from the external program. I have this
vague idea of writing an external program which somehow figures
this out and writes the information to a file, then reading in the
file inside VEE and continuing. However I _don't_ see how an external
program can figure out where VEE resides since while I could
look for VEE, there may be 2 or more versions installed and I see no
way to see which one I am actually accessing.
SO- from inside VEE- how can I tell where VEE is installed in a Windows
environment?
This is ciritical for me since my only other choice is hard-coding this
information in my VEE program- in which case my program is no longer
portable, which is a requirement.
thanks for any hints
----------------------------------------------------------------------
Stan Bischof Hewlett Packard Company 707-577-3994 stanb@sr.hp.com
----------------------------------------------------------------------
little trouble in HP-UX but am a newcomer to PC's so could use
some guidance.
In short, inside VEE I need to programmatically figure out where
VEE is installed. In Unix the script that initiates VEE first
sets a variable VEEROOT to the appropriate directory and then
in VEE I use the Execute Program to access this variable and return
it to VEE. This works fine and is pretty much foolproof since
the unix call to initiate VEE is $VEEROOT/veetest, so that
VEEROOT is always valid.
Well now I'm looking at Windows and don't see how to proceed. VEE
doesn't start from a script and even if it did the Execute Program
can't return values from the external program. I have this
vague idea of writing an external program which somehow figures
this out and writes the information to a file, then reading in the
file inside VEE and continuing. However I _don't_ see how an external
program can figure out where VEE resides since while I could
look for VEE, there may be 2 or more versions installed and I see no
way to see which one I am actually accessing.
SO- from inside VEE- how can I tell where VEE is installed in a Windows
environment?
This is ciritical for me since my only other choice is hard-coding this
information in my VEE program- in which case my program is no longer
portable, which is a requirement.
thanks for any hints
----------------------------------------------------------------------
Stan Bischof Hewlett Packard Company 707-577-3994 stanb@sr.hp.com
----------------------------------------------------------------------
>
> I have a need to pass variables into VEE and have been able to with
> little trouble in HP-UX but am a newcomer to PC's so could use
> some guidance.
>
> In short, inside VEE I need to programmatically figure out where
> VEE is installed. In Unix the script that initiates VEE first
> sets a variable VEEROOT to the appropriate directory and then
> in VEE I use the Execute Program to access this variable and return
> it to VEE. This works fine and is pretty much foolproof since
> the unix call to initiate VEE is $VEEROOT/veetest, so that
> VEEROOT is always valid.
>
> Well now I'm looking at Windows and don't see how to proceed. VEE
> doesn't start from a script and even if it did the Execute Program
> can't return values from the external program. I have this
> vague idea of writing an external program which somehow figures
> this out and writes the information to a file, then reading in the
> file inside VEE and continuing. However I _don't_ see how an external
> program can figure out where VEE resides since while I could
> look for VEE, there may be 2 or more versions installed and I see no
> way to see which one I am actually accessing.
>
> SO- from inside VEE- how can I tell where VEE is installed in a Windows
> environment?
>
> This is ciritical for me since my only other choice is hard-coding this
> information in my VEE program- in which case my program is no longer
> portable, which is a requirement.
>
> thanks for any hints
>
> ----------------------------------------------------------------------
> Stan Bischof Hewlett Packard Company 707-577-3994 stanb@sr.hp.com
> ----------------------------------------------------------------------
I also have done most of my VEE programming on unix platforms and routinely
set environment variables that can be read by VEE. I am no windows expert
but I have used a slightly clumsier method for windows that works for me.
I copy the VEE startup icon for each application and rename it appropriately.
I then edit the icon's properties and modify the working directory to be the
correct one for that application. Then in the directory for the application
I place a text file that can be read from vee that points to the corect vee
version for that application.
--
Tom Sanders
toms@microunity.com http://www.microunity.com
MicroUnity Systems Eng., Inc.
255 Caspian Sunnyvale, CA 94089 (408)734-8100
From: toms@microunity.com (Tom Sanders)
Subject: Re: VRF - Pass Variables
To: stanb@hpnmrsb2.sr.hp.com
Date: Fri, 12 Jul 96 8:37:08 PDT
Stan Bischof wrote:
>
> I have a need to pass variables into VEE and have been able to with
> little trouble in HP-UX but am a newcomer to PC's so could use
> some guidance.
>
> In short, inside VEE I need to programmatically figure out where
> VEE is installed. In Unix the script that initiates VEE first
> sets a variable VEEROOT to the appropriate directory and then
> in VEE I use the Execute Program to access this variable and return
> it to VEE. This works fine and is pretty much foolproof since
> the unix call to initiate VEE is $VEEROOT/veetest, so that
> VEEROOT is always valid.
>
> Well now I'm looking at Windows and don't see how to proceed. VEE
> doesn't start from a script and even if it did the Execute Program
> can't return values from the external program. I have this
> vague idea of writing an external program which somehow figures
> this out and writes the information to a file, then reading in the
> file inside VEE and continuing. However I _don't_ see how an external
> program can figure out where VEE resides since while I could
> look for VEE, there may be 2 or more versions installed and I see no
> way to see which one I am actually accessing.
>
> SO- from inside VEE- how can I tell where VEE is installed in a Windows
> environment?
>
> This is ciritical for me since my only other choice is hard-coding this
> information in my VEE program- in which case my program is no longer
> portable, which is a requirement.
>
> thanks for any hints
>
> ----------------------------------------------------------------------
> Stan Bischof Hewlett Packard Company 707-577-3994 stanb@sr.hp.com
> ----------------------------------------------------------------------
I also have done most of my VEE programming on unix platforms and routinely
set environment variables that can be read by VEE. I am no windows expert
but I have used a slightly clumsier method for windows that works for me.
I copy the VEE startup icon for each application and rename it appropriately.
I then edit the icon's properties and modify the working directory to be the
correct one for that application. Then in the directory for the application
I place a text file that can be read from vee that points to the corect vee
version for that application.
--
Tom Sanders
toms@microunity.com http://www.microunity.com
MicroUnity Systems Eng., Inc.
255 Caspian Sunnyvale, CA 94089 (408)734-8100
From Darryl_Pendergrass-P22012@email.mot.com Fri Jul 12 09:50:31 PDT 1996
From: Darryl_Pendergrass-P22012@email.mot.com
Date: 12 Jul 96 11:35:48 -0500
To: stanb@hpnmrsb2.sr.hp.com, toms@microunity.com
Subject: Re: VRF - Pass Variables
You can also associate the file extension .VEE with the VEE executable.
Then using the file manager traverse to your app directory and double click
the model filename, which launches VEE using the start directory as the
root.
----------
>From: toms@microunity.com
>To: stanb@hpnmrsb2.sr.hp.com
>Cc: hpvxd_xc@hpislsup.lvld.hp.com
>Subject: Re: VRF - Pass Variables
>Date: Friday, July 12, 1996 9:05AM
>
>X-Mailer: ELM [version 2.3 PL11]
>
>Stan Bischof wrote:
>>
>> I have a need to pass variables into VEE and have been able to with
>> little trouble in HP-UX but am a newcomer to PC's so could use
>> some guidance.
>>
>> In short, inside VEE I need to programmatically figure out where
>> VEE is installed. In Unix the script that initiates VEE first
>> sets a variable VEEROOT to the appropriate directory and then
>> in VEE I use the Execute Program to access this variable and return
>> it to VEE. This works fine and is pretty much foolproof since
>> the unix call to initiate VEE is $VEEROOT/veetest, so that
>> VEEROOT is always valid.
>>
>> Well now I'm looking at Windows and don't see how to proceed. VEE
>> doesn't start from a script and even if it did the Execute Program
>> can't return values from the external program. I have this
>> vague idea of writing an external program which somehow figures
>> this out and writes the information to a file, then reading in the
>> file inside VEE and continuing. However I _don't_ see how an external
>> program can figure out where VEE resides since while I could
>> look for VEE, there may be 2 or more versions installed and I see no
>> way to see which one I am actually accessing.
>>
>> SO- from inside VEE- how can I tell where VEE is installed in a Windows
>> environment?
>>
>> This is ciritical for me since my only other choice is hard-coding this
>> information in my VEE program- in which case my program is no longer
>> portable, which is a requirement.
>>
>> thanks for any hints
>>
>> ----------------------------------------------------------------------
>> Stan Bischof Hewlett Packard Company 707-577-3994 stanb@sr.hp.com
>> ----------------------------------------------------------------------
>
>I also have done most of my VEE programming on unix platforms and routinely
>set environment variables that can be read by VEE. I am no windows expert
>but I have used a slightly clumsier method for windows that works for me.
>
>I copy the VEE startup icon for each application and rename it
appropriately.
>I then edit the icon's properties and modify the working directory to be
the
>correct one for that application. Then in the directory for the
application
>I place a text file that can be read from vee that points to the corect vee
>version for that application.
>
>--
>Tom Sanders
>toms@microunity.com http://www.microunity.com
>MicroUnity Systems Eng., Inc.
>255 Caspian Sunnyvale, CA 94089 (408)734-8100
>
>