Perhaps there are some Flexers out there who can take Phil's vCOM
source
code, set things up to cause the problem to happen, and debug it. (No,
not you, Bob.) But if this is a community, and the source is open, it
seems like there ought to be a better solution than spend another
$100
when the
I have a feeling that it may be some subtle difference with the way
vCOM handles the lines like RTS/CTS and DSR/DTR that may be causing
problems with certain third party applications. Or it may be that the
serial port access code in PowerSDR (which I wrote) is expecting some
timing of those
At 08:10 AM 8/18/2007, Peter G. Viscarola wrote:
I have a feeling that it may be some subtle difference with the way
vCOM handles the lines like RTS/CTS and DSR/DTR that may be causing
problems with certain third party applications. Or it may be that the
serial port access code in PowerSDR
At 07:43 AM 8/18/2007, Philip Covington wrote:
On 8/18/07, Jim Lux [EMAIL PROTECTED] wrote:
There's sort of a fundamental problem here in that what's needed is a
way to interconnect two programs which expect a legacy interface, and
were never intended to talk directly to each other. Think
Perhaps there are some Flexers out there who can take Phil's vCOM source
code, set things up to cause the problem to happen, and debug it. (No,
not you, Bob.) But if this is a community, and the source is open, it
seems like there ought to be a better solution than spend another $100
when the
5 matches
Mail list logo
