ICE

Quite often for no explicable reason our terminal session ends with a visual basic runtime error. We are using V5.1.19 telnet pro on XP machines and it happens on all machines.

Does anyone else have a similar problem.

Are you sure it's a VB error? None of the ICE products have a VB component...

The error messages that appear when the program crashes are as follows:

First one says:

Microsoft Visual C++ Runtime Library

Runtime Error!

Program: c:\JRiver\ICETCP5\TelnetPro.exe

Abnormal Program Termination


Second Message Says:

Application Error Telnet Pro.exe

The instruction at "0x77e7a67a" referenced memory at "0xO0324804". The memory could not be "wriiten".

Any assistance you can provide would be appreciated.

Ah, so it's not a VB error, it's a C++ runtime error.
The numbers aren't very useful unfortunately. So, more info on what's going on when it happens would be useful.

Running what application?
What terminal type are you using?
Does it REALLY happen on multiple machines?
Are you certain that the machine(s) it's happening on are running 5.1.19?
 ( do help -> version info)
Is there anything unusual about your setup? (VPN or dialup networking connection, etc)

Application is TelnetPro.

Terminal type is Wy60, however  I have tried using ansi and adjusting every other configuration setting in the profile and the error still happens.

Yes it happens on all machines running Windows 2000 or XP. Users had to swap to Dejawint. Millenium and 98 users don't have the problem.

Are you certain that the machine(s) it's happening on are running 5.1.19?
( do help -> version info)

Sorry to report it as a VB and not C++ error I don't know much about this stuff. I am no expert but I can verify running 5.1.19.

Is there anything unusual about your setup? (VPN or dialup networking connection, etc). It happens both on dial up and LAN connections so I can't think of anything special here.

Holding down the page down key for 5 - 10 seconds will trigger the crash.

I appreciate your efforts to assist.

Are you using telnet or ssh?

Using telnet not SSH.

We haven't seen this behavior before. We'll try to see if we can duplicate it here.

I'll need some more info to try to come close to duplicating your conditions.  

Approximately how fast are the machines you are running on?

What type of unix are you using and what application are you using?

It would be useful to know if the problem occurs using the 4.4 (classic) client as well. Can you install that on one machine and try using it with the same app??

4.4 classic works fine although doesn't have the feature set we are after.

System specs as follows.

OS Name   Microsoft Windows XP Professional
Version   5.1.2600 Service Pack 1 Build 2600
OS Manufacturer   Microsoft Corporation
System Manufacturer   Compaq
System Model   Evo D510 SFF
System Type   X86-based PC
Processor   x86 Family 15 Model 1 Stepping 2 GenuineIntel ~1794 Mhz
BIOS Version/Date   Compaq 686O2 v2.14, 15/08/2002
SMBIOS Version   2.3
Windows Directory   C:\WINDOWS
System Directory   C:\WINDOWS\System32
Boot Device   \Device\HarddiskVolume1
Locale   United States
Hardware Abstraction Layer   Version = "5.1.2600.1106 (xpsp1.020828-1920)"
Time Zone   W. Australia Standard Time
Total Physical Memory   512.50 MB
Available Physical Memory   229.32 MB
Total Virtual Memory   1.68 GB
Available Virtual Memory   1.20 GB
Page File Space   1.19 GB
Page File   C:\pagefile.sys

Connecting to SCO Unix system.

We are in the process of considering an upgrade to our terminal softwate for about 500 users. I'd like to use Telnet Pro if we can sort this issue out.

We are going to make a version which avoids dynamic links to the mfc42.dll file. It appears that the mfc42.dll file is getting altered by some other software you are installing.

The next release of PRO will contain the changes. I'll announce it in the TCP-PRO forum when it's released.

Yes it does. It's version 5.1.21. Give it a try and let us know how it works out for you.