|
Archive for the 'File Transfer' Category
Thursday, April 19th, 2007
These were added to the SecureFT graphical file transfer client in TinyTERM Plus 4.30. They are not available in any emulator.
CR 242, SecureFT
CR 464, request to add SCP to emulator
CR 781, request to add SFTP to emulator
Posted in SCP, SecureFT, SFTP | Comments Off on SFTP and SCP Capability
Thursday, April 19th, 2007
Then NFS server and client included with TinyTERM Plus 4.12 give errors that the license is invalid. The same thing happens in TERM Professional 3.3 for Medical Manager. There is no patch for this.
CR 178, 4.12 fixed in TinyTERM Plus 4.20
CR 362, TERM Professional
Posted in License, NFS | Comments Off on Invalid NFS License
Thursday, April 19th, 2007
When you have two sessions open in TinyTERM 4.12 and do an FTP transfer in one, the transfer succeeds. But when you switch to the other session, you get the error “Error (4558) Set property ‘AutoAddValue’ failed: Invalid object instance.” Also, the Ribbon Bar is lost. There is no patch for this problem.
CR 150, fixed in TinyTERM 4.20.
Posted in FTP | Comments Off on Second Session Errors After FTP in First Session
Thursday, April 19th, 2007
This error comes from the FTGet() command in TinyTERM 4.11. There is no patch or workaround. This was fixed in TinyTERM 4.12.
CR 124
Posted in CScript, File Transfer | Comments Off on Wrong Number of Arguments Passed to Function FTRecvEx
Monday, April 16th, 2007
Most Century Software, Inc., products have file transfer capabilities. They can send and receive files using several common protocols, as well as the proprietary TERMCRC and WTERMCRC protocols. But all the protocols have some common requirements:
- An active connection. FTP transfers create TCP/IP connections on the fly. For any other protocol, you must already be connected to the remote system before starting a transfer.
- A valid source file name and directory path. If the name of the file to be transferred or the directory its in is misspelled, or if the file does not exist in the specified directory, the transfer will fail.
- A valid receive directory. If the directory where the file should go does not exist, the results are unpredictable. A file of the wrong name may be created, a new directory may be created, or it may not transfer at all.
- A file transfer application running on both the sending and receiving system. TinyTERM and TERM count as file transfer applications. When sending a file to a remote system, that system must be running an application that will receive the file. Likewise, the host system must send the file if you are trying to receive it through TERM or TinyTERM.
If these conditions are not met, the transfer will fail. The exact failure depends on what’s missing.
Note that there are no limits to the size of files that can be transferred. Larger files will take longer to transfer, of course, so plan accordingly when using a serial or modem connection.
Posted in File Transfer | Comments Off on File Transfer Requirements
Monday, April 16th, 2007
With TinyTERM Plus Edition 4.05 installed, you can’t capture a network printer to LPT1:. The problem goes away when TinyTERM is uninstalled. To fix the problem, reinstall TinyTERM Plus Edition without the NFS component.
Posted in NFS, Plus, Printing | Comments Off on Can’t Capture to LPT1:
Monday, April 16th, 2007
In TinyTERM 4.0x, the Source file to get box in the Get File dialog will not accept upper case letters when using the FTP protocol. The only solution is to upgrade to a newer version of TinyTERM. There is no patch.
Posted in File Transfer, FTP | Comments Off on Get File Won’t Accept Upper Case
Monday, April 16th, 2007
After installing TinyTERM Plus Edition version 4.05 or earlier, at reboot you may see an error about vxdldr or vcdfsd. You can only boot in safe mode after that.
This error comes from a timing conflict with a virtual device loader. To fix it, uninstall TinyTERM Plus Edition, then reboot. On reinstall, deselect the NFS component.
Posted in NFS, Plus | Comments Off on VXDLDR or VCDFSD Error Forces Safe Mode
Monday, April 16th, 2007
After uninstalling TinyTERM Plus, on reboot you may see load errors about mar_nfs.386 and ncdnp32.dll. To fix that, do the following:
- Open Windows Explorer or My Computer and remove any Century folder (C:\Century or C:\Program Files\Century).
- Go to the C:\Windows\Temp folder. Remove any files or folders that start with _istmp.
- Search the C: drive for files named mar*.*. From the list of files found, delete the following:
- marathon.*
- marsetup.*
- mar_inet.exe
You may receive an error that this file is in use. If so, check the far right of the Start bar, next to the clock. If a hammer&wrench icon is there, right-click it and select Exit. You will then be able to delete mar_inet.exe
- Click the Start menu and select Programs. Delete any Century or TinyTERM Program group.
- Click Start and select Run. In the Open line, type regedit and click OK.
- In the Registry Editor, go to HKEY_Current_User\Software. Delete any “Century” or “NCD Software” folders found there.
- Still in the Registry Editor, go to HKEY_Local_Machine\Software. Delete any “Century” or “NCD Software” folders found there. Close the Registry Editor.
- Right click on Network Neighborhood and select Properties.
- Remove “Century NFS” and “Century Internet Services” from the list of installed network components
- Reboot your PC.
Posted in NFS, Uninstall | Comments Off on NFS Errors After Uninstall
Monday, April 16th, 2007
Transferring a file using ASCII format in TinyTERM 4.0x, line feeds are not properly converted. This is a known issue in versions 4.00-4.04. It was resolved TinyTERM 4.05. There is no patch.
Posted in File Transfer | Comments Off on ASCII File Transfer Does Not Convert LF Characters
|