Ask a Question related to SCO, Design and Development.
-
Jorge_Beteta #1
Terminal Interface Big Problem
Hello,
Sorry for bother you guys with the same problem again , but I can't
solve it.
For several weeks I've got a terrible problem with Terminal
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, like a FoxPro
for DOS.
I have installed several differents terminal emulators, like SCO
TermLite 1.0.7, ShellTelNet, NetTerm and finally SCO TermVision 2.1 on
my Windows PC.
Each one was able to connect to SCO Unix, but neither one could load
up properly the Business Basic System that is running on the server.
When I access that system on Unix via TermVision 2.1 (ANSI emulator)
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
READY2S>RUN "MAIN"
2°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°° °°°°°°°°°°°°°°°°°°°°°°°°°°°°°°
°2ACME COMPANY2
ððððððððððððððððððððððððððððððððððððððððððððððððð ððððððð2MAIN MENU2
ððððððððððððððððððððððððððððððððððððððððððððððððð ððððððð2
ðððððððððððððððððððððððððððððððððððððððððððððððððð ðððððð2
ðððððððððððððððððððððððððððððððððððððððððððððððððð ðððððð22,0032K2,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
2ENTER YOUR CHOISE:
<End of Screen>
I have tried every possible setting on TermVision 2.1 (and in the
other terminal emulators, too) but nothing changes that terrible
interface.
Checking for the TERM variable:
TERM=vt100
export TERM
and checking for the config.bbx file, doesn't work at all. The problem
is still there.
I think I should install some files on the SCO Unix in order to get a
properly Windows connection. What files am I missing to install,
please? Or how could I contact SCO to ask this question? I access its
web site but it seems quite difficult to find where to post a
technical question and to get an answser as well.
Thank you very much
Jorge_Beteta Guest
-
Terminal Server problem
I am trying to access a Windows 2003 Server via Terminal Server client, on Windows 2K Pro desktop. When I do this I am getting the error message,... -
windows 2003 terminal server problem
I have a win 2003 terminal server (also a domain controller). It is running Citrix Metaframe XP. All is well except for when users connect and run... -
Terminal Server Licensing Problem
I have a Windows 2003 server and had purchased 7 TS licenses. I installed the server as a member server in our NT4.0 domain. I install TS... -
modul Net::Telnet with ssh Terminal --> login problem
I try to manage a ssh Terminal by Net::Telnet. The second (great) example on CPAN von the Module Net::Telnet was the inspiration for my Script. I... -
Problem with X terminal in Linux 9
hi, I have Linux 9 in my computer and I tried connecting my computer to solaris through telnet and did setenv display with the hostname as I have... -
Jean-Pierre Radley #2
Re: Terminal Interface Big Problem
Jorge_Beteta typed (on Thu, Aug 07, 2003 at 11:14:57AM -0700):
| Hello,
| Sorry for bother you guys with the same problem again , but I can't
| solve it.
| For several weeks I've got a terrible problem with Terminal
| 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, like a FoxPro
| for DOS.
|
| I have installed several differents terminal emulators, like SCO
| TermLite 1.0.7, ShellTelNet, NetTerm and finally SCO TermVision 2.1 on
| my Windows PC.
|
| Each one was able to connect to SCO Unix, but neither one could load
| up properly the Business Basic System that is running on the server.
Try anzio, from [url]www.anzio.com[/url].
--
JP
Jean-Pierre Radley Guest
-
Bob Bailin #3
Re: Terminal Interface Big Problem
"Jorge_Beteta" <jbeteta@yahoo.com> wrote in message
news:5140b91e.0308071014.62535ca3@posting.google.c om...2°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°° °°°°°°°°°°°°°°°°°°°°°°°°°°> Hello,
> Sorry for bother you guys with the same problem again , but I can't
> solve it.
> For several weeks I've got a terrible problem with Terminal
> 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, like a FoxPro
> for DOS.
>
> I have installed several differents terminal emulators, like SCO
> TermLite 1.0.7, ShellTelNet, NetTerm and finally SCO TermVision 2.1 on
> my Windows PC.
>
> Each one was able to connect to SCO Unix, but neither one could load
> up properly the Business Basic System that is running on the server.
>
> When I access that system on Unix via TermVision 2.1 (ANSI emulator)
> 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
> ðððððððððððððððððððððððððððððððððððððððððððððððððð ðððððð22,0032K2,003
> BOXÿÿ
> ÿÿ9ÿ
> 2< Time : 12:17 PM
>
°°°°03/08/20032°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°°° °°°°°°°°°°°> °°2DATE:(Note: It's not a good idea to run bbx2 logged in as root. Later releases> °°°°°°°°°°°°°°°°°°°°°°°°°
> 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>
>
> I have tried every possible setting on TermVision 2.1 (and in the
> other terminal emulators, too) but nothing changes that terrible
> interface.
> Checking for the TERM variable:
>
> TERM=vt100
> export TERM
>
> and checking for the config.bbx file, doesn't work at all. The problem
> is still there.
>
>
> I think I should install some files on the SCO Unix in order to get a
> properly Windows connection. What files am I missing to install,
> please? Or how could I contact SCO to ask this question? I access its
> web site but it seems quite difficult to find where to post a
> technical question and to get an answser as well.
of bbx refuse to be run as root.)
Try:
# cd /u/bbx2
# l termcap*
There should be a specialized termcap file in this directory for bbx.
It may be called "termcap", it may be called "termcap.bbx".
Let's assume it's called "termcap". Enter:
# TERMCAP=/u/bbx2/termcap
# export TERMCAP
# ./bbx2
READYNow try running your menu program and the escape sequences>
unique to bbx should now display properly.
Bob Bailin Guest
-
Jorge_Beteta #4
Re: Terminal Interface Big Problem
"Ronald J Marchand" <rojomar@covad.net> wrote in message news:<bguhji$p57$1@sun-news.laserlink.net>...
Thank you very much, Ron. You were rigth about the config.bbx file.> Post the alias lines from your config.bbx for the "T" devices ... as in
> alias T0 .....
> That product uses a modified termcap file which usually lives in the
> directory where the executable lives. Depending on the configuration, it
> may not care what terminal type is set on login.
>
> Is this the second time you have asked this question?
>
> Ron
The terminal interface problem was actually a Business Basic problem.
It couldn't be seen properly the bbx windows interface because I
accessed the SCO Unix 5.0.5 with a terminal type "ttyp0" from my W98.
I had to add the line: "alias T4 /dev/ttyp0 vt100" on my config.bbx,
like:
stblen=2688
fcbs=40
cibs=30
aliases=21
alias T1 /dev/tty01 scoansi
alias P0 /dev/tty01 "Epson 100 series"
CR,CP=0F,SP=12,CPCOLS=240,SPCOLS=132,EPON=0E,EPOFF =14,EPCOLS=2,EPLINES=1,SLON=1B5B3569,SLOFF=1B5B346 9
alias T2 /dev/tty02 vt100
alias T3 /dev/tty03 vt100
alias T4 /dev/ttyp0 vt100
alias P1 /dev/ttyp0 "Epson 100 series"
CR,CP=0F,SP=12,CPCOLS=240,SPCOLS=132,EPON=0E,EPOFF =14,EPCOLS=2,EPLINES=1,SLON=1B5B3569,SLOFF=1B5B346 9
alias LP ">lpr 2>/dev/null" "Epson 100 Series"
That resolved the terminal interface problem.
However, I still have the "memory fault - core dumped" error. It
happens when I hit the DEL key (when I'm trying to escape from the
program, because of that I hit the down-arrow key instead) or when the
program makes some processes. Sorry I don't know too much about those
processes, I'm just viewing the install matter.
I tried:
hoping that it could be a "too many files open" problem. But it> start 255
> run "MAIN"
doesn't.
I think that it has to be some settings that I have to do on some
files like config.bbx or termcap.
Do you think it could be the solution?
Thanks very much.
Jorge_Beteta Guest
-
Ronald J Marchand #5
Re: Terminal Interface Big Problem
"Jorge_Beteta" <jbeteta@yahoo.com> wrote in message
news:5140b91e.0308091615.2f544058@posting.google.c om...news:<bguhji$p57$1@sun-news.laserlink.net>...> "Ronald J Marchand" <rojomar@covad.net> wrote in messageit> > Post the alias lines from your config.bbx for the "T" devices ... as in
> > alias T0 .....
> > That product uses a modified termcap file which usually lives in the
> > directory where the executable lives. Depending on the configuration,CR,CP=0F,SP=12,CPCOLS=240,SPCOLS=132,EPON=0E,EPOFF =14,EPCOLS=2,EPLINES=1,SLO>> > may not care what terminal type is set on login.
> >
> > Is this the second time you have asked this question?
> >
> > Ron
> Thank you very much, Ron. You were rigth about the config.bbx file.
> The terminal interface problem was actually a Business Basic problem.
> It couldn't be seen properly the bbx windows interface because I
> accessed the SCO Unix 5.0.5 with a terminal type "ttyp0" from my W98.
> I had to add the line: "alias T4 /dev/ttyp0 vt100" on my config.bbx,
> like:
>
> stblen=2688
> fcbs=40
> cibs=30
> aliases=21
> alias T1 /dev/tty01 scoansi
> alias P0 /dev/tty01 "Epson 100 series"
>
N=1B5B3569,SLOFF=1B5B3469CR,CP=0F,SP=12,CPCOLS=240,SPCOLS=132,EPON=0E,EPOFF =14,EPCOLS=2,EPLINES=1,SLO> alias T2 /dev/tty02 vt100
> alias T3 /dev/tty03 vt100
> alias T4 /dev/ttyp0 vt100
> alias P1 /dev/ttyp0 "Epson 100 series"
>
N=1B5B3569,SLOFF=1B5B3469Ok. Forget the slave printer for now and try the following:> alias LP ">lpr 2>/dev/null" "Epson 100 Series"
>
> That resolved the terminal interface problem.
>
> However, I still have the "memory fault - core dumped" error. It
> happens when I hit the DEL key (when I'm trying to escape from the
> program, because of that I hit the down-arrow key instead) or when the
> program makes some processes. Sorry I don't know too much about those
> processes, I'm just viewing the install matter.
>
> I tried:
>>> > start 255
> > run "MAIN"
> hoping that it could be a "too many files open" problem. But it
> doesn't.
> I think that it has to be some settings that I have to do on some
> files like config.bbx or termcap.
> Do you think it could be the solution?
> Thanks very much.
edit the config.bbx file to contain
alias T5 /dev/tty term
In the shell:
TERMCAP=path_to_bbx/config.bbx
BBTERM=T5
export TERMCAP BBTERM
then invoke bbx.
I see that you have posted on the bbx-list. Any future discussion really
belongs there.
Ron
Ronald J Marchand Guest



Reply With Quote

