This is the first non beta version (V1.0) of a windows based archie client. There are two changes from the previous release (V0.8) The changes are: 1) If the ftp fails, more detailed error messages are displayed. 2) A bug that caused directory expansion to fail sometimes has been fixed. If you have problems ==================== Do please tell me of any problems via email (david.woakes@dial.pipex.com). Please do not send queries about WSARCHIE to any other email addresses. I'm currently working full time so I have less time to spend on this than previously. As a result I may not get back to you straight away, but I will do my best. David Woakes (david.woakes@dial.pipex.com) Credits: This archie client is based upon the archie client that is included in the Prospero V5.2a release. It was written by Clifford Neuman with changes by Brendan Kehoe and George Ferguson. If you want to know more about Prospero send an email message to info-prospero@isi.edu. Do not send questions about WSARCHIE to this address, send them to david.woakes@dial.pipex.com, PLEASE. Keep an eye on my WWW home page for latest releases: http://dspace.dial.pipex.com/town/square/cc83/ Installation. ============= This instructions assume that you have some form of WINSOCK installed and working. 1. Unzip wsarchie.zip in a directory by itself. There should be four files altogether: wsarchie.exe - this is the program itself. wsarchie.hlp - this is wsarchie's windows help file. This should probably reside in the same directory as wsarchie.exe. wsarchie.ini - contains the list of archie servers, and user preference settings. This file can be left in wsarchie's working directory or placed in c:\windows. wsarch10.txt - this file 2. Use the FTP Setup command in the Options menu to setup the command line for the FTP client. This is a non essential step, but is useful. Note that the FTP command is the full path and name of the FTP program in use. The directory is the directory where you want files to be downloaded to. If the ftp command doesn't work, check that you have got a hold of a recent copy. See below for details. That's it. As long as wsarchie.ini is in wsarchie.exe's working directory everything should go swimmingly. You can add an icon in a program manager group in the usual fashion (ie drag wsarchie.exe from the file manager to the desired group, or use {file, new} from the program manager menu). The icon is derived from the Winsock icon. To use, enter your search term in the "Search for" field, and then press return, or select the Search button. If things go successfully then you should see the title bar change informing you of packets being recieved. When complete the results will be displayed in the host, directories and files list boxes. Full details of the selected file will be displayed below. Note some archie servers seem to give fewer details than others. To change the default Archie server use the Option Menu command User Preferences. A dialog will be displayed, currently this allows default archie client and default search type to be set. The domain box can be used to limit the sites that the Archie Server will consider during it's search. The following is the list of known problems with wsarchie and how they can be solved (or not). 1. WS_FTP (16 or 32 bit versions) fail to execute. Get the latest version from either ftp.usma.edu:/pub/msdos or somewhere on 147.51.200.18 (it is fairly obvious if you try). Also check the content of the FTP dialog box. The command line should contain the full command line including the directory that WS_FTP.EXE or WS_FTP32.EXE reside. The Directory box should contain the directory you want files down loaded to. Read the help on setting this up for full details. 2. There is no response from the server, even though you can telnet to it. This is usually caused by a firewall on your site blocking the incoming packets because they are UDP packets. You will need to talk to your network supervisor. Wsarchie (Version 0.2+) uses a non privileged port number above 2050 (the actual number may vary), so there shouldn't be problems with letting them in. Some administrators take a different view and refuse to let these packets in. There is nothing I can do if you cannot get the network administrator to change there philosophy. Try the latest version of wsarchie available from ftp.demon.co.uk:/pub/ibmpc/winsock/apps/wsarchie. 3. You get the message "WINSOCK ERROR: NO_DATA: No entry found". This means that the name server lookup failed. Try using telnet to connect to the archie client. If this succeeds from the same machine then there is a problem with name resolution. If you are probably using Chameleon's winsock, try reducing your list of name servers to one or check whether the latest version fixes this. 4. With PC-NFS V5.1 you will often get the error WINSOCK ERROR: EMSGSIZE. I believe this is caused by an underlying restriction in the winsock stack. There is nothing that I can do about this. 5. With Novell Winsock, an empty error dialog is displayed when a search is started. Hopefully this version should at least display an error number here. 6. With Novell Winsock, searches fail with the error ENOBUFS. Check your net.cfg file. If there are lines in it like: tcp_sockets 32 udp_sockets 8 raw_sockets 1 then taking them out might fix the problem, but will probably restrict the winsock capabilities. I wouldn’t really suggest that you play with these settings unless you are fairly expert on Novell. WSARCHIE may be distributed freely on a non profit basis subject to the licensing agreement from USC below. If you like the software then feel free to send me (David Woakes) 5 Pounds Sterling (or the equivalent in your local currency). This is however optional, and I am not going to chase anyone who hasn't paid up. The address to send your donation to is: David Woakes 88 Spottiswoode St Edinburgh EH9 1DJ I attach a copy of the latest licensing agreement from the University of Southern California: /* * Copyright (c) 1991-1994 by the University of Southern California * All rights reserved. * * PROSPERO(TM) LICENSE AGREEMENT * * 1. COPYRIGHT. The Prospero software is owned by the University of * Southern California and is protected by the United States copyright * laws and international treaty provisions. Other copyrights may * apply to parts of the Prospero distribution and are so noted when * known to be applicable. * * 2. DISCLAIMER OF WARRANTY. THIS SOFTWARE IS PROVIDED "AS IS". The * University of Southern California MAKES NO REPRESENTATIONS OR * WARRANTIES, EXPRESS OR IMPLIED. By way of example, but not * limitation, the University of Southern California MAKES NO * REPRESENTATIONS OR WARRANTIES OF MERCHANTABILITY OR FITNESS FOR ANY * PARTICULAR PURPOSE OR THAT THE USE OF THE LICENSED SOFTWARE * COMPONENTS OR DOCUMENTATION WILL NOT INFRINGE ANY PATENTS, * COPYRIGHTS, TRADEMARKS OR OTHER RIGHTS. The University of Southern * California shall not be held liable for any liability nor for any * direct, indirect, or consequential damages with respect to any * claim by the user or distributor of the Prospero software or any * third party on account of or arising from this Agreement or the use * or distribution of the Prospero software. * * 3. GRANT OF LICENSE. * * a) Permission to use, copy, modify, and distribute this software and * its documentation in source and binary forms is hereby granted, * provided that: * * i) the use, copying, or distribution is not done for direct * commercial advantage; * * ii) any distribution of the software is on the same terms as in * this Prospero License Agreement, and each copy contains the * copyright notices and the license agreement that appear in * this software and supporting documentation; and * * iii) any documentation or other materials related to such * distribution or use acknowledge that the software was developed * by the University of Southern California. * * b) Permission to copy, modify, and distribute this software and its * documentation in source and binary forms AS PART OF ANOTHER * PRODUCT for commercial advantage is hereby granted, provided that: * * i) notice is provided to the University of Southern California * describing the use of Prospero in the product; * * ii) any distribution of the software is on the same terms as in * this Prospero License Agreement, and those terms apply also to * the distribution and use of that part of the product derived * from the Prospero distribution (it is acceptable to * impose additional restrictions on other parts of the product), * and each copy contains the copyright notices and the license * agreement that appear in this software and supporting * documentation; * * iii) any documentation or other materials related to such * distribution or use acknowledge that the software was developed * by the University of Southern California; and * * iv) one of the following three conditions is met: * * a. The product so distributed has been developed * independently and it incorporates only files and related * functions (e.g. allocators) from the Prospero distribution * needed to providing compatibility with the Prospero * distribution; or * * b. the product so distributed has been developed independently * and the parts of the Prospero distribution included * constitute less than 25% of the product, and the total annual * sales of products incorporating Prospero does not exceed * $100,000 (U.S. Dollars); or * * c. parties to which the product is sold or distributed are * allowed to use or distribute the product in source and binary * forms without fee if the party's use or distribution of the * product is not for direct commercial advantage. * * c) Permission to use this software to provide a service for a fee is * granted provided that notice is provided to the University of * Southern California describing the nature of the service and * provided that the total annual revenues for the service provided * using Prospero does not exceed $250,000 (U.S. dollars). * * d) Any use, copying, modification, or distribution other than as * provided for above requires an additional license from the * University of Southern California. The University of Southern * California is prepared to license this software for such use on * reasonable terms. * * 4. OTHER RESTRICTIONS. Nothing in this Agreement shall be construed * as conferring rights to use in advertising, publicity, or * otherwise, the name of the University of Southern California, or * any trademark thereof. * * This agreement shall be construed, interpreted, and applied in * accordance with the laws of the State of California, United States of * America. If any part of this Agreement is held illegal or * unenforceable, the remaining portions shall not be affected. * * Any notice required under this agreement shall be sent to the Prospero * Project; Information Sciences Institute; University of Southern * California; 4676 Admiralty Way; Marina del Rey, California 90292-6695 * USA. Any questions concerning the Prospero distribution should be * directed to info-prospero@isi.edu. * * Prospero was originally written by Clifford Neuman (bcn@isi.edu) while * a graduate student at the University of Washington, and subsequently at * the Information Sciences Institute of the University of Southern * California. Contributors include Steven Seger Augart (swa@isi.edu), * Santosh Rao (srao@isi.edu), and other individuals identified in the * software distribution and accompanying documentation. * * Prospero, the Prospero Directory Service, the Prospero File System, * and the Prospero Resource Manager are trademarks of the * University of Southern California. * */ Good Luck David Woakes (david.woakes@dial.pipex.com).