>>Hi John,
>>
>>Sorry to barge in, but your problem interested me. I set up a Link MC-5 here running Wyse 50 emulation to check. I dropped it into monitor mode and it looks like your sequence gets through OK but is somehow 'misinterpreted'? I get a SOH A CR like you want but an 'A' appears in normal mode. Are you running other than straight Wyse 50 mode, some other emulation perhaps?
>
>Jim,
>Barge in, barge in!!! We have some old Telex terminal hooked up to an even older DEC machine. I've been able to determine thus far that it can handle wyse50, wyse50+, and wyse60 emulation, but unless you specify, wyse50 is default. I've tried the same character sequence under all 3 emulation types (it is the same string for all 3), but to no avail. The real bummer here is that the wyse50 +F16 (which, by the way, is CHR( 1 ) + CHR( 111 ) + CHR( 13 )) works just fine. This has become a vendetta. I will figure it out, no matter how long it takes. I will send you more info as it becomes available, but don't expect much soon. If you have any info you can share with me on this, I will trade you years off my life for it. Thanks Jim,
>John

Well, I have no good news. I tried Hyperterminal and Procomm (Both DOS and Windows) and they all react exactly the same. Seems like the problem is elsewhere other than the MScomm32.ocx. Putting the terminal in Monitor Mode (CTRL 1 and ESC U) and I see your command by the book. Why the terminal doesn't respond properly is beyond me. All I have at hand is a "Quick Reference Guide" to the MC-5. Gives all the codes but doesn't expound any. What should this command really do for you?