> How do I force calls to vee to use the > runtime rather than the development version?
Uninstall development?
That is kind of weird. The sequence should go libvapi->veerun->libvapi. VEE.exe really shouldn't be involved at all. Of course I don't *know* that, but...
Ok, how about put VEE Pro RunTime in the path, or make the app's current directory VEE Pro RunTime? -SHAWN-
--- You are currently subscribed to vrf as: rsb@soco.agilent.com To subscribe please send an email to: "vrf-request@lists.it.agilent.com" with the word subscribe in the message body. To unsubscribe send a blank email to "leave-vrf@it.lists.it.agilent.com". To send messages to this mailing list, email "vrf@agilent.com". If you need help with the mailing list send a message to "owner-vrf@it.lists.it.agilent.com". Search the "unofficial vrf archive" at "www.oswegosw.com/vrf_archive/".
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML><HEAD><META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1"><STYLE>BODY { FONT-WEIGHT: normal; MARGIN-LEFT: 10px; COLOR: rgb(51,51,51); FONT-FAMILY: "Verdana","sans serif"; BACKGROUND-COLOR: rgb(255,255,247)}</STYLE><META content="MSHTML 6.00.2900.2802" name=GENERATOR></HEAD><BODY><DIV><FONT color=#000000 size=2><SPAN class=484075116-12032006>All,</SPAN></FONT></DIV><DIV><FONT color=#000000 size=2><SPAN class=484075116-12032006></SPAN></FONT> </DIV><DIV><FONT color=#000000 size=2><SPAN class=484075116-12032006>How do I force calls to vee to use the runtime rather than the development version?</SPAN></FONT></DIV><DIV><FONT color=#000000 size=2><SPAN class=484075116-12032006></SPAN></FONT> </DIV><DIV><FONT color=#000000 size=2><SPAN class=484075116-12032006>The problem I'm having is every time a call is made to VEE the 30 day evaluation nag screen comes up, which means a tech has to sit there clicking OK all day long.</SPAN></FONT></DIV><DIV><FONT color=#000000 size=2><SPAN class=484075116-12032006></SPAN></FONT> </DIV><DIV><FONT color=#000000 size=2><SPAN class=484075116-12032006>I tried reinstalling the runtime version in the hopes it would change something in the registry, but no, I'm still getting nagged.</SPAN></FONT></DIV><DIV><FONT color=#000000 size=2><SPAN class=484075116-12032006></SPAN></FONT> </DIV><DIV><FONT color=#000000 size=2><SPAN class=484075116-12032006>Anyone?</SPAN></FONT></DIV><DIV><FONT color=#000000 size=2><SPAN class=484075116-12032006></SPAN></FONT> </DIV><DIV><FONT color=#000000 size=2><SPAN class=484075116-12032006>Thanks,</SPAN></FONT></DIV><DIV><FONT color=#000000 size=2><SPAN class=484075116-12032006>Bill</SPAN></FONT></DIV><BR>---<BR>You are currently subscribed to vrf as: rsb@soco.agilent.com<BR>To subscribe please send an email to: "vrf-request@lists.it.agilent.com" with the word subscribe in the message body.<BR>To unsubscribe send a blank email to "leave-vrf@it.lists.it.agilent.com".<BR>To send messages to this mailing list, email "vrf@agilent.com". <BR>If you need help with the mailing list send a message to<BR>"owner-vrf@it.lists.it.agilent.com".<BR>Search the "unofficial vrf archive" at "www.oswegosw.com/vrf_archive/".</BODY></HTML><BR><P><FONT SIZE=2 FACE="Arial"> This e-mail and subsequent attachments may contain information which is proprietary to L-3 Communications Corporation. The contents shall not be disclosed, copied, distributed or used unless authorized by L-3 Communications Narda - East.</FONT></P>
> If you're not sure, then I don't know who would be.
I'm sure somebody from Agilent would know.
> It just seems like if the runtime was > installed after the devel, then the > runtime should take over the callable > stuff.
It sure should. Something somewhere was probably overlooked. I wonder if maybe it's a service manager issue? Check if veesm.exe is different between dev and runtime. Mine are different, but I think that's because dev is patched and runtime isn't. I see the runtime has a different reg key than dev (HKLMSOFTWAREAgilent...). Maybe getting rid of the dev key would do it. -SHAWN-
--- You are currently subscribed to vrf as: rsb@soco.agilent.com To subscribe please send an email to: "vrf-request@lists.it.agilent.com" with the word subscribe in the message body. To unsubscribe send a blank email to "leave-vrf@it.lists.it.agilent.com". To send messages to this mailing list, email "vrf@agilent.com". If you need help with the mailing list send a message to "owner-vrf@it.lists.it.agilent.com". Search the "unofficial vrf archive" at "www.oswegosw.com/vrf_archive/".
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"><HTML><HEAD><META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1"><META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2658.34"><TITLE>RE: [vrf] Callable VEE Runtime</TITLE></HEAD><BODY><P><FONT SIZE=2>If you're not sure, then I don't know who would be. I might just transfer a license to that machine and forget about it.</FONT></P><P><FONT SIZE=2>It just seems like if the runtime was installed after the devel, then the runtime should take over the callable stuff.</FONT></P><P><FONT SIZE=2>Thanks,</FONT><BR><FONT SIZE=2>Bill</FONT></P><P><FONT SIZE=2>> -----Original Message-----</FONT><BR><FONT SIZE=2>> From: Shawn Fessenden [<A HREF="mailto:shawn@testech-ltd.com">mailto:shawn@testech-ltd.com</A>]</FONT><BR><FONT SIZE=2>> Sent: Sunday, March 12, 2006 12:52 PM</FONT><BR><FONT SIZE=2>> To: 'Drago, William @NARDAEAST'; 'VRF'</FONT><BR><FONT SIZE=2>> Subject: RE: [vrf] Callable VEE Runtime</FONT><BR><FONT SIZE=2>> </FONT><BR><FONT SIZE=2>> </FONT><BR><FONT SIZE=2>> > How do I force calls to vee to use the</FONT><BR><FONT SIZE=2>> > runtime rather than the development version?</FONT><BR><FONT SIZE=2>> </FONT><BR><FONT SIZE=2>> Uninstall development?</FONT><BR><FONT SIZE=2>> </FONT><BR><FONT SIZE=2>> That is kind of weird. The sequence should go </FONT><BR><FONT SIZE=2>> libvapi->veerun->libvapi.</FONT><BR><FONT SIZE=2>> VEE.exe really shouldn't be involved at all. Of course I </FONT><BR><FONT SIZE=2>> don't *know* that,</FONT><BR><FONT SIZE=2>> but...</FONT><BR><FONT SIZE=2>> </FONT><BR><FONT SIZE=2>> Ok, how about put VEE Pro RunTime in the path, or make the </FONT><BR><FONT SIZE=2>> app's current</FONT><BR><FONT SIZE=2>> directory VEE Pro RunTime?</FONT><BR><FONT SIZE=2>> -SHAWN-</FONT><BR><FONT SIZE=2>> </FONT></P><P><FONT SIZE=2> This e-mail and subsequent attachments may contain information which is proprietary to L-3 Communications Corporation. The contents shall not be disclosed, copied, distributed or used unless authorized by L-3 Communications Narda - East.</FONT></P><BR>---<BR>You are currently subscribed to vrf as: rsb@soco.agilent.com<BR>To subscribe please send an email to: "vrf-request@lists.it.agilent.com" with the word subscribe in the message body.<BR>To unsubscribe send a blank email to "leave-vrf@it.lists.it.agilent.com".<BR>To send messages to this mailing list, email "vrf@agilent.com". <BR>If you need help with the mailing list send a message to<BR>"owner-vrf@it.lists.it.agilent.com".<BR>Search the "unofficial vrf archive" at "www.oswegosw.com/vrf_archive/".</BODY></HTML>
The service manager looks for installed VEE Pro bits preferentially over VEE Runtime. It doesn't care if it is eval or licensed. You can, however, tell veesm.exe where to look for the vee "install" directory. Run it this way:
veesm.exe -d "c:program filesagielntVEE Pro 6.2 Runtime"
(substituting the proper runtime install directory) And it should start up the executable in that directory.
Ken
-----Original Message----- From: Shawn Fessenden [mailto:shawn@testech-ltd.com] Sent: Sunday, March 12, 2006 11:31 AM To: VRF Subject: RE: [vrf] Callable VEE Runtime
> If you're not sure, then I don't know who would be.
I'm sure somebody from Agilent would know.
> It just seems like if the runtime was > installed after the devel, then the > runtime should take over the callable > stuff.
It sure should. Something somewhere was probably overlooked. I wonder if maybe it's a service manager issue? Check if veesm.exe is different between dev and runtime. Mine are different, but I think that's because dev is patched and runtime isn't. I see the runtime has a different reg key than dev (HKLMSOFTWAREAgilent...). Maybe getting rid of the dev key would do it. -SHAWN-
--- You are currently subscribed to vrf as: ken_colasuonno@agilent.com To subscribe please send an email to: "vrf-request@lists.it.agilent.com" with the word subscribe in the message body. To unsubscribe send a blank email to "leave-vrf@it.lists.it.agilent.com". To send messages to this mailing list, email "vrf@agilent.com". If you need help with the mailing list send a message to "owner-vrf@it.lists.it.agilent.com". Search the "unofficial vrf archive" at "www.oswegosw.com/vrf_archive/".
--- You are currently subscribed to vrf as: rsb@soco.agilent.com To subscribe please send an email to: "vrf-request@lists.it.agilent.com" with the word subscribe in the message body. To unsubscribe send a blank email to "leave-vrf@it.lists.it.agilent.com". To send messages to this mailing list, email "vrf@agilent.com". If you need help with the mailing list send a message to "owner-vrf@it.lists.it.agilent.com". Search the "unofficial vrf archive" at "www.oswegosw.com/vrf_archive/".
All, Â How do I force calls to vee to use the runtime rather than the development version? Â The problem I'm having is every time a call is made to VEE the 30 day evaluation nag screen comes up, which means a tech has to sit there clicking OK all day long. Â I tried reinstalling the runtime version in the hopes it would change something in the registry, but no, I'm still getting nagged. Â Anyone? Â Thanks, Bill
---
To subscribe please send an email to: "vrf-request@lists.it.agilent.com" with the word subscribe in the message body. To unsubscribe send a blank email to "leave-vrf@it.lists.it.agilent.com". To send messages to this mailing list, email "vrf@agilent.com". If you need help with the mailing list send a message to "owner-vrf@it.lists.it.agilent.com". Search the "unofficial vrf archive" at "www.oswegosw.com/vrf_archive/".
This e-mail and subsequent attachments may contain information which is proprietary to L-3 Communications Corporation. The contents shall not be disclosed, copied, distributed or used unless authorized by L-3 Communications Narda - East.
All, Â How do I force calls to vee to use the runtime rather than the development version? Â The problem I'm having is every time a call is made to VEE the 30 day evaluation nag screen comes up, which means a tech has to sit there clicking OK all day long. Â I tried reinstalling the runtime version in the hopes it would change something in the registry, but no, I'm still getting nagged. Â Anyone? Â Thanks, Bill
---
To subscribe please send an email to: "vrf-request@lists.it.agilent.com" with the word subscribe in the message body. To unsubscribe send a blank email to "leave-vrf@it.lists.it.agilent.com". To send messages to this mailing list, email "vrf@agilent.com". If you need help with the mailing list send a message to "owner-vrf@it.lists.it.agilent.com". Search the "unofficial vrf archive" at "www.oswegosw.com/vrf_archive/".
This e-mail and subsequent attachments may contain information which is proprietary to L-3 Communications Corporation. The contents shall not be disclosed, copied, distributed or used unless authorized by L-3 Communications Narda - East.
> How do I force calls to vee to use the runtime rather than the > development version?
Uninstall development?
That is kind of weird. The sequence should go libvapi->veerun->libvapi. VEE.exe really shouldn't be involved at all. Of course I don't *know* that, but...
Ok, how about put VEE Pro RunTime in the path, or make the app's current directory VEE Pro RunTime? -SHAWN-
--- To subscribe please send an email to: "vrf-request@lists.it.agilent.com" with the word subscribe in the message body. To unsubscribe send a blank email to "leave-vrf@it.lists.it.agilent.com". To send messages to this mailing list, email "vrf@agilent.com". If you need help with the mailing list send a message to "owner-vrf@it.lists.it.agilent.com". Search the "unofficial vrf archive" at "www.oswegosw.com/vrf_archive/".
If you're not sure, then I don't know who would be. I might just transfer a license to that machine and forget about it.
It just seems like if the runtime was installed after the devel, then the runtime should take over the callable stuff.
Thanks, Bill
> -----Original Message----- > From: Shawn Fessenden [mailto:shawn@testech-ltd.com] > Sent: Sunday, March 12, 2006 12:52 PM > To: 'Drago, William @NARDAEAST'; 'VRF' > Subject: RE: [vrf] Callable VEE Runtime > > > > How do I force calls to vee to use the > > runtime rather than the development version? > > Uninstall development? > > That is kind of weird. The sequence should go > libvapi->veerun->libvapi. > VEE.exe really shouldn't be involved at all. Of course I > don't *know* that, > but... > > Ok, how about put VEE Pro RunTime in the path, or make the > app's current > directory VEE Pro RunTime? > -SHAWN- >
 This e-mail and subsequent attachments may contain information which is proprietary to L-3 Communications Corporation. The contents shall not be disclosed, copied, distributed or used unless authorized by L-3 Communications Narda - East.
---
To subscribe please send an email to: "vrf-request@lists.it.agilent.com" with the word subscribe in the message body. To unsubscribe send a blank email to "leave-vrf@it.lists.it.agilent.com". To send messages to this mailing list, email "vrf@agilent.com". If you need help with the mailing list send a message to "owner-vrf@it.lists.it.agilent.com". Search the "unofficial vrf archive" at "www.oswegosw.com/vrf_archive/".
> If you're not sure, then I don't know who would be.
I'm sure somebody from Agilent would know.
> It just seems like if the runtime was > installed after the devel, then the > runtime should take over the callable > stuff.
It sure should. Something somewhere was probably overlooked. I wonder if maybe it's a service manager issue? Check if veesm.exe is different between dev and runtime. Mine are different, but I think that's because dev is patched and runtime isn't. I see the runtime has a different reg key than dev (HKLMSOFTWAREAgilent...). Maybe getting rid of the dev key would do it. -SHAWN-
--- To subscribe please send an email to: "vrf-request@lists.it.agilent.com" with the word subscribe in the message body. To unsubscribe send a blank email to "leave-vrf@it.lists.it.agilent.com". To send messages to this mailing list, email "vrf@agilent.com". If you need help with the mailing list send a message to "owner-vrf@it.lists.it.agilent.com". Search the "unofficial vrf archive" at "www.oswegosw.com/vrf_archive/".
The service manager looks for installed VEE Pro bits preferentially over VEE Runtime. It doesn't care if it is eval or licensed. You can, however, tell veesm.exe where to look for the vee "install" directory. Run it this way:
veesm.exe -d "c:program filesagielntVEE Pro 6.2 Runtime"
(substituting the proper runtime install directory) And it should start up the executable in that directory.
Ken
-----Original Message----- From: Shawn Fessenden [mailto:shawn@testech-ltd.com] Sent: Sunday, March 12, 2006 11:31 AM To: VRF Subject: RE: [vrf] Callable VEE Runtime
> If you're not sure, then I don't know who would be.
I'm sure somebody from Agilent would know.
> It just seems like if the runtime was > installed after the devel, then the > runtime should take over the callable > stuff.
It sure should. Something somewhere was probably overlooked. I wonder if maybe it's a service manager issue? Check if veesm.exe is different between dev and runtime. Mine are different, but I think that's because dev is patched and runtime isn't. I see the runtime has a different reg key than dev (HKLMSOFTWAREAgilent...). Maybe getting rid of the dev key would do it. -SHAWN-
--- You are currently subscribed to vrf as: ken_colasuonno@agilent.com To subscribe please send an email to: "vrf-request@lists.it.agilent.com" with the word subscribe in the message body. To unsubscribe send a blank email to "leave-vrf@it.lists.it.agilent.com". To send messages to this mailing list, email "vrf@agilent.com". If you need help with the mailing list send a message to "owner-vrf@it.lists.it.agilent.com". Search the "unofficial vrf archive" at "www.oswegosw.com/vrf_archive/".
--- To subscribe please send an email to: "vrf-request@lists.it.agilent.com" with the word subscribe in the message body. To unsubscribe send a blank email to "leave-vrf@it.lists.it.agilent.com". To send messages to this mailing list, email "vrf@agilent.com". If you need help with the mailing list send a message to "owner-vrf@it.lists.it.agilent.com". Search the "unofficial vrf archive" at "www.oswegosw.com/vrf_archive/".
> runtime rather than the development version?
Uninstall development?
That is kind of weird. The sequence should go libvapi->veerun->libvapi.
VEE.exe really shouldn't be involved at all. Of course I don't *know* that,
but...
Ok, how about put VEE Pro RunTime in the path, or make the app's current
directory VEE Pro RunTime?
-SHAWN-
---
You are currently subscribed to vrf as: rsb@soco.agilent.com
To subscribe please send an email to: "vrf-request@lists.it.agilent.com" with the word subscribe in the message body.
To unsubscribe send a blank email to "leave-vrf@it.lists.it.agilent.com".
To send messages to this mailing list, email "vrf@agilent.com".
If you need help with the mailing list send a message to
"owner-vrf@it.lists.it.agilent.com".
Search the "unofficial vrf archive" at "www.oswegosw.com/vrf_archive/".