>>>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?
>>
>>
>>It does get through to the terminal, like you said, it's just that the characters are printed. In this particular application, that should refresh the screen. I've sent it binary to, using VFP's createbinary() function, but I get the same result. This is a tough one!
>>John
>
>Can you monitor what data is actually being sent - I used to have a small DOS utility, which ran on a 2nd PC, placed between the two communicating devices - using 2 comms ports - it would display the hex codes of the data going in each direction.
>
>Maybe theres some extra data being sent prior to you command sequence, which is stopping the sequence being recognised.

Hi Len,

Yeah, I thought that might be the case. I tried a crossover from COM1: to COM2: and ran 2 instances of Procomm. Also took a single port over to an Epson LQ-850 in Hex Dump mode. In all cases, all I see is hex(01 41 0D) for his F2 sequence. All function keys in Wyse-50 emulation exhibit the exact same behavior in Procomm. I am beginning to think these default function keys are meant to be terminal to host only, not to drive the terminal.