NSLink (TM) Driver for the Windows(R) XP, Windows Server 2003, and Windows 2000 Operating System Part # 1800288 ============================================================================ REVISION HISTORY v 4.01 Changes to rpshsi.sys: - Modify interface so Comtrol troubleshooting utility can provide driver with user defined trace pool logging configuration. - Modify code so that if driver is attempting to restart the microcode load sequence because of some sort if interuption during the last load attempt, that it will fail out of code loading to re-establish a connection to the device after a threshold of loading restart attempts has been reached. Changes to ctmproto.inf: Changes to ctmsport.inf: Changes to netctmsi.inf: - Book keeping changes for Microsoft driver signing requirements. v 4.00 Initial release for 64 bit Windows OS support. 32 Bit components are based on Windows XP/2000 Driver (A/N 18000198) version 7.23. The following are the additional changes which have occurred to components since the v7.23 release: Changes to rpshsi.sys: Added enhanced debug for memory debugging and other customer troubleshooting Fix ports ports which stop working after a period by clearing a flag when the current Read is canceled irregardless of whether the pending read request is queued up to complete. Fix occasional Blue Screen exception fault which occurred when uninstalling devices by addin code to traverse TCP extension list to remove any pointers to extensions for MAC addressed devices being removed from the system. Changes to devmast.bin: This version is built with eCos 2 ver 1.87. It also has a change to eCos to fix a data loss/corruption problem caused by DMA pointer. The following SocketServer changes where made to prevent ports to quit receiving data while in socket mode: 1) Increased priority of admin command handlers so that they will run even under heavy CPU load. This prevents Ethernet frame buffers from accumulating in the MAC rx queue (was causing the system to run out of Ethernet frame buffers and stopping data flow). 2) Made SocketServer rx polling period adjustable in "network settings" on web page. Default setting is 50 (milliseconds). This is a good default for 8-16 port hubs, but is too fast for running 20+ ports. With a setting of 100ms, Socketserver can run all 32 ports simultaneously without problems. Added a flag to the ID Reply structure to all PortVision to distinguish DeviceMaster UP from other models. Fixed problem which delayed communication reconnection to device after PC reboots but the device is not reset when driver is using IP mode by ensuring that out of window SYNs receive an ACK response, rather than simply being dropped. Changed the corporate display graphics and added help to SocketServer web page. Changed handling of password entry over a telnet connection to suppress echo back to terminal. Fixed EOL input termination handling in SocketServer UDP handling which cause device to fail TX when input timeout value set to a value greater than 0. Removed fix to lock scheduler so that IP info query would never return bad values when accessing IIC memory because the lock resulted in data loss on DeviceMaster RTS 1 port by preventing data moving thread from being able to execute in time. Changes to netctmsi.inf: Removed RPSH Si 4 and 8 port selection DOCUMENT NUMBER: 8001113Download Driver Pack
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.