Hi Scott,

The only problem I have that still appears in the current CVS version is
the problem with it crashing in XP when the tn5250 screen updates when
windows is locked.
Our terminals using inquiry or update or reports don't crash because
they don't update when the window is locked. However, we have an
application for labor data reporting that updates a screen clock every 5
to 10 seconds, and it would crash with the screen locked. I don't think
this is the same problem that Bill Evans has.
I probably wouldn't have found the problem if the patch in CVS hadn't
been different from the patch in the mailing list archive:
I hope this helps someone.

Thanks for all your work on this project (all of you).
John Chambers

PS. I tried sending a message through sourceforge to you about this a
couple of weeks ago, but I only got an error message when clicking

-----Original Message-----
From: linux5250-bounces@xxxxxxxxxxxx
[mailto:linux5250-bounces@xxxxxxxxxxxx] On Behalf Of Scott Klement
Sent: Saturday, December 19, 2009 3:23 AM
To: Linux 5250 Development Project
Subject: Re: [LINUX5250] Run time error in TN5250.EXE version 0.17.4

Hi Bill,

I can reproduce your problem with the 0.17.4 release of TN5250.
However, I can't reproduce it in the current CVS version (despite John
Chambers assertion that the problem exists there as well.)

Can you please try the current version from CVS? Since you've had
trouble building it yourself, I built a copy for you, you can get it


Let us know how that goes...

Bill Evans wrote:
Hi Bill
There is a patch for winterm.c in the repository that fixes some bugs,
maybe that one, but it is applied after 0.17.4. You can get mingw and
compile it yourself.

It was supposed to fix the crash in XP when the system goes into lock
mode, but it doesn't if there is any screen activity after it goes
lock mode.

The patch in the repository doesn't match the patch in the archives of
this list. The patch in the archives removes line 2154:
I recompiled it without this line, and it no longer locks up. I don't
know if this will fix your problem or not. I don't even know enough to
know if this might cause problems elsewhere, but it's worked ok on 4
systems for the last two weeks.
John Chambers

As I mentioned in my reply to James Rich, I'm pretty much out of my
league with this stuff but I just wanted to give myself a stress test
pressing the envelope, so to speak. I ran into a roadblock during the

make step. However, it was educational looking thru the source code
the various modules. I even tried a source-compare between 17.3 and
17.4 since this "click on line 24" bug didn't exist in 17.3 and I
thought I might "miraculously" see the issue. That turned out to be
just hubris on my part. Nonetheless, it was an interesting exercise.

Thanks for replying.
--Bill Evans

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2020 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].