“The technical support team at Century Software was an integral part in making everything work for us. We were very pleased with the interest they took in our project. They even followed up by calling us for a status of how things were going in the installation process.”
— Dallas Pilcher
Archive for the 'File Transfer' Category
Thursday, October 11th, 2012
TinyTERM for Mac does not have file transfer capabilities. Century Software has received a request to add this capability.
CR 1061, ZMODEM protocol
Monday, April 9th, 2012
In TinyTERM Plus 4.7.0, opening a saved configuration file in SecureFT causes it to crash with the message, “SecureFT has stopped working.” This can also happen when saving a configuration.
CR 998, fixed in version 4.7.2, 15 March 2012
Wednesday, August 3rd, 2011
Using SecureFT, the Century FTP graphical client, a remote directory with a sufficiently large number of files will not open. Because the files won’t list, they can’t be downloaded to a local directory.
Wednesday, October 28th, 2009
When using the FTP file transfer option in the TinyTERM emulator, the progress bar doesn’t update. It stays at 0% throughout the transfer.
Thursday, February 21st, 2008
Using TERM-to-TERM server mode transfer, download a file to your Linux PC. Nothing transfers. The same is true for uploading to TERM in server mode using term -1x or term -2x. Both manual and scripted file transfers fail. This works using TinyTERM connecting to Linux.
Tuesday, May 15th, 2007
Some versions of TERM and TinyTERM for Windows include the EMAIL file transfer protocol. This allows you to send files via email.
To set up an email transfer, open the Transfer File(s) dialog. In the File Name field, enter the full path to the file you want to send, or click the folder button next to this line to open a browse window.
Once the file is selected, enter the recipient’s email address in the Destination field. Set the Transfer Protocol to EMAIL.
If you set the Transfer Type to ASCII, carriage return/line feed pairs will be converted to single line feeds. This will happen whether you’re sending a text or binary file, so choose the type according to the file you’re sending.
Click the Email button next. In the Email Server line, enter the hostname or IP address of the outgoing email server. Set the Username and Password to your username and password on that server. Set the Email Address to your return address. The Subject line should be self-explanatory.
Click OK to return to Transfer File(s). Click the Send File button to send the email. Any replies will go to the email address specified above.
Thursday, May 10th, 2007
Flow control issues in file transfer can manifest several different ways in a TERM-to-TERM environment. CRC errors typically occur. Often a file can only be transferred one direction. Only a portion of the file transfers, or perhaps none at all. There are several troubleshooting steps:
- Make sure you have selected the same protocol on both sides.
- Login to the remote system and put it in the server mode appropriate to the protocol. Server mode is invoked with
term -1x for WTERMCRC, or
term -x for TERMCRC.
- Initiate the file transfer by doing an XFER or GET. Enter the complete path in the source or destination directory, or use a period . for the default directory. Transfers from UNIX to DOS require that file conversion be turned on as well.
- If you still cannot transfer the file, you may have flow control problems. You may have to turn flow control off, location by location, beginning with your modem if possible. Flow control is turned off in each modem differently, so see your modem documentation.
- The next location to turn flow control off is in TERM itself. This is done by editing the .termsys file in the user’s home directory or the C:\Term directory. Add the following entry in the “!file transfer” section:
This must be done in TERM on both sides.
- If the file will still not transfer, try turning flow control off at the unix ports themselves. The UNIX command
stty -a display the “ixon,” “ixany” and “ixoff” flow control parameter settings. The command
stty -ixany will turn off “ixany,” and the command
stty ixany will turn it on. You will need to experiment with various combinations of these flow control parameters.
Thursday, May 10th, 2007
The Wollongong TCP/IP stack included with TinyTERM Plus NFS for DOS includes an NFS client that allows a DOS PC to use UNIX printers. To print using NFS, Wollongong TCP/IP must be running. It then requires the following steps:
- At the DOS prompt type NFS, then press Enter. If NFS has been installed correctly, the following screen will be displayed:
Century Client NFS for DOS (Version 2.0)
Copyright (C) 1990,1993 The Wollongong Group.
If the above lines are not displayed or an error message is received, check the NFS installation guide and try again.
- The host system must be running version 2 of the pcnfsd daemon. To confirm this, log into the host and run the following command:
This program can usually be found in the /usr/etc directory. If you can not run this program, you may not have permissions. Talk to your system administrator to use this program. Assuming you can run the above command, you will see a screen similar to the following:
program vers proto port
100000 2 tcp 111 portmapper
100000 2 udp 111 portmapper
150001 1 udp 1028 pcnfsd
150001 2 udp 1028 pcnfsd
150001 1 tcp 1024 pcnfsd
150001 2 tcp 1024 pcnfsd
100003 2 udp 2049 nfs
100005 1 udp 1027 mountd
100024 1 udp 1042 status
100024 1 tcp 1025 status
100020 1 udp 1050 llockmgr
100020 1 tcp 1026 llockmgr
100021 2 tcp 1028 nlockmgr
100017 1 tcp 1027 rexd
100021 1 tcp 1029 nlockmgr
100021 1 udp 1062 nlockmgr
Under the program column you will be looking for the number 150001. Under the vers column you will need the number 2. You must have pcnfsd version 2 in order for the NFS services to work. Versions 1 and 2 can run in conjunction. If you only have version 1 running, you will have to upgrade to version 2 on your host.
- Determine which hosts on your network are running NFS services. To do this, type the following:
This command may take a few seconds to process, depending on the number of servers available and the current network traffic. It will return a screen similar to the following:
4 servers available on your subnet.
If no servers are available, talk with your network administrator.
- Next you will need to see which servers, if any, have print services available. To do this, use the
/l option along with the hostname in question. For example:
mount /l century
A screen similar to the following will be displayed:
NAME DEVICE LOCATION
---------- ------------ ---------------
epson1 /dev/lp0 Local
Note that the sunprint line above doesn’t show a device. On some systems this is normal.
- You are now ready to mount an NFS printer. In the example above, you might enter the following at the DOS prompt:
mount lpt1 century:/sunprint user passwd
In the above example the host is century, the printer is sunprint device, the username is user, and the password is passwd. If auth had been run, it would not be necessary to add the username or password, although doing so would not cause any problems.
If all went well, you will see a line similar to the following:
Device lpt1 redirected to \century\/sunprint successfully
If you get “permission denied” or “invalid path” when mounting the printer:
- Using the rpcinfo command outlined above, verify that pcnfsd version 2 is up and running on the NFS server.
- Verify that the spool directory has been exported by looking for /usr/spool/pcnfs (or higher) in the /etc/exports file.
- From the DOS prompt, type
mount /e servername. You should see /usr/spool or higher directory exported.
- Verify that you can mount /usr/spool and that you have permissions of 777 by copying a file to /usr/spool. On some systems the directory will be /var/spool instead.
- From the DOS prompt execute PWSETUP and select View Current Settings. Make a note of the PC’s IP address, the user id and hostname of the PC. On the server, verify that the PC’s hostname is in the /etc/hosts file.
- Finally, if you have any logical links to /usr/spool, verify that the linked file as well as /usr/spool is also exported.
Wednesday, May 9th, 2007
The NFS Server may be set up for individual users or groups and may be used to set up directories to be exported, including permissions for files included. The server itself must be set up, as well as the users and groups for the server. Detailed explanations follow for each item on the NFS Server main screen.
To initiate NFS Server, select the Network Shared Files icon from the Century program group. The following steps are required for initial setup of the NFS Server. Detailed explanations for each of the options are in the “Guided Tour” section of this document:
- Set up the Log File that will record NFS Server events. This includes startups and transfers. From the NFS Server main screen, go to the Options menu and select Log File Setup.
- The server itself may be customized for various options. These options include turning the server on, starting the server minimized, packet size of transfers, whether or not the files will be transferred in UNIX format and whether or not the server will act as an authenticator for the network.
- The group(s) that will be allowed access to the NFS Server must then be set up. When users are set up, the group the user belongs to must be entered as a valid NFS Server group. The user as well as the group the user belongs to will determine permission rights to files exported using the NFS Server. From the Options menu, select Setup Groups.
- Set up the individual users that will have access to the NFS Server. From the Options menu, select User.
- The directories to be exported must then be entered. These directories may be changed as often as necessary. In addition, user permissions for the directories may be changed as necessary. From the Options menu, select Setup Exports.
After initializing NFS Server, the following selections are available:
- Log to File
- Log File Setup
- Setup Server
- Setup Users
- Setup Groups
- Setup Exports
Log to File
This item works as an on switch for the Log File. If a check is placed on this item, events occurring on the NFS Server will be recorded in the Log File. Without a check mark, events will not be recorded. To have the ability to change this option, the Log File must be set up first.
Log File Setup
This option sets up the file where events in the NFS Server are logged. After selecting this option, enter the desired directory and file. If the name of the file or the path name is not known, click Files. You can then browse for the file.
Usually a .tmp (temporary) file is used for log files. This file will need to be maintained by manually clearing the entries to the file.
Events logged to this file include such items as file transfers, startups of the server, daemon functions and other NFS functions. The history may then be reviewed as required.
Changes may be made to server operation here. The following are detailed descriptions of each of the options available:
- Server On
This checkbox will turn the server on and off. Click this box if the server should be initialized on startup.
- Start Minimized
This option determines whether the server will be initialized as a full window display or if it will be minimized at startup. Place a check in this box if the server should be minimized at startup.
- Preferred Transfer Size
The size of the read/write blocks may be changed as required. Select the desired size from the pull down list.
- Export Mounts in UNIX Style
If the files exported from the erver should be formatted for UNIX, place a check in this box. When files are viewed in UNIX format, clients will see the exported directory as /c/tmp rather than C:\tmp, for example.
- PCNFS Daemon On
Place a check in this box if the server should act as an authenticator for the network.
- Port Mapping Daemon On
This checkbox must be selected as on if the Server On option is checked. This determines if the server is running on a port.
Users must be set up on the server to be allowed access. Select Options | Setup Users to display the Setup User dialog box:
- User Name
Type the username that will be allowed access. To delete a user, click the Remove button after selecting the username.
Type the password for the user. This will be required when the user is attempting to access the server.
Type a User Identification (UID) number, or click Create Unique ID to have the UID created automatically. The UID will be used when transferring files to or from a UNIX machine. UNIX determines read, write and execute privileges from the UID. If the UID entered for the user does not allow privileges to the files specified to transfer, the transfer will not complete.
Type the Group name or select the correct group for the user from the pull down list. The group the user is assigned to will be used in conjunction with the actual user name to determine read, write and execute privileges.
- Secondary Groups
The user may be assigned to Secondary Groups to allow additional permissions for the individual. Implement Secondary Groups by clicking the Change button. Highlight the desired Secondary Group from the list displayed and click the Accept button.
Groups must be set up prior to setting up users. The group name and group ID entered in this option will determine the privileges allowed to users assigned to the group. Select Options | Setup Groups:
- Group Name
Type the group name to be added, changed or removed. If the group name entered should be removed, click on the Remove button.
- Group ID
Type the Group ID for the name entered. The group ID entered will determine file privileges allowed to users assigned to this group. The group ID should be consistent with the group ID of files that will be transferred to or from the UNIX machine. If the group ID does not match the permissions set for the file(s) transferred, the transfer will not be completed.
Entire directories or specific files within the directories may be specified for export. Select Options | Setup Exports:
Type the full directory path to export or select the desired directory from the pull-down list.
Select the username from the pull-down list. The permissions for the user, the group the user has been assigned to, as well as the permissions for Other will be displayed. The permissions may be changed as necessary for the export.
Wednesday, May 9th, 2007
Plus[NFS] and Simply[NFS] include an NFS client capable of mounting any NFS server. It runs on both Windows 3.1 and Windows 95.
Windows 3.1 or Windows for Workgroups 3.11
To access the NFS capabilities from Windows 3.1 or Windows for Workgroups, run File Manager. From the Disk menu, select Network Connections and click the Browse button. You are then able to add an NFS server, after which the mountable directories will be displayed.
Multiple Networks with Windows 3.1 or Windows for Workgroups 3.11
Windows 3.1 allows only one network driver to run at a time. Windows for Workgroups allows only two. If you need to run a network s) such as Novell NetWare or Windows NetBEUI in addition to Century NFS, you must run the THIRDNET.EXE program found in the Century directory:
- Make sure the other networks are set up and running correctly. Make a backup copy of the SYSTEM.INI file in your Windows directory.
- Load Century NFS and allow the installer to replace the Network in Windows 3.1, or the Secondary Network in Windows for Workgroups.
- Edit the SYSTEM.INI in a text editor such as Notepade. Replace the Network.drv= line with the driver indicated in the backup SYSTEM.INI. In Windows for Workgroups, replace the Secondnet.drv= with the indicated driver.
- Create an icon for the application C:\CENTURY\THIRDNET.EXE and put it in the StartUp program group.
- Restart Windows. The Century Thirdnet dialog will appear. Check the Show this message only once box and click OK. Double-click the Century Thirdnet icon and click Connect. Follow the prompts to connect to NFS drives. You will need to close and re-open File Manager before you can see newly mounted drives.
Please be aware that if you use THIRDNET.EXE, you will be unable to access remote LPR printers via Windows Print Manager. You will still be able to access them via Century Network Printing.
In Windows 95, the NFS client is not automatically installed. To install the NFS client, install TERM Professional, Simply[NFS] or Plus[NFS]. Make sure you install the following components: “Century File Sharing (NFS),” “Terminal Emulator,” and “TCP/IP Network Applications.” After the machine reboots, follow these instructions:
- From Control Panel, select the Network icon.
- From the Network dialog, select the Add button, then click Client.
- Select Century Software, Inc. from the Select Network Client list. Click the Have Disk button.
- Specify the directory where Century software was installed, or click Browse to find the directory, then click OK. You will then be returned to the Windows 95 Network dialog.
- Select Century NFS, Century Software, Inc. and click the Properties button. Type your username, password and PCNFSD host name in the indicated boxes. This step allows your PC to be recognized by NFS servers on your network.
- Type the name of an NFS server in the New Server box and click Add Server. Click OK until you exit the Network dialog, then reboot the machine. You may be asked to insert Windows 95 disks during this process. The indicated files may already be installed, in the C:\Windows and C:\Windows\System directories, so it may not be necessary to use the Windows 95 disks.
- Once the system has rebooted, open Network Neighborhood. Go to Entire Network and open NFS Servers. Select the NFS server to mount. Highlight the desired export directory. From the File menu, select Map Network Drive.
Invalid PCNFSD Host
To resolve this problem, set the authentication server must be set to the server’s hostname, not its IP address. If there is no name server or DNS, create a hosts file in the windows directory.
Also, check that the PCNFSD Version 2 is running on the server.
This is usually an authentication issue. One or more of the following suggestions shouuld resolve this error:
- The user name and password in the Century NFS Client Properties must be a valid user name on the system that is to be mounted.
- If the user name is “root,” try a different user. Some PCNFSD daemons consider root permissions the same as “nobody”.
- If the PCNFSD authentication server is different than the server that is to be mounted, verify that the user id for the authentication user is the same on both servers.
- If the exports file on the server is listing only some nodes with permission to mount, verify that the PC is listed.
- If the user name and password is left blank in the Century NFS Client Properties, verify that the Primary Network Logon is set to Century NFS (Windows 95 only).
- Verify that PCNFSD Version 2 is running on the server with the udp protocol.
- Make sure the user is not cancelling the Windows login. If the user name and password are not entered when Windows is started, there will be an authentication problem. Windows has not been told who the user is or the password for the user.
Make sure the user name and password are correct. If the name or password has been changed, Windows will need to be restarted.
Unable to see exported Directories/Drives
Use the hostname, not the IP address for the server in the NFS setup. Then verify the server name. Also, verify that the directories have been exported.
Also, check the hosts file to make sure that there are only entries for the IP address and the hostname. Any other alias, etc., should be removed from the file.
The Local Device type and Network resource type are not the same
Open Windows Explorer and double-click the NFS export. Do not attempt this in Network Neighborhood.
Updating Century NFS in Windows 95
If you are installing an updated version of Century NFS in Windows 95, we recommend that you follow these steps:
- Go to Control Panel | Network and remove Century NFS.
- Delete the following files from your C:\Windows\System directory: MAR_INET.EXE, MARLOG32.DLL, MARMON32.DLL and NCDMFCX.DLL. You may need to restart Windows in DOS mode and delete the files there.
- Reboot the PC, then install the new version. Once the system has restarted after the install, check the C:\Windows\System directory. Verify the above four files are there, and make sure they’re all dated 6/19/1996. If necessary, copy them manually from the C:\Century directory.
- Return to “Installing NFS in Windows 95″ above.