AWSOME!! Thanks again DJ. Keep up the amazing work!

Will

DJ, I've tried creating a shortcut with your new feature (tried Windows 7 and XP) with no success. At the last step when I click "create shortcut" it gives the following error message.

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.

What am I doing wrong?

If it helps to figure out the problem... I click "continue" at the error message and close the ARC file, then search on my computer for latest modified files, I find the shortcut has been created in C:\Users\Robo\AppData\Roaming\Microsoft\Windows. When I click on it, it opens my ARC file but does not auto-execute the robot program I selected earlier in the shortcut wizard.

Thanks for your help.

I'm unsure what that error could mean. Very strange - i'll look and see. I mean, i do understand what it is saying, but why would you get it? The file should be included with the .Net framework. Maybe your computer needs a reboot?

hey DJ Sures what is new with the ARC 8-14 everything is the same confused stress tired mad mad

also you say that your ez-sdk is in c++but it is only in vb & c# mad

@hamada, no more entire pages of repeated phrases or images.

@hamada, the SDK is COM enabled for C++. If you are familiar with C++ programming in Windows, you'll be able to use the DLL. There are plenty of resources to help you on the internet and through MSDN.

@hamada, sometimes there are new releases with small fixes or optimized code - neither of these are worth mentioning as a major release.

Thanks DJ, We've tried it on three laptops and a mini ITX board with the same results. I am going to reload one of the laptops. Should I be running in 32 bit or 64 bit mode, does it matter?

It shouldn't matter which bit CPU. The software is forced to 32 bit for speed. I haven't had any other reports of that issue. Difficult to diagnose

Seems to work fine for me.

What version of .NET Framework are you guys running? Also having an issue with the shortcut creation. Going to try and Uninstall ARC and .NET Framework. Then install .NET Framework and ARC. My system is pretty barebones built it to be dedicated so the problem seems to be a missing peice of software.

Did the above ran all the updates for .NET and still no luck. Do you guys have visual studio installed? Thats the only thing left I can think of that is missing

I don't have visual studio installed. But, the update is running fine.

Our testing machines do not have visual studio.

Are you windows 7 or xp? 64 or 32? Latest .Net framework?

OK, So here is what I have done.

I have installed a clean copy of Windows 7 Enterprise 64 Installed needed drivers Ran Windows update until none were left to find Rebooted Ran Update check to make sure no updates were available Downloaded and Installed .NET Framework 4 Rebooted Ran Updates again till none left Rebooted Checked for updates again to make sure none were available Downloaded ARC 2012.08.14.00 and installed it Went to C:\Program Files (x86)\EZ-Robot\ARC Installer and set compatilbility to run as administrator for all users Rebooted Launched ARC built a test project with 2 servos and saved the project Tried to create shortcut using the shortcut creator under the file menu

It did not work and I received the error below, I also did the same thing as above using windows 7 Enterprise 32. I have also tried it on my main desktop running Win 7 Ent 64 that stays fully updated and is also running the visual studio 2010 same error.

Is there a way that I can just create my own shortcut using switches, or possible a .cmd or .bat file?

Mainly just need to know the switches if there are any.

See the end of this message for details on invoking just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text ************** System.BadImageFormatException: Could not load file or assembly 'Interop.IWshRuntimeLibrary, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The module was expected to contain an assembly manifest. 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.5456 (Win7SP1GDR.050727-5400) CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll

EZ-Builder Assembly Version: 2012.8.14.0 Win32 Version: 2012.08.14.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.5460 (Win7SP1GDR.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.5456 (Win7SP1GDR.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.5462 (Win7SP1GDR.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.14.0 Win32 Version: 2012.08.14.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:/Windows/assembly/GAC/Microsoft.DirectX.DirectInput/1.0.2902.0__31bf3856ad364e35/Microsoft.DirectX.DirectInput.dll

WindowsBase Assembly Version: 3.0.0.0 Win32 Version: 3.0.6920.5448 built by: Win7SP1GDR 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:/Windows/assembly/GAC/Microsoft.DirectX/1.0.2902.0__31bf3856ad364e35/Microsoft.DirectX.dll

2uesq9w5 Assembly Version: 2012.8.14.0 Win32 Version: 2.0.50727.5456 (Win7SP1GDR.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.