Release Notes	PN 93000159_M
				 Digi RealPort

				 Version 2.4.5
			   SCO OpenServer Release 5.x
			 Software Package PN 40001044_L
				   8/28/2001


	  CONTENTS
	  Section      Description
	  1	       Intro
	  2	       Supported Products
	  3	       Enhancements
	  4	       Bug Fixes
	  5	       Known Limitations
	  6	       History
	  7	       Notes


	  1. INTRO

	  The RealPort driver is a set of  TCP	network	 drivers  that
	  provides  real tty's functionality for Digi's	Ethernet-based
	  Serial Products.


	  2. SUPPORTED PRODUCTS

	      PortServer
	      PortServer II
	      PortServer TS
	      Digi One RealPort	Device Server
	      Etherlite	2, 80, 160 and 162 units with RealPort firmware

	  The general term Serial Unit	can  mean  any	of  the	 units
	  listed above.


	  3. ENHANCEMENTS


	  The dgipserv utility and man	page  were  added  to  support
	  Etherlite units.


	  4. BUG FIXES


	  TTY closes after a working unit goes offline or is unplugged
	  will now timeout within 120 seconds. It could	take about ten
	  minutes in prior releases.


	  5. KNOWN LIMITATIONS




				     - 1 -






	  The driver sends a SIGHUP to the controlling terminal	when a
	  network  connection  has  been broken.  A process that is no
	  longer part of the process group may not receive the SIGHUP.

	  If the network  connection  is  lost	between	 the  RealPort
	  driver  and  the  Serial  Unit,  it may take several minutes
	  before communications	can be re-established with the unit.

	  The default TCP port for RealPort units is 771.   This  port
	  is  officially reserved for rtip.  If	you are	using rtip you
	  will need to configure your units and	RealPort driver	to use
	  a  different	TCP  port.   See  the NOTES sections below for
	  information on how to	do this.

	  The only way to change the  configuration  is	 to  reinstall
	  RealPort.   Digi recommends configuring extra	units to allow
	  for future expansion.


	  6. HISTORY

	  08/09/2001 SCO OSR5 2.4.4

	  The driver now supports setting and retrieving  custom  baud
	  rates	 using	the  DIGI_SETCUSTOMBAUD	and DIGI_GETCUSTOMBAUD
	  ioctls. You can also use ditty -cspeed followed by the  baud
	  rate to set custom rates.

	  A man	page for ditty has been	added. New unit	types such  as
	  PortServer  TS  can  be  used.  The  fastbaud	table has been
	  extended to support baud rates as high as 921600.


	  The write section of the driver now  properly	 reflects  the
	  characters  written  when  the  write	 is  interrupted  by a
	  signal.

	  Under	SCO Merge, if a	line control command was sent while  a
	  break	 was  in progress, a extra break would accidentally be
	  generated.  This has been fixed.


	  Under	 certain  conditions,	the   driver   would   receive
	  continuous  update  packets  from  the Serial	Unit unit that
	  would	cause unnecessary network traffic.

	  07/31/2000 SCO OSR5 2.4.2

	  Under	 certain  conditions,	the   driver   would   receive
	  continuous  update  packets  from  the Serial	Unit unit that
	  would	cause unnecessary network traffic.


	  02/01/2000 SCO OSR5 2.4.1

	  Ports	not accessible problem fixed.



				     - 2 -








	  7. NOTES

	  To configure a PortServer II and RealPort to use a TCP  port
	  other	 than  771,  follow  these  steps.   For this example,
	  assume you want to change to TCP port	3000.

	  To configure a PortServer II,	login  to  the	PortServer  as
	  root,	 run  the  command  "set  config  realport=3000", then
	  reboot the PortServer.  See the PortServer documentation for
	  more information.

	  To configure RealPort	edit the file  /etc/rc2.d/S86ncxa  and
	  add  " -p 3000 "  just  before  the  "&"  at	the end	of the
	  appropriate ncxd command line, then reboot the system.   For
	  example, the line might look like this after editing:

	      /etc/ncxd	-d /dev/cts0 -n	portservA -p 3000 &

	  Each ncxd command line in S86ncxa  has  the  IP  address  or
	  hostname  of	the  Serial Unit, so you can associate command
	  lines	 to  Serial  Units.    The   Serial   Unit   and   the
	  corresponding	 ncxd  command must both use the same TCP port
	  number.

	  The fastbaud table of	substitute baud	rates is now:
	  0 - 0
	  50 - 57600
	  75 - 76800
	  110 -	115200
	  134 -	131657
	  150 -	153600
	  200 -	230400
	  300 -	460800
	  600 -	921600
	  1200 - N/A
	  1800 - N/A
	  2400 - 2400
	  4800 - 4800
	  9600 - 9600
	  19200	- 19200
	  38400	- 38400

	  The new ioctls to get	and set	custom baud rates are  defined
	  here:
	  #define DIGI_SETCUSTOMBAUD (('e'<<8) | 106) /* Set custom baud */
	  #define DIGI_GETCUSTOMBAUD (('e'<<8) | 107) /* Get custom baud */

	  Keep in mind that the	ioctls do not know the valid range of baud rates
	  supported by each unit, and will let you set the baud	rate to	values
	  that are unsupported by that port.

	  In the examples below, the variable fd is the	file descriptor	of a
	  RealPort tty device that is currently	open by	the calling process.




				     - 3 -






	  {
	  int speed, check;

	  if (ioctl(fd,	DIGI_SETCUSTOMBAUD, &speed))
		  {
		  fprintf (stderr,"ioctl DIGI_SETCUSTOMBAUD fails: errno =%x0,errno);
		  }
	  if (ioctl(fd,	DIGI_GETCUSTOMBAUD, &check))
		  {
		  fprintf (stderr,"ioctl DIGI_SETCUSTOMBAUD fails: errno =%x0,errno);
		  }
	  }















































				     - 4 -