怎么从CD运行VXE？

> AutorunSimplicity本身。
按照微软的指示 - 那些其他人正在谈论流利。
在root中创建autorun.ini，添加一个[autorun]节头，并在其中放置open = veerun.exe myprog.vxe。真正的菜单根本不难创建，你已经知道每个人都有IE。
启动程序是来自VBS或JS的儿童游戏，尽管大多数安装都关闭了IE选项（或者至少它们设置为提示）。
您可以通过编写一个简单的VB菜单程序来解决这个问题.Autorun，并从那里开始。它可以看起来令人印象深刻，但请咨询平面设计师。它需要技巧来制作看起来不像的东西。
啊，dookie，但几乎每个人都可以从 - dookie说出优秀。>运行CD的一个小缺点（我认为）是程序>需要一些ActiveX或其他那些>花哨的东西.Advantage API：没有库
必要的，除了已经存在的那些。
大多数自动化库只不过是围绕API函数的轻量级包装器。
正如我们前几天看到的那样甚至可以使用VEE实现回调函数。>或者可能会有一种方法>“自动”注册ActiveX>临时并在> demo.No问题之后取消注册。
对于您需要的任何ProgID，尝试打开密钥HKCR（例如SubCls.Subclass）。
如果open失败，则从容器中提取二进制文件，编写并注册（搜索WriteAndReg）。
始终取消注册并删除任何自定义库。
类似的技术适用于.NET。整个过程可以静默执行，也可以使用常规安装程序。
我觉得沉默是一个更好的选择。
人们想要插入CD并观看演示。
他们不想被问及在哪里安装什么。-SHAWN ----要订阅，请发送电子邮件至：“vrf-request@lists.it.agilent.com”，邮件正文中包含subscribe一词。
要取消订阅，请发送一封空白电子邮件至“leave-vrf@it.lists.it.agilent.com”。要向此邮件列表发送邮件，请发送电子邮件至“vrf@agilent.com”。
如果您需要有关邮件列表的帮助，请发送邮件至“owner-vrf@it.lists.it.agilent.com”。在“www.oswegosw.com/vrf_archive/”上搜索“非官方vrf档案”。



     以下为原文

  > Autorun

Simplicity itself. Follow directions from Microsoft - those other people are talking giberish. Create autorun.ini in the root, add an [autorun] section header and put open=veerun.exe myprog.vxe in there.

A real menu is not difficult at all to create, and you already know that everybody has IE. Launching programs is child's play from VBS or JS, though most installations have those IE options turned off (or at least they're set to prompt). You can get around that by writing a simple VB menu program.
Autorun that, and launch from there.

It can look as impressive as you want, but please consult a graphic designer.
It takes skill to make something that doesn't look like ... ah, dookie but almost everybody can tell excellence from - dookie.

> One little disadvantage of running
> of a CD (I think) is if the program
> needs some ActiveX or other of that
> fancy stuff.

Advantage API: no libraries necessary, other than those that are already there. Most of the Automation libraries are nothing more than lightweight wrappers around API functions.  As we saw just the other day even callback functions can be implemented with VEE.

> Or maybe there will be a way to
> "automatically" register the ActiveX
> temporarily and unregister after the
> demo.

No problem at all. For any ProgID you do need, attempt to open the key HKCR (like SubCls.Subclass for instance). If the open fails then extract the binary from a container, write it and register it (search for WriteAndReg). Always unregister and delete any custom libraries. Similar techniques work for .NET.

The entire process can be carried out silently or you can use regular installers. I feel that silent is a far better option. People want to insert a CD and watch a demo. They don't want to be interrogated about where to install what.
-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/".

@page Section1 {size：8.5in 11.0in;
保证金：1.0in 1.25in 1.0in 1.25in;
} M.MsoNormal {FONT-SIZE：12pt;
MARGIN：0英寸0英尺0;
FONT-FAMILY：“Times New Roman”} LI.MsoNormal {FONT-SIZE：12pt;
MARGIN：0英寸0英尺0;
FONT-FAMILY：“Times New Roman”} DIV.MsoNormal {FONT-SIZE：12pt;
MARGIN：0英寸0英尺0;
FONT-FAMILY：“Times New Roman”} A：链接{COLOR：blue;
TEXT-DECORATION：下划线} SPAN.MsoHyperlink {颜色：蓝色;
文字装饰：强调} A：访问{COLOR：＃606420;
TEXT-DECORATION：下划线} SPAN.MsoHyperlinkFollowed {COLOR：＃606420;
文字装饰：下划线} P {FONT-SIZE：12pt;
MARGIN-LEFT：0in;
MARGIN-RIGHT：0in;
FONT-FAMILY：“Times New Roman”;
mso-margin-top-alt：auto;
mso-margin-bottom-alt：auto} SPAN.EmailStyle18 {COLOR：windowtext;
FONT-FAMILY：Arial;
mso-style-type：personal} SPAN.EmailStyle19 {COLOR：navy;
FONT-FAMILY：Arial;
mso-style-type：personal} SPAN.EmailStyle20 {COLOR：navy;
FONT-FAMILY：Arial;
mso-style-type：personal-reply} DIV.Section1 {page：Section1} DearNicole，我不喜欢VEE Pro的15岁生日，但作为具有10年经验的VEE设计师，我希望安捷伦更准确地定义VEE路线图。
我的拙见认为VEE有几个缺点：1）缺乏Windows 64位支持。
我想VEE将能够在Windows 64位系统上运行，但由于无法在Windows 64位系统上安装Agilent I / O库，因此无法在Windows 64位系统上安装VEE 7.5。
顺便说一下，NI为LabView提供Windows 64位系统支持.2）缺乏本机VISA库支持。
现在GPIB调用通过SICL库。
不可能为GPIB /以太网设备设计自动设置.3）可怕的界面设计能力。
很难说服客户接受VEE类型的用户界面而不是LabView类型的用户界面.4）非常老的内置Matlab版本。
新的Matlab信号处理工具包功能更强大。
在VEE中使用为新的Matlab信号处理工具包设计的Matlab代码是不可能的。最好的问候，Mikhail Kozlov ---您目前订阅vrf为：r***@soco.agilent.com要订阅，请发送电子邮件至：“vrf
-request@lists.it.agilent.com“在邮件正文中单词subscribe。要取消订阅，请发送空白电子邮件至”leave-vrf@it.lists.it.agilent.com“。要向此邮件列表发送邮件
，发送电子邮件至“vrf@agilent.com”。
如果您需要有关邮件列表的帮助，请发送邮件至“owner-vrf@it.lists.it.agilent.com”。在“www.oswegosw.com/vrf_archive/”上搜索“非官方vrf档案”。



     以下为原文

  @page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.25in 1.0in 1.25in; }P.MsoNormal {     FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"}LI.MsoNormal {     FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"}DIV.MsoNormal {     FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"}A:link {     COLOR: blue; TEXT-DECORATION: underline}SPAN.MsoHyperlink {     COLOR: blue; TEXT-DECORATION: underline}A:visited {     COLOR: #606420; TEXT-DECORATION: underline}SPAN.MsoHyperlinkFollowed {     COLOR: #606420; TEXT-DECORATION: underline}P {     FONT-SIZE: 12pt; MARGIN-LEFT: 0in; MARGIN-RIGHT: 0in; FONT-FAMILY: "Times New Roman"; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto}SPAN.EmailStyle18 {     COLOR: windowtext; FONT-FAMILY: Arial; mso-style-type: personal}SPAN.EmailStyle19 {     COLOR: navy; FONT-FAMILY: Arial; mso-style-type: personal}SPAN.EmailStyle20 {     COLOR: navy; FONT-FAMILY: Arial; mso-style-type: personal-reply}DIV.Section1 {     page: Section1} Dear   Nicole, I do not like to  mar VEE Pro's 15th birthday but as VEE designer with 10 years experience I would like that Agilent define more exactly VEE roadmap.In my humble opinion there are several disadvantages of VEE: 1) Lack of Windows 64 bit support. I guess that VEE will be able to run on Windows 64 bit system but it is impossible to install VEE 7.5 on Windows 64 bit system since it is impossible to install Agilent I/O library on Windows 64 bit system. By the way NI offers  Windows 64 bit system support for LabView. 2) Lack of native VISA library support. Right now GPIB calls go through SICL library. It is impossible to design auto setup for GPIB/Ethernet devices. 3) Awful interface design ability. It is very difficult to persuade customer to accept VEE type user interface instead of LabView type user interface. 4) Very old built-in Matlab version. New Matlab signal processing toolkit is more powerful. It is impossible to use Matlab code designed for new Matlab signal processing toolkit in VEE. With best regards, Mikhail Kozlov  ---You are currently subscribed to vrf as: [email=r***@soco.agilent.com]r***@soco.agilent.com[/email]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/".