>Very simple, isn't it? I cobbled together an interface yesterday so I could >peek at the wire with a logic analyzer. In all cases, FPD, VFP6, Procomm for >DOS and Windows, put hex 01 41 0D on the wire. In VFP's case, using MSCOMM32, >is the DEC returning screen info or a response code or something that you >might be missing on the return side? What are the non default settings of the >control? What are you doing with the DEC response?

Yes, very simple (just a test right now). I'm just taking the data out of the Input property (data returned from DEC) of the MSCOMM32 and stuffing it into an editbox. This displays everything correctly up until the F2. It returns no refreshed screen info, just shows that the control characters were printed to the screen. It's really weird that it works with the low level file functions. MSCOMM32 must be sending something else down the wire with it. I'm going to try playing around a little bit with some other emulator commands (locking the keyboard, putting it into and out of Protected mode, and Block mode) in tandem with these commands and see if that does anything for me. I'll keep you posted if anything works. Thanks for all the help, it is very appreciated!
John