Author Topic: Is it a problem with drivers.....  (Read 3685 times)


  • Frequent Contributor
  • ****
  • Posts: 141
Is it a problem with drivers.....
« on: September 23, 2010, 05:26:09 am »
Hi All,

I have an interesting issue some code generates the following error:

_COMPlusExceptionCode = 0xe0434f4d

This was due to code being shipped and coming back with a mod needed some of the Hardware was different meaning few changes are needed to get it working I made the changes and recompiled and bang! A quick google/internet search somebody got this type of error from a DateTimeValue being wrong.  So from this I'm guessing that its a grown up version of the Turbo (Borland) C(++) Lvalue or casting type error. The worst thing is the code 'worked' before it was modded by the customer it came for an extra feature to be added.
Anybody any ideas I'm posting here as it is Serial Comms that has brought up this error.  I'm assuming it caused by the seperate threads being used because a single threaded version works so are there any issues with accessing com ports from the UI string if they are created on in a different string.

(Heavy I know but....)