nanogui: Thread: Terminal Emulator

Hi!

I we would have a good running Terminal emulator for nano-X, we could at least
use all console like stuff (even this is not the goal of this project).

So we could use lynx etc. on embedded systems, till we get more graphicle stuff

Martin

Hi,

Some time ago I started hacking the nterm code into a more fully fledged
"linux console" compatable term-emu.  The code was very very bare, still,
and missing an awful lot, but I gave it to greg and he uploaded it to the
microwin site.  Please feel free to take and use it for your own, due to a
number of problems I've had no chance to work on it in quite some time,
infact time to work on any aspect of the Mwin/nanox project -- I hope this
will change shortly..... but don't hold your breath..... sorry.

If anyone does decide to take it over, please can they let me have any
patches they make against it, so I can keep myself updated. Consider the
code GPL'ed. I don't think it says that, but hey, it's rather poo anyway
:)

	-Darran

-- 
Darran David Rimron-Molloy                 |     ####@####.####
Managing Director, Digital Science Limited | http://www.digital-science.net
   -=- Customer Driven Bespoke Internet Solutions & Internet Access -=-
                -=- Beaten Paths Are For Beaten Men -=-

On Fri, 28 Apr 2000 ####@####.#### wrote:

> Date: Fri, 28 Apr 2000 7:47:21 +0200
> From: ####@####.####
> To: ####@####.####
> Subject: Terminal Emulator
> 
> Hi!
> 
> I we would have a good running Terminal emulator for nano-X, we could at least
> use all console like stuff (even this is not the goal of this project).
> 
> So we could use lynx etc. on embedded systems, till we get more graphicle stuff
> 
> Martin
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ####@####.####
> For additional commands, e-mail: ####@####.####
> 

: I we would have a good running Terminal emulator for nano-X, we could at least
: use all console like stuff (even this is not the goal of this project).
:
: So we could use lynx etc. on embedded systems, till we get more graphicle
stuff

I will implement a terminal emulator this weekend, that will work
for basic VT series terminals.  This shouldn't be too hard, since
that's what we do for a living over here at Century Software.

This work will be an extension of the mterm program currently
distributed with Microwindows.

Regards,

Greg

: This might be a little off-topic, and maybe not even appreciated, but what
: about a terminal program like telnet for WinCE?  I have an Ethernet card
: now for my Cassiopeia and am looking for one.  I've been thinking about
: writing one since I havent been able to locate one.

The terminal emulator that I'm going to be writing for Microwindows
will use the Win32 api.  That means that it will run unmodified on WinCE.
I'd love it if you compiled it up under WinCE after I get it running on
Microwindows.

I assume you have the SDK and cross compilers for your WinCE box.
If not, you might check the MS site for details.  I'm not sure
if gcc toolchains support WinCE development yet...

Regards,

Greg

"Greg Haerr" wrote:

> The terminal emulator that I'm going to be writing for Microwindows
> will use the Win32 api.  That means that it will run unmodified on WinCE.
> I'd love it if you compiled it up under WinCE after I get it running on
> Microwindows.

while this is a great validation of microwindows, you need a bit more
to make it useful under WinCE.  Unlike the One True OS, winCE does not
have a command line telnet app that would make mterm for CE useful ;-(
still, mterm with full vt-100 will be great for Linux.  The fact that
WinCE does not come with a telnet still astounds me...

for the original poster, a quick search on google for "telnet wince" used
to point to a few bad telnets - all of them on my clio had appalling
scrolling performace.  ie builtin 300bps emulation over a 11Mbit wavelan!

-J

> 
> while this is a great validation of microwindows, you need a bit more
> to make it useful under WinCE.  Unlike the One True OS, winCE does not
> have a command line telnet app that would make mterm for CE useful ;-(
> still, mterm with full vt-100 will be great for Linux.  The fact that
> WinCE does not come with a telnet still astounds me...
> 
> for the original poster, a quick search on google for "telnet wince" used
> to point to a few bad telnets - all of them on my clio had appalling
> scrolling performace.  ie builtin 300bps emulation over a 11Mbit wavelan!
> 

Well, I'm the original poster and my target is a Casio Cassiopeia E-100.
The trick is going to be to get it to work with the little pop-up screen
keyboard that these PPC devices use.  I've dabbled with the WinCE stuff
in the 1.1 release SDK but havent done anything with the 2.0 release
so it should be fun.

I too am absolutely astounded that there is no terminal app.  I got a
10 Mbps Ethernet CF card and I really want to use my Casio as a remote
terminal but all I can do now is ping the damn thing, unbelievable.

FM

--
Frank W. Miller
Cornfed Systems Inc
www.cornfed.com

Maybe try porting putty to CE.

Regards,
Brad

----- Original Message -----
From: Frank W. Miller ####@####.####
To: ####@####.####
Cc: ####@####.#### Frank W. Miller
####@####.####
Sent: Saturday, April 29, 2000 7:14 AM
Subject: Re: Terminal Emulator


> >
> > while this is a great validation of microwindows, you need a bit more
> > to make it useful under WinCE.  Unlike the One True OS, winCE does not
> > have a command line telnet app that would make mterm for CE useful ;-(
> > still, mterm with full vt-100 will be great for Linux.  The fact that
> > WinCE does not come with a telnet still astounds me...
> >
> > for the original poster, a quick search on google for "telnet wince"
used
> > to point to a few bad telnets - all of them on my clio had appalling
> > scrolling performace.  ie builtin 300bps emulation over a 11Mbit
wavelan!
> >
>
> Well, I'm the original poster and my target is a Casio Cassiopeia E-100.
> The trick is going to be to get it to work with the little pop-up screen
> keyboard that these PPC devices use.  I've dabbled with the WinCE stuff
> in the 1.1 release SDK but havent done anything with the 2.0 release
> so it should be fun.
>
> I too am absolutely astounded that there is no terminal app.  I got a
> 10 Mbps Ethernet CF card and I really want to use my Casio as a remote
> terminal but all I can do now is ping the damn thing, unbelievable.
>
> FM
>
> --
> Frank W. Miller
> Cornfed Systems Inc
> www.cornfed.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ####@####.####
> For additional commands, e-mail: ####@####.####
>

: while this is a great validation of microwindows, you need a bit more
: to make it useful under WinCE.  Unlike the One True OS, winCE does not
: have a command line telnet app that would make mterm for CE useful ;-(
: still, mterm with full vt-100 will be great for Linux.  The fact that
: WinCE does not come with a telnet still astounds me...

Now, are you talking about having a telnet client that allows you to
telnet to another box from winCE, or are you talking about a telnet
daemon, which allows you to talk to winCE from another box?

I'm suggesting that mterm work under WinCE, which only requires
a command.com or cmd.exe shell, with output redirected to mterm,
where I take take of the scrolling, etc.  Does WinCE have a
cmd.exe?  If not, it would be fairly straightforward to write one,
that basically has a few internal commands, and execs the rest
of the stuff using CreateProcess...  perhaps we should hack
sash.


: 
: for the original poster, a quick search on google for "telnet wince" used
: to point to a few bad telnets - all of them on my clio had appalling
: scrolling performace.  ie builtin 300bps emulation over a 11Mbit wavelan!

For scrolling performance you mean that winCE telneted to another
box, but the screen scrolled very slowy..  right?

Regards,

Greg

> Now, are you talking about having a telnet client that allows you to
> telnet to another box from winCE, or are you talking about a telnet
> daemon, which allows you to talk to winCE from another box?

the former, ie a telnet client that allows a login on a remote machine
running telnetd.

> I'm suggesting that mterm work under WinCE, which only requires
> a command.com or cmd.exe shell, with output redirected to mterm,
> where I take take of the scrolling, etc.  Does WinCE have a
> cmd.exe?  If not, it would be fairly straightforward to write one,
> that basically has a few internal commands, and execs the rest
> of the stuff using CreateProcess...  perhaps we should hack
> sash.

yeah, a simple shell would be straight forward.  I have not looked very
hard for a wince shell - I bought the device to run linux but did not get
the time I hoped to help on the port (sorry brad!).  You'd still need a
command line telnet client for WinCE to fulfill frank's original request.
Not that hard either, I guess.  And a nice Unix-style solution ;-)

Time is looking better now and I am looking at getting a non-X dist up
and running and was hoping to make use of microwindows.  A decent 
terminal app would fit in well.

> For scrolling performance you mean that winCE telneted to another
> box, but the screen scrolled very slowy..  right?

thats right.  its partly due to the lame epson LCD controller in the
clio which has no bitblt, but also just bad software.  the fb console
of linux has much better scrolling on the same hardware. 

-J

Why must telnet be in NanoGUI?  I have a command line one on my ftp
site.  /pub/linuxvr/nettools/termix-static .  I've used it to log in
from my WinCE device to my main machine and it works well.

Thanks,
Shane.