
MovieMaker
USA
Asked
— Edited
It may be me. But I cannot create a shortcut
I tried on two computers, but it did not work. It was a GREAT idea to have.
Thanks for all of your hard work.
Mel
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.IO.FileNotFoundException: Could not load file or assembly 'Interop.IWshRuntimeLibrary, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The system cannot find the file specified.
File name: 'Interop.IWshRuntimeLibrary, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null'
at EZ_Load_Creator.FormMain. (Object , EventArgs )
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
EZ-Builder
Assembly Version: 2012.8.19.0
Win32 Version: 2012.08.19.00
CodeBase: file:///C:/Program%20Files%20(x86)/EZ-Robot/ARC.20Installer/ARC.exe
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
EZ_B
Assembly Version: 2012.8.19.0
Win32 Version: 2012.08.19.00
CodeBase: file:///C:/Program%20Files%20(x86)/EZ-Robot/ARC.20Installer/EZ_B.DLL
----------------------------------------
System.Configuration
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Xml
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System.Speech
Assembly Version: 3.0.0.0
Win32 Version: 3.0.6920.1109 (lh_tools_devdiv_wpf.071009-1109)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Speech/3.0.0.0__31bf3856ad364e35/System.Speech.dll
----------------------------------------
Microsoft.DirectX.DirectInput
Assembly Version: 1.0.2902.0
Win32 Version: 5.04.00.2904
CodeBase: file:///C:/Program%20Files%20(x86)/EZ-Robot/ARC.20Installer/Microsoft.DirectX.DirectInput.DLL
----------------------------------------
WindowsBase
Assembly Version: 3.0.0.0
Win32 Version: 3.0.6920.5011 built by: Win7SP1
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/WindowsBase/3.0.0.0__31bf3856ad364e35/WindowsBase.dll
----------------------------------------
Microsoft.DirectX
Assembly Version: 1.0.2902.0
Win32 Version: 5.04.00.2904
CodeBase: file:///C:/Program%20Files%20(x86)/EZ-Robot/ARC.20Installer/Microsoft.DirectX.DLL
----------------------------------------
ugrxyfne
Assembly Version: 2012.8.19.0
Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.
For example:
When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.
It craps out with an error and then locks open the .EZB file so
I have to re-name and save my file as something else.
I created an autoconnect script that called init.
then I right clicked and sent the shortcut to the desktop.
then, I dragged the shortcut to the start bar.
then I dragged the shortcut to the Start-up folder.
Now, when i turn on the computer and EZB, the robot starts and initializes and waits for verbal commands.
Oh, i had to place connect Robot please
and disconnect robot, please to the speech recognition script.
Look at the auto connect script under examples.
I finally have my basic finished robot and she works good. I just don't have a suitable place to operate her because I have no room in my apartment.
yeh!
I'll do some screen captures tonight.
I have seen this with some of my apps and its usually been the above or registry permissions set on the reg hive do not allow the installer service to write to them.
If anyone is really interested in seeing what happens during the installation and where the failure occurs you can enable MSI (windows installer ) logging and look through the logs for failure or fail
Trevor
I just tried it today for the first time but am unable to click on the final button "Create Shortcut" as it is grayed out.
Clicking the other button crashes something
Even though all the folder and file options defaulted to the correct choices, If I manually select them anyhow, then it works...
So, not quite right, but workable
Now something that may or may not affect the situation is that I have redirected my user folders to my D: drive (thus this is what I see, but still must select the same file manually)...
Not sure if that would have any affect or not on how the shortcut program looks at things? Hope this info helps.