Denicomp Systems

  Print This Page
 
 Shopping Cart
   HOME | CONTACT| STORE


Updates are free to licensed users.  Click on Licensed Users above to download the latest version.

News

 

 
Product Updates
This is where we'll announce the most recent software updates that are available, and a history of previous updates. If you've visited us before and want to know what's changed, take a look here first.


April 8, 2006: Winsock RSHD/NT 2.24.00 released.  These releases include the ability to specify a time limit on rsh commands, specify the process priority level of the service and commands, and fixes a problem with large sets of environment variables.


July 10 , 2005: Winsock RSHD/NT 2.23.08 and Winsock REXECD/NT 1.08.06 released.  These releases include a change that occurred with some rsh and rexec clients, where it would appear that the rsh or rexec was hung and output was truncated (usually when the rsh/rexec was issued from a mainframe).  This seemed to occur due to the order in which the stdin/stdout/stderr connections were closed.


March 28 , 2005: Winsock RSHD/NT 2.23.07 and Winsock REXECD/NT 1.08.05 released.  These releases include a few fixes - see the Change Log link on each product's page for details or see the history.txt file included in the download.


October 25 , 2004: Winsock RSHD/NT 2.23.06 and Winsock REXECD/NT 1.08.04 released.  These releases include relatively minor changes - see the Change Log link on each product's page for details or see the history.txt file included in the download.


May 9 , 2004: Winsock RCP/RSH/REXEC Version 2.07.06 is now available.  This version corrects a problem when using the -p option to preserve file modification times.  When file times could be off by one hour, depending on the current status of daylight savings time.


January 3, 2003: Winsock RSHD/NT 2.23.03 and REXECD/NT 1.08.01 are now available.  These versions correct a problem that could randomly occur when two or more nearly simultaneous commands were received.  The message log would show a "connection aborted" TCP/IP error and the error log would show a "Protocol negotiation error".  The client would either appear to be hung or it would time out (depending on how gracefully the client handled it).


November 29, 2003: Version 2.00.01 of Winsock RCP32.DLL is now available.  This new version allows you to programmatically set options affecting the operation of the DLL, such as connect timeouts.  It also allows the use of the rexec protocol for the rcp instead of the default of the rsh protocol.



Finding Your Version
Use this guide to find the product version you currently have on your system:

Winsock RCP/RSH/REXEC
Execute the rsh command at a command prompt with no command line parameters.  The version number will display in the "usage" message.  If you are using Windows NT, 2000, or XP and you don't see "Denicomp Systems" in the usage message, you are executing the native Windows command instead of ours.

Winsock RSHD/NT
Open the RSHD Control Panel applet.  If you have a Service Control tab (not a button), look on that tab for the version number.  If you do not have a Service Control tab, get to a Command Prompt, CD to the RSHD/NT directory (usually c:\wrshdnt), and type "wrshdnt /v" and the version number will display.

Winsock REXECD/NT
Open the REXECD Control Panel applet.  If you have a Service Control tab (not a button), look on that tab for the version number.  If you do not have a Service Control tab, get to a Command Prompt, CD to the REXECD/NT directory (usually c:\wrexecnt), and type "wrexecnt /v" and the version number will display.

Winsock RSHD/95

Get to a DOS Prompt, CD to the RSHD/95 directory (usually c:\wrshd95), and type "wrshd95 /v" and the version number will display.

Winsock REXECD/95
Get to a DOS Prompt, CD to the REXECD/95 directory (usually c:\wrexec95), and type "wrexec95 /v" and the version number will display.

Winsock RCMD32.DLL and RCP32.DLL
Look at the file HISTORY.TXT included with the software.  Look for the highest version number shown.