Cardinal Internet Access Solutions/Cardinal_Internet_Access_Solutions(1996-08-19).iso/files/internet/slipnet/slipnet.z/WSARCH07.TXT

Text File | 1994-11-17 | 5.5 KB | 135 lines

This is the seventh ALPHA version (V0.7) of a windows based archie client. The
major changes from the previous release are as follows:

1.  Edit Menu:  It is now possible to copy search results to the clipboard.

2.  When using file retrieve the FTP command will be displayed in an Edit box,
    so that you can alter it prior to executing it.

If you have problems
====================

Do please tell me of any problems via email ([e-mail]).
I'm currently working full time on a 9 month contract 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 ([e-mail])

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.


Installation.
=============

This instructions assume that you have some form of WINSOCK installed and
working and that you are using Windows 3.1.

I use Peter Tattam's Trumpet Winsock. It's shareware and has SLIP built in
and can be found at the follwing sites:

ftp.demon.co.uk:/pub/ibmpc/winsock/stacks/trumpwsk/twsk10a.zip
ftp.sunet.se:/pub/pc/news/trumpet/winsock/twsk10a.zip
tasman.cc.utas.edu.au:/pub/pc/news/trumpet/winsock/twsk10a.zip

I mention this winsock as it is the only one that I've tried this with and
it might not work with others, although theorectically it should.

1. Unzip wsarchie.zip in a directory by itself. There should be three 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.
wsarch07.txt    - this file
dispmsg.exe     - a trace display program, which if running at the same time
                  as wsarchie will display various traces as wsarchie performs
                  searches.

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.

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).

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.

Good Luck

David Woakes ([e-mail]).