CPNET       
CPNBOOT     bCPNETLDR    CPNETSTS    xDSKRESET    KENDLIST      !HELP        $>LOCAL       /qLOGIN       2YLOGOFF      8ONETBOOT     ;SNETDOWN     B7NETSTAT     INETWORK     KxRDATE       QGSRVSTAT     TTPA         WXTR          Zy$           $           $           $           $           $           
  ///1CPNET

                        CP/NET ver 1.2

  CP/NET ver 1.2 loads on top of  an existing CP/M 2.2 system to provide
  network capabilities. A variation of CP/NET called CP/NOS runs with no
  local drives, and may be used on  systems where there are no disks. It
  is usually started  by the CPNETLDR, NETBOOT, or  CPNBOOT commands. On
  some systems it  may be started using a network  boot command from the
  system boot/monitor ROM.

  There is currently no way to unload CP/NET, except by cold booting the
  system, typically by  performing a hardware reset  or power-cycle. The
  command NETDOWN should be used to  provide for a clean shutdown of the
  network before performing a cold boot.

  ///1CPNBOOT

  Syntax:

      CPNBOOT {sid} {maps...} {tag}

  Explanation:

  The  CPNBOOT command  loads  and  starts CP/NET  on  an existing  CP/M
  system, using files from the designated server. It must be linked to a
  SNIOS configured for the network hardware in use on the system.

  By default, it maps drive A: to  the server drive A:. The server drive
  A: must have  CCP.SPR in order for  the boot to succeed.  It also maps
  LST: to List  #0 by default. If  maps are given, the  defaults are not
  used. Note,  drive A: must  contain CCP.SPR  and if not  mapped, local
  drive A: must have CCP.SPR on it before booting.

  Maps  are the  simple  form (no  server ID)  of  expressions used  for
  NETWORK.

  Example:

      A>CPNBOOT
      MinZ ASCI1 Network Loader

      BIOS        F600 0A00
      BDOS        E800 0E00
      SNIOS   SPR E500 0300
      NDOS    SPR D900 0C00

      54K TPA

      A>

  ///1CPNETLDR

  Syntax:

      CPNETLDR

  Explanation:

  The  CPNETLDR command  loads and  starts  CP/NET on  an existing  CP/M
  system. It requires the files NDOS.SPR and SNIOS.SPR in order to load,
  and to run CP/NET  the file CCP.SPR must be on  the A: drive (whatever
  A: is mapped to after CP/NET starts). CPNETLDR has no knowledge of the
  network architecture, it requires all files to be local.

  Example:

      A>CPNETLDR


      CP/NET 1.2 Loader
      =================

      BIOS         EB00H  1500H
      BDOS         DD00H  0E00H
      SNIOS   SPR  D900H  0400H
      NDOS    SPR  CD00H  0C00H
      TPA          0000H  CD00H

      CP/NET 1.2 loading complete.

      A>

  ///1CPNETSTS

  Syntax:

      CPNETSTS

  Explanation:

  The CPNETSTS  command displays the requester  configuration table.
  The  requester configuration  table indicates  the status  of each
  logical  device that  is either  local or  assigned to  a specific
  server on the network.

  Example:

      A>NETSTAT

      CP/NET 1.2 Status
      =================
      Requester ID = 02H
      Network Status Byte = 10H
      Disk device status:
        Drive A: = LOCAL
        Drive B: = LOCAL
        Drive C: = LOCAL
        Drive D: = LOCAL
        Drive E: = LOCAL
        Drive F: = LOCAL
        Drive G: = LOCAL
        Drive H: = LOCAL
        Drive I: = LOCAL
        Drive J: = LOCAL
        Drive K: = LOCAL
        Drive L: = LOCAL
        Drive M: = LOCAL
        Drive N: = LOCAL
        Drive O: = LOCAL
        Drive P: = Drive F: on Network Server ID = 00H
      Console Device = LOCAL
      List Device = LOCAL

  ///1DSKRESET

  Syntax:

      DSKRESET {drive(s)}

  Explanation:

  The DSKRESET command functions exactly  like the PRL that executes
  under MP/M II. DSKRESET resets the  specified drive, so a disk can
  be changed. drive(s) is a  comma-separated list of the drive names
  to be reset.

  Example:

      A>DSKRESET P:

  ///1ENDLIST

  Syntax:

      ENDLIST

  Explanation:

  The   ENDLIST   command   terminates  a  listing  by  sending  the
  end-of-job  character  to the current list device. It is typically
  used  on  networked  list  devices  but  may  be  used on any list
  device  that  understands  the  end-of-job  character.  It must be
  used  when  the  list  device is networked in order to release the
  printer  on  the  server  as well as to flush list output that may
  be buffered locally.

  Example:

      A>ENDLIST

  ///1HELP

  Syntax:

     HELP {topic} {subtopic1 ... subtopic8} {[NOPAGE|LIST]}

  Explanation:

  HELP  displays  a  list  of  topics   and   provides   summarized
  information for CP/M 3 commands.

  HELP topic displays information about that topic.
  HELP topic subtopic displays information about that subtopic.

  One or two letters is enough to identify the topics.  After  HELP
  displays   information   for   your  topic,   it   displays   the
  special  prompt  HELP> on your screen,  followed  by  a  list  of
  subtopics.

   -  Enter ? to display list of main topics.
   -  Enter a period and subtopic name to access subtopics.
   -  Enter a period to redisplay what you just read.
   -  Press the RETURN key to return to the CP/M 3 system prompt.
   -  Press any key to exit a display and return to the HELP> prompt.

  Option [LIST] disables the clearing of the screen between pages.

  Option [NOPAGE] disables the pause at the end of a page.

  Undocumented option [CREATE] causes the  file HELP.DAT to be processed
  into a new HELP.HLP. No help topics are displayed.

  Undocumented option  [EXTRACT] is the reverse  of [CREATE], generating
  HELP.DAT from HELP.HLP. No help topics are displayed.

  Examples:

       A>HELP
       A>HELP DATE
       A>HELP DIR OPTIONS
       A>HELP>.OPTIONS
       HELP>SET
       HELP>SET PASSWORD
       HELP>.PASSWORD
       HELP>.
       HELP><cr>

  ///1LOCAL

  Syntax:

      LOCAL local-dev

  Explanation:

  The LOCAL  command enables  a requester  to reassign  selected I/O
  back  to local  from the  network. The  LOCAL command  updates the
  requester configuration table. local-dev is the specification of a
  local device such as LST:, A:,... CON:.

  Example:

      A>LOCAL P:

  ///1LOGIN

  Syntax:

      LOGIN {password}{[mstrID]}

  Explanation:

  The LOGIN  command allows  a requester  to log  in to  a specified
  server. A requester must log in before any resources on the server
  can  be accessed.  Once  a  requester has  logged  in,  it is  not
  necessary to  log in again  even though the requester  might power
  down and then power up again. A requester can only be logged off a
  server by  an explicit LOGOFF  command issued from  the requester.
  password is  an optional  8 ASCII-character password;  the default
  password  is PASSWORD.  [mstrID] is  an optional  two-digit server
  processor ID; the default is [00]. Not all servers require login.

  Example:

      A>LOGIN mypasswd[02]

  ///1LOGOFF

  Syntax:

      LOGOFF {[mstrID]}

  Explanation:

  The LOGOFF command allows a requester  to log off from a specified
  server.  Once a  requester has  logged off,  the server  cannot be
  accessed again  until you  issue a LOGIN  command. [mstrID]  is an
  optional two-digit server processor ID; the default is [00].

  Example:

      A>LOGOFF [02]

  ///1NETBOOT

  Syntax:

      NETBOOT {sid} {tag}

  Explanation:

  The NETBOOT command  loads and starts an OS from  a network server. It
  must  be linked  to a  SNIOS configured  for the  network hardware  in
  use  on the  system.  The actual  type  of OS  depends  on the  server
  configuration and the  optional tag string. Typically,  the default OS
  is CP/NOS  - a CP/NET  OS that uses no  local disk drives.  However, a
  server may be configured to boot another OS image as the default.

  Any existing  OS is completely  replaced by  the booted OS  image. The
  booted  image might  not even  be an  OS, but  could be  a stand-alone
  program.

  Example:

      A>NETBOOT

      COBIOS   SPR  FE00 0200
      COBDOS   SPR  FB00 0300
      SNIOS    SPR  F800 0300
      NDOS     SPR  EC00 0C00

      59K TPA

      A>

  ///1NETDOWN

  Syntax:

      NETDOWN

  Explanation:

  The NETDOWN command  allows a requester to shutdown  its connection to
  the network and all servers.  This allows servers to cleanup resources
  associated with  this requester  and also  ensures that  the requester
  network hardware  is properly  quiesced. This  command should  be used
  before powering off, or resetting, the requester computer.

  In  the case  of CP/NET  3,  this command  unloads the  NDOS3 RSX  and
  returns to non-networked CP/M 3. See also RSXRM.

  In the case of CP/NET 1.2, it  is not possible to unload CP/NET so the
  program stops  and waits for you  to RESET or power  off. Pressing any
  key will resume running CP/NET.

  Example:

      A>NETDOWN
      Ready for RESET/power-off
      (press any key to resume CP/NET)

  ///1NETSTAT

  Syntax:

      NETSTAT

  Explanation:

  The NETSTAT command is a terse  version of CPNETSTS. It only shows
  networked devices.

  Example:

      A>NETSTAT

      CP/NET Status
      =============
      Requester ID = 02H
      Network Status Byte = 10H
      Device status:
        Drive P: = Drive F: on Network Server ID = 00H

  ///1NETWORK

  Syntax:

      NETWORK local-dev=server-dev{[srvrID]}

  Explanation:

  The  NETWORK  command  enables  a  requester  to  assign  selected
  I/O  to the  network. The  NETWORK command  updates the  requester
  Configuration  table. local-dev  is the  specification of  a local
  device such  as A:,  B: ...  P:, CON: or  LST:. server-dev  is the
  specification of a server device such as A:, B: ... P: in the case
  of a disk  device, or 0, 1 ...  15 in the case of CON:  or LST:. A
  missing server-dev  defaults to  0 in  the case  of CON:  or LST:.
  [srvrID] is an optional two-digit hexadecimal server processor ID.
  The default is [00].

  Example:

      A>NETWORK P:=F:

  ///1RDATE

  Syntax:

      RDATE {mstrID}

  Explanation:

  The RDATE command allows a requester to display the time and date from
  a  server. mstrID  is an  optional  two-digit server  processor ID  in
  hexadecimal; the default is 00.

  Example:

      A>RDATE 2
      Remote Time is: Mon 03/08/21 18:00:49

  ///1SRVSTAT

  Syntax:

      SRVSTAT {sid}

  Explanation:

  The  SRVSTAT command will display a CP/NET server's configuration.
  sid is the server ID to display, default is 00.

  Example:

      A>SRVSTAT

      Server Status
      =============
      Server ID = 00H
      Server Status Byte = 10H
      Temp Drive = P:
      Maximum Requesters = 16
      Number of Requesters = 1
      Requesters logged in:
        C9H

  ///1TPA

  Syntax:

      TPA

  Explanation:

  The TPA Command  displays the amount of memory  available for TPA.
  The amount of  memory is a direct translation of  the current BDOS
  entry  page,  including any  active  RSXs.  This  can be  used  to
  determine if RSXs are resident, by  comparing the TPA to the value
  seen immediately after boot.

  Example:

      A>TPA
      57.25K TPA

  ///1TR

  Syntax:

      TR d:{filespec}=filespec[C|U]

  Explanation:

  The  TR Command  copies  one  or more  files  and translates  line
  endings between  Unix and  CP/M conventions.  The option  C causes
  every line feed  character to be prefixed with  a carriage return,
  unless already present. The U  option removes all carriage returns
  from the file. Neither source nor destination drive is required to
  be networked, although  that would be the normal  case. The source
  filespec cannot be ambiguous if a destination filespec in given.

  Example:

      A>TR C:=P:*.ASM[C]
