HISTORY.TXT Driver File Contents (1800002b.exe)

InterChangeVS(TM) 1000/2000, RocketPort Serial Hub
VS-Link for Windows(TM) NT Operating System

=============================================================================
REVISION HISTORY

v2.35
  9/16/99 - New portmon, peer, wcom, setup, and driver because of changes for Win2000.
    Added the '-f' option to wcom32 for FCC testing.
    Fix where hub would not ignore NULL characters (vslinka.bin).
  8/24/99 - Multiple fixes for problems found while testing for Win2000.  Also fixed the
    problem where the starting COM port would appear with an extra zero,
    COM3/COM30, in the setup program.

v2.34
  8/05/99 - Fix where a VS port was not reporting CTS on.  Open a port, have device turn
    off our CTS, close port, have device turn on our CTS, open port and port
    reports CTS off when it should be on.

v2.33
  5/26/99 - Added RTS toggling to VS.

v2.31
  3/15/99 - Fix event wait cancel handling to avoid potential bug-check
    on wait irp cancel.
    Clean up mdmctm1.inf modem inf file.

v2.29
  2/15/99 - Fix port re-naming problems in setup program.
    Add ClkPrescaler & ClkRate registry options(allows better control
    over non-standard baudrate generation.)
    Reset transmit flow control conditions on port open(avoid problems
    with stuck xoff conditions.)

v2.27
  1/25/99 - Correct spinlock operations which might cause
    dual-proc machine problems.
    Change device object name exported to same as earlier versions.

v2.26.7
  1/21/99 - Fix busted EV_TXEMPTY from V2.26.6 changes.
    Adjust port device names to start at RocketPort0.
    Adjust immediate character write ioctl to generate EV_TXEMPTY.
    Fix peer.exe log traces to include tick count time stamp [#].

v2.26.6
  1/18/99 - Implement WaitOnTx write handling.
  Adjust read Total timeout handling, apply 50ms minimum.
  Adjust device firmware to avoid port data overflow to server.

v2.26.1
  11/23/98 - Minor purge adjustment when WaitOnTx option set.
    Fix setup Wizard to always start on the first page.

v2.26
  11/03/98 - RK updates only
    Convert S37 to binary files.
    Change initial handshaking with Rockwell modems.
    Merge changes for PnP and NT5 into source.

v2.25
  10/23/98 - Fix potential transmit data corruption under some circumstances.
  Fix setup to rename itself to setupold.exe on driver uninstallation
  to avoid problems installing older driver version.

v2.12
  9/24/98 - Adjust device code to lower data latency.
  Add wait on tx-data on port-close for VS.
  Adjust port close to use configurable wait on tx timeout.
  Add modem hardware RING Emulation port option.
  Adjust setup to startup driver on setup-exit during initial install.
  BugFix for occasionally dropped single byte of tx-data.

v2.08
  7/28/98 - Implement tx-data tracking in device which allows more accurate
  reporting of tx-data data levels.

v2.07 - Internal Beta Test Release
  7/28/98 

v2.06 - Internal Beta Test Release
  7/27/98 - Fix setup program so device property pages appear in nt3.51.
  Add unimodem ID to modem inf file.

v2.05 - Internal Beta Test Release
  7/17/98 - Fix, mdmctm1.inf file embedded slash in string problem - RAS
  would fail to open the modem/port for RocketModem selection.
  Fix, setup program now deletes older mdmarckt.inf, mdmvsa1.inf files.

v2.04 - Internal Beta Test Release
  7/15/98 - Fix lock baud(port options) read bug on startup.
    Fix setup program context sensitive help ID problem.
    Fix setup program add-wizard cancel crash.

v2.03 - Internal Beta Test Release
  7/14/98 - Fix dynamic device configuration problems.
    Fix port level configuration option problems(lockbaud, etc)
    Update bitmaps in setup program.

v2.02 - Internal Beta Test Release
  7/9/98 - Updated MdmCtm1.Inf with new ModemIDs
  Added support for RocketPort Serial Hub
  Cosmetic changes to setup program
  Occurances of VSLink changed to generic Device or
    VS1000/VS2000/RocketPort Serial Hub
  Added code for VS2000 international settings (not enabled)

v2.00 - Internal Alpha Test Release
  7/2/98 - Common code base with NT5 and RocketPort/RocketModem drivers

v1.18
  6/2/98 - More Citrix modem.inf changes.
  Fix problem with AutoSelect comport number on devices other than first.
  Naming changes for VsReset utility in group and program.
  Skipped rev 1.17 to pull driver and setup versions into sync.

v1.99 - Second internal alpha release of changes.
  5/28/98 -  New are options processing, modem reset page,...

v1.16
  5/11/98 - VS2000 modem reset support added, including VsReset utility.
  Changed S95 register value in VsaMdm35.inf to fix Citrix problem.
  Added new ModemID value to MdmVsa1.inf
  Adjust tx-queue handling to obtain and report tx-level information from
  VS device.

v1.15
  4/1/98 - Add TxHolding report and SETXON,SETXOFF EscapeComm support.
  Change to perform device tx-flush when holding.
  
v1.14
  3/16/98 - VS Recovery fix. If RAS lost box, it would continue
  to see active connections, then on recovery, DSR,CD,CTS input
  signals might not update correctly.

v1.13
  3/12/98 - Minor setup name changes.

v1.12
  2/26/98 - Fix for running VS on other ethernet switch segments,
 previously VS device would not be found.

v1.11
  2/19/98 - Minor changes(Citrix modem.inf install issue and
  Tx-holding light.)

v1.08
  11/05/97 - Fix backup server to handle Device ioctl commands
  from the setup program and to add the backup field to the Registry.
  Add more of the renaming (VS1000 to VSLink) to files.  Changed Setup
  Help screen window title and menu title from InterChangeVS 1000 to
  InterChangeVS.  Add peer.exe to the distribution and install in VSLink
  directory.  Remove tagfile=ntdiskid from inf file.

v1.07.02B
  10/28/97 - Re-organize much of the setup.exe code to
  support vs2000(modem capability) and also provide better code
  compatibility for NT5.0 version.  Add backup server implementation
  where a backup NT server could be arranged to assume control
  if the main server fails.

v1.07.01B
  10/15/97 - Fix NT3.51 setup.exe screen bug with ghost
  window.  Change naming in a number of places(VS1000 to VSLink).
  Re-organize code.

v1.07
  9/25/97 - Fix Port monitor program due to recent change it
    would not connect to driver.

v1.06B
  9/22/97 - Fix potential crash on modem detection.  Add
    support for VS2000(8-port w/modems) device.

v1.05B
  9/15/97 - Allow hot swapping boxes(changing network address
    on the fly).  Fix setup.exe ghost window problem.  Add setup.exe
    capability to query network for mac-addresses.

v1.03B
  /8/05/97 - Update Setup.exe.

v1.02B
  7/07/97 - Fix Portmon.exe(causing system crash),
    adjust portmon.hlp.

v1.00.017B
  6/19/97 - Fix:Setup advanced menu selection not working,
    adjust some setup help doc and screen text.  Some updates to
    driver(should have no effect on operation.)

v1.00.016B
  6/19/97 - Fix occasional timeout error seen in NetBios
    transfer.

v1.00.015B
  6/17/97 - Adjust HDLC packet sequencing and link-integrity
    check to fix error condition seen by testing.  Adjust packet
    timeout down some, to 1.0 second value.
  
v1.00.014B
  6/13/97 - Adjust xon,xoff control char handling,
    adjust setup to handle automated install.  Fix VS1100 LED
    handling(wrong port), take out auto-mac address detect
    feature.

v1.0.012B
  5/13/97  Fixed xon,xoff handling.

v1.0.011B
  5/07/97  Beta.

v1.0.010B
  5/05/97 - Beta, internal testing.

v1.0.002B
  4/16/97 - Beta, internal development.


Download Driver Pack

How To Update Drivers Manually

After your driver has been downloaded, follow these simple steps to install it.

  • Expand the archive file (if the download file is in zip or rar format).

  • If the expanded file has an .exe extension, double click it and follow the installation instructions.

  • Otherwise, open Device Manager by right-clicking the Start menu and selecting Device Manager.

  • Find the device and model you want to update in the device list.

  • Double-click on it to open the Properties dialog box.

  • From the Properties dialog box, select the Driver tab.

  • Click the Update Driver button, then follow the instructions.

Very important: You must reboot your system to ensure that any driver updates have taken effect.

For more help, visit our Driver Support section for step-by-step videos on how to install drivers for every file type.

server: ftp, load: 3.45