General

• ICE.TCP has been replaced by ICE.TCP-Plus
• The following archival information is for legacy unsupported 16 bit versions of ICE.TCP (versions older than 4.4)
• In order to use ICE.TCP with Windows 95 you must use version 4.1 or greater.

Upgrading to the Full Version from the Trialware Version

To order ICE.TCP contact the J. River sales department at +1.612.339.2521.

"Fatal ICE.TCP Configuration Error 888. Contact J. River Immediately."

This message occurs when there is either a duplicate IP address or there is a duplicate sequence number.

A sequence number is a number that is entered upon installation of the ICE.TCP software on a PC. These sequence numbers correspond to the number of licences you have purchased and they must be unique. If sequence numbers overlap, the "Fatal Configuration 888" error will occur.

To determine a PCs sequence number, open a dejawin session and go to the File menu where you will see an option to view the sequence number.

In version 4.3 of ICE.TCP, the version number can be changed in by going to File --> View Sequence Number and changing the sequence number. For all other versions of ICE.TCP, to change PCs sequence number you must reinstall the ICE.TCP software.

The 888 error may also occur if the IP address of a station is changed on a PC with ICE.TCP previously installed. To correct this, all the current sessions of ICE.TCP must be closed out and started up again.

ICE.TCP and Novell Netware

ICE.TCP works with Novell Netware as long as the version of LSL being used is version 2.14 or greater. Contact Novell to obtain the current version of Novell's drivers or download them from Novell's website.

Installation

If you are using NDIS or trying to install ICE.TCP 3.0 or less with ODI, you may want to consult the installation section of our Technical Support Library.

Can't Access IP Packet Type. The Packet Driver is Probably not Loaded

The packet driver (DIS_PKTC.DOC) or ODI driver (ODIPKTx.COM) is not installed properly. Check the autoexec.bat file and review the installation procedure.

When Trying to Install ICE.TCP a Stack Overflow Error Occurs, Aborting the Installation

This is from a problem with your video driver.

• Windows 3.x and Windows for Work Groups: Change the video driver in Windows to a standard VGA driver, reboot the PC, restart the installation.
• Windows NT: Load NT in VGA mode.
• Windows 95: Start Windows 95 in safe mode and try the installation over again.

Assigning a Sequence Number

A sequence number is a number that is entered upon installation of the ICE.TCP software on a PC. These sequence numbers correspond to the number of licences you have purchased and they must be unique. If sequence numbers overlap, the "Fatal Configuration 888" error will occur.

To change a PCs sequence number you must reinstall the ICE.TCP software.

It is strongly recommended that the individual responsible for maintaining the network keep a list of sequence numbers that are being used and the IP address of the machine that they correspond to in order to avoid conflicts.

Emulation

Screen Doesn't Clear When ICE.TCP is Activated

The problem probably centers on the video card type you've selected. This setting should correspond to the video adapter card, not the monitor.

ICE.TCP Loads, but will not Pop Up

• If you are running a DOS application with a bit-mapped image, ICE.TCP won't pop up because it requires the screen to be in text mode.
• The program you're running is engaged in an activity that prevents it from looking for commands.

Garbage Characters Appear on the Screen, System Freezes at Login.

Check that the following variables in SetTCP match the UNIX system settings as well as the settings of any UNIX application you are running.

• Emulation type
• Word length (most likely if there is minor garbage throughout the screen)
• Parity.

Screen Hesitation

Screen hesitation refers to a brief pause that occurs when the screen is being updated, or "re-painted." Because ICE.TCP cannot perform beyond the capability of your hardware, some screen hesitation may be particularly noticeable if you are using DEJATN, ICE.TCP's non-TSR program for DOS.

Screen hesitation can be reduced or eliminated by adjusting setting for high window and low window. Run SetTCP and select Net Custom, then select TCP Specific Customization. Because the optimum high and low window settings are dependent on a variety of variables related to network setup, there are no completely reliable rules (except that high window must be set higher than low window). You can experiment with different settings to fine-tune performance.

Using SCO Open Server 5 a Brief Pause Appears in the Middle of the Screen Along with Some Other Screen Hesitations.

This is caused by a problem with SCO's TCP/IP. To fix this problem contact SCO or download the net100 and rs500d series patches from SCO's ftp site. These patches are provided by SCO, any problems or questions about installing them, please contact SCO.

DejaWinT Occasionaly Locks up the Computer.

Check to be sure that your network card is not sharing the same IRQ with another device. In the config.sys file add the following statement STACKS=9,512.

Windows 95 Users: There is a known problem with Microsoft's TCP/IP for Windows 95 OSR1 that will cause DejaWinT to lock up under heavy usage. Microsoft has released a kernel update to address this problem.

Slow Login with IBM AIX

This is caused by a file on AIX called /etc/resolv.conf that AIX is using to try to resolve the workstation login name. Move or rename this file.

Error Can Not Load File 4370.FON in Windows 95

This error occurs when a user has large numbers of font files on their local PC. To correct this error, reduce the number of font files on your hard drive to less than 600.

File Transfer

Trouble with FTPCOPY

On the UNIX machine type ftcopy c. This should return a copyright; if it does not recopy ftcopy over to the UNIX machine as a binary file. Verify that tftp is running on the UNIX machine, ftcopy makes use of this service.

When Trying to Transfer a 20 Megabyte File and FTCOPY Aborts

The largest file that ftcopy can copy is 16 megabytes, anything larger requires that you use JRGFTP to transfer it.

FTCOPY isn't Working in Windows

Ftcopy will not work from within Windows. Windows 95 and NT users must use FTPWin. Other Windows users must either exit completely out of Windows or use FTPWin to transfer files.

Windows for Workgroup users: ftcopy will only work with J. River's TCP/IP stack.

Scripting FTPwin

Please consult our Technical Support Library on this issue.

Make sure PC Print and/or UNIX Host Print have been activated. Run SET.TCP, select Print Services and make sure the check box(es) next to PC Print and/or UNIX Host Print have been checked.

Check to make sure that the icelpd daemon is running on UNIX. Enter the command nestat -a at the UNIX prompt and check to see whether icelpd is listed among the services and whether it is "listening." (For more information on netstat, consult your UNIX documentation). If icelpd is not listed, refer to the installation proceedure in Chapter 3 to install it. AIX, Esix and Unixware users may also refer to the printing section of our Technical Support Library.

To find out whether the icelpd program is executable, enter icelpd c from a UNIX prompt. A copyright message should be displayed.

Check to make sure that a file is being placed in the /usr/tmp/printername/icelp_jobs directory when you print using the UNIX lp print spoooler.

You may also use ICElp's debugging feature, creates a log file in the directory from which ICElp loaded called ICElp.DBG. To start ICElp in debug mode, add a -d option to the command line of the Windows ICElp program.

Problems with HOSTP for DOS -> Nothing Happens When You Try to Print

Check all the following items:

• HOSTP.EXE and HOSTP.DAT files are present in your ICETCP directory. If they are missing, try re-installing ICE.TCP
• HOSTP has been configured to print to the correct UNIX printer.
• The UNIX program hostp is installed by entering the command hostp c at the UNIX prompt. This should produce a copyright message.
• Check to see that hostp is listed among the UNIX services and that it's listening by entering netstat -a at the UNIX prompt.
• Your DOS application may be printing to the same LPT that HOSTP is set to intercept.

HOST Printouts are Broken or Altered

Make sure the application is formatting its output correctly for the selected printer.

The UNIX print spooler may be formatting the print job after it has already been formatted by the DOS application. You may have to define another printer for HOSTP using the "dumb serial or parallel" printer interface file. This spooled printer can use the same port as the original printer file.

If you have trouble printing with Personal Print for DOS, try to determine whether the problem is with ftcopy (the ICE.TCP file transfer program on UNIX) or the UNIX spooling system.

Try to print using ftcopy. Enter the following command line:

ftcopy -a ipaddress filename LPTx

Where ipaddress is the ipaddress of you PC workstation, filename is the name of file to be printed and LPTx is the appropriate LPT port on the PC.

If ftcopy works, (i.e. if the file prints to the printer), the problem is probably in the UNIX spooling system.

If ftcopy does not work, please consult our File Transfer section of this document.

If problems occur with Local Print, first test it at the system level. Create a file called lpf by using vi or another editor ( cat > lpf will also work; end with a CTRL - D). Use the name lpf as a filename. Different escape sequences are required for different terminal emulations, consult your UNIX adminsitrator or UNIX documentation for the appropriate escape sequences for your system.

Use chmod to make the file executable (chmod 755 lpf). Then, at a UNIX system prompt, enter ./lpf lpf. This should cat the file lpf to the printer connected to the parallel port of the PC workstation.

If the test doesn't work, make sure you can print to LPT1 from DOS (For example, from a DOS C:> prompt, try entering copy autoexec.bat lpt1 to print the contents of the AUTOEXEC.BAT file to the printer connected to LPT1). If you can't print to LPT1 in DOS, use SetTCP to check the settings for Host Print to make sure Host print isn't set to "capture" (and send to UNIX) print jobs intended for LPT1. If it is, use LPT2 or LPT3 instead or disable Host printing.

In order to use our TCP/IP software, you must have a Microsoft compliant TCP/IP stack installed on your PC. DOS users must use Jriver's proprietary TCP/IP stack Dejatnt. Windows 95 users must use Microsoft's TCP/IP stack.

If you are using Windows for Workgroups, J. River technical support recommends you use the Microsoft Winsock. Windows for Workgroups users may want to consult the installation section of our Technical Support Library.

Error Message "Winsock connect failed" Appears

This means that the TCP/IP stack cannot find the host you are attempting to connect to. Check your IP address, make sure it is the IP address of the PC you are working on. Verify that there are no numbers entered incorrectly, transposed or missing. Check your other network settings including your subnet mask, any gateways or routers, and your DNS. If you are unsure of any of these settings, confirm them with your network or system administrator.

Other possible reasons are that the host is shutdown or not responding, there is bad/loose cabling, or the network card is not responding correctly.

Error Message "Winsock cannot allocate a socket" Appears

This means that either a Microsoft compliant TCP/IP stack has not been installed or that it has been installed improperly. Check you network configuration and IP addressing to be sure that they are both installed and setup correctly.

Error Message "Winsock not installed or does not support version 1.1" Appears

There is more then one file called winsock.dll on your hard drive. Do a search of your hard drive and remove or rename any extra winsock.dll files. The winsock.dll that you want to keep is located in the windows directory.