Subject: VRF- "HOME" variable?
Author: stanb-at-sr (stanb@hpnmrsb2.sr.hp.com) at HP-USA/o2=mimegw3
Date: 7/25/97 11:54 AM
> Hi all.
>
> I just installed an application on my computer totally unrelated to VEE
> and when I went into VEE found that my IO Configuration was gone!
>
> I poked around and found that the vee.io file was still intact in the
> install directory but for some reason was not being read in by VEE.
> Strange to say the least.
>
> After some experimentation ( I went into vee, created a new IO config
> and saved it. Then went to my explorer and did a "find" looking
> for vee.io) I found that VEE is now looking in the new application's
> directory!
>
> Afetr a little more poking I found that the new application is setting
> an environment variable called HOME. And it appears that if HOME is set
> then VEE looks in the HOME directory for vee.io instead of it's own
> install directory.
>
> VEE _doesn't_ appear to use HOME for anything else, like default
> directory, startup directory, looking for menu files, etc.
>
> Any way around this?
>
I don't think there's a way around it. See below.
> Is this intended behavior or a bug?
Intended behavior - the following has been in the VEE help files
section titled "To Include All Needed Files" since at least VEE 3:
"When distributing your program, you need to include your instrument
configuration file. On Windows, it is located in %HOME%/vee.io, if
HOME is defined. Otherwise, it is located in C:Program
FilesHewlett-PackardVEE 4.0vee.io (unless HP VEE is installed in a
different directory). On UNIX, it is located in $HOME/.veeio. Other
files you must include (if you use them) are:
Data files.
*.cid files for instrument drivers you've written.
*.cid files for instrument drivers not installed on the destination
system.
Graphics files you've created.
DLLs or compiled functions that you call.
Copyright (c) 1991-1997 Hewlett-Packard Company"
It looks like if you have a HOME variable set, VEE'll use it.
Regards,
Bruce Wenner
HP St.Paul
Author: stanb-at-sr (stanb@hpnmrsb2.sr.hp.com) at HP-USA/o2=mimegw3
Date: 7/25/97 11:54 AM
> Hi all.
>
> I just installed an application on my computer totally unrelated to VEE
> and when I went into VEE found that my IO Configuration was gone!
>
> I poked around and found that the vee.io file was still intact in the
> install directory but for some reason was not being read in by VEE.
> Strange to say the least.
>
> After some experimentation ( I went into vee, created a new IO config
> and saved it. Then went to my explorer and did a "find" looking
> for vee.io) I found that VEE is now looking in the new application's
> directory!
>
> Afetr a little more poking I found that the new application is setting
> an environment variable called HOME. And it appears that if HOME is set
> then VEE looks in the HOME directory for vee.io instead of it's own
> install directory.
>
> VEE _doesn't_ appear to use HOME for anything else, like default
> directory, startup directory, looking for menu files, etc.
>
> Any way around this?
>
I don't think there's a way around it. See below.
> Is this intended behavior or a bug?
Intended behavior - the following has been in the VEE help files
section titled "To Include All Needed Files" since at least VEE 3:
"When distributing your program, you need to include your instrument
configuration file. On Windows, it is located in %HOME%/vee.io, if
HOME is defined. Otherwise, it is located in C:Program
FilesHewlett-PackardVEE 4.0vee.io (unless HP VEE is installed in a
different directory). On UNIX, it is located in $HOME/.veeio. Other
files you must include (if you use them) are:
Data files.
*.cid files for instrument drivers you've written.
*.cid files for instrument drivers not installed on the destination
system.
Graphics files you've created.
DLLs or compiled functions that you call.
Copyright (c) 1991-1997 Hewlett-Packard Company"
It looks like if you have a HOME variable set, VEE'll use it.
Regards,
Bruce Wenner
HP St.Paul
I just installed an application on my computer totally unrelated to VEE
and when I went into VEE found that my IO Configuration was gone!
I poked around and found that the vee.io file was still intact in the
install directory but for some reason was not being read in by VEE.
Strange to say the least.
After some experimentation ( I went into vee, created a new IO config
and saved it. Then went to my explorer and did a "find" looking
for vee.io) I found that VEE is now looking in the new application's directory!
Afetr a little more poking I found that the new application is setting
an environment variable called HOME. And it appears that if HOME is set
then VEE looks in the HOME directory for vee.io instead of it's own
install directory.
VEE _doesn't_ appear to use HOME for anything else, like default
directory, startup directory, looking for menu files, etc.
Any way around this?
Is this intended behavior or a bug?
Stan Bischof
stanb@sr.hp.com
From: "Tom Sanders" <toms@symca.com>
Subject: Re: VRF- "HOME" variable?
To: Stan Bischof <stanb@hpnmrsb2.sr.hp.com>
------------------------
From: Stan Bischof <stanb@hpnmrsb2.sr.hp.com>
Subject: VRF- "HOME" variable?
Date: Fri, 25 Jul 1997 08:54:24 -0700 (PDT)
To: hpvxd_xc@hpislsup.lvld.hp.com
> Hi all.
>
> I just installed an application on my computer totally unrelated to VEE
> and when I went into VEE found that my IO Configuration was gone!
>
> I poked around and found that the vee.io file was still intact in the
> install directory but for some reason was not being read in by VEE.
> Strange to say the least.
>
> After some experimentation ( I went into vee, created a new IO config
> and saved it. Then went to my explorer and did a "find" looking
> for vee.io) I found that VEE is now looking in the new application's directory!
>
> Afetr a little more poking I found that the new application is setting
> an environment variable called HOME. And it appears that if HOME is set
> then VEE looks in the HOME directory for vee.io instead of it's own
> install directory.
>
> VEE _doesn't_ appear to use HOME for anything else, like default
> directory, startup directory, looking for menu files, etc.
>
> Any way around this?
>
> Is this intended behavior or a bug?
>
> Stan Bischof
> stanb@sr.hp.com
>
>
---------------End of Original Message-----------------
Stan,
I think the intent is that HOME would/could point to a users HOME directory to be more like the way unix would behave. Personally I never use the default vee.io directory. I always set up a seperate VEE icon for each different set of hardware and use the -veeio command line option to get the corresponding IO configuration for that hardware. Just my 2 cents.
Tom Sanders