AraMix, do you have a USB to serial adapter cable you can plug in? Curious if adding a new COM port at least resolves the startup crash...

DJ, I was concerned about the unmanaged interop calls when I first stepped through some of the EZ-B SDK functions. Have you considered replacing the DirectX calls using the SlimDX framework? Shouldn't be too difficult and would do a lot to bring the code up to current standards. I'd be happy to help any way I can despite my general disdain for programming...

Okay I built a new release of ARC with a new connection routine and initialization routine. I am wondering if my threaded model might have had a conflicting init in the designer. Try the new download and see if it works for you

radmeck, I don't have any (( but I have at least two virtual com ports active..

DJ, hell yeah.. that worked.. but the drop-down list is still unpopulated

also sample projects are crashing when I try to run them, since you said the builder and sdk use the same EZ.dll, maybe the problem is there???

The sample projects in the SDK are crashing? Do they give an error when executing, or is it a compile error?

(i have not released a new SDK because there haven't been significant changes to it that requires a release yet. ARC has been where the changes are lately.

If the list is unpopulated, I wonder why! Hmmmmmm.. I'm using the buggy SerialPort.GetPortNames() method. It has given me lots of grief over time. I've used a few options to not use the method (such as collecting the com ports by the registry directly), but even the registry has the names registered incorrectly.

One of the issues is unterminated strings for the com port names in the registry. So occasionally the registry will return strange characters at the end of a com port name. (i.e. COM31 or COM3i instead of COM3)

I was doing a presentation the other day with ARC at the computer history museum and Windows kept messing up with that issue. The only way around it was to delete the Bluetooth Device, reboot and Re-Add. It was embarassing but a problem that is out of my control

The only other option I can possibly think of is hardcoding the listbox with COM Port names. But that's not very nice ... I just wish Microsoft would fix their reported bugs!

yeah they crash.. I have attached the screenshot.. and no.. no errors during the building operation and running.. however I get some warnings and maybe this one will be interesting for you

================================================================== Warning 25 Referenced assembly 'C:UsersOwnerDesktopEZ-B Win32 v2011.05.09.00DLLEZ_B.dll' targets a different processor than the application. Tutorial 12 - Speech Recognition

I'm using Sony Vaio VPCEB36GM with Intel i5 processor...

and here is the content of the error that occurs:

and in the project "Tutorial 14 - HC-SR04 Ping Sensor" when I double click on Form1.cs a page with this error opens:

I can skip this, but sure the program won't work as far as the variable 'uC_EZ_Connect1' is never assigned. Even if I skip it and try to run the program it crashes, and the content of the eror is the same as for the project "Tutorial 12 - Speech Recognition"...

why am I so unlucky... tired btw, I am participating in a competition here in Armenia, called ArmRobotics that takes place every year, and our objective is to make a minesweeper robot.. so as far as I don't have any practice in hardware programming using assembler I decided to use your EZ-B, cause it's really awesome anyway.. thanks for the wonderful support and hopefully everything will be fixed soon and be alright

AraMix, let's start with resolving your missing References:

In Visual Studio, expand the project's References folder and Right-click/Remove the ones with exclamation points: Fadd.dll, HttpServer.dll & xunit.dll.

Open Windows Explorer and copy those three DLLs from one of the other SDK project's Resources folder into the current project's Resources folder.

Back in Visual Studio, Right-click/Add Reference... on the References folder and add the three DLLs using the Browse tab. Save/Rebuild and see where we're at...

DJ, I noticed the need to manually add those three references for several of the SDK projects for the last few releases...

On some installations of windows, you may need to choose 32 or 64 bit binaries.

There is a disclaimer in the TXT file for the SDK that the references will be broken in the examples. That is because the DLL location is different per installation folder. You will have to add the reference per project yourself.

But, stupid me might have included the fadd, http and xunit accidently in some of the projects. Oooopsie I'll remove those