1. Make sure that Windows for Workgroups is installed correctly and that a connection can be made to other Windows for Workgroup machines using the NetBEUI protocol.
2. Ensure that Windows for Workgroups is installed for Real and/or Enhanced mode NDIS.
3. Check the CONFIG.SYS file. No Protocol Manager or MAC driver should be included.
4. Now install PathWay Runtime using PWSETUP, specifying C:\Windows as the directory containing the driver and related files.
5. PWSETUP will prompt you for a modification of CONFIG.SYS. Respond with No. This will avoid having to modify it later. If this was missed for some reason, remark out or delete the Wollongong Group section of that file.
6. In AUTOEXEC.BAT add the bolded lines to the Wollongong section as indicated:

SET PATH=C:\PATHWAY;%PATH%
PWCONFIG -N:65
C:\WFW3.11\NET INIT ;this loads the device driver
NDIS -I:X -D:Y ;this loads the NDIS driver interface
C:\WFW3.11\NET START NETBIND ;this completes the binding process
PWTCP

Make sure that the NET START command is not executed at the beginning of AUTOEXEC.BAT.

The -I: parameter on the NDIS line refers to the IRQ level of the network card. Please verify your card setting and make sure the Pathway setting matches. Remember to use the hex value for 10 and above. Symptoms of an IRQ mismatch include slow connection speed, intermittent hanging or loss of connection, and kernel initialization failure.

The -D: parameter on the NDIS line refers to the bracketed section in your protocol.ini file which contains your card name and settings. For example, if the sixth section in your protocol.ini contains this information, the NDIS line should read -D:6. Errors which indicate “unable to bind” or “incomplete binding” can be resolved by double-checking this value and/or verifying that the protocol.ini contains the proper information for your network card.

Once you have installed Pathway, reboot the machine. Watch for any errors. If no errors occur, first try to ping at a DOS prompt, then make sure Windows for Workgroups loads successfully. You should then be able to use FTP, telnet or NFS to connect to your host.

In 1998 Century Software, Inc., developed an internal training course for TERM Script Language (TSL), as implemented in TinyTERM Application Developer 3.3. That is now available for download as a zip file. This complements the PDF TSL documentation and the TinyTERM 3.3 PDF documentation.

When uncompressed, several subdirectories will be created. The documents are all in Microsoft Office formats, except for a few text files.

Please be aware that the DDE course is not complete. Only an example and a lab exercise were ever completed for that section.

Windows Vista no longer supports Microsoft Help files. Opening the Help file in TinyTERM produces a message to that effect.

There is a Help compatibility module for Vista, available for download from Microsoft. But it doesn’t seem to work with TinyTERM. Installing it does not change the “not supported” message from TinyTERM’s Help.

CR 845

Century Software, Inc., has had a request for an option to append to or overwrite a file of the same name during an FTP transfer. This has not been implemented thus far.

CR 94

Century Software, Inc., has had a request for IBM 5250e emulation. This has not been implemented thus far.

CR 93

The Century FTP Client only partially supports passive mode for FTP transfers. It’s fully supported in SecureFT.

CR 88

TinyTERM for Windows has a Display DIM attribute as option for Wyse50 and Wyse60 emulations. Century Software, Inc., has had a request to add this functionality to TERM for UNIX/Linux.

CR 842

Selecting Print Screen from TinyTERM’s File menu on Windows XP causes the error, “CSL Run Engine ActiveX Doc Object Server has encountered a problem and needs to close.” The customer who reported this can transparent print once, but after that transparent printing gives the same error.

Changing the printer did not help, nor did upgrading TinyTERM. This could only be duplicated on the original PC, no other on the customer’s network. Century Software, Inc., has also been unable to duplicate this.

CR 841

When using TinyTERM Web Server Client 4.50, clicking a browser link always opens TinyTERM in a separate window. The OLE Settings don’t affect this.

CR 840, fixed in TinyTERM Web Server Client 4.53 (May 2007)
CR 869, problem occurs in TinyTERM 4.60 if TinyTERM was not previously installed on the PC

In TinyTERM’s Session Properties, check the Use custom emulation size box and set the Columns to 132. Text will remain on screen that should be cleared, depending on how the host application clears the screen. The same thing will work properly without a custom emulation size.

CR 839