请问Windows加载错误怎么解决？

在“www.oswegosw.com/vrf_archive/”上搜索“unofficial vrf archive”。

这些天似乎有点慢，特别是如果有嵌入式数据......现在再次只是文本... ... - UrsprünglicheNachricht----- Von：Baranski，DetlefGesendet：Mittwoch
，2006年4月12日：52：“Dykema，Jim-P14701”;
VRFBetreff：AW：[vrf] - AxtiveX QuestionOkay，你使用的是V7.5-很棒。你要记住的是，如果你复制那些不在excellib菜单中的所有activeX调用都会被xlApp.So引用
excel宏只是在它们前面增强xlApp，它会起作用（有时候，。,,）。在activex这个词中也必须有一些变化。你忘了为selection.paste做一个（）。
...在这些情况下，您必须在设备菜单中查找正确的activeX语法...希望样本可以帮助您超越... >>最好的问候，detlef -----UrsprünglicheNachricht----
-Von：Dykema，Jim-P14701 [mailto：Jim.Dykema@gdc4s.com] Gesendet：Montag，13。März200620：59An：VRFBetreff：[vrf] - AxtiveX Question我正在尝试从Excel复制嵌入式图表
并将其粘贴到Word。
我在Excel中记录了以下宏并将其粘贴到VEE中。
我收到错误消息“找不到变量：ActiveSheet”。
我在ActiveX Automation References下选择了Microsoft Office Excel 9.0对象库。
我缺少什么？ActiveSheet.ChartObjects（“Chart 1”）。激活;
ActiveChart.ChartArea.Select;
ActiveChart.ChartArea.Copy Jim DykemaGENERAL DYNAMICS8201 E. McDowell Rd.Scottsdale，AZ 85257电话：（480）675-2104FAX：（480）441-3625Pager数字：（877）526-7062Pager Text：8775267062@skytel.comEmail：jim.dykema
@ gdc4s.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档案”。

>关于它是什么或如何跟踪itInterop程序集的任何想法都是在它们被选中时创建的。
它可能只是丢失了dll。
在.vee文件中，您将在开头附近找到它：（assemblyRef（assemblyRef 1（displayName“Shell32，Version = 1.0.0.0”）（libid“{50A7E9B0-70EF-11D1-B75A-00A0C90564FE}”）（desc“
Microsoft Shell控件和自动化“）（文件名”C： WINDOWS  system32  SHELL32.dll“）（verMajor 1）（verMinor 0）（lcid 0）（isPIA 0）（IAFilename”C： Documents and Settings  Shawn
我的Documents  VEE Programs  Cache  Shell32.dll“））这是缺少的IAFilename。进入.NET程序集参考...，单击”COM“选项卡并向下滚动到”Microsoft Shell控件和自动化“，取消选中它
然后单击OK。返回，检查，单击OK并保存程序。我认为应该清除它。-SHAWN-

Hello!
Simon, Gregg Levine here. Perhaps you've seen my posts? Okay, I see
where your going with this, and Shawn I think you forgot this one.
I'll put it down to a temporary blind spot.

Basically it might easily be one of the user account that your running
VEE under. It might actually need more privileges to access everything
it needs. For example, examine the methods behind installing VEE 7.51
from its disk, they describe a means where you'd need to invoke it
using the "runas" syntax. It sounds preposterous, but in an
environment where people do not have their own privileges to install
and manage their own software, these things tend to surface.
---
Gregg C Levine hansolofalcon@worldnet.att.net
---
"Remember the Force will be with you. Always." Obi-Wan Kenobi

> -----Original Message-----
> From: Simon Parfitt [mailto:Simon.Parfitt@renesas.com]
> Sent: Thursday, April 06, 2006 4:04 AM
> To: VRF
> Subject: RE: [vrf] Error on loading
>
> Hi Shawn
>
> I have tried that and as soon as I reselect the "Microsoft Shell
Controls
> And Automation" I  get the error message again. I looks like it is
not on my
> system!!
>
> Simon
>
> -----Original Message-----
> From: Shawn Fessenden [mailto:shawnfess@comcast.net]
> Sent: 05 April 2006 17:40
> To: VRF
> Subject: RE: [vrf] Error on loading
>
>
> > Any ideas on what it is or how to trace it
>
> Interop assemblies are created at the time they are selected. It
probably
> just lost the dll. In the .vee file you'll find this near the
beginning:
>
> (assemblyRefs
> (assemblyRef 1
> (displayName "Shell32, Version=1.0.0.0")
> (libid "{50A7E9B0-70EF-11D1-B75A-00A0C90564FE}")
> (desc "Microsoft Shell Controls And Automation")
> (filename "C:WINDOWSsystem32SHELL32.dll")
> (verMajor 1)
> (verMinor 0)
> (lcid 0)
> (isPIA 0)
> (IAFilename
> "C:Documents and SettingsShawnMy DocumentsVEE
> ProgramsCacheShell32.dll"
> ))
>
> It's the IAFilename that's missing. Go into .NET Assembly
References...,
> click the "COM" tab and scroll down to "Microsoft Shell Controls And
> Automation", uncheck it and click OK. Go back in, check it, click OK
and
> save the program. I think that should clear it up.
> -SHAWN-
>
> ---
> You are currently subscribed to vrf as:
hansolofalcon@worldnet.att.net
> 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: [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/".

From: "Jay Nemeth-Johannes"
To: "'Stan Bischof (Richard S)'"
Subject: RE: Re[2]:  [vrf] Instrument driver question...
Date: Tue, 4 Apr 2006 11:48:00 -0600

Just to you.

Yep, obviously an LXI fan.  It may be interesting to note that I have been
working with the smart sensor community the last several years, and our
access methods pretty much converge with LXI.  After awhile it is going to
be difficult to figure out if something is a DAQ box, or a collection of
smart wireless sensors.

Jay Nemeth-Johannes
Smart Sensor Systems
720 SW 14th Street
Loveland, Colorado 80537
(970) 663-0006
www.SmartSensorSystems.com



> -----Original Message-----
> From: Stan Bischof (Richard S) [mailto:r***@soco.agilent.com]
> Sent: Tuesday, April 04, 2006 10:24 AM
> To: VRF
> Cc: vrf@agilent.com
> Subject: Re[2]: [vrf] Instrument driver question...
>
> "Brian H. Powell" wrote:
> >       I think the instrument driver vs. Direct I/O question
> transcends
> > development environments, so I hope you'll allow me to offer a
> > perspective from the LabVIEW side...
>
>
> >       I think this applies to VEE as well.  For one-time
> use, Direct
> > I/O is nice and easy.  For reusability, wrap it in
> higher-level user
> > functions.  Build up your code from there.
> >
>
> Now this is getting downright interesting!
>
> Using IO commands directly has the big advantage that it will
> work with any programming language since the actual
> instrument commands sent will be the same regardless of from
> where they are sent. That's a real plus. The downside of
> course is that the end user has a lot of work to do in
> assimilating the programming languages of every instrument
> that will be used. And of course all such languages are
> extremely sensitive to syntax.
>
> As Brian suggests, this is ameliorated to a large extent by
> wrapping sets of IO commands into higher-level functions that
> can be used within a given environment. All sophisticated
> code is written this way anyhow for many reasons. The big
> downside is that any work done becomes application specific
> since each programming environment is proprietary. This gets
> really ugly when environments get rev'd in a manner that
> breaks older code.
>
> Existing "Drivers" on the other hand are really just a
> different form of function wrapper around the same sets of IO
> commands.
> The intent of "drivers" is that they are cross-environment so
> can be used anywhere. However reality has shown that the
> industry has never agreed to the extent necessary to actually
> make this happen. No existing drivers handle more than a
> handful of special cases, so for all practical purposes they
> are proprietary in nature- severely hastening their eventual demise.
>
> Coupled with the difficulties in just attaching and
> communicating with instruments in the first place, this very
> often makes basic instrument control issues the bottleneck in
> automation. Which is crazy of course since the end user will
> almost never have instrument control as the end goal, but
> rather as a necessary evil that has to be overcome.
>
> My own feeling is that the only way this will fundamentally
> change is when instruments start being produced used portable
> objects of one form or another- such that command languages,
> drivers, and so on all vanish. Instead instrument control
> becomes as simple as web browsing- browse to the instrument,
> grab displays or other objects, drop them into your program
> and continue onwards. Just as the basic interfacing will need
> to move to computer standards ( ethernet, USB, etc.) this
> portable object technology will also have to be computer standards.
>
> I fully realize that this will take a long time to happen-
> but just imagine being able to use your instrument from any
> environment as easily as from the front panel, and then being
> able to spend most of your time doing useful programming
> rather than playing with instrument control. Pipe dream?
> Sure- but quite technically feasible at the same time.
>
> back to the fray---
>
> Stan
>
>
> --------------------------------------------------------------
> ------------
> Stan Bischof  Agilent Technologies  707-577-3994
> stan_bischof@agilent.com
> --------------------------------------------------------------
> ------------
>
> ---
> You are currently subscribed to vrf as:
> jay.johannes@completetest.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/".
>

Hello!
Simon, Gregg Levine here. Perhaps you've seen my posts? Okay, I see
where your going with this, and Shawn I think you forgot this one.
I'll put it down to a temporary blind spot.

Basically it might easily be one of the user account that your running
VEE under. It might actually need more privileges to access everything
it needs. For example, examine the methods behind installing VEE 7.51
from its disk, they describe a means where you'd need to invoke it
using the "runas" syntax. It sounds preposterous, but in an
environment where people do not have their own privileges to install
and manage their own software, these things tend to surface.
---
Gregg C Levine hansolofalcon@worldnet.att.net
---
"Remember the Force will be with you. Always." Obi-Wan Kenobi

> -----Original Message-----
> From: Simon Parfitt [mailto:Simon.Parfitt@renesas.com]
> Sent: Thursday, April 06, 2006 4:04 AM
> To: VRF
> Subject: RE: [vrf] Error on loading
>
> Hi Shawn
>
> I have tried that and as soon as I reselect the "Microsoft Shell
Controls
> And Automation" I  get the error message again. I looks like it is
not on my
> system!!
>
> Simon
>
> -----Original Message-----
> From: Shawn Fessenden [mailto:shawnfess@comcast.net]
> Sent: 05 April 2006 17:40
> To: VRF
> Subject: RE: [vrf] Error on loading
>
>
> > Any ideas on what it is or how to trace it
>
> Interop assemblies are created at the time they are selected. It
probably
> just lost the dll. In the .vee file you'll find this near the
beginning:
>
> (assemblyRefs
> (assemblyRef 1
> (displayName "Shell32, Version=1.0.0.0")
> (libid "{50A7E9B0-70EF-11D1-B75A-00A0C90564FE}")
> (desc "Microsoft Shell Controls And Automation")
> (filename "C:WINDOWSsystem32SHELL32.dll")
> (verMajor 1)
> (verMinor 0)
> (lcid 0)
> (isPIA 0)
> (IAFilename
> "C:Documents and SettingsShawnMy DocumentsVEE
> ProgramsCacheShell32.dll"
> ))
>
> It's the IAFilename that's missing. Go into .NET Assembly
References...,
> click the "COM" tab and scroll down to "Microsoft Shell Controls And
> Automation", uncheck it and click OK. Go back in, check it, click OK
and
> save the program. I think that should clear it up.
> -SHAWN-
>
> ---
> You are currently subscribed to vrf as:
hansolofalcon@worldnet.att.net
> 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: [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/".

From: "Jay Nemeth-Johannes"
To: "'Stan Bischof (Richard S)'"
Subject: RE: Re[2]:  [vrf] Instrument driver question...
Date: Tue, 4 Apr 2006 11:48:00 -0600

Just to you.

Yep, obviously an LXI fan.  It may be interesting to note that I have been
working with the smart sensor community the last several years, and our
access methods pretty much converge with LXI.  After awhile it is going to
be difficult to figure out if something is a DAQ box, or a collection of
smart wireless sensors.

Jay Nemeth-Johannes
Smart Sensor Systems
720 SW 14th Street
Loveland, Colorado 80537
(970) 663-0006
www.SmartSensorSystems.com



> -----Original Message-----
> From: Stan Bischof (Richard S) [mailto:r***@soco.agilent.com]
> Sent: Tuesday, April 04, 2006 10:24 AM
> To: VRF
> Cc: vrf@agilent.com
> Subject: Re[2]: [vrf] Instrument driver question...
>
> "Brian H. Powell" wrote:
> >       I think the instrument driver vs. Direct I/O question
> transcends
> > development environments, so I hope you'll allow me to offer a
> > perspective from the LabVIEW side...
>
>
> >       I think this applies to VEE as well.  For one-time
> use, Direct
> > I/O is nice and easy.  For reusability, wrap it in
> higher-level user
> > functions.  Build up your code from there.
> >
>
> Now this is getting downright interesting!
>
> Using IO commands directly has the big advantage that it will
> work with any programming language since the actual
> instrument commands sent will be the same regardless of from
> where they are sent. That's a real plus. The downside of
> course is that the end user has a lot of work to do in
> assimilating the programming languages of every instrument
> that will be used. And of course all such languages are
> extremely sensitive to syntax.
>
> As Brian suggests, this is ameliorated to a large extent by
> wrapping sets of IO commands into higher-level functions that
> can be used within a given environment. All sophisticated
> code is written this way anyhow for many reasons. The big
> downside is that any work done becomes application specific
> since each programming environment is proprietary. This gets
> really ugly when environments get rev'd in a manner that
> breaks older code.
>
> Existing "Drivers" on the other hand are really just a
> different form of function wrapper around the same sets of IO
> commands.
> The intent of "drivers" is that they are cross-environment so
> can be used anywhere. However reality has shown that the
> industry has never agreed to the extent necessary to actually
> make this happen. No existing drivers handle more than a
> handful of special cases, so for all practical purposes they
> are proprietary in nature- severely hastening their eventual demise.
>
> Coupled with the difficulties in just attaching and
> communicating with instruments in the first place, this very
> often makes basic instrument control issues the bottleneck in
> automation. Which is crazy of course since the end user will
> almost never have instrument control as the end goal, but
> rather as a necessary evil that has to be overcome.
>
> My own feeling is that the only way this will fundamentally
> change is when instruments start being produced used portable
> objects of one form or another- such that command languages,
> drivers, and so on all vanish. Instead instrument control
> becomes as simple as web browsing- browse to the instrument,
> grab displays or other objects, drop them into your program
> and continue onwards. Just as the basic interfacing will need
> to move to computer standards ( ethernet, USB, etc.) this
> portable object technology will also have to be computer standards.
>
> I fully realize that this will take a long time to happen-
> but just imagine being able to use your instrument from any
> environment as easily as from the front panel, and then being
> able to spend most of your time doing useful programming
> rather than playing with instrument control. Pipe dream?
> Sure- but quite technically feasible at the same time.
>
> back to the fray---
>
> Stan
>
>
> --------------------------------------------------------------
> ------------
> Stan Bischof  Agilent Technologies  707-577-3994
> stan_bischof@agilent.com
> --------------------------------------------------------------
> ------------
>
> ---
> You are currently subscribed to vrf as:
> jay.johannes@completetest.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/".
>

您好ShawnI已经尝试过，一旦我重新选择“Microsoft Shell ControlsAnd Automation”，我再次收到错误消息。
我看起来好像不在mysystem上!!西蒙-----原帖-----来自：Shawn Fessenden [mailto：shawnfess@comcast.net]发送时间：2006年4月5日17:40去：VRFS主题：RE：[
vrf]加载时出错>任何关于它是什么或如何跟踪itInterop程序集的想法都是在选择它们时创建的。
它可能只是丢失了dll。
在.vee文件中，您将在开头附近找到它：（assemblyRef（assemblyRef 1（displayName“Shell32，Version = 1.0.0.0”）（libid“{50A7E9B0-70EF-11D1-B75A-00A0C90564FE}”）（desc“
Microsoft Shell控件和自动化“）（文件名”C： WINDOWS  system32  SHELL32.dll“）（verMajor 1）（verMinor 0）（lcid 0）（isPIA 0）（IAFilename”C： Documents and Settings  Shawn
我的文档 VEEPrograms  Cache  Shell32.dll“））这是缺少的IAFilename。进入.NET程序集参考...，单击”COM“选项卡并向下滚动到”Microsoft Shell Controls AndAutomation“，取消选中它并单击
好的。回去，检查一下，点击确定并保存程序。我认为应该清除它.- SHAWN- ---您目前订阅了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档案”。

在“www.oswegosw.com/vrf_archive/”上搜索“unofficial vrf archive”。

Shawn和Gregg，我已经看过system32和ii了！
此外，我多年来一直在这台机器上使用它。
这是傻瓜西蒙-----原帖-----来自：Gregg C Levine [mailto：hansolofalcon@worldnet.att.net]发送时间：2006年4月6日13:38致：Simon Parfitt;
'VRF'主题：RE：[vrf]加载错误你好！西蒙，格雷格莱文在这里。
也许你看过我的帖子？
好的，我看到你的地方，Shawn我想你忘记了这个。
我会把它归结为一个临时的盲点。基本上它可能很容易成为你运行VEEunder的用户帐户之一。
它实际上可能需要更多权限来访问它所需的一切。例如，检查从其磁盘安装VEE 7.51背后的方法，它们描述了一种需要使用“runas”语法调用它的方法。
这听起来很荒谬，但在人们没有自己的特权安装和管理他们自己的软件的环境中，这些事情往往浮出水面。
--- Gregg C Levine hansolofalcon@worldnet.att.net ---“记住，部队会和你在一起。永远。”
Obi-Wan Kenobi> -----原帖----->来自：Simon Parfitt [mailto：Simon.Parfitt@renesas.com]>发送时间：2006年4月6日星期四上午4:04> To：VRF
>主题：RE：[vrf]加载时出错>> Hi Shawn >>我试过了，一旦我重新选择“Microsoft ShellControls> And Automation”，我再次收到错误消息。
我看起来好像不在我的>系统上!! >> Simon>> -----原帖----->来自：Shawn Fessenden [mailto：shawnfess@comcast.net]>发送时间：2006年4月5日17：
40>收件人：VRF>主题：RE：[vrf]加载时出错>>>>有关它是什么或如何跟踪它的任何想法>> Interop程序集在选择它们时创建。
它可能>刚丢失了dll。
在.vee文件中，你会发现它接近开始：>>（assemblyRef>（assemblyRef 1>（displayName“Shell32，Version = 1.0.0.0”）>（libid“{50A7E9B0-70EF-11D1-B75A-00A0C90564FE}”
）>（desc“Microsoft Shell Controls and Automation”）>（文件名“C： WINDOWS  system32  SHELL32.dll”）>（verMajor 1）>（verMinor 0）>（lcid 0）>（isPIA 0）>（
IAFilename>“C： Documents and Settings  Shawn  My Documents  VEE> Programs  Cache  Shell32.dll”>））>>这是缺少的IAFilename。进入.NET AssemblyReferences ...，>单击“COM”
“选项卡并向下滚动到”Microsoft Shell Controls和> Automation“，取消选中它并单击”确定“。返回，检查它，单击”确定“并>保存程序。我认为应该清除它。> -SHAWN- >> -
- >您目前订阅了vrf：hansolofalcon@worldnet.att.net>要订阅，请发送电子邮件至：“vrf-request@lists.it.agilent.com”，并在邮件正文中使用> subscribe字样。
>要取消订阅，请发送一封空白电子邮件至“leave-vrf@it.lists.it.agilent.com”。>向此发送消息
iling list，电邮“vrf@agilent.com”。
如果>您需要有关邮件列表的帮助，请发送邮件至>“owner-vrf@it.lists.it.agilent.com”。>在“www.oswegosw.com/vrf_archive/”上搜索“非官方vrf档案”。
---您目前订阅了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档案”。

嗨再次更多信息这发生在每台PC上!!西蒙-----原始消息-----来自：Shawn Fessenden [mailto：shawnfess@comcast.net]发送时间：2006年4月6日13:39：Simon Parfitt;
'VRF'主题：RE：[vrf]加载错误>我看起来它不在我的系统上!!这真的很奇怪。
我不会发誓，但我认为shell32.dll是那些必要的组件......好吧无论如何它将在system32目录中。
您可能希望扫描注册表以查找问题。-SHAWN- ---您目前订阅了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档案”

您好ShawnI已经尝试过，一旦我重新选择“Microsoft Shell控件和自动化”，我再次收到错误消息。
我看起来好像不在我的系统上!!西蒙-----原帖-----来自：Shawn Fessenden [mailto：shawnfess@comcast.net]发送时间：2006年4月5日17:40转到：VRFS主题：RE：
[vrf]加载时出错>有关它是什么或如何跟踪itInterop程序集的任何想法都是在选择它们时创建的。
它可能只是丢失了dll。
在.vee文件中，您将在开头附近找到它：（assemblyRef（assemblyRef 1（displayName“Shell32，Version = 1.0.0.0”）（libid“{50A7E9B0-70EF-11D1-B75A-00A0C90564FE}”）（desc“
Microsoft Shell控件和自动化“）（文件名”C： WINDOWS  system32  SHELL32.dll“）（verMajor 1）（verMinor 0）（lcid 0）（isPIA 0）（IAFilename”C： Documents and Settings  Shawn
我的文档 VEEPrograms  Cache  Shell32.dll“））这是缺少的IAFilename。进入.NET程序集参考...，单击”COM“选项卡并向下滚动到”Microsoft Shell Controls AndAutomation“，取消选中它并单击
好的。回去，检查一下，点击确定并保存程序。我认为应该清除它.- SHAWN- ---要订阅，请发送电子邮件至：“vrf-request@lists.it.agilent.com”
在邮件正文中单词subscribe。要取消订阅，请发送一封空白电子邮件至“leave-vrf@it.lists.it.agilent.com”。要向此邮件列表发送邮件，请发送电子邮件至“vrf@agilent.com”。
您需要有关邮件列表的帮助，请发送邮件至“owner-vrf@it.lists.it.agil
“在www.oswegosw.com/vrf_archive/上搜索”非官方的vrf档案“。



     以下为原文

  Hi Shawn

I have tried that and as soon as I reselect the "Microsoft Shell Controls And Automation" I  get the error message again. I looks like it is not on my system!!

Simon

-----Original Message-----
From: Shawn Fessenden [mailto:shawnfess@comcast.net]
Sent: 05 April 2006 17:40
To: VRF
Subject: RE: [vrf] Error on loading


> Any ideas on what it is or how to trace it

Interop assemblies are created at the time they are selected. It probably
just lost the dll. In the .vee file you'll find this near the beginning:

(assemblyRefs
(assemblyRef 1
(displayName "Shell32, Version=1.0.0.0")
(libid "{50A7E9B0-70EF-11D1-B75A-00A0C90564FE}")
(desc "Microsoft Shell Controls And Automation")
(filename "C:WINDOWSsystem32SHELL32.dll")
(verMajor 1)
(verMinor 0)
(lcid 0)
(isPIA 0)
(IAFilename
"C:Documents and SettingsShawnMy DocumentsVEE
ProgramsCacheShell32.dll"
))

It's the IAFilename that's missing. Go into .NET Assembly References...,
click the "COM" tab and scroll down to "Microsoft Shell Controls And
Automation", uncheck it and click OK. Go back in, check it, click OK and
save the program. I think that should clear it up.
-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/".

>我看起来它不在我的系统上!!这真的很奇怪。
我不会发誓，但我认为shell32.dll是必要的组件之一...好吧无论如何它将在system32目录中。
您可能希望扫描注册表以查找问题。-SHAWN-



     以下为原文

  > I looks like it is not on my system!!

That's really strange. I wouldn't swear to it, but I think shell32.dll is one of those necessary components... well anyway it would be in the system32 directory. You might want to scan the registry for problems.
-SHAWN-

你好！西蒙，格雷格莱文在这里。
也许你看过我的帖子？
好吧，我看到你在这里发生了什么，Shawn我认为你忘了这个。我会把它归结为一个临时的盲点。基本上它可能很容易成为你运行VEE的用户帐户之一。
它实际上可能需要更多权限来访问它所需的一切。
例如，检查从其磁盘安装VEE 7.51背后的方法，它们描述了一种需要使用“runas”语法调用它的方法。
这听起来很荒谬，但在人们没有自己的特权来安装和管理他们自己的软件的环境中，这些事情往往浮出水面。
--- Gregg C Levine hansolofalcon@worldnet.att.net ---“记住，部队会和你在一起。永远。”
Obi-Wan Kenobi> -----原帖----->来自：Simon Parfitt [mailto：Simon.Parfitt@renesas.com]>发送时间：2006年4月6日星期四上午4:04> To：VRF
>主题：RE：[vrf]加载时出错>> Hi Shawn >>我试过了，一旦我重新选择“Microsoft ShellControls> And Automation”，我再次收到错误消息。
我看起来好像不在我的>系统上!! >> Simon>> -----原帖----->来自：Shawn Fessenden [mailto：shawnfess@comcast.net]>发送时间：2006年4月5日17：
40>收件人：VRF>主题：RE：[vrf]加载时出错>>>>有关它是什么或如何跟踪它的任何想法>> Interop程序集在选择它们时创建。
它可能>刚丢失了dll。
在.vee文件中，你会发现它接近开始：>>（assemblyRef>（assemblyRef 1>（displayName“Shell32，Version = 1.0.0.0”）（libid>“{50A7E9B0-70EF-11D1-B75A-00A0C90564FE}”
）>（desc“Microsoft Shell Controls and Automation”）（文件名>“C： WINDOWS  system32  SHELL32.dll”）>（verMajor 1）>（verMinor 0）>（lcid 0）>（isPIA 0）>（
IAFilename>“C： Documents and Settings  Shawn  My Documents  VEE> Programs  Cache  Shell32.dll”>））>>这是缺少的IAFilename。进入.NET AssemblyReferences ...，>单击“COM”
“选项卡并向下滚动到”Microsoft Shell Controls和> Automation“，取消选中它并单击”确定“。返回，检查它，单击”确定“并>保存程序。我认为应该清除它。> -SHAWN- >> -
- >您目前订阅了vrf：hansolofalcon@worldnet.att.net>要订阅，请发送电子邮件至：“vrf-request@lists.it.agilent.com”，并在邮件正文中使用> subscribe字样。
>要取消订阅，请发送空白电子邮件至“leave-vrf@it.lists.it.agilent.com”。>向此发送消息
邮件列表，请发送电子邮件至“vrf@agilent.com”。>如果您需要有关邮件列表的帮助，请发送邮件至>“owner-vrf@it.lists.it.agilent.com”。>搜索“非官方的vrf档案”
在“www.oswegosw.com/vrf_archive /".---要订阅，请发送电子邮件至：”vrf-request@lists.it.agilent.com“，并在邮件正文中添加”订阅“一词。要取消订阅，请发送空白
发送电子邮件至“leave-vrf@it.lists.it.agilent.com”。要发送邮件到此邮件列表，请发送电子邮件至“vrf@agilent.com”。
如果您需要有关邮件列表的帮助，请发送邮件至“owner-vrf@it.lists.it.agilent.com”。在“www.oswegosw.com/vrf_archive/”上搜索“非官方vrf档案”。



     以下为原文

  Hello!
Simon, Gregg Levine here. Perhaps you've seen my posts? Okay, I see where your going with this, and Shawn I think you forgot this one.
I'll put it down to a temporary blind spot.

Basically it might easily be one of the user account that your running VEE under. It might actually need more privileges to access everything it needs. For example, examine the methods behind installing VEE 7.51 from its disk, they describe a means where you'd need to invoke it using the "runas" syntax. It sounds preposterous, but in an environment where people do not have their own privileges to install and manage their own software, these things tend to surface.
---
Gregg C Levine hansolofalcon@worldnet.att.net
---
"Remember the Force will be with you. Always." Obi-Wan Kenobi

> -----Original Message-----
> From: Simon Parfitt [mailto:Simon.Parfitt@renesas.com]
> Sent: Thursday, April 06, 2006 4:04 AM
> To: VRF
> Subject: RE: [vrf] Error on loading
>
> Hi Shawn
>
> I have tried that and as soon as I reselect the "Microsoft Shell
Controls
> And Automation" I  get the error message again. I looks like it is
not on my
> system!!
>
> Simon
>
> -----Original Message-----
> From: Shawn Fessenden [mailto:shawnfess@comcast.net]
> Sent: 05 April 2006 17:40
> To: VRF
> Subject: RE: [vrf] Error on loading
>
>
> > Any ideas on what it is or how to trace it
>
> Interop assemblies are created at the time they are selected. It
probably
> just lost the dll. In the .vee file you'll find this near the
beginning:
>
> (assemblyRefs
> (assemblyRef 1
> (displayName "Shell32, Version=1.0.0.0") (libid
> "{50A7E9B0-70EF-11D1-B75A-00A0C90564FE}")
> (desc "Microsoft Shell Controls And Automation") (filename
> "C:WINDOWSsystem32SHELL32.dll")
> (verMajor 1)
> (verMinor 0)
> (lcid 0)
> (isPIA 0)
> (IAFilename
> "C:Documents and SettingsShawnMy DocumentsVEE
> ProgramsCacheShell32.dll"
> ))
>
> It's the IAFilename that's missing. Go into .NET Assembly
References...,
> click the "COM" tab and scroll down to "Microsoft Shell Controls And
> Automation", uncheck it and click OK. Go back in, check it, click OK
and
> save the program. I think that should clear it up.
> -SHAWN-
>
> ---
> You are currently subscribed to vrf as:
hansolofalcon@worldnet.att.net
> 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/".

>这种情况发生在每台PC上......嗯，那是假的。
让我看看我是否能弄清楚发生了什么。-SHAWN-



     以下为原文

  > This happenes on every PC!!

Hmm, that's bogus. Let me see if I can figure out what's going on.
-SHAWN-

Shawn和Gregg，我已经看过system32和ii了！
我也一直在这台机器上使用它多年。
这是傻瓜西蒙-----原帖-----来自：Gregg C Levine [mailto：hansolofalcon@worldnet.att.net]发送时间：2006年4月6日13:38致：Simon Parfitt;
'VRF'主题：RE：[vrf]加载错误你好！西蒙，格雷格莱文在这里。
也许你看过我的帖子？
好的，我看到你的地方，Shawn我想你忘记了这个。
我会把它归结为一个临时的盲点。基本上它可能很容易成为你运行VEEunder的用户帐户之一。
它实际上可能需要更多权限来访问它所需的一切。例如，检查从其磁盘安装VEE 7.51背后的方法，它们描述了一种需要使用“runas”语法调用它的方法。
这听起来很荒谬，但在人们没有自己的特权安装和管理他们自己的软件的环境中，这些事情往往浮出水面。
--- Gregg C Levine hansolofalcon@worldnet.att.net ---“记住，部队会和你在一起。永远。”
Obi-Wan Kenobi> -----原帖----->来自：Simon Parfitt [mailto：Simon.Parfitt@renesas.com]>发送时间：2006年4月6日星期四上午4:04> To：VRF
>主题：RE：[vrf]加载时出错>> Hi Shawn >>我试过了，一旦我重新选择“Microsoft ShellControls> And Automation”，我再次收到错误消息。
我看起来好像不在我的>系统上!! >> Simon>> -----原帖----->来自：Shawn Fessenden [mailto：shawnfess@comcast.net]>发送时间：2006年4月5日17：
40>收件人：VRF>主题：RE：[vrf]加载时出错>>>>有关它是什么或如何跟踪它的任何想法>> Interop程序集在选择它们时创建。
它可能>刚丢失了dll。
在.vee文件中，你会发现它接近开始：>>（assemblyRef>（assemblyRef 1>（displayName“Shell32，Version = 1.0.0.0”）>（libid“{50A7E9B0-70EF-11D1-B75A-00A0C90564FE}”
）>（desc“Microsoft Shell Controls and Automation”）>（文件名“C： WINDOWS  system32  SHELL32.dll”）>（verMajor 1）>（verMinor 0）>（lcid 0）>（isPIA 0）>（
IAFilename>“C： Documents and Settings  Shawn  My Documents  VEE> Programs  Cache  Shell32.dll”>））>>这是缺少的IAFilename。进入.NET AssemblyReferences ...，>单击“COM”
“选项卡并向下滚动到”Microsoft Shell Controls和> Automation“，取消选中它并单击”确定“。返回，检查它，单击”确定“并>保存程序。我认为应该清除它。> -SHAWN- >> -
- >您目前订阅了vrf：hansolofalcon@worldnet.att.net>要订阅，请发送电子邮件至：“vrf-request@lists.it.agilent.com”，并在邮件正文中使用> subscribe字样。
>要取消订阅，请发送一封空白电子邮件至“leave-vrf@it.lists.it.agilent.com”。>向此发送消息
iling list，电邮“vrf@agilent.com”。
如果>您需要有关邮件列表的帮助，请发送邮件至>“owner-vrf@it.lists.it.agilent.com”。>在“www.oswegosw.com/vrf_archive/”上搜索“非官方vrf档案”。
---要订阅，请发送电子邮件至：“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档案”。



     以下为原文

  Shawn and Gregg,

I have looked in system32 and ii's there! Also I have been using it on this machine for years. This is getting silly

Simon

-----Original Message-----
From: Gregg C Levine [mailto:hansolofalcon@worldnet.att.net]
Sent: 06 April 2006 13:38
To: Simon Parfitt; 'VRF'
Subject: RE: [vrf] Error on loading


Hello!
Simon, Gregg Levine here. Perhaps you've seen my posts? Okay, I see where
your going with this, and Shawn I think you forgot this one. I'll put it
down to a temporary blind spot.

Basically it might easily be one of the user account that your running VEE
under. It might actually need more privileges to access everything it needs.
For example, examine the methods behind installing VEE 7.51 from its disk,
they describe a means where you'd need to invoke it using the "runas"
syntax. It sounds preposterous, but in an environment where people do not
have their own privileges to install and manage their own software, these
things tend to surface.
---
Gregg C Levine hansolofalcon@worldnet.att.net
---
"Remember the Force will be with you. Always." Obi-Wan Kenobi

> -----Original Message-----
> From: Simon Parfitt [mailto:Simon.Parfitt@renesas.com]
> Sent: Thursday, April 06, 2006 4:04 AM
> To: VRF
> Subject: RE: [vrf] Error on loading
>
> Hi Shawn
>
> I have tried that and as soon as I reselect the "Microsoft Shell
Controls
> And Automation" I  get the error message again. I looks like it is
not on my
> system!!
>
> Simon
>
> -----Original Message-----
> From: Shawn Fessenden [mailto:shawnfess@comcast.net]
> Sent: 05 April 2006 17:40
> To: VRF
> Subject: RE: [vrf] Error on loading
>
>
> > Any ideas on what it is or how to trace it
>
> Interop assemblies are created at the time they are selected. It
probably
> just lost the dll. In the .vee file you'll find this near the
beginning:
>
> (assemblyRefs
> (assemblyRef 1
> (displayName "Shell32, Version=1.0.0.0")
> (libid "{50A7E9B0-70EF-11D1-B75A-00A0C90564FE}")
> (desc "Microsoft Shell Controls And Automation")
> (filename "C:WINDOWSsystem32SHELL32.dll")
> (verMajor 1)
> (verMinor 0)
> (lcid 0)
> (isPIA 0)
> (IAFilename
> "C:Documents and SettingsShawnMy DocumentsVEE
> ProgramsCacheShell32.dll"
> ))
>
> It's the IAFilename that's missing. Go into .NET Assembly
References...,
> click the "COM" tab and scroll down to "Microsoft Shell Controls And
> Automation", uncheck it and click OK. Go back in, check it, click OK
and
> save the program. I think that should clear it up.
> -SHAWN-
>
> ---
> You are currently subscribed to vrf as:
hansolofalcon@worldnet.att.net
> 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/".

嗨再次更多信息这发生在每台PC上!!西蒙-----原始消息-----来自：Shawn Fessenden [mailto：shawnfess@comcast.net]发送时间：2006年4月6日13:39：Simon Parfitt;
'VRF'主题：RE：[vrf]加载错误>我看起来它不在我的系统上!!这真的很奇怪。
我不会发誓，但我认为shell32.dll是那些必要的组件......好吧无论如何它将在system32目录中。
您可能希望扫描注册表以查找问题。-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档案”。



     以下为原文

  Hi again

More information

This happenes on every PC!!

Simon

-----Original Message-----
From: Shawn Fessenden [mailto:shawnfess@comcast.net]
Sent: 06 April 2006 13:39
To: Simon Parfitt; 'VRF'
Subject: RE: [vrf] Error on loading


> I looks like it is not on my system!!

That's really strange. I wouldn't swear to it, but I think shell32.dll is
one of those necessary components... well anyway it would be in the system32
directory. You might want to scan the registry for problems.
-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/".

>这变得愚蠢我们会到达那里。
在整个硬盘驱动器中搜索shell32.dll。
您应该找到至少两个：一个在system32中，另一个在一个名为Cache的目录中（这将是COM Interop创建VEE导入的程序集）.- SHAWN-



     以下为原文

  > This is getting silly

We'll get there. Search your entire hard drive for shell32.dll. You should find at least two: one in system32 and one in a directory called Cache (that will be the assembly COM Interop creates that VEE imports).
-SHAWN-

您好Vee专家，我刚刚得到Vee 7.51而我正在尝试编写一个“驱动程序”以获得8到10个热电偶温度，例如来自HP34970a的1秒扫描，这是一个多通道录音机，我想你可以打电话
它。当然我可以从一次温度开始。
我的想法是，任何人都会连接的最常见的设备是HP34970a，但这只是一个猜测。到目前为止，我只有一个RS232连接到设备。
我想我需要使用Direct I / O与它交谈。
我有设备的编程书，并试图发送“* IDN？”
还是“IDN？”
到设备，看看我是否能得到回报。
我收到了一堆语法错误/等等。
只需进入第一个写行。
它确实看起来像Vee看到设备在＃1 RS232端口的末端。它看起来像一个面板驱动程序只能用于我有一个我没有的HPIB连接，并且无法弄清楚VXIplug和
玩.....所以我要尝试直接的I / O方法。任何帮助appriciated。
抱歉newbee跑来跑去。
也许有一个文件或旧电子邮件，有人可以发送给我帮助。非常感谢.-亨利---要订阅，请发送电子邮件至：“vrf-request@lists.it.agilent.com”与
单词订阅在邮件正文中。要取消订阅，请发送一封空白电子邮件至“leave-vrf@it.lists.it.agilent.com”。要向此邮件列表发送邮件，请发送电子邮件至“vrf@agilent.com”。
如果您需要有关邮件列表的帮助，请发送邮件至“owner-vrf@it.lists.it.agilent.com”。在“www.oswegosw.com/vrf_archive/”上搜索“非官方vrf档案”。

嗨Shawn我有三个副本的C：windowssystem32C：windowssevicepackfilesi386C：windowslastgoodsystem32simon -----原始消息-----来自：Shawn Fessenden [mailto：shawnfess@comcast.net]发送时间：2006年4月6日18:22：Simon Parfitt
;
'VRF'主题：RE：[vrf]加载错误>这很傻我们会到达那里。
在整个硬盘驱动器中搜索shell32.dll。
你应该找到至少两个：一个在system32中，一个在一个名为Cache的目录中（这将是COM Interop创建VEE导入的程序集）.- SHAWN- ---您目前订阅的是vrf：r***@soco.agilent.comTo
订阅请发送电子邮件至：“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档案”。