 |
|
|
Topic: Input Failure
|
By: Gerry | Posted on: Jul 31 2011 at 09:14:07 PM | I have a VB6 app that I have been successfully using for some years employing the comm32 control. I run a very simple serial comm program that sends a 4 digit Output and then returns a 260 byte transmission. The protocol I use is common to three different models of a sound analyzer I work with. Recently, it stopped working with one of the devices but not the others.
I have reproduced this problem with four different units so its not a unit malfunction. The analyzer signals receipt of the output code and signals that it has sent the reply but there is no data received at the port. I used a sniffer to verify that.
The other two models of the analyzer work perfectly with the same VB6 app and the same protocol. I am totally stumped and this is turning into a major problem.
I'm glad to share the code but I don't beleive this is a code issue. I'm guessing its a Windows issue because a colleage tested the app on a Mac notebook using a Windows emulator and it worked fine. By the way, the problem occurs on an XP and a W7 machine.
Has there been a recent Windows Security update that would explain the sudden failure of a long working app?
Thanks much!
| |
By: Support | Posted on: Jul 31 2011 at 10:38:16 PM | Are you sure that you are using our comm32.OCX?
You said you've been using it for a few yes. our OCX was released around feb 2010.
Maybe you're using MSComm32 ?
But to answer you question. no we've tested our ocx against all Microsoft OS updates without any problems. | |
|