| Title: | Digital PATHWORKS 32 |
| Moderator: | SPELNK::curless |
| Created: | Fri Nov 01 1996 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 337 |
| Total number of notes: | 1612 |
Hi, a customer of mine has a strange problem with PowerTerm525 and OpenVMS AXP. He has two Alpha systems OpenVMS 6.2, when he connects via LAT to first Alpha the words "Username" and "Password" are not correctly displayed: the lowercase characters are substituted by semigraphic characters, after login the lowercase characters are displayed correctly (a SET TERM/INQU is performed). If he connects to second Alpha all works fine, the PW525 setup is the same for both connections. VT320 works correctly with both Alpha systems. Could someone tell me any suggestion ? Thank in advance. Gino De Poli (crossposted PATHWORKS32 and VMSNOTES conferences)
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 222.1 | What OS? | JAMIN::MCCARRON | Mon Apr 14 1997 12:46 | 10 | |
Gino,
What platform are you running PowerTerm on? Windows95, NT/Intel or
NT/Alpha? I've seen a similar problem only on Windows95 and only with
a later version than the one that is shipped on the kit. In my case,
the Username & Password prompt are OK, but once you get to the $ prompt
you get the graphics characters. Since this isn't reproducable on the
shipping kit, we thought it was a new bug. Maybe not.
bruce,
| |||||
| 222.2 | JAMIN::OSMAN | Eric Osman, dtn 226-7122 | Fri Apr 25 1997 18:38 | 25 | |
When you're on vms and *not* seeing the problem, see if the following
*produces* the problem (this puts terminal into graphics mode):
$ es=""
$ es[0,8]=27
$ write sys$output es,"(0"
If so, you can restore ascii mode like this:
$ write sys$output es,"(B"
The next step in analysis would be to use a logging facility (does
powerterm include one ?) to capture all the characters going to the
mystery session (i.e. the session showing graphics characters even
when you *don't* use the above method) and see if a similar escape sequence
is anywhere in the log, for example
<escape> ( 0
/Eric
| |||||