Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!zaphod.mps.ohio-state.edu!van-bc!ubc-cs!uw-beaver!milton!sumax!amc-gw!thebes!polari!rwing!pat
From: pat@rwing.UUCP (Pat Myrto)
Newsgroups: comp.unix.sysv386
Subject: Re: VP/ix over serial/modem lines
Keywords: VP/ix, serial, modem, possible
Message-ID: <225@rwing.UUCP>
Date: 10 Feb 91 09:14:33 GMT
References: <170@rubys.UUCP>
Organization: Totally Unorganized
Lines: 54

In article <170@rubys.UUCP> dnb@rubys.UUCP (Dave Buonomo) writes:
>I'm running VP/ix on top of Interactive UNIX Sys V 3.2.2.  I would like to
>dial-in to this box from a PC and run VP/ix remotely and would like to know
>of any experiences with this, or wheather it is even practical.  In
>
>I'd also like to know of any other configuration items I need to be concerned
>with on the UNIX box in relation to VP/ix.  Thanks in advance.

What you propose to do works fine.  The terminal types supported are
listed in /usr/vpix/term, and the files can be modified if you want to
emulate some other special PC key combinations.  The keys like right
shift, left shift, alt, etc are handled by mapping a character to the
key press and key release codes - read the VP/ix docs for more info.
Note that if you map a key to some special key, you also need to map
something to generate the char the key you previously mapped
generates, usually its TWO hits on the given key - look at how escape
is handled.

The remote terminal, if its not a PC (like a vt100) doesn't understand
the IBMPC special graphic chars, you will get the 7 bit equiv
displayed, but still most screens are easily understandable.  Screen
updates on the remote are reasonably intelligent.

As an example of how well it works (for me, at least), I can call the
UNIX system from remote over dialup, log in, bring up VP/ix, run IPX
and NET3, attach to the Netware LAN at work, login to THAT, and run
Netware utilities, like SYSCON, etc to do maint (I am the "lan admin"
at work).

While VP/ix isn't the be-all end-all, I am impressed such a lashup
kludge described above works AT ALL, let alone very well.  I even have
reconfigured the LAN to use Ethernet II packets, and have the BYU IPX
and a Clarkson driver installed, with future intent of trying to get
NFS or something going with the Netware LAN and UNIX, and The PD IPX
and Clarkson driver works fine using VP/ix.  I figure if that works,
just about anything will.  Only constraint on VPix apps are that they
cannot diddle with the DMA (that requires a special kernel driver
addition).  The NIC also has to be set up to use a FREE IRQ number and
I/O port addresses - the setup asks you for the IRQ and starting and
ending I/O port address.

Just be sure your ASYNC driver for the UNIX supports VP/ix - you have
to either be using the stock async driver, or FAS 207 or later.
Otherwise VP/ix complains about not understanding your keyboard, and
is not accessable to your keystrokes.

Try it - I think you will like it.  I also suggest a decent line speed
like 9600 or PEP.  Stuff that likes to redo the whole screen may be
rather slow to run at low line speeds like 1200/2400.....
-- 
pat@rwing                                       (Pat Myrto),  Seattle, WA
                            ...!uunet!pilchuck!rwing!pat
      ...!uw-beaver!uw-entropy!dataio!/
WISDOM:    "Travelling unarmed is like boating without a life jacket"