WHAT'S NEW IN KSP-DVMX


     1.4:  Bug  Fix:  Found  a bug in the initialization code where it
           tries  to  locate  an existing Quarterdeck XDI driver; this
           bug  would  sometimes cause DESQview to crash on startup if
           KSP-DVMX  had  already  been  installed,  depending on what
           other Quarterdeck device drivers were loaded.  Corrected.  

     1.3:  Bug  Fix:  Broke  IP address comparison when adding support
           for broadcast addresses of all 1's; corrected.  

     1.2:  Bug  Fix:  Broadcast  packets with an IP address of all 0's
           were  handled  properly  by KSP-DVMX, but not those with an
           IP address of all 1's; corrected.  

           New  Feature:  All  of  our  software  is now available via
           anonymous   ftp   at   "scizzl.scu.edu",  directory  "ksp".
           Please note that there is no "e" at the end of "scizzl".  

     1.1:  Bug  Fix:  Usage summary displayed when run with /? or HELP
           incorrectly    listed   "PVECTOR"   option   as   "VECTOR".
           Corrected.  

           Enhancement:  Improved  performance on 386 and better cpu's
           by use of PUSHA, POPA, and MOVSD instructions.  

           Enhancement:  Now  erases  screen  when terminating monitor
           option.  

           Enhancement:  To  reduce  cpu load, the MONITOR update loop
           has  been  revised  to  give  up  the remainder of its time
           slice at the end of each pass through the loop.  

           Enhancement:    KSP-DVMX    extracts    and    records   an
           application's  IP  address  from its outbound packets; that
           address  is  used later to determine who should be given an
           inbound  packet.   KSP-DVMX  did  this  on  EVERY  outbound
           packet;  one  corrupted  outbound  packet (containing a bad
           source   IP  address)  could  thus  prevent  KSP-DVMX  from
           properly  handling  the  next  inbound  packet arriving for
           that application.  

           This   situation   cannot   occur  for  most  applications.
           However,  KSP-SLIP simply repackages IP packets it receives
           on  the  serial  line  and  retransmits  them  as  Ethernet
           packets;  since  errors  do  sometimes  occur during serial
           transmission,   it   was  possible  for  KSP-SLIP  to  give
           KSP-DVMX  a corrupted outbound IP packet.  This is not true
           for  ARP  packets  since they do not travel over the serial
           line,  but  rather  originate within the door.  (Note: This
           phenomenom   was  observed  using  the  MONITOR  option  of






                          WHAT'S NEW IN KSP-DVMX


           KSP-DVMX.) 

           KSP-DVMX  now  extracts  and  records  an  application's IP
           address  from  only  its  FIRST  outbound  IP  packet, thus
           eliminating   the  possibility  of  later  corruption.   In
           addition,  KSP-SLIP  version  2.1 was modified to originate
           its  first IP packet from within KSP-SLIP, rather than as a
           repackaged  packet  that  had been received over the serial
           line.  

     1.0:  Initial release.