This is a multi-part message in MIME format.
[ Picked text/plain from multipart/alternative ]
I was subscribed under an other username and:
>>Your request to the LINUX5250 mailing list
>> Posting of your message titled "Re: [LINUX5250] State of TN5250"
>>has been rejected by the list moderator.  The moderator gave the
>>following reason for rejecting your request:
>>"Non-members are not allowed to post messages to this list.
High-security information on the list ????
Ok, Second try, original message as refused:

----- Original Message -----
From: "Duane Kehoe" <>
> > I hate to grip you have a great emulator here for the Linux
> > environment but it is not going anywhere and CVS checkouts to get......
<end snip>

First, let it be known that English is NOT my native language, so it's
highly possible
(probably most likely) that this message will be un-dechipherable?? by most
the English-enabled community.....

But , disregarding that, and the VERY large possibility that this is only
the ramblings of yet another
frustrated developer, lets go...
<Rambling mode ON>
It's even worse than what you thought!
It is also a GREAT emulator for DOS and Windows 32 (i.e 95/98/NT/2000 etc)
(Not only for the Linux environment)

To clarify my position:
My native platform is DOS, and I dabble in Win32.
I have been programming for more than 25 years.
My prefered languages are (in order of preference)
1: Standard C
2: Intel 80x8xx Assembler ( or dis-assembly)
3: MS C++ 1.52 (for DOS)
4: MS C++ 6.??  (for Windows 32)

My knowledge of these languages are (in order of knowledge):
1: Intel 80x8xx Assembler ( or dis-assembly)
2: Standard C
3: MS C++ 1.52 (for DOS)
4: MS C++ 6.??  (for Windows 32)

RE: C++ Win32: I mostly use it for debugging, the tools available (NuMega
makes it a VERY easy to find things like memory leaks,
(and they are frequent in 17.?? version of TN5250).

I have ported the emulator to both MS DOS 3.00+ and Windows
and it works GREAT! , (but it required a complete rewrite of the terminal
I/O routines
(i.e cursesterm.c, and numerous fixes to other routines, to make it perform
as needed (by me) ).

Whenever there is an update on CVS, I have to conduct a thorough analyzis
1: What has changed
2: Do I need the changes
(or are they only related to some obscure change of  linkage library related
to the Linux platform)
3: How do I implement the changes (if I determine I need them)

I have intimate knowledge of the code, how it works and why (but only on
NON-Linux platforms!)
I would like to help if  I can, but (as I already told the observant
listener) I don't run Linux,
so questions about:
 keyboard functionality,
 X-Windows under Linux,
 the various Linux libraries needed for linking the current version,
A.S.O, I cannot answer!

I also wonder if the current release is supposed to be "End-User-Ready"
i.e. a thoroughly debugged, via controlled Alpha, Beta etc. releases,
 market tested, and  (bugs/performance issues/features requested) fixed, or
and the whole thing packaged for distribution with extremily easy
installation ?.

I think not!
This is not, and have (so far) never been, an "End-User-Ready" application.
Why not ?
The documentation (for most of the application), is the source code !!!
This is GOOD for all of us that can read source. (But BAD for all OTHER's!!)

The links are outdated, and most people don't know how to do a checkout
and even if they manage, they most probably get stucked with some obscure
from the pre-processing phase (all those scripts are deadly!!)
For us non-Linux users, they are even deadlier!
(Because things normally contained in a source file,
 is prepared in an operating-system-dependant way (script),
inpossible for users not running the OS to dechipher!!! )

<Rambling mode OFF>

As a non-Linux user I wonder what is a source tarball ??.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

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

This mailing list archive is Copyright 1997-2022 by 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].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.