If you are using FTP command to transfer files from a RI System to a FTP server, you may encounter file corruption if you fail to use "binary" mode. Using an alternative FTP client that default to binary mode is recommended.

nftp-1.72.zip

name=Anyone
code=YQSQ8hJ64U2lD0BY6fH4FS

To register your copy of NFTP, please do the following:

1) Start NFTP, select "Options" submenu, then "Registration code".

2) Small window with two entry fields will appear. Type your registration name and code into the entry fields. Make sure you do *not* enter any quotes around the name/code. You can switch between fields with Tab or up/down arrow keys.

It is always safer to use cut-n-paste instead of retyping to avoid errors; when underlying platform supports it (OS/2: VIO, PM, X11; Unix: X11; Windows), Shift-Insert will paste clipboard contents into the entry field. On platforms where NFTP does not support clipboard natively (OS/2 xterm, Unix console/xterm, BeOS), you can usually use OS-provided means to paste clipboard contents into the entry fields.

3) When done, press Enter. NFTP should display a window with message: "Thank you for registering NFTP!". Select "OK" button or simply press Enter. If you will ever want to check whether NFTP is running in registered or unregistered mode, open "Help" submenu, then select "About NFTP...".

1. Requirements are
• OS/2 2.x or later;
• TCP/IP stack: IBM TCP/IP 2.0 for OS/2, OS/2 Warp 3.0 Connect, OS/2 Warp 3.0 Internet Access Kit, OS/2 Warp 4.0, TCP/IP 4.1;
• HPFS formatted drive (for installation and downloading files which are not 8.3-compliant).
• In addition, you also have to install the emx runtime package. Make sure your emx runtime is at 0.9d level.
  The EMX runtime package can be obtained from the following anonymous ftp servers:
  ftp://ftp.leo.org/pub/comp/os/os2/leo/gnu/emx+gcc/
  hobbes.nmsu.edu/pub/os2/dev/emx/v0.9c/
  crydee.sai.msu.ru/pub/comp/os/os2/leo/gnu/emx+gcc/
  EMX runtime support is contained in the file emxrt.zip; instructions on installing it can be found inside the archive.
2. Installation. Unpack archive nftp*.zip into some directory. You can also unpack it into the directory where it will reside. Run install.cmd. After answering some questions necessary files will be copied to the directory you specified and your WPS desktop will contain an NFTP folder. Inside it you'll find "NFTP" (executable), "NFTP Manual" and other icons (most of which are self-explanatory). You have probably already done that, since you're reading the "NFTP Manual".
If you want to install NFTP manually (without install.cmd), copy all files into the directory of your choice (eg, "d:\apps\tcpip\nftp"), rename nftp.i to nftp.ini, load it into your favourite ASCII text editor (eg, TEDIT shipped with Warp) and insert your e-mail address (it will be used as a password for anonymous logins) at the appropriate place:

anonymous-password=



Then decide where you will keep your bookmarks and transfer history and set corresponding variables accordingly. If you like to launch programs from the desktop, create program object for NFTP. Rename the supplied nftp.bm file to nftp.bmk and put it into the directory which you've specified in nftp.ini. BMKCONV.CMD can be used to convert old bookmarks file (nftp.mrk) into new format (nftp.bmk).

install.cmd creates a Workplace shell object to run NFTP. This feature can be useful even you are a die-hard command-line user (see below). NFTP can run in a fullscreen session or in a VIO window. The installation script sets it to run in a window which will not be closed automatically after exit -- this can help to diagnose problems. You may change the session setting to "Close window on exit" once everything works as expected.

If somehow the WPS NFTP folder gets lost, you can create it again with makeobjs.cmd.