vi problem

[mightyscotchpine]

I'm trying to run vi on the console on a sco 5.05 system. I'm getting the error "terminal too wide". I'm pretty sure this has something to do with what vi thinks the character width of my console is. I've tried many different TERM environment settings. I'm sure this is a common thing. Can anyone tell me what I'm missing?

Thanks for any help you can give.

 

[stanhubble]

char mode or open desktop?

 

[itcamefrommars]

hi, im working with scotchpine...
character only.
thanks stan.

 

[itcamefrommars]

character... im working with him.

 

[stanhubble]

assuming you have tried setting TERM to ansi, you might want to check out what is in the /etc/default/mapchan file.
sometimes the codepage(?) stuff gets confused.
when in doubt i blank the entry for tty01 in that file.

stan

 

[edfair]

How about TERm to scoconsole or possibly setting the .profile to do an eval and pull the info from ttytype. Ed Fair
efair@atlnet.com

Any advice I give is my best judgement based on my interpretation of the facts you supply.

Help increase my knowledge by providing some feedback, good or bad, on any advice I have given.

 

[itcamefrommars]

ok, on the native tty1a port dialin.... works ok...
on tty1a2 (equinox) port dialin is where the problem occurs.

 

[itcamefrommars]

setting to different emulations does not help...
tried:
ansi
ansic
scoansi
wy50
wy60
wy150
vt100

and have tried using different dialin softwares :
ice10
tinyterm
arnetterm
hyperterm
etc.

thanks again for the help...
any idea why tty1a2 would do this?
have had it happen before on a ttyp! it seemed to disappear?!?!
didn't happen again after a few days...
but this tty1a2(equinoxsst64) has got me.

marshallbrown
mbrown@computereaseinc.net

 

[edfair]

tty1a2 or tty1A2? dialin modem on other cards uses a different port to indicate that it is dialin, and therefore the ttytype settings would be different.
How about setting your TERM in the login .profile?
TERM=wy60
export TERM
if these are the terminals you are using.
Earlier you said console, later you said tty1a. Normally these are not the same. Ed Fair
efair@atlnet.com

Any advice I give is my best judgement based on my interpretation of the facts you supply.

Help increase my knowledge by providing some feedback, good or bad, on any advice I have given.

 

[itcamefrommars]

sorry about the confusion... and thank you again for your attention. i always try to help here and i appreciate the advice you (ed) and stan give everyone.

specifically...
sco505
equinox sst with a 4 port fan cable
multitech modem
tty1a2 case correct... we always use little 'a' for dialin and big 'A' for dial-out.
im dialing in with tinyterm ver4.0
scoansi set all around and have tried .profiles setting term, and changing the ttytype entries.
also tried all other combos i mentioned earlier.

do you have any recommendations for managing the modems... like i said... we use big for outgoing and little for incoming... simply enabling the port when we want to dial in and having them disable when we log out.
ive tried modem manager, but it always locks up.
i wouldn't mind a cleaner way, seeing that i manage 150+ sco servers that dial out 1-4 times daily each!
lots of modem issues. oh, yeah... we normally dial out with blast... some (3-5) with TERM.

again... thanks alot!
mbrown@computereaseinc.net

 

[edfair]

I've found that the modem version of the port is cleaner for resolving problems. I don't remember what version it was that created the problem, but I spent days troubleshooting a minor glitch, and the problem was one definition in gettydefs that was different. Think it was something related to hangup. Of course , you'll have to change Devices if you make the change.
There are some glitches that show up when you have to make things talk together. You may want to look at the termcaps to see what the difference is in scoansi and ansi. Most of my stuff is wyse60, but for those locations where I am locked into ansi I use ArnetTerm(an obsolete,discontinued, DOS package) or Hyperterm.
I think scoansi was originally a color monitor definition in Xenix days. I would be suspicious. I would be using ansi or ansic or would revert back to wyse for troubleshooting purposes, but that is more because of my experience there than anything else.
Are your terminal types settable via an equinox program. I've run across some differences with digi where changing in ttytype wasn't the correct place to do it. Ed Fair
efair@atlnet.com

Any advice I give is my best judgement based on my interpretation of the facts you supply.

Help increase my knowledge by providing some feedback, good or bad, on any advice I have given.