[net.micro.pc] UN*X PC

rnm@akgua.UUCP (R.N. McIntyre [Bob]) (07/19/85)

***********

For those of you thinking of purchasing a UNIX PC, here's a
brief list of shortcomings I've run across with mine.

1. Unless you purchase the UNIX Development and Utilities Packages,
   there is NO DOCUMENTATION on the UNIX commands provided in the
   bundled software.
2. I have had no success in running screen dependent programs
   on the PC when hooked up to a host 3B20 through the RS232 port,
   and file transfers can only be accomplished with "cu" and "uucp".
3. There is no advantage in having say a 4800 baud connection to a
   host UNIX for screen operations. The UNIX PC screen seems to
   run at a slow 1200. I have had no problems using the modem
   port at 1200 baud for screen dependent programs but phone lines 
   seem to be scarce around here.


   
In short, the terminal emulator must have been an after thought
and design objectives must have been focused on stand alone business
applications with users knowing nothing of UNIX.

Of course, the frustration factor always runs highest during the
initial installation phase on a new AT&T product. :-)

Bob McIntyre - in the net.

gritz@homxa.UUCP (R.SHARPLES) (07/19/85)

Bob:

To use the serial port on the 7300 requires a weird type of nullmodem cable:
		
	  UNIXPC     serial cable to host or terminal
		1 - 1
		2 - 3
		3 - 2
	      4&5&6 - tie together on unixpc, leave open on cable
		7 - 7
		8 - 20
		20 - 8

The HOST&CALLER entry doesn't work on the RS232 setup.  HOST and CALLER refer
to the unixpc, ie it is a CALLER if you are connecting to another host.

To get really good vi response you must use the "s4" termcap entry in the
unixpc's /etc/termcap file.  You will have to edit out this one entry, cu it up
to your host and set the proper environment variables.  I and others on the net
can provide you with terminfo entries if your host uses UNIX 5.2.  Your right
the terminal emulator doesn't do much.

By the way, to use cu, you must specify -l/dev/ph1 for the data line or
-l/dev/ph0 for the voice line or -l/dev/tty000 for the serial port.

Once you get uucp set up with your host, there is no problem moving files
around.  I think this thing is great!

Russ Sharples
AT&T-BL
homxa!gritz

rnm@akgua.UUCP (R.N. McIntyre [Bob]) (08/20/85)

Newsgroups: att.micro.pc net.micro.pc
Subject: Re: UN*X PC
References: <1589@akgua.UUCP>, <1041@homxa.UUCP> <729@houxa.UUCP>

********************

  Thank You.

  Clay Schneider and Russ Sharples of Bell Labs.

  After posting my problems to the net on connecting this UN*X PC
to our host 3B20, they have provided answers to most of my immediate
problems. For use of the terminal emulator at 9600 baud with the
RS232 port, a profile must be created for the phone manager to use.
It must be set to the serial option instead of modem. The PC
is working very nicely now when connected to the 3B20 at 4800 baud.
  A termial emulator is still needed to do file transfers and handle
graphics output. With those options, I think this PC would be hard to
beat.

   Thanks Again.