Telnet Interface big problem

[Jorge_Beteta]

Hello,
I've got a terrible problem with Telnet Interface. I have an SCO
Unix 5.0.5 as server and clients Windows PC who access it via Telnet.
There's an old system running on the SCO Unix. The system was
developed in Business Basic, an old programming language which is
running just on console mode, not GUI. When I access that system via
Telnet from a Windows PC, the system interface appears to be
completely untidy on my Windows PC:

SCO OpenServer(TM) Release 5 (scosysv.my_domain_name) (ttyp0)

login: root
Password:
Last successful login for root: Sat Aug 02 12:00:08 2003 on ttyp0
Last unsuccessful login for root: Sat Aug 02 11:32:04 2003 on tty01

SCO OpenServer(TM) Release 5

(C) 1976-1998 The Santa Cruz Operation, Inc.
(C) 1980-1994 Microsoft Corporation
All rights reserved.

For complete copyright credits,
enter "copyrights" at the command prompt.
TERM = (ansi)
Terminal type is ansi
# cd u
# cd bbx2
# ./bbx2

READY

>RUN "MAIN"

2S
2°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°° °°°°°°°°°°°°°°°°°°°°°°°°°°°°°°
°2ACME COMPANY2
ððððððððððððððððððððððððððððððððððððððððððððððððð ððððððð2MAIN MENU2
ððððððððððððððððððððððððððððððððððððððððððððððððð ððððððð2

ðððððððððððððððððððððððððððððððððððððððððððððððððð ðððððð2
ðððððððððððððððððððððððððððððððððððððððððððððððððð ðððððð2
2,0032K
2,003
BOXÿÿ
ÿ
ÿ9ÿ
2< Time : 12:17 PM
2°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°° °°°°°°°°°°°°°°°°°°°°°°°°°°°°°°
°°2DATE: 03/08/20032°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°° °°°°°°°°°°°
°°°°°°°°°°°°°°°°°°°°°°°°°
2[1] QUERY OF CUSTOMERS / TOTAL SALES
2[2] QUERY OF CHECKS 1992-2003
[3] QUERY OF INCOMES HR-PU-PR
2 [4] QUERY OF LICENCES
-> OUTPUT OF FORMATS
2 ENTER YOUR CHOISE:

<End of Screen>

It seems that the columns on the Telnet interface are fewer than the
columns on the Unix screen, and that's why it seems a mess.
What can I do to fix the problem?

I have configured the Telnet interface on Windows in this way:
Main Menu -> Terminal -> Preferences:
+----------------------------------------------+
¦ Terminal Options Emulacion ¦
¦ [ ] Local Echo [ ] VT-52 ¦
¦ [x] Blinky Cursor [x] VT-100/ANSI ¦
¦ [x] Fixed Cursor ¦
¦ [x] VT100 Arrows ¦
¦ ¦
¦ Buffer Size: [50] ¦
+----------------------------------------------+

Fonts:
+----------------------------------------------+
¦ Fonts Font Style Size ¦
¦ Terminal Normal 6 ¦
¦ ¦
¦ ¦
¦ Alphabet ¦
¦ OEM/DOS ¦
+----------------------------------------------+

[Bill Campbell]

On Sat, Aug 02, 2003 at 09:24:41PM -0400, Gary L. Burnore wrote:

>On 2 Aug 2003 18:14:09 -0700, [email]jbeteta@yahoo.com[/email] (Jorge_Beteta) wrote:

....

>
>basic probably can't understand SCO's ansi. Try just plain VT100
>(turn off VT100/ANSI>

More basic problem, the Microsoft telnet sucks rocks. Get a decent
terminal emulation program such as Anzio, teraterm putty, etc. that does a
proper SCO ansi or other emulation.

Bill
--
INTERNET: [email]bill@Celestial.COM[/email] Bill Campbell; Celestial Software LLC
UUCP: camco!bill PO Box 820; 6641 E. Mercer Way
FAX: (206) 232-9186 Mercer Island, WA 98040-0820; (206) 236-1676
URL: [url]http://www.celestial.com/[/url]

Marijuana will be legal some day, because the many law students
who now smoke pot will someday become congressmen and legalize
it in order to protect themselves.
-- Lenny Bruce

[tony@aplawrence.com]

Bill Vermillion <bv@wjv.comremove> wrote:

>>>
>>>More basic problem, the Microsoft telnet sucks rocks. Get a decent
>>>terminal emulation program such as Anzio, teraterm putty, etc. that does a
>>>proper SCO ansi or other emulation.

>>Even with a decent telnet, Business Basic is brain damaged. ALthough
>>you're right about MS's alleged telnet client.

>Maybe it should be charged with 'identity theft'.

I have long suspected that this is quite purposeful. What else would
would Windows use telnet for than to go to Unix? Crappy client
makes Unix even more horrible for the Windows user, thus reinforcing
their prejudice.

--
[email]tony@aplawrence.com[/email] Unix/Linux/Mac OS X resources: [url]http://aplawrence.com[/url]
Get paid for writing about tech: [url]http://aplawrence.com/publish.html[/url]

[Ronald J Marchand]

"Jorge_Beteta" <jbeteta@yahoo.com> wrote in message
news:5140b91e.0308021714.5aecfc63@posting.google.c om...

> Hello,
> I've got a terrible problem with Telnet Interface. I have an SCO
> Unix 5.0.5 as server and clients Windows PC who access it via Telnet.
> There's an old system running on the SCO Unix. The system was
> developed in Business Basic, an old programming language which is
> running just on console mode, not GUI. When I access that system via
> Telnet from a Windows PC, the system interface appears to be
> completely untidy on my Windows PC:
>
> SCO OpenServer(TM) Release 5 (scosysv.my_domain_name) (ttyp0)
>
> login: root
> Password:
> Last successful login for root: Sat Aug 02 12:00:08 2003 on ttyp0
> Last unsuccessful login for root: Sat Aug 02 11:32:04 2003 on tty01
>
> SCO OpenServer(TM) Release 5
>
> (C) 1976-1998 The Santa Cruz Operation, Inc.
> (C) 1980-1994 Microsoft Corporation
> All rights reserved.
>
> For complete copyright credits,
> enter "copyrights" at the command prompt.
> TERM = (ansi)
> Terminal type is ansi
> # cd u
> # cd bbx2
> # ./bbx2
>

Very old version of bbx; but, your config.bbx file probably doesn't know who
your tty is. tty when you log in and then check for that terminal in the
alias list in config.bbx -- or whatever name they chose for the
configuration file.

Ron

[Dan Martin]

[email]jbeteta@yahoo.com[/email] (Jorge_Beteta) wrote in message news:<5140b91e.0308021714.5aecfc63@posting.google. com>...

> Hello,
> I've got a terrible problem with Telnet Interface. I have an SCO
> Unix 5.0.5 as server and clients Windows PC who access it via Telnet.
> There's an old system running on the SCO Unix. The system was
> developed in Business Basic, an old programming language which is
> running just on console mode, not GUI. When I access that system via
> Telnet from a Windows PC, the system interface appears to be
> completely untidy on my Windows PC:
>
> SCO OpenServer(TM) Release 5 (scosysv.my_domain_name) (ttyp0)
>
> login: root
> Password:
> Last successful login for root: Sat Aug 02 12:00:08 2003 on ttyp0
> Last unsuccessful login for root: Sat Aug 02 11:32:04 2003 on tty01
>
> SCO OpenServer(TM) Release 5
>
> (C) 1976-1998 The Santa Cruz Operation, Inc.
> (C) 1980-1994 Microsoft Corporation
> All rights reserved.
>
> For complete copyright credits,
> enter "copyrights" at the command prompt.
> TERM = (ansi)
> Terminal type is ansi
> # cd u
> # cd bbx2
> # ./bbx2
>
> READY

> >RUN "MAIN"

>

.... snip ...

Jorge,

Check your TERM variable:
echo $TERM

If you have to use Window's telnet, set your TERM variable to vt100 if it's
not already set:

TERM=vt100
export TERM

Check for a config.bbx file:

find /u -name config.bbx
(it's probably under /u, but you could search from the root dir as well)

view config.bbx and check the alias associated with your tty. Set the alias
line to "term" (to use whatever your TERM variable is set to) or to
vt100.

Good luck,
Dan









Do you have a config.bbx file?

[Jorge_Beteta]

Thanks, Dan. I will do it rigth now.