Here is the official word from the SSH people back earlier this month. I had missed it the first time around. Hope that helps explain it. Mr. Babcock, thanks for pointing me in the right direction on finding the original official answer. --Scott Date: Fri, 13 Jul 2001 11:11:15 -0700 From: Stephanie Thomas <[EMAIL PROTECTED]> Organization: SSH Communications Security To: Ian Carter White <[EMAIL PROTECTED]> Cc: SSH List <[EMAIL PROTECTED]>, Greg MacKinnon <[EMAIL PROTECTED]> Subject: Re: SSH 3.0 license files References: <[EMAIL PROTECTED]> Content-Transfer-Encoding: 7bit Sender: [EMAIL PROTECTED] Precedence: bulk Content-Type: text/plain; charset=us-ascii X-UIDL: be483edef7dc8b004ee4d848659a7a79 Status: O X-Status: Hi Ian, Greg, et al., SSH Secure Shell version 3.0 handles licenses differently than previous versions did. Uninstall all instances of SSH Secure Shell using Add/Remove programs. Then go to ftp://ftp.ssh.com/pub/ssh and download the SSH Windows client 3.0 binary found there. SSH Secure Shell Windows client 3.0 (Build 199) and later works the following way: - If the installation package does not contain a license.dat file at all, the software will run in non-commercial mode. For users, the most visible change is that the non-commercial version of SSH Secure Shell Windows Client does not require a license.dat file any more. Previously all non-commercial users had to apply for a license from our ecommerce site. If you downloaded a version prior to Build 199, please discard that binary and download Build 199 instead. If you have a license.dat file in the install path for SSH Secure Shell, please rename or move that file elsewhere so that the software will not attempt to use it. Hope this helps. Best Regards, Steph At 02:33 PM 7/29/01 -0400, you wrote: >and how would i do that? > >by the way.. the funny thing is it worked on one computer.. i mean upgrade >and license isn't complaining
