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
Good info, thanks Colin and others. I don't see a clear solution at the
moment but I'll keep looking. I have to believe "someone" is using AccuTerm
with Unidata. :) Suggestions still welcome.
Thanks and Regards,
Tony
Alfke, Colin wrote:
> I don't use Accuterm but if you check in the udthome/
lin
>Sent: Friday, 3 September 2004 12:19 AM
>To: [EMAIL PROTECTED]
>Subject: RE: [U2] Unidata with AccuTerm?
>
>I don't use Accuterm but if you check in the udthome/include directory
>there is a file udtermcap that has the terminal definitions. TERM will
>accept the term
I don't use Accuterm but if you check in the udthome/include directory there is a file
udtermcap that has the terminal definitions. TERM will accept the terminal definition
(see HELP TERM) but you're right - it won't display confirmation or denial. Perhaps
checking this file will help you config
> Date: Wed, 1 Sep 2004 20:10:16 -0700
> From: "Tony Gravagno" <[EMAIL PROTECTED]>
> Are there any other settings in AccuTerm that should or should
> not be set for best results?
Can't speak specifically for your situation, but...
I use AccuTerm 97 with SystemBuilder 5.2.4 and UniData 5.2 on AIX
I'm no Wintegrate person, so I can't say what's happening there, but I
have seen terminal types send an ASCII 127 (DEL) for a BS. To the
terminal it looks perfectly normal but to the command interpreter it's
totally whacked. What does PTERM -DISPLAY show?
-Original Message-
From: [EMAIL
