gmane.comp.emulators.tn5250

Re: Best way to boot into tn5250 full screen

John Chambers — 2012-05-01T13:56:01

I don't know what is "best" but I have some old "low resource" machines
running tinycore linux, booting straight to green.
Once you figure out persistance, just put:
tty1::respawn:/sbin/getty -nl /usr/local/bin/as400 38400 tty1
Into inittab, where as400 is a script that starts tn5250, pointing to
our AS400.

-----Original Message-----
From: linux5250-bounces-Zwy7GipZuJhWk0Htik3J/w< at >public.gmane.org
[mailto:linux5250-bounces-Zwy7GipZuJhWk0Htik3J/w< at >public.gmane.org] On Behalf Of Jonathan Burishkin
Sent: Tuesday, April 24, 2012 4:02 PM
To: linux5250-Zwy7GipZuJhWk0Htik3J/w< at >public.gmane.org
Subject: [LINUX5250] Best way to boot into tn5250 full screen

I need to set up some tn5250 terminals at work; I prefer them to boot
straight into the green screen, no gui. What linux distro and
configuration is best for this?

I have been using Lubuntu 11.10 32bit with IBM iSeriesAccess and have
some lost connection issues with the software. I would like to see how
tn5250 works.
--
This is the Linux 5250 Development Project (L

Guidelines for LINUX5250 mailing list

2012-05-01T11:30:17

Monthly posting of the guidelines for participation in the LINUX5250
Mailing List.

Answers to common questions, including installation issues for FreeBSD,
Linux and Windows are included in the documentation in the README file
in the source tarball, the manual included with the Windows installer,
and the other documentation found on our web site at
http://tn5250.sourceforge.net

Answers to other questions which may have already been asked are available in
the linux5250 email list archive, which is available at
http://archive.midrange.com/linux5250/

Keep to the subject.  The topic of the list is the Linux Tn5250
Emulation project.   (Though, the name "Linux" is a misnomer, since
the software will work in Microsoft Windows and any modern Unix or
Unix-like operating system)

When quoting messages, do not quote the entire message.  Just quote the
parts that are needed to make the appropriate references.

Flames are absolutely prohibited.  If you disagree with someone, feel
free to argue the facts, but no person

Re: LINUX5250 Digest, Vol 10, Issue 9

Jonathan Burishkin — 2012-04-30T15:41:40

iSeriesAccess appears to be working just fine when I have it on a different
static range (and even DHCP) than the one our network guy gave me to use.
For some odd reason it drops connections on that range... I don't have to
use that range, maybe its some networking problem.


On Thu, Apr 26, 2012 at 5:33 PM, Jonathan Burishkin <gypsumwolf-Re5JQEeQqe8AvxtiuMwx3w< at >public.gmane.org>wrote:

Re: LINUX5250 Digest, Vol 10, Issue 9

Jonathan Burishkin — 2012-04-26T21:33:25

I made the appropriate changes to the bios and tested it. It did not go
down until after I added it to the domain with likewise-open and set it up
with static IP. I wonder if that has anything to do with it... Our network
is very screwy. I can't say much about our Network guy...

I am now letting it stay connected all night without being joined to domain
and with DHCP. Will see if its still connected in morning.


If I can't get it to stay up I will try:

"It can be found here. http://ibm5250onubuntu.sourceforge.net/
He also has instruction for CentOS on his website.
http://natetron.net/b/?p=273"

Re: ASUS EB1007 eeeBox PC bolted onto the back of a 4:3 FlatScreen Monitor

Jim Oberholtzer — 2012-04-25T22:20:26

Very cool, glad to know that.  Your technique looks like it's a great 
idea.  I agree with another post that the idle settings may be giving 
you the grief.  On my EeePC loaded with Ubuntu I had to use bios to shut 
that off too.

Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects


On 4/25/2012 3:31 PM, fschnittke-mI4xJ4qlgtBiLUuM0BA3LQ< at >public.gmane.org wrote:

Another tact for installing iSeriess Access for Linuxon Ubuntu

Jay Peasley — 2012-04-25T20:51:15

Nate Bounds has developed a neat script to install any version of
iSeries Access for Linux on Ubuntu.

It can be found here. http://ibm5250onubuntu.sourceforge.net/

He also has instruction for CentOS on his website.
http://natetron.net/b/?p=273

HTH,

Jay

Re: ASUS EB1007 eeeBox PC bolted onto the back of a 4:3 FlatScreen Monitor

2012-04-25T20:23:59

 I suppose you could always try disabling power settings in the BIOS of 
 the ASUS box.

 Here's how we set ours:

   Suspend ModeS1 (POS) only
   ACPI 2.0 Support        Disabled
   Restore on Power LossLast State


 Maybe something's putting the network card to sleep....

 On Wed, 25 Apr 2012 16:10:02 -0400, Jonathan Burishkin 
 <gypsumwolf-Re5JQEeQqe8AvxtiuMwx3w< at >public.gmane.org> wrote:

Re: ASUS EB1007 eeeBox PC bolted onto the back of a 4:3 FlatScreen Monitor

2012-04-25T20:31:15

 Hi Jim:

 That's an avenue we explored. We tried a handful of terminals 
 (including WYSE) but found they were all sluggish. For instance if you 
 did a DSPLOG and page forward through the logs, it could not keep up.

 The method we chose is lightening fast, and gives us complete control 
 over the device. Now we also have some 'Advanced Terminals' that run 
 Ubuntu, iSeriesAccess, Lotus Notes for Linux, Web Browser, OpenOffice, 
 etc..on the same ASUS boxes....




 On Wed, 25 Apr 2012 15:21:41 -0500, Jim Oberholtzer 
 <midrangel-zbO79nAUJZvJTQUaaPvyeQC/G2K4zDHf< at >public.gmane.org> wrote:

Re: ASUS EB1007 eeeBox PC bolted onto the back of a 4:3 FlatScreen Monitor

Jim Oberholtzer — 2012-04-25T20:21:41

The process below is very cool!.. but I do have a question.  Since lower 
end WYSE thin clients are about $350ish, and they all include a 
5250/3270 emulator, why not just put the WYSE terminals out there?  Plug 
it in, your done.  The thing can be made to boot directly into the 
emulation.  HP and others make similar products, I have just used the 
WYSE before.

Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects


On 4/25/2012 3:10 PM, Jonathan Burishkin wrote:

ASUS EB1007 eeeBox PC bolted onto the back of a 4:3FlatScreen Monitor

Jonathan Burishkin — 2012-04-25T20:10:02

That is what I am using. ASUS EB1007 eeeBox PC bolted onto the back of a
flat screen.

I am not very familiar with BSD.

What I am currently doing atm is Lubuntu and iSeriesAccess.

The only problem I am having is that every 20 minutes or so the
iSeriesAccess drops the connection and has the user login again. Its very
annoying. Sometimes its more often.

Here is the details (from a how-to I wrote for the other techs < at > company.:

+++++++++++++++++++++++WHAT I DID+++++++++++++++++++++++++++

Instructions on how to make a lightweight Linux terminal for the AS400.

-
Specific Software: iSeriesAccess-5.4.0-1.6.i386.rpm on Lubuntu 11.10 32-bit
Specific model: ASUS EB1007

Note: Some scripts I (name) provided, you just need to copy them to the
correct location.

-
Index

1...........ASUS EB1007 Booting from USB

2...........HOW TO BUILD THE SYSTEM

3...........A few BASH commands you may want to reference

4...........Fixing APT GPG errors


================================================== ====
==================

Re: Best way to boot into tn5250 full screen

2012-04-24T20:59:19

 Hi:

 We replaced all of our 3477 Terminals last year with homegrown 
 ThinClients and it's been working great. Many thanks to Scott and 
 others.

 I know you said you didn't want a gui, but our ThinClients use a gui 
 (X) and boot right into a green screen at startup, just like a terminal, 
 except it takes a little longer.

 Here's what we used:

 Hardware: ASUS EB1007 eeeBox PC bolted onto the back of a 4:3 
 FlatScreen Monitor
 OS: FreeBSD B1 8.2-RELEASE FreeBSD 8.2-RELEASE #0
 5250 Software: tn5250 0.17.4 (xt5250)
 X Server: X.Org X Server 1.7.7

 Everything is installed on a 4Gb Compact Flash card, and the root of 
 the OS is read only. Things like /tmp and /var, are loaded as memory 
 drives. We don't have to worry about the cards getting burnt out from 
 too many writes, and we don't have to worry about the abuse the software 
 might take out on the floor. Users can power it off and on, and we don't 
 have to worry about corruption.

 We did have to do a fair bit of customizing, (both to X and 
 tn

Re: Best way to boot into tn5250 full screen

Carey Evans — 2012-04-24T20:39:38

On 25 April 2012 08:23, Porterfield, Sean <
SPorterfield-rhMrrli3/3qkuuVfRtBVU5ND+EKTeMMv< at >public.gmane.org> wrote:


You're probably thinking of http://www.chowhouse.com/~james/tn5250-HOWTO.pdf
.

It can also be tricky getting the program to start automatically with the
right TTY settings without a login. We had a modified getty line in
/etc/inittab that started a shell script, that statred login with the right
options, that started tn5250 with the right options. We probably still have
the whole thing saved somewhere.

Re: Best way to boot into tn5250 full screen

Porterfield, Sean — 2012-04-24T20:23:28

I played with something similar in 2003, most likely based on http://www.scottklement.com/picobsd/

The trick with no GUI is getting the keys mapped properly.  How you do that will vary by what OS you're running.  It's been too long for me to remember, but I think there is a man page, HOWTO, or README that explains it.
--
Sean Porterfield

-----Original Message-----

I need to set up some tn5250 terminals at work; I prefer them to boot straight into the green screen, no gui. What linux distro and configuration is best for this?

I have been using Lubuntu 11.10 32bit with IBM iSeriesAccess and have some lost connection issues with the software. I would like to see how tn5250 works.

This email is confidential, intended only for the named recipient(s) above and may contain information that is privileged.  If you have received this message in error or are not the named recipient(s), please notify the sender immediately and delete this email message from your computer as any and all unauthorized distribution or

Best way to boot into tn5250 full screen

Jonathan Burishkin — 2012-04-24T20:01:47

I need to set up some tn5250 terminals at work; I prefer them to boot
straight into the green screen, no gui. What linux distro and configuration
is best for this?

I have been using Lubuntu 11.10 32bit with IBM iSeriesAccess and have some
lost connection issues with the software. I would like to see how tn5250
works.

Re: Ubuntu 11.10 x5250 compile error

Guillermo Garcia — 2012-04-18T17:14:47

Thanks I'll do the same

Re: Ubuntu 11.10 x5250 compile error

Porterfield, Sean — 2012-04-18T13:26:53

-----Original Message-----

Porterfield, Sean <SPorterfield< at >...> writes:






I did not solve the problem.  I just resigned myself to using xt5250 instead of x5250.
--
Sean Porterfield


This email is confidential, intended only for the named recipient(s) above and may contain information that is privileged.  If you have received this message in error or are not the named recipient(s), please notify the sender immediately and delete this email message from your computer as any and all unauthorized distribution or use of this message is strictly prohibited.  Thank you.

Re: Ubuntu 11.10 x5250 compile error

Guillermo Garcia — 2012-04-17T21:51:48

sslv2, the files that were
directories (Root and Entries).
(Tn5250Config *This,
**argv)
what it needs for some reason.
debug.o dialog.o help.o
the latest version I could find.
may contain information
named recipient(s), please
as any and all

Did you ever solved this I'm having the same problem
make  all-recursive
make[1]: Entering directory `/home/guillermo/Downloads/x5250-0.5.4'
Making all in src
make[2]: Entering directory `/home/guillermo/Downloads/x5250-0.5.4/src'
gcc -DDATADIR=\"/usr/local/share\" -g -O2 -l5250  -o x5250 alloccolors.o debug.o
dialog.o help.o mouse.o key.o resources.o x5250.o x5250term.o  -lSM -lICE  -lX11
-lXext 
x5250.o: In function `check_options':
/home/guillermo/Downloads/x5250-0.5.4/src/x5250.c:1895: undefined reference to
`tn5250_config_parse_argv'
/home/guillermo/Downloads/x5250-0.5.4/src/x5250.c:1900: undefined reference to
`tn5250_config_get'
/home/guillermo/Downloads/x5250-0.5.4/src/x5250.c:1905: undefined reference to
`tn5250_config_get'
/home/guillermo/Downloads/x5250-0.5.

Guidelines for LINUX5250 mailing list

2012-04-01T11:30:22

Monthly posting of the guidelines for participation in the LINUX5250
Mailing List.

Answers to common questions, including installation issues for FreeBSD,
Linux and Windows are included in the documentation in the README file
in the source tarball, the manual included with the Windows installer,
and the other documentation found on our web site at
http://tn5250.sourceforge.net

Answers to other questions which may have already been asked are available in
the linux5250 email list archive, which is available at
http://archive.midrange.com/linux5250/

Keep to the subject.  The topic of the list is the Linux Tn5250
Emulation project.   (Though, the name "Linux" is a misnomer, since
the software will work in Microsoft Windows and any modern Unix or
Unix-like operating system)

When quoting messages, do not quote the entire message.  Just quote the
parts that are needed to make the appropriate references.

Flames are absolutely prohibited.  If you disagree with someone, feel
free to argue the facts, but no person

Guidelines for LINUX5250 mailing list

2012-03-01T12:30:23

Monthly posting of the guidelines for participation in the LINUX5250
Mailing List.

Answers to common questions, including installation issues for FreeBSD,
Linux and Windows are included in the documentation in the README file
in the source tarball, the manual included with the Windows installer,
and the other documentation found on our web site at
http://tn5250.sourceforge.net

Answers to other questions which may have already been asked are available in
the linux5250 email list archive, which is available at
http://archive.midrange.com/linux5250/

Keep to the subject.  The topic of the list is the Linux Tn5250
Emulation project.   (Though, the name "Linux" is a misnomer, since
the software will work in Microsoft Windows and any modern Unix or
Unix-like operating system)

When quoting messages, do not quote the entire message.  Just quote the
parts that are needed to make the appropriate references.

Flames are absolutely prohibited.  If you disagree with someone, feel
free to argue the facts, but no person

Guidelines for LINUX5250 mailing list

2012-02-01T12:30:31

Monthly posting of the guidelines for participation in the LINUX5250
Mailing List.

Answers to common questions, including installation issues for FreeBSD,
Linux and Windows are included in the documentation in the README file
in the source tarball, the manual included with the Windows installer,
and the other documentation found on our web site at
http://tn5250.sourceforge.net

Answers to other questions which may have already been asked are available in
the linux5250 email list archive, which is available at
http://archive.midrange.com/linux5250/

Keep to the subject.  The topic of the list is the Linux Tn5250
Emulation project.   (Though, the name "Linux" is a misnomer, since
the software will work in Microsoft Windows and any modern Unix or
Unix-like operating system)

When quoting messages, do not quote the entire message.  Just quote the
parts that are needed to make the appropriate references.

Flames are absolutely prohibited.  If you disagree with someone, feel
free to argue the facts, but no person

Guidelines for LINUX5250 mailing list

2012-01-01T12:30:25

Monthly posting of the guidelines for participation in the LINUX5250
Mailing List.

Answers to common questions, including installation issues for FreeBSD,
Linux and Windows are included in the documentation in the README file
in the source tarball, the manual included with the Windows installer,
and the other documentation found on our web site at
http://tn5250.sourceforge.net

Answers to other questions which may have already been asked are available in
the linux5250 email list archive, which is available at
http://archive.midrange.com/linux5250/

Keep to the subject.  The topic of the list is the Linux Tn5250
Emulation project.   (Though, the name "Linux" is a misnomer, since
the software will work in Microsoft Windows and any modern Unix or
Unix-like operating system)

When quoting messages, do not quote the entire message.  Just quote the
parts that are needed to make the appropriate references.

Flames are absolutely prohibited.  If you disagree with someone, feel
free to argue the facts, but no person