cursor blink

[Kassler]

hi all,

excuse me if i write this in the wrong community.

One of my users have a problem with "entry fields" of some tools and software (eg. nedit...). The cursor normally flashes but on one server the cursor disappear or stop. I have 3 server with the same hardware and same software (hpux11i clone, L3000 server).

Does anybody knows where i can look for a mismatch or error??

Many thanks in advance.

Best Regards,
Markus Kassler

[SureshKumar_2]

Hi Markus

Plz check the /etc/profile, user's .profile

in working m/c and suspected m/c

Make all terminal emulation as same. & Check ur problem has to get solved.......

Do u connect to the server thru' fixed/pseudo port????

If u use fixed port, could u give the content of
*) /etc/inittab
*) /etc/gettydefs

All the best!!

suresh

[Robert-Jan Goossens]

Hi Markus,

Check for a similar like the example below in your users .profile.

# Sets a promp which reflects hostname and oracle environment
PS1=`hostname`'[$ORACLE_SID]'`echo "\0033[5m\c"`'$PWD> '`echo "\0033[0m"`
export PS2="> "

HTH,
Robert-Jan

[Elmar P. Kolkman]

Are the screens/tools/terminals the same for all those environments?

The cursor blinking is done by the terminal or terminal emulator, so perhaps the difference is in those.

If you have a prompt like in Robert's example, kill the one installing that one and replace him by someone who can work with tput, because putting escape sequences hard in a prompt without testing which terminal emulator is being used is a real sin...

[Kassler]

hi all,

Many thanks for your fast replies.

We use nis so the users .profile file is the same on all servers and the /etc/profile file is also identical.

Our designer contact the unix environment with Hummingbird Exceed but i have tried it with rlogin from a linux host and there it also don´t work.

The files /etc/inittab and /etc/gettydefs are also indentical.

I have also tried to change the Prompt in the .kshrc_privat file and the same result.
Also without Escape-Characters it will not work.

Yes we use the same tools/software on all server (from one software server).

one example:
in the nedit window the cursor blinks at startup. After i entered a few lines and move around the cursor stops flashing and in some cases the cursor disappear after i move arround it normally starts working.

Best Regards,
Marku

[Elmar P. Kolkman]

Problem, in that case, is probably with differen terminfo or termcap databases on the different systems. Compare the untic output on the machines in question. Perhaps post the differences if you don't understand them yourself ;-) (They are hard to understand if you haven't hacked on terminals as much as some of us, so don't be ashamed...)

[Kassler]

Hi Elmar,

Here is the output of the server which causes the error:

cai01 sa: ../sa > untic
xterm|vs100|xterm terminal emulator,
am, xenl, km,
cols#80, lines#65,
bel=^G, cr=\r, csr=\E[%i%p1%d;%p2%dr, tbc=\E[3g,
clear=\E[H\E[2J, el=\E[K, ed=\E[J, cup=\E[%i%p1%d;%p2%dH,
cud1=\E[B, home=\E[1;1H, civis=\E[?25I, cub1=\b,
cnorm=\E[?25h, cuf1=\E[C, cuu1=\E[A, cvvis=\E[?25h,
dch1=\E[P, dl1=\E[M, blink=@, bold=\E[1m,
rev=\E[7m, smso=\E[7m, sgr0=\E[m, rmso=\E[m,
ich1=\E[@, il1=\E[L, kbs=\177, kcud1=\EOB,
kf2=\EOQ, kf3=\EOR, kf4=\EOS, kcub1=\EOD,
knp=\E[U, kpp=\E[V, kcuf1=\EOC, kcuu1=\EOA,
rmkx=\E[?1l, smkx=\E[?1h, dch=\E[%p1%dP, dl=\E[%p1%dM,
cud=\E[%p1%dB, ich=\E[%p1%d@, il=\E[%p1%dL, cub=\E[%p1%dD,
cuf=\E[%p1%dC, cuu=\E[%p1%dA, rs1=\E>\E[1;3;4;5;6l\E[?7h\E[m\E[r\E[2J\E[H, rs2=@kf1=\EOP,
rc=\E8, sc=\E7, ind=\n, ri=\EM,
sgr=\E[%?%p1%t;7%;%?%p2%t;4%;%?%p3%t;7%;%?%p4%t;5%;%?%p6%t;1%;m, hts=\EH, ht=\t,


an here from one server with no problems:

cci01 sa: ../sa > untic
xterm|vs100|xterm terminal emulator,
am, xenl, km,
cols#80, lines#65,
bel=^G, cr=\r, csr=\E[%i%p1%d;%p2%dr, tbc=\E[3g,
clear=\E[H\E[2J, el=\E[K, ed=\E[J, cup=\E[%i%p1%d;%p2%dH,
cud1=\E[B, home=\E[1;1H, civis=\E[?25I, cub1=\b,
cnorm=\E[?25h, cuf1=\E[C, cuu1=\E[A, cvvis=\E[?25h,
dch1=\E[P, dl1=\E[M, blink=@, bold=\E[1m,
rev=\E[7m, smso=\E[7m, sgr0=\E[m, rmso=\E[m,
ich1=\E[@, il1=\E[L, kbs=\177, kcud1=\EOB,
kf2=\EOQ, kf3=\EOR, kf4=\EOS, kcub1=\EOD,
knp=\E[U, kpp=\E[V, kcuf1=\EOC, kcuu1=\EOA,
rmkx=\E[?1l, smkx=\E[?1h, dch=\E[%p1%dP, dl=\E[%p1%dM,
cud=\E[%p1%dB, ich=\E[%p1%d@, il=\E[%p1%dL, cub=\E[%p1%dD,
cuf=\E[%p1%dC, cuu=\E[%p1%dA, rs1=\E>\E[1;3;4;5;6l\E[?7h\E[m\E[r\E[2J\E[H, rs2=@kf1=\EOP,
rc=\E8, sc=\E7, ind=\n, ri=\EM,
sgr=\E[%?%p1%t;7%;%?%p2%t;4%;%?%p3%t;7%;%?%p4%t;5%;%?%p6%t;1%;m, hts=\EH, ht=\t,


As far as i can see there is no difference between these two.

Many thx.

Markus

[Kassler]

hi,

today a designer gives me another hint.

The problem that the cursor stops blinking appears also at the login prompt when you want to access the system.

So i think there is no user-problem, it`s
a common system problem of the server.

Thx for help.

Regards,
Markus

[Bruno Ganino]

I believe depending by terminfo settings.
Read
http://www.informatik.uni-frankfurt.de/doc/man/hpux/terminfo.4.html

http://www.informatik.uni-frankfurt.de/doc/man/hpux/curses.3x.html

HTH
Bruno

[Mark Greene_1]

"The problem that the cursor stops blinking appears also at the login prompt when you want to access the system."

With that being the case, the cursor blinking, or not, is being controlled by whatever terminal or terminal emulation program being used to access the system, and not anything setting or config on the system.

mark

[Elmar P. Kolkman]

It looks like Mark is right. It could still be in /etc/issue or /etc/motd, though...

[Wodisch]

Hi Markus,

since X-Windows cannot blink, actually, the blinking has to be done by the application. In your cases, that's your terminal window "frame", i.e. "dtterm" or "xterm" or "hpterm".
Of those, only "dtterm" does blinking, so my question is: which terminal emulation program do your users use?
And for the one, which does not blink, what is used there?
Switching to "dtterm" (the titlebar shows "Terminal" on those) should sove that problem...

FWIW,
Wodisch

[Bill Hassell]

Xwindows is always a problem with terminal windows. Your PC is just interpreting cides sent from the terminal emulator that resides on some other computer, typically the one you are contacting. You need to get all the xterms, hpterms and dtterms out of the way and run a simple client-based telnet program. That way, the terminal emulator will behave the same way with all servers. A blinking cursor (or visible cursor for that matter) is defined by the emulator and it's configuration. Some emulators turn off their cursor when the remote connection is dead, etc.

Otherwise, standardize on one server to provide your terminal window. Once the window is displayed, login, then telnet to your desired host from that window.

Also check the stty settings once you login on each host. There are a couple of dozen options that might change the telnet behavior (which can affect terminal emulators). Also, if your applications are making any ioctl calls, there may be differences in the executables between servers.

[Kassler]

Hi,

We use xterm as our standard terminal. I have seen that for the terminals only dtterm blink, but the blink also stop 5 - 10 seconds after coming up as all the other applications.

I have examined the stty config and there is no difference between the servers. I have also tried it with telnet, the same effect.

I think like Bill said that he lose the connection or get a timeout but i do not know how i can examine that.

Best Regards,
Markus

[Mark Greene_1]

In addition to stty -a, run xset -q and compare the two for potential conflicting behavior.

Also, if you are using Exceed, check the setup strings you are passing from xstart for each host; e.g., here's one I use to connect to one my HP 11i systems:

@(XTerm, method=stdappdb) -display @d -fn 7x10 -fg white -bg black -geometry 80x24 -name "[system name here]" +s -sl 13767 -ls &;


FWIW, I don't get a blinking cursor when I connect to this system.

mark