VanDyke Software

CRT™ FAQ

CRT FAQ

Is CRT Year 2000 compliant?

Yes, CRT is Year 2000 compliant.

CRT only does date processing in two instances. The first instance is in determining the expiration date for the 30 day trial version. This uses a four digit date, which is Year 2000 compliant. The other instance is in Zmodem file transfer. This uses 32-bit time/date processing which is also Year 2000 compliant.

How do I turn the button bar (a.k.a. toolbar) off?

The toolbar can be toggled on and off via the View menu.

How do I get CRT to work with AOL?

If you are running Windows 95, you need to download AOL for Windows 95 which is different than AOL for Windows. Check Help/About in the AOL main window to verify you are running the correct version. You can download AOL for Windows 95 directly from AOL.

If you are running Windows 3.x, then the version of AOL you need is AOL for Windows. CRT also requires that you are running Win32s version 1.30 or later.

How can I get CRT to be my default Telnet application in Netscape?

In Netscape 4.X or earlier:

Select:

  • Edit / Preferences
  • Click on Navigator / Applications
  • URL:Telnet Protocol
  • Click on Edit
  • Click on Application (it may already be selected)

Change application to be:

"C:\Program Files\CRT\CRT.exe" %1

In Netscape 7.X or Mozilla 1.X

Select:

  • Edit / Preferences
  • Click on Navigator / Helper Applications
  • Click "New Type..." button
  • Decription of type: Telnet
  • FIle Extension: url:telnet
  • MIME type: telnet
  • Application to use: either enter the path to CRT or use the Browse... button to navigate to the folder where CRT is installed on your system. The default path is: "C:\Program Files\CRT\CRT.exe"

When running in VT100 emulation, F1...F4 don't work correctly. Why?

Check your keymap setting. CRT allows you select your keyboard mapping separate from the emulation.

Under CRT 1.1.4, select
Preferences / Session / Keyboard / Keymap / VT100

Under CRT 2.2, select
Options / Session Preferences / Emulation / Keyboard Mapping / VT100

I cannot get CRT to save the New line mode setting under Session Options/Emulation/Modes. Any suggestions?

When you are connected, CRT displays the current "New Line Mode" setting. This setting is either the initial value or could have been changed by the remote system sending an escape sequence to change the mode. CRT does not save the current setting. CRT only saves the initial setting.

Under CRT 1.1.4, the initial "New Line Mode" setting can be set by editing the session from the connect dialog.

Under CRT 2.0, the initial "New Line Mode" setting can be set by clicking the "Advanced" button on the emulation tab of the Session Preferences dialog.

Where can I download the latest release of CRT?

You will always find information on the latest releases from our Download page.

Does CRT support direct connection via the serial port?

CRT 2.2 and later releases include serial (a.k.a. COM) support.

Does CRT include any modem support?

CRT 2.3 and later versions contain full modem support. Select the TAPI protocol to access the modem setup and dialer. It is also possible to use the serial protocol which can be used to connect to your modem and then the modem can be dialed manually, usually via the atdt modem command.

How do I clear the four sites listed in CRT's File menu?

For CRT 3.X and newer, you have to delete the file called "Recent File List.ini", found in CRT's Config directory.

Under Windows XP/2000, the default location is:
C:\Documents and Settings\<user>\Application Data\
VanDyke\CRT\Config\Recent File List.ini

Under Windows Me/98/NT/95, the default location is:
C:\Program Files\CRT\Config\Recent File List.ini

For CRT version 2.4 and earlier, you have to edit the registry. Use regedit to delete:

CURRENT_USER / Software / Van Dyke Technologies / CRT / Recent File List

When I paste to a remote VMS host, I sometimes lose some of the characters being pasted.

You need to issue the VMS command:

SET TERMINAL/HOSTSYNC

This enables flow control by the VMS host system to control the terminal device transmission (in this case CRT's Telnet or rsh connection).

When I create a CRT shortcut, what should the Target be?

"Start in" should be

"C:\Program Files\CRT"

"Target" should be

"C:\Program Files\CRT\CRT.EXE" /S session_name

Assuming that C:\Program Files\CRT is where you installed CRT and the session_name is a valid session name that has been created in CRT. If the session name contains spaces, it should be enclosed in quotes.

How can I send non-printable characters, such as carriage return and escape?

If you are trying to map a function key, any non printing character can be sent by a \ and the octal ASCII code. For example, a CTRL+A can be sent via a \001 or a CTRL+H can be send via a \010. The ASCII control characters are listed in the ASCII Character Codes topic in the online help.

Two common non-printing characters, carriage return and the escape code have the easy to remember sequences \r and \e in addition to \015 and \033.

I am running Windows NT Service Pack 3. When I Rlogin to a host, certain applications such as pine and emacs only use 24 lines. I have the number of line set to a higher value. Why does this happen?

Service Pack 3 included a bug which affects how TCP/IP Out Of Band (OOB) data is handled. Unlike most TCP/IP protocols, Rlogin requires OOB.

You can download the fix from Microsoft:

ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/usa/NT40/hotfixes-postSP3/teardrop2-fix

Why do my toolbars and/or tooltips appear white or do not display?

Toolbars may appear white and/or tool tips may not display on systems that do not have the latest common control DLLs. The latest version of the common control DLLs may be downloaded from the following location:

http://www.microsoft.com/msdownload/ieplatform/ie/comctrlx86.asp

You should download the version of the DLLs that corresponds to the version of Internet Explorer that is installed on your system.

How do I send a STOP-A to a Sun to drop it into it's boot monitor?

When using a serial port on a Sun as the console, STOP-A is defined as the Break line condition. To generate a Break using CRT, you can use the F5 key if the VT220 keymapping is selected.

Break can also be generated using CTRL and the PAUSE/BREAK key when using any of the keymappings supplied with CRT.

You may also use the Keymap Editor to arbitrarily map the Telnet Function TN_BREAK to any key you wish.

Why does my keyboard sometimes lock up on Windows 2000?

According to Microsoft, the Windows 2000 keyboard driver may or may not handle toggling NUM LOCK, CAPS LOCK, and SCROLL LOCK correctly; this can cause the keyboard status to be incorrect or cause the keyboard to freeze.

To fix this problem, install Service Pack 2 for Windows 2000.

If you do not want to install Service Pack 2, here are two possible workarounds:

  • In the Session Options dialog, under the Emulation / Modes category, select the "Application keypad" option instead of the "Numeric keypad" option.
  • In the Session Options dialog, under the Emulation category, set Keyboard to "Default" in the Emulation group

I keep trying to change my foreground and background colors in CRT 3.4 (or later) for just one session, but when I do, the colors for all of my sessions change. This didn't happen in 2.x versions. Am I doing something wrong?

Probably, when you attempt to change the session colors, you are actually changing the values for foreground and background color for one of the globally defined color schemes.

To have each session use a different combination of foreground and background colors, you need to create a color scheme for each color combination you want to use.

For example, if "Session1" is using a custom color scheme named "blue-black" and you want another session to have a red foreground and a black background, you would create a new color scheme (e.g., named "red-black") and have Session2 use that color scheme.

How can I get syntax highlighting to work in Vim with CRT/SecureCRT ?

The most common issue in getting syntax highlighting to work is emulation.

In general, vt220 emulation should work well with most systems for Vim with Syntax highlighting.

Under a Linux system, use the Linux emulation for best results.

Regardless of emulation, you must enable "ANSI color" in your Emulation options for syntax highlighting to work properly.

On many systems, you will also need to make the following changes/additions to your ~/.vimrc file:

set t_Co=8
set t_Sf=\033[3%p1%dm
set t_Sb=\033[4%p1%dm
syntax on

These settings assume that syntax highlighting was enabled at install-time for the version of VIM you are using.

How do I move my CRT sessions to a different machine?

The following steps describe how to migrate your CRT sessions to another machine.
Note: These instructions will not work if you are migrating from 2.x or lower to 3.x or higher.

  1. Install CRT on the new machine.


  2. Find the location of the session configuration folder on the old machine. To do this, start CRT, open the "Options" menu and select "Global Options...". Then select the "General" category or the "Options/Advanced" category in the versions of CRT prior to 5.0. The configuration folder location will be displayed in the "Configuration folder" field.


  3. Copy the configuration folder and its contents to the new machine.

    Under Windows XP/2000, the default location is:
    C:\Documents and Settings\<user>\Application Data\
    VanDyke\CRT\Config


    Under Windows Me/98/NT/95, the default location is:
    C:\Program Files\CRT\Config


  4. Run CRT on the new machine. If CRT does not find the sessions, open the "Options" menu and select "Global Options". Then select the "General" category or the "Options/Advanced" category in versions of CRT prior to 5.0. Browse to the correct location of the configuration folder and save your settings. When you restart CRT, it should use the migrated sessions.

Why am I seeing strange characters on the screen when I log onto RedHat, particularly when I look at man pages?

The problem you are experiencing is that RedHat by default uses UTF-8 to encode its output. Either the version of CRT that you are using does not support UTF-8 encoded output, or the output encoding is not set to UTF-8 for the session in use.

The following are three possible solutions to this problem:

Solution 1: Enable UTF-8 output encoding for the session in use.

If you are using a version of CRT prior to 4.0.1, you will need to update your version. This may be a free upgrade for you depending on when you purchased your CRT license. Please check the upgrade eligibility page on the VanDyke web site to determine if you qualify:

http://www.vandyke.com/pricing/upgrades/index.html

To enable UTF-8 encoding for a session in CRT 5.0, go to the Session Options dialog. In the Terminal/Appearance category, set the "Character encoding" in the "Fonts" group to "UTF-8".

To enable UTF-8 encoding for a session in CRT 4.0.1 through 4.1.x, go to the Session Options dialog. In the Emulation/Advanced category, set the “Output” entry in the “Character encoding” group to "UTF-8".

Solution 2: Turn off UTF-8 encoding for your user on the RedHat machine.

In your .bash_profile, add the following lines (this is for the bash shell; if you are using a different shell, the settings may be slightly different):

LANG=en_US
SUPPORTED=en_US:en
export LANG SUPPORTED

Note: The above commands use en_US as an example; other languages can also be used.

Solution 3: Turn off UTF-8 encoding system wide on the RedHat machine. (Note: This solution requires that you have root access.)

In the file /etc/sysconfig/i18n there is a line that reads:

LANG="en_US.UTF-8"

Change the line to read:

LANG="en_US"

Note: The above commands use en_US as an example; other languages can also be used.

How can I make CRT the default Rlogin application so that I can launch it from a web browser?

This functionality was added to CRT 4.1 and will not work with earlier versions of CRT. To set up CRT as your default Rlogin application, make the following changes in your registry.

  1. Open regedit and navigate to HKEY_CLASSES_ROOT\telnet.
  2. Export this branch to a registry file by selecting "Export" from the "File" menu. Be sure to choose "Selected branch" as the "Export range" option.
  3. Edit the .reg file and replace every instance of "telnet" with "rlogin".
  4. If the key KEY_CLASSES_ROOT\telnet\shell\open\command is not in the .reg file, manually add the following lines to the end of the file.
    [HKEY_CLASSES_ROOT\rlogin\shell\open\command]
    @="\"C:\\Program Files\\CRT\\CRT.exe\" %1"
    Be sure to put in the appropriate protocol name. If your CRT location is different than the one shown above, you will need to modify it to use your install folder.
  5. After saving the registry file, double click on it to import it to the registry.

You will now be able to start CRT from your web browser by typing "rlogin://<hostname>" or by inserting that link in a web page.

What settings should I use so that the emulation is correct for SCO OpenServer 5.0.6 (and later)?

Changing the following settings should improve the emulation when the remote machine is running SCO OpenServer 5.0.6 or later:

  1. On the CRT or SecureCRT Session Options dialog, Emulation category, select "SCOANSI" as the "Terminal" emulation. The SCOANSI emulation should be used with any SCO server. Also, ensure that the rows and column settings are appropriate. SCO applications generally prefer 25x80.
  2. On the Session Options dialog, Emulation/Advanced category, check the "Terminal type" check box and enter "ansi" in the associated text box. This will send "ansi" instead of "scoansi" when you connect. In SCO OpenServer 5.0.6 and later, "scoansi" is no longer mapped to "ansi", and so "ansi" must be specified manually.
  3. In versions of CRT and SecureCRT prior to 4.1, the Terminal font works best. On the Session Options dialog, Appearance category, select "Terminal" as the "Normal font". Make sure that the "Character encoding" option is set to "Default" in the Emulation/Advanced category.
  4. In CRT and SecureCRT 4.1 and later, use the Terminal font by selecting "Terminal" as the "Normal font" on the Session Options dialog, Appearance category. Make sure that "Character encoding" is set to "Default" in the same category.

    It is also possible to use a TrueType Windows font. To do this, on the Session Options dialog, Appearance category, select a TrueType Windows font such as Courier New or Lucida Console and set "Character encoding" to OEM.
  5. Finally, on the remote machine, make sure the TERM environment variable is set to "ansi".

Why isn't the audio bell working?

If you cannot hear beep sounds when CRT receives BELL characters while connected to a remote system, the first step is to make sure that your CRT session is configured to play the beep sounds:

  1. From the CRT "Options" menu, select "Session Options".
  2. In the "Options" category of the "Session Options" dialog, verify that the "Audio bell" option is enabled.

    If you still cannot hear beep sounds, the next step is to check the system audio settings.
  3. From your system's "Start" menu, select "Control Panel".
  4. Open the "Sounds and Multimedia" applet. In Windows XP, this is called "Sounds, Speech, and Audio Devices" and then you will have to select "Sounds and Audio Devices".
  5. Select the "Sounds" tab on the "Sounds and Audio Devices" dialog.
  6. Make sure that the "Windows/Default Beep" event is set to something other than "(None)". You can test this setting by pressing the "Play" button (the button with the right-facing arrow next to the "Sounds" field).
  7. If the "Play" button is grayed-out or you can't hear a sound when you press it, then you probably need to install or repair your system's sound drivers.

If the system audio setting appears to be correct and you still do not hear beep sounds in CRT, it may be due to a registry setting made by Tweak UI, which is an optional utility application from Microsoft.

  1. From the "Start" menu, select "Control Panel".
  2. If you see Tweak UI on the list of Control Panel applets, open it and verify that the "Beep on errors" option on its "General" tab is enabled. If you change this setting, you may need to reboot in order for it to take effect.

If you still cannot hear beep sounds, please contact VanDyke Software technical support at support@vandyke.com.

How do get my color scheme settings to work?

If you are having problems getting color scheme settings to work, you may need to uncheck the "ANSI Color" option on the "Emulation" page in the Session Options dialog. The "ANSI Color" option will override any color scheme defined in the "Appearance/Color Schemes" page in the Global Options dialog.

Where do I find the Scripting FAQ?

How will 2007 Daylight Saving Time (DST) changes affect VanDyke Software products?

The Energy Policy Act of 2005 mandates a change in the observation of Daylight Saving Time (DST). This change will affect products which provide an option for automatically adjusting the system clock for DST. Since observation of DST will be changing in 2007, an update will most likely need to be applied to the operating system in order for the automatic adjustment to be made on the correct date.

VanDyke Software products do not keep track of time in and of themselves. Instead, our products rely on the underlying operating system to provide the correct date and time as needed.

Although the underlying operating system will likely need to be updated or patched to adjust for DST changes for 2007, VanDyke Software products will not need to be updated or patched. If you notice any problems related to the DST changes, please contact VanDyke Software technical support.