New or Revised TAs on websco, 970218

New or Revised TAs on websco, 970218

Post by RadleyRob » Thu, 20 Feb 1997 04:00:00



The following problems are addressed in Technical Articles that appeared on
SCO's websco.sco.com site on 970218.

Some of these TAs are new, others are revisions of prior versions.

lli/60:
PROBLEM:  When doing large file transfers using rcp(C) or ftp(TC), this
          error message sporadically occurs:

            Warning SMPW (iobase 0x0000fc00) possible cable fault

          (where the iobase value will depend on where the NIC is configured),
          and the networking subsystem on the server may lock up.  In some
          cases, a reboot may be necessary to clear the hang.

merge/159:
PROBLEM:  The Merge documentation has examples of starting DOS with cron.
          When that is attempted with DOS applications that require a
          graphical screen, or if a MicroSoft Windows application is run
          with cron, this error occurs:              

            INIT_FAIL:dos:ERROR:Could not initialize device 'stdin/stdout'

 
 
 

New or Revised TAs on websco, 970218

Post by RadleyRob » Thu, 20 Feb 1997 04:00:00


The following problems are addressed in Technical Articles that appeared on
SCO's websco.sco.com site on 970218.

Some of these TAs are new, others are revisions of prior versions.

lli/60:
PROBLEM:  When doing large file transfers using rcp(C) or ftp(TC), this
          error message sporadically occurs:

            Warning SMPW (iobase 0x0000fc00) possible cable fault

          (where the iobase value will depend on where the NIC is configured),
          and the networking subsystem on the server may lock up.  In some
          cases, a reboot may be necessary to clear the hang.

merge/159:
PROBLEM:  The Merge documentation has examples of starting DOS with cron.
          When that is attempted with DOS applications that require a
          graphical screen, or if a MicroSoft Windows application is run
          with cron, this error occurs:              

            INIT_FAIL:dos:ERROR:Could not initialize device 'stdin/stdout'

merge/160:
PROBLEM:  Merge documentation has examples of starting DOS with cron.
          When that is attempted with DOS applications that require a
          graphical screen, or if a MicroSoft Windows application is run
          with cron, this error occurs:           ed:

            INIT_FAIL:dos:ERROR:Could not initialize device 'stdin/stdout'

nfs/94:
PROBLEM:  The following error messages may be seen on the console or in
          the syslog file:

 WARNING: NLM: RPC call failed: RPC error: RPC_CANTRECV, errno 22
 WARNING: NLM: RPC call failed: RPC error: RPC_PROGUNAVAIL, errno 118
 WARNING: NLM: no memory for client's address in nlm_blklock,
               lock request dropped
 WARNING: NLM: unlock request to server <IP> failed: RPC_CANTRECV

          Shortly thereafter, the system may panic with the message:  

 PANIC: k_trap - Kernel mode trap type 0x0000000E

          Crash dumps indicate panics in klm_lock and in nlm_runblklcks.

nfs/95:
PROBLEM:  I want to know how to tune NFS to run an optimum number of
          nfsd and biod daemons.

os/2674:
PROBLEM:  When I type uname(C) on an SCO UNIX Release 3.2v4.x, the node
          name of the machine is returned. The same command on an SCO
          OpenServer Release 5.0 returns "SCO_SV" and not the machine node
          name.

tcpip/441:
PROBLEM:  I would like to hide the hostname in the origin (From:) line
          of my mail address using sendmail.  

tcpip/442:
PROBLEM:  The SCO OpenServer 5 or Internet FastStart system is mysteriously
          losing entries from the /etc/services file which causes these
          services to become unavailable.

tcpip/443:
PROBLEM:  The libsocket library for SCO UnixWare Release 2.1.1 has problems
          that impact the access and transfer of files.

vision/141:
PROBLEM:  Identifying components of XVision licensing.

vision/142:
PROBLEM:  The documentation on XVision Eclipse 7.0 licensing is unclear.
          When customers open their XVision Eclipse 7.0 box, they find
          documentation that says:

                This product does not require a License (serial) Number
                or License Code (activation key) for installation.  
                Please refer to the enclosed documentation and release
                notes for detailed installation instructions.

          However, during the installation process the user is prompted to
          enter a license number.

vision/143:
PROBLEM:  Connecting to a VMS host with the Remote Program Starter returns
          this error message:

                  Network error

          If the Connection Monitor is invoked during the connection (by
          holding down the <Shift> key while pressing "Run"), the trace
          shows the following:

                     11/12/96 11:08:41 Message: Loading script file
                     11/12/96 11:08:44 Message: Begin script playback.
                     11/12/96 11:08:44 Message: Calling function 'DOEXEC'
                     11/12/96 11:08:44 Message: DOEXEC
                     11/12/96 11:08:45 Status:  Executing the command
                     11/12/96 11:08:45 Message: Setting terminal type
                     11/12/96 11:08:46 Message: End of function 'DOEXEC'
                     11/12/96 11:08:46 Error: Network error
                     11/12/96 11:08:46 Message: Script operation complete.

          If the Remote Program Starter is run with "SET VERIFY" enabled on
          the VMS host, the log shows:

                      S_COMMAND = "."
                      S_BURTON  job terminated at 10-JAN-1997 23:41:17.17

          That is, the command is not being sent to the VMS host.