General ICE.TEN Information

• The current version number of ICE.TEN is 4.2.
• ICE.TEN is serial based only. ICE.TEN does not work over a network.
• ICE.TEN is not intended for use with a modem at home. The correct product for dial-up use is called ICE.OFFSITE.
• The earliest version of ICE.TEN that runs on Windows 95 is 4.0.
• J. River technical support supports versions 3.5 and up.

ICE.TEN's terminal emulation programs, DEJAWIN for Windows and DEJAVU for DOS, emulate the following terminlas: SCO ANSI Color Console, AT386 ANSI Color Console, IBM 3151, AT&T 605, VT102, VT220, WYSE60, WSE160, and PCTERM. The terminal type can be defined either in the SET.ICE program or in DEJAWIN. In the DEJAWIN window select either Permanent or Session from the menu Settings.

Emulation Trouble Shooting ICE.TEN Loads, but will not Pop Up

• If you are running a DOS application with a bit-mapped image, ICE.TEN 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.

After Opening Dejavu/DejaWin There is No Login Prompt and Nothing Appears on the Screen.

• Hit return a few times
• Make sure no other device (such as a mouse or a modem) is sharing the com port or IRQ.
• Make sure that SET.ICE is set to use the com port your serial cable is attatched to.
• Try attaching a null modem adapter to the serial cable.
• Do a loopback test to ensure your hardware is functioning properly.

Garbage Characters Appear in Dejavu/Dejawin

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

• Baud rate (most likely if there is major garbage)
• Emulation type
• Word length (most likely if there is minor garbage)
• Parity.

These settings can be changed temporarily by selecting Session under the Settings menu in DEJAWIN or entering ALT+h c in DEJA VU.

If you are unsure how to check your UNIX settings, please contact your UNIX administrator.

Screen Does Not Clear When ICE.TEN 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. The available video card types are as follows:

• A = auto detect. This is the default. ICE.TEN tries to determine the video card type automatically.
• C = color display adapters (CGA).
• E = EGA/VGA cards in their native compatible text modes.
• F = Hercules cards in full mode.
• H = Hercules cards in half mode
• S = color display adapters (CGA) with snow removal
• V = VGA cards
• M = monochrome display adapters
• P = PS2 MCGA cards (models 25 and 30)

ICE.TEN Does Not Work, or Works Incompletely or Insconsistently

There may be a problem with your hardware.

• Two boards in the same PC may be sharing the same interupt.
• Another memory resident program may be interfering, even something as innocent as a mouse driver or the DOS SHARE program. You may need to rebuild your AUTOEXEC.BAT and CONFIG.SYS files step by step to see which program or driver is causing the problem.

Funtion Keys or Arrow Keys Do Not Work

• Check and make sure the terminal type and word length are set correctly in SETICE for your UNIX system and/or application.
• Make sure the flow control regulators are set to XON and XOFF in ICE.TEN, the com port ICE.TEN is using and the UNIX connection.
• If you are using a multi-port board, try connecting your PC directly to the UNIX machine, bypassing the board. If this corrects the problem, contact the manufacturer of your multi-port board.
• These keys can be problematic in some earlier versions of ICE.TEN. Try downloading a more recent version of ICE.TEN from our web site and see if that corrects the problem.

System Specific Problems

There is a problem with the serial drivers that were shipped with Windows for Workgroups that causes an error in DejaWin. A self-extracting update file is available update your serial drivers.

ICE.TEN includes utilities that enable the transferring of files between the UNIX host and the local PC. In order to take advantage of ICE.TEN's file transfer utilities you will need to have the ucopy program installed on the UNIX host and a correctly configured, compatible version of either UCOPYWIN for Windows or UCOPY for DOS installed on your PC.

Windows users must use UCOPYWIN, not ucopy.

• Make sure dejavu/dejawin is open and you are at a UNIX prompt.
• Make sure the ucopy on the host is compatible with the version of UCOPY on the PC. For the versions of UCOPY to be compatible, all the digits in the version number must match except the hundreths place (i.e. 5.3x to 5.3x).
  
  • To determine the version of ucopy that is running on the Unix host type: ucopy c at the Unix prompt.
  • To determine the version of UCOPYWIN that is running on your PC select "About UCOPY" under the File menu in the program.
  • To determine the version of UCOPY that is running in DOS, at the DOS prompt type: ucopy c.
    
• Test that ucopy is a binary file. On the host, type: ucopy c (you should get a copyright message).
• Intel-based Unix systems should use the ucopy file in the UNIX directory of the DOS files disk (disk 2). AT&T and Interactive UNIX systems should use the file ucopy.unix in the unix directory on the DOS files disk. Non-Intel UNIX systems will need to use files located on the non-Intel host disk. If you do not have a non-Intel host disk, contact your retailer.
• Make sure you have correct permissions for ucopy on the host (typically 555).
• Try different transfer protocols (xmodem, ymodem, zmodem, etc.)
• Lower the baud rate.
• If you are using a multi-port board, try connecting the PC directly to the UNIX machine via UNIX com port, not through the board.

There are three printing options in ICE.TEN: screen print, local print and host print.

Local Print allows you print from a Unix application to a printer connected to your PC.

Local Print is triggered by a begining escape sequence sent from the UNIX side. Subseqent characters are sent to the printer until a termination escape sequence is sent. For a full list of escape sequences and terminal types, consult your ICE.TEN manual.

Trouble Shooting with Local Print -> Local Printing is Not Working

• Make sure you are using the correct escape sequences for the terminal type you have SET.ICE configured to.
• You may need to set up a UNIX print spooler, especially if the application you are in does not support escape sequences. The UNIX print spooler will use escape sequences.

Local Prints Using a DOS Printer Skips Pages

The DOS printer's memory is becoming filled so it is overwriting what it hasn't printed yet. The only way to fix this is either by installing a DOS print spooler or switching to a Windows environment that has print spooling built-in.

If the ICE.TEN ucopy program is installed and running on the UNIX host, you can use Host Print, a feature that allows Windows 3.x or DOS applications running on a PC to print transparently to a UNIX printer.

Note: Host Print is not available for Windows 95.

Host Print can intercept calls to the PC BIOS printer ports and reroutes print jobs to the UNIX host computer where they are automatically passed to a UNIX printer via any UNIX spooler.

Trouble Shooting with Host Print -> Failure to Print

• hostps.com must be loaded. To use Host Print with Windows, hostps must be started in DOS before Windows is run.
• Make sure the ICE.TEN program ucopy is working.
• Make sure that the com port set in the Host Print Set Up is the same as the com port that ICE.TEN is configured to.
• Make sure the lp string is correct. It should read lp -dprinter_name -c
• Try varying the Printer Timeout variable in the Host Print Setup.

Printing Occurs, but the Output is Flawed

• Make sure the UNIX print spooler is set to a "dumb serial or parallel" printer interface. This may require you to define another printer.
• Make sure the lp string has a -c on it (example: lp -dlaser -c).
• If you are using a multiport board, that may be interfering with file transfer. Use the setting for control character (XON/XOFF) pass-through. Do not set your board for a specific terminal type.