headers
Blaz Antonic | 1 Apr 2003 19:15
Favicon

Terminal settings (which termcap entry to use)

Hello,

I have WinXP telnetting to my VS running NetBSD (and PC running Linux)
using builtin telnet.exe. Upon telnetting the terminal type is set to
ansi but obviously WinXP and termcap disagree on their definitions of
"ansi" as bunch of stuff doesn't work correctly (scrolling up and doiwn
in joe, some control keys not working properly, etc.). At the time being
i set

export TERM=vt100 

to be able to edit files at the very least but this way i lost some
functionality in other areas (bash history for example). 

This very same telnet.exe seems to work reasonably well with Linux's
linux-c termcap entry (almost everything workds, except few things in
'make menuconfig' display wrong after moving around).

I was wondering if anybody else is using same or similar telnet (Windoze
version) and has figured out a termcap entry that will work as expected
?

Unretaled question: i got Philips 17T monitor which allegedly supports
sync on green (it has a toggle switch on the back) on its 5 BNC inputs
that can apparently function as 3 BNC. Before i rush and buy $38
DB15-BNC cable from website i found (which prolly has Mac pinout anyway
:-)))) i was wondering whether there is any point in hooking my VS to
this monitor at all: will this PC monitor be able to sync to 1024x864 (i
understand that they are able to sync on multiple frequency ranges but
docs afaik don't tell whether 1024x864  <at>  60 Hz is supported or not) ?
(Continue reading)

Permalink | Reply | 2 comments |
headers
John Klos | 1 Apr 2003 11:15

Re: Terminal settings (which termcap entry to use)

Hi,

> I have WinXP telnetting to my VS running NetBSD (and PC running Linux)
> using builtin telnet.exe. Upon telnetting the terminal type is set to
> ansi but obviously WinXP and termcap disagree on their definitions of
> "ansi" as bunch of stuff doesn't work correctly (scrolling up and doiwn
> in joe, some control keys not working properly, etc.). At the time being
> i set
>
> export TERM=vt100
>
> to be able to edit files at the very least but this way i lost some
> functionality in other areas (bash history for example).

Windows telnet is one of the worst programs of its kind anywhere, in my
opinion. I'd recommend you get any of a number of free programs to replace
it (TeraTerm, putty).

John Klos
Sixgirls Computing Labs
Permalink | Reply | 0 comments |
headers
ogdenk | 1 Apr 2003 17:32

Re: Re: Terminal settings (which termcap entry to use)


> 
> From: John Klos <john <at> sixgirls.org>
> Date: 2003/04/01 Tue AM 04:15:38 EST
> To: Blaz Antonic <blaz.antonic <at> siol.net>
> CC: port-vax <at> netbsd.org
> Subject: Re: Terminal settings (which termcap entry to use)
> 
> Hi,
> 
> > I have WinXP telnetting to my VS running NetBSD (and PC running Linux)
> > using builtin telnet.exe. Upon telnetting the terminal type is set to
> > ansi but obviously WinXP and termcap disagree on their definitions of
> > "ansi" as bunch of stuff doesn't work correctly (scrolling up and doiwn
> > in joe, some control keys not working properly, etc.). At the time being
> > i set
> >
> > export TERM=vt100
> >
> > to be able to edit files at the very least but this way i lost some
> > functionality in other areas (bash history for example).
> 
> Windows telnet is one of the worst programs of its kind anywhere, in my
> opinion. I'd recommend you get any of a number of free programs to replace
> it (TeraTerm, putty).
> 
> John Klos
> Sixgirls Computing Labs
>
(Continue reading)

Permalink | Reply | 0 comments |
headers
Brian Chase | 1 Apr 2003 17:45

Re: Terminal settings (which termcap entry to use)

On Tue, 1 Apr 2003, Blaz Antonic wrote:

> Hello,
>
> I have WinXP telnetting to my VS running NetBSD (and PC running Linux)
> using builtin telnet.exe. Upon telnetting the terminal type is set to
> ansi but obviously WinXP and termcap disagree on their definitions of
> "ansi" as bunch of stuff doesn't work correctly (scrolling up and doiwn
> in joe, some control keys not working properly, etc.). At the time being
> i set
>
> export TERM=vt100
>
> to be able to edit files at the very least but this way i lost some
> functionality in other areas (bash history for example).
>
> This very same telnet.exe seems to work reasonably well with Linux's
> linux-c termcap entry (almost everything workds, except few things in
> 'make menuconfig' display wrong after moving around).
>
> I was wondering if anybody else is using same or similar telnet (Windoze
> version) and has figured out a termcap entry that will work as expected
> ?

Alternatively, you could fix the source of the problem instead of
working around it.  That problem being Microsoft's ridiculous excuse for
a telnet client.  PuTTY is one excellent alternative client; it supports
SSH, telnet, and rsh connections.

  <http://www.chiark.greenend.org.uk/~sgtatham/putty/>
(Continue reading)

Permalink | Reply | 0 comments |
headers
sridhar | 2 Apr 2003 11:28

Ultrix Driver Question


Hi people.  I assume that SDI disks show up as /dev/ra* on Ultrix?  What
do the SDI controllers show up as?  Specifically, the XMI ones?

Peace...  Sridhar
Permalink | Reply | 2 comments |
headers
Dave McGuire | 2 Apr 2003 11:31

Re: Ultrix Driver Question

On Wednesday, April 2, 2003, at 04:28 AM, sridhar <at> neurotica.com wrote:
> Hi people.  I assume that SDI disks show up as /dev/ra* on Ultrix?  
> What
> do the SDI controllers show up as?  Specifically, the XMI ones?

   If memory serves, they'd show up as kdm<n>.

       -Dave

--
Dave McGuire             "I've grown hair again, just
St. Petersburg, FL           for the occasion."       -Doc Shipley
Permalink | Reply | 1 comment |
headers
Johnny Billquist | 2 Apr 2003 11:49
Picon
Picon

Re: Ultrix Driver Question

On Wed, 2 Apr 2003, Dave McGuire wrote:

> On Wednesday, April 2, 2003, at 04:28 AM, sridhar <at> neurotica.com wrote:
> > Hi people.  I assume that SDI disks show up as /dev/ra* on Ultrix?  
> > What
> > do the SDI controllers show up as?  Specifically, the XMI ones?
> 
>    If memory serves, they'd show up as kdm<n>.

Looks like it, yes...

From GENERIC:

controller      kdm0    at xmi?         node?

but then you also av uq?, which is the port driver, that goes through any
of the MSCP controllers.

controller      uq24    at kdm0         vector uqintr

And then, disks talk mscp:

disk            ra0     at mscp         drive 0

So, it might show up as kdm<n>, but I'm certain that uq<n> will show up.

	Johnny

Johnny Billquist                  || "I'm on a bus
                                  ||  on a psychedelic trip
(Continue reading)

Permalink | Reply | 0 comments |
headers
M J Dowden | 3 Apr 2003 05:12
Picon
Favicon

battery replacement on VAX 4000-300

     The batteries on my VAX 4000-300 have gone dead and won't hold a 
charge. I understand that the unit takes 3 AAA NiCad's, but I have no 
idea where they are or how to install them. Is there any 
documentation on the web?

     Best regards,
     M J Dowden

--

-- 
M J Dowden <mjdowden <at> panix.com>
PGP key: <http://www.panix.com/~mjdowden/keys.shtml>
No Microsoft products were used in the preparation or transmission of 
this message
Permalink | Reply | 7 comments |
headers
Dave McGuire | 3 Apr 2003 05:28

Re: battery replacement on VAX 4000-300

On Wednesday, April 2, 2003, at 10:12 PM, M J Dowden wrote:
>     The batteries on my VAX 4000-300 have gone dead and won't hold a 
> charge. I understand that the unit takes 3 AAA NiCad's, but I have no 
> idea where they are or how to install them. Is there any documentation 
> on the web?

   They are in the bulkhead/connector panel that covers the processor 
board.

        -Dave

--
Dave McGuire             "I've grown hair again, just
St. Petersburg, FL           for the occasion."       -Doc Shipley
Permalink | Reply | 6 comments |
headers
M J Dowden | 3 Apr 2003 12:04
Picon
Favicon

Re: battery replacement on VAX 4000-300

At 10:28 PM -0500 4/2/2003, Dave McGuire wrote:
>
>   They are in the bulkhead/connector panel that covers the processor board.

     I thank you kindly. Are they ordinary NiCad batteries or are they 
taped together like cordless phone batteries? I was hoping to have 
the parts on hand before starting the job. Is there a bracket or are 
they hardwired and soldered to the board.

     Thanks again,
     M J Dowden

--

-- 
M J Dowden <mjdowden <at> panix.com>
PGP key: <http://www.panix.com/~mjdowden/keys.shtml>
No Microsoft products were used in the preparation or transmission of 
this message
Permalink | Reply | 5 comments |

Gmane