home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
High Voltage Shareware
/
high1.zip
/
high1
/
DIR35
/
PCUCP101.ZIP
/
USE.DOC
< prev
Wrap
Text File
|
1993-03-31
|
6KB
|
148 lines
Starting the program
---------------------------------------------------------------------
To start pcucp use the command line
pcucp [config file]
where [config file] is an optional argument specifying the
configuration file to be used. The configuration file name
should not include the ".cfg"-suffix, which is automaticly
added. If no configuration file is specfied, the settings
in the default configuration file apply. (For configuration
file details, see CONFIG.DOC.)
In Windows you'll probably want to add pcucp as a program
item in the Program Manager window using the Program
Manager's File/New -command. If you have multiple setups,
it is easiest to create an entry for each, specifying a
different configuration file as a command line argument.
Exiting the program
---------------------------------------------------------------------
Use Options/Exit to exit Pcucp.
Pcucp main window
---------------------------------------------------------------------
The Pcucp main window contains the menus to control Pcucp
run-time operation. Also, the window displays various
messages, such as error messages or messages related to
the progress of file transfer. In the unix-end, these
messages are written to the file pcucp.log in PCUCPDIR.
Connecting
---------------------------------------------------------------------
In addition to the Pcucp main window, an initial terminal
window (Terminal(0)) is created at startup. Use this window
to log in your unix host. After login run the unix
executable of pcucp (possibly with a configuration file name
as command line argument). Provided that no error occurs,
you should quite instantly see a message like :
[pcucp : you have 10 seconds to connect]
Now select Options/Connect from the Pcucp main window. After
a few seconds you should see the message :
connect : connected to <host>
If so, the connection is established. If connection times out,
the configuration files in the unix- and the pc-end are probably
inconsistent.
After the connection, a shell is automaticly executed in the
initial terminal window. If not, the configuration files in
both ends don't probably match.
Disconnecting
---------------------------------------------------------------------
To disconnect, select Options/Disconnect from the Pcucp main
window. After a few seconds you should see the message :
disconnect : ok
The initial terminal window now resumes the login shell.
If disconnecting fails, processes may be left running on
your unix host. If this happens, go check this with the ps
command and kill any uneccessary processes.
New Tty sessions (shells)
---------------------------------------------------------------------
Select Windows/Tty session. A new terminal window with a shell
should appear before long.
Existing tty sessions (shells)
---------------------------------------------------------------------
Active sessions can be brought to the foreground by selecting
the window name in the Window-menu.
Removing Tty sessions (shells)
---------------------------------------------------------------------
The prefered method is to exit from the shell. You can also
close a shell window from the system menu. If you try to
close the initial terminal window, the unix process is killed,
but the window remains. Next time a new tty session is created,
the initial terminal window is used for the session.
File transfer
---------------------------------------------------------------------
The pcucp uses two directories in both the unix and dos end
for file transfer. One of the directories (OUTDIR) contains
the files to be sent to the remote system, while the other
(INDIR) is used to store the files received from the remote
system.
Pcucp sends the files in OUTDIR one by one to the remote
system and then DELETES the file sent. Hence, if you
want to keep a copy of a file after the file has been sent,
copy the file to OUTDIR. If not, move the file to OUTDIR.
In the unix end, the copying is best done by creating a
(symbolic) link in OUTDIR (ln (-s)). In dos you'll just
have to keep two copies during the transfer.
The file transfer has an automatic restart feature, which
works as follows : If there is a file with the same name as
the incoming file in INDIR and the file times match, the
file in INDIR is assumed to be the starting part of the
incoming file and only the missing part (incoming file size
- INDIR file size) is transfered.
If the file times do not match, the existing file is renamed
by replacing the last character of the filename with a tilde
(~). If a file with this name already exists in INDIR, it is
first deleted.
The file transfer must be explicitly started with Options/
File transfer/start. File transfer can be explicitly stopped
using Options/File transfer/stop. File transfer is automaticly
stopped when disconnecting.
If you want to remove/add/modify files in INDIR or OUTDIR, be sure
to leave alone the file being currently transfered. It is safest
to stop file transfer first to avoid errors.
Note that Pcucp has no BINARY/TEXT file types. All files are
transfered 'as is' without any conversions.
---------------------------------------------------------------------
This file is a part of Pcucp, Copyright (C) 1992 Jouni Leppäjärvi
---------------------------------------------------------------------