Beruflich Dokumente
Kultur Dokumente
Version 1.05
Novemeber 6, 1993
By Lindsey Smith
Email: lsmith@symantec.com
I. What is PCFSP?
-----------------
Basically you need a PC that is connected to the Internet and has some
sort of packet driver loaded. Exactly what drivers you need to load
and what other configuration tweaking needs to be done before you can
access the Internet is far beyond the scope of this document. There are
far to many networking operating systems and PC TCP/IP implementations
for me to give you much help in this department. Don't be intimidated
by this, though. You'll proabably just need to talk to your network
administrator before you begin configuring PCFSP. He/she should be able
to get you up and running. Just remember that PCFSP itself is very simple
to configure, it's making your system capable of running PCFSP or any
other Internet access software that can be tricky.
my_ip=192.246.63.98
netmask=255.255.255.0
nameserver=38.145.250.2
gateway=192.246.63.1
The my_ip line should be set to your unique IP address. The netmask
line should be set to the netmask of your LAN's configuration. The
nameserver line should be set to a numeric IP address that will resolve
IP names into IP numbers. And finally, the gateway line should be set
to the address of your Internet gateway.
If gateways and netmasks are Greek to you, don't worry. As I've said
before, your network administrator should be able to fill in the
information for you. It's really not as complicated as it might seem.
Once you have WATTCP.CFG filled in, run the SETFSP batch file. This
file sets the FSP_HOST and FSP_PORT environment variables to usable
defaults. Now run FVER. If your WATTCP.CFG is set properly, then
FVER should first print "[SEISMO.SOAR.CS.CMU.EDU : 21]". If it
does not, there is either something wrong in your WATTCP.CFG file
or the Waterloo TCP/IP library used in PCFSP is incompatible with
your network configuration. Double check your WATTCP.CFG, then try
again. If FVER still doesn't work, contact me at the email address at
the top of the file.
FSP_HOST and FSP_PORT must be defined for any PCFSP command to work.
The SETFSP batch file is a convenient way of doing this.
When you want to change sites, merely change the settings of FSP_HOST
and FSP_PORT at the DOS prompt like this:
C:\>set fsp_host=alpha.gnu.ai.mit.edu
C:\>set fsp_port=21
Whenever you change sites be aware of the fact that the site you want
to access might be down. I recommend that whenever you change sites
that you either run "FVER" or "FCD /" to verify that the site will
respond.
Also be aware that changing sites does not reset the FSP_DIR. This is
another good reason to do an "FCD /" right after you change sites.
where
[-switches] are optional command line switches that modify the behavior
of the command. Switches are combinable so "FLS -l -a" is equivalent to
"FLS -la"
FCAT is similar to the DOS TYPE command. It reads text files from the
server machine and then displays them on your screen. The files are
not saved on your machine as they would be during an FGET.
FCD [directory]
FGET attempts to retrieve files from the server machine. The * and ?
wildcards are expanded.
During the course of PCFSP use you are certain to run into UNIX long
filenames: files that do not meet the DOS limitation of 8 characters,
a dot (.), and a 3 character extension. FGET attempts to "fix" long
filenames into valid, unique DOS filenames. For example if you were
to "FGET Long.File.Name.1 Long.File.Name.2", FGET would create 2
unique files instead of merely overwriting the first file with the
second.
Also be aware of the fact that UNIX filenames are case sensitive, so
READ.ME, Read.Me, and read.me are all different files.
FGET has four, mutually exclusive command line switches that modify
its behavior when it detects that it might overwrite a file that
already exists on your harddrive.
-s Skip the file without overwriting the file that already exists
FLS lists the contents of directories in the same way as the UNIX ls
command. If you are not a UNIX user, ls is an ancestor of the DOS DIR
command. If you do not specify a path, FLS lists the contents of the
current directory. By default FLS displays only the names of files
in the directory and sorts them alphabetically. You can modify FLS's
behavior using the following command line switches.
-A List all entries beginning with a period (.) except for . and ..
Be aware that you may not have rights to create directories on server
machines.
Be aware that you may not have rights to delete files on server
machines.
Be aware that you may not have rights to delete certain directories
on server machines.
FVER
FSP_TRACE
Setting this variable will cause PCFSP commands to print hash marks
periodically during the course of operation so you know that the
operation is proceeding. The marks, the letters 'R', 'I', and 'E', each
have a certain meaning. 'R' is printed the first time the client
listens for a response from the server. An 'I' is printed for each
listen after the first. E means an error has occured and PCFSP will
retry the last operation. You can set (enable) tracing or unset
(disable) tracing with the following commands.
FSP_LOG
If you take a look at the provided SETFSP.BAT there are few ALIAS
commands REM'd out. If you are using 4DOS I highly recommend removing
the REMs and using the aliases. I find they are very handy.
There are two discussion groups at present for FSP. The first is the
alt.comp.fsp Usenet newsgroup and the second is an Internet mailing
list which can be subscribed to by sending mail to
listserv@germany.eu.net.
If you have any ideas or bug reports for PCFSP, drop me a line. All
suggestions are appreciated.
Finally, many thanks to Keith Grimes for all the testing and coding
he has done to PCFSP. Many of features were conceived and/or implemented
by him.