Mitsubishi Electric - Computing for a Connected World Insight CD Home Page

Products
Services
Knowledgebase
Bulletins (IPBs)
Guides
FAQs
Owner's Handbooks
Product Datasheets
Miscellaneous Items
Upgrades
Downloads
Search Insight
E-Mail us
Insight Service
Year 2000
Other Mitsubishi Sites
Site Disclaimer

 
Xenix - Unix I.P.B. 3135 18th September 1992 (PW)
Department Category Implementation
Unix Software On Failure
Previous IPB Next IPB

SCO TCP/IP for SCO UNIX Systems

SCO have just released SCO TCP/IP 1.2.0 for SCO UNIX V/386 3.2v4.1. There are a number of important points to note with this new product and its installation on Apricot equipment.

  1. SCO TCP/IP 1.2.0 is replacing SCO TCP/IP 1.1.3f which SCO has now discontinued. SCO TCP/IP 1.2.0 will only install on SCO UNIX V/386 3.2v4.1 and therefore anyone wishing to install TCP/IP from now on must upgrade their SCO UNIX to 3.2v4.1.
  2. The new product comes with two supplement disks which upgrade the Operating System from 3.2v4.0 to 3.2v4.1, these must be custom installed before TCP/IP 1.2.0.
  3. When upgrading from an earlier release of TCP/IP Runtime, if any of the following are installed, they should be fully removed before starting the installation of TCP/IP Runtime 1.2.0:
    lng321
    lng287
    NFS Maintenance Supplement
    TCP/IP Maintenance Supplement
    NFS Runtime
    TCP/IP Runtime
  4. When upgrading from an earlier release, the Extended Utilities Package "MAIL" should be re-installed before TCP/IP is installed.
  5. The SCO LLI drivers disk must be "custom" installed before the TCP/IP Runtime.
  6. The daemons "rwhod" and "rarpd" are not started by default. You should edit "/etc/tcp" to enable the daemons to allow programs like rwho and arp to function correctly.
  7. You are likely to experience problems using cursor and function keys when using the DOS Workstation Pack utility "tn". The problem can be avoided by using "rloginvt" in place of "tn".
  8. Installation of network cards should now be carried out by using the netconfig command. However at this moment the Apricot on-board e5920 Ethernet driver does not install using this method. It is however possible to install the driver as for TCP/IP Runtime 1.1.3 by running "mkdev e5920" and "mkdev e5920tcp", but the functionality of "netconfig" is then lost.
  9. When running "mkdev e5920" to install the Apricot on-board Ethernet driver you must enter the required interrupt explicitly, entering carriage return to accept the default value will fail with an error. You should only use release 4 or later of the e592 on-board Ethernet driver.
  10. After installing the Apricot on-board Ethernet driver using "mkdev e5920" and "mkdev e5920tcp" pseudo ports must be configured manually, before rlogin and telnet will function. Use "mkdev ptty" to add pseudo ports.
  11. It is possible to configure one 3Com 3C527 card using "netconfig", if the Apricot UNIX Server Environment disk Release 6, e3m package is installed in place of the SCO LLI drivers disk. However any attempts to configure a second card will fail, a new release of the 3C527 driver will remove this limitation.
  12. At this moment in time the driver for the new on-board Ethernet on LS Pro and XEN-LS II is not released. We will clarify the installation of this driver in a later IPB.

Finally, please remember to read the SCO Release Notes for TCP/IP and the LLI drivers disk as these contain a number of useful points.

----------oOo----------

 

Computing for a Connected World