Might not be related, but this is from the readme file... they changed the meaning of DEL which might have an impact on BS (?) ...that might make sense on a destructive backspace, but... I don't really recall. I wouldn't expect vt100 to have anything to do with this, but it seems you're not sure if your vt100 command is even working? ------------------------------------------------------------------------------ -------------------------------------------- The default code transmitted by the DELETE key in Wyse 50, Wyse 60 and Viewpoint A2 Enhanced mode was changed in AccuTerm 2000 to match the true Wyse terminal using a PC keyboard. The original Wyse keyboard (the one with 16 function keys) has two DEL keys: DEL Char/Line and DEL. The PC keyboard has only one DEL key. AccuTerm 97 programmed the DEL key to send the DEL control code (Char(127)) by default; the real Wyse terminal sends ESC:'W" or ESC:'l' instead, which is what the DEL Char/Line key would send. One of the main reasons for doing this is that System Builder resets all the keys to their default values all the time, and expects the DEL key to act like DEL Char/Line so no matter how you program the DEL key in AccuTerm, System Builder resets it and it doesnt work. Now, System Builder should work with the DEL key, but other apps may not. But, you can program the DEL key to send the DEL control code by programing ^? in the key. ------------------------------------------------------------------------------ ----------------------------------------- Ron In a message dated 9/1/2004 11:31:30 PM Eastern Daylight Time, [EMAIL PROTECTED] writes:
I've been having a heck of a time at ECL on Unidata PE 6.0 with AccuTerm 2k2 - all over WinXP Pro. I'm not sure of which terminal emulation is best, or even how to check/set the term type in Unidata. "term vt100" doesn't return a confirmation and "term" just returns "A,B,C,D" help with nothing about term type. Are there any other settings in AccuTerm that should or should not be set for best results? Gosh I hope this isn't a case of reading friendly manuals cuz I think I've been through them. The problem seems to be that a backspace "looks" like a backspace, but it seems to leave some character embedded in the entered string, so what is seen on the screen is not what is being processed by the system, and I get lots of "syntax error"s. I get a lot of these errors even if I enter a command perfectly. Sometimes just doing a .x will return a good execution, othertimes a copy/paste of what's on the screen works - sometimes not... Thanks much! Tony Nebula R&D ------- u2-users mailing list [EMAIL PROTECTED] To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list [EMAIL PROTECTED] To unsubscribe please visit http://listserver.u2ug.org/
