Originally data capture was the only method available in TinyTERM for saving the data stream. In version 4.61, the Save scrollback buffer option was added to the Tools menu. This option writes the contents of the scrollback buffer to a user-specified text file.

CR 850, added in TinyTERM 4.61

When a data capture file grows to over 1 Mb, though some reports say it can get as large as 9 Mb, TinyTERM stops capturing and apparently freezes. This may be accompanied by a “stack overflow” error.

CR 670

Century Software, Inc., has received a request to modify the Get File functionality so that it can be used to capture ASCII data to a file. This would save the steps required for data capture. It has not been implemented thus far.

CR 548

If you set up data capture to a named pipe, TERM for UNIX/Linux hangs. This is not strictly a TERM problem; it’s an OS issue. Unlike files or serial devices, named pipes can fill up. At that point, TERM hangs.

The only known fix at this time would involve adding detection and non-blocking code to TERM for situations where the named pipe is full. This has the potential for introducing bugs, especially in serial communications and file writes.

CR 520

When you configure TERM or TinyTERM for ASCII format data capture, it captures and writes to file every character in the ASCII range 0-255. This includes control characters such as ^T and the escape character. There is no way to prevent this behavior.

CR 263

By scrolling back through the session buffer, you can view text that would otherwise be gone. But you cannot highlight more than one screen for copy operations. There is no way to select text across both the current screen and one in the scrollback buffer at the same time.

To work around this limitation, turn on data capture before scrolling starts. The entire session will be saved to the capture file. You can then get the screens you need from that file.

CR 196

This problem only occurs when capturing to a file in binary or ASCII mode. If you display text with bare line feeds, it does not show correctly until you refresh the screen. You can do that by minimizing TinyTERM, or by bringing up another application in front of TinyTERM. This was fixed in TinyTERM 4.30.

CR 394

A binary data capture that receives hex 0A (line feed) not preceded by hex 0D (carriage return) adds the CR just before the line feed. This should only happen in ASCII data captures. This was corrected in TinyTERM 4.40.

CR 387

TN5250 emulation allows binary data capture for troubleshooting purposes. However, turning on data capture often opens the Page Setup dialog instead. If you click OK, the data is captured to the printer. This is fixed in TinyTERM Plus 4.40.

CR 172

An entire host session or part of one can be saved to a file through TinyTERM’s data capture function. To set that up, open TinyTERM’s Settings or Session Properties and go to the Data Capture tab. Enter a path and file name, or accept the default.

The default file name is capt#.fil. The # will be replaced by a number when you start data capture, beginning with 00. This will create the file capt00.fil in the TinyTERM directory. If capt00.fil already exists, capt01.fil will be created, and so on up to capt99.fil. You can use the # sign in your own data capture file names as well.

To turn data capture on, go to TinyTERM’s Tools menu and select Capture File. This starts the capture process, represented by a butterfly net on the status bar at the bottom of the TinyTERM window. Go to the same menu option to turn data capture off.

The Capture device line allows you to select a file (the default option), a system device like LPT1, or the Windows print manager. If you choose PRINTMNGR, data will be captured to the default Windows printer.

Capture mode should generally be set to ASCII. The other mode options capture non-printable characters as special information, and are usually reserved for troubleshooting display issues.

Capture file creation describes what to do when the file name chosen already exists. If Append is chosen, the new data will be added at the end of the existing file. Overwrite causes the original file to be replaced with the new data. If you used the # sign in your file name, a new file will be created regardless of this setting, unless all files numbered 00 through 99 already exist.

The Flush receive buffer on capture off option makes sure everything captured gets written to the file when you stop data capture. Otherwise, the data will be written at the best available moment, or when TinyTERM is closed.