public inbox for linux-8086@vger.kernel.org
 help / color / mirror / Atom feed
From: Rob Helmer <robert@namodn.com>
To: Linux-8086@vger.kernel.org
Subject: Re: 286 xterm?
Date: Sun, 1 Sep 2002 12:10:20 -0700	[thread overview]
Message-ID: <20020901121020.A5462@namodn.com> (raw)
In-Reply-To: <200209011048.g81AmweF097667@postino.fi.infn.it>; from bardelli@fi.infn.it on Sun, Sep 01, 2002 at 12:48:58PM +0300

Hello,


You can't currently do this on a 286 with Linux, although there are some X
servers for DOS available.

I used "X Appeal" for DOS a long time ago, it may run under 
FreeDOS also -

http://www.xtreme.it/xappeal.html

"X Appeal" is based on XFree86, but it is proprietary software. There
is a trial version available.



HTH,
Rob Helmer


On Sun, Sep 01, 2002 at 12:48:58PM +0300, Luigi Bardelli wrote:
> Dear all,
> 	thank you for your replies. Dan, i'd like to do it with a *2*86, not
> a 386...
> Any new suggestion?
> Thanks
> 	Luigi
> 
> -------------------
> > This is a little late, so maybe someone already commented, but a
> text
> > terminal and an Xterm are two different things.  There is supposedly
> a
> > program, DesqView-X that allows a 286 to be used as an Xterm, but
> I've
> > never found it.  I finally gave up and just started using a 386
> running
> > Linux with a minimal amount of packages installed.  I can just boot
> Linux,
> > run X, and then redirect my display to that machine over the
> ethernet.
> > Maybe someone else has some ideas on the Xterm question, there was
> some
> > work on a GUI for ELKS but I don't think it's to the point of doing
> what
> > you want.
> > 
> > 	Dan
> -
> To unsubscribe from this list: send the line "unsubscribe linux-8086" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 

  reply	other threads:[~2002-09-01 19:10 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-25 18:54 286 xterm? Bardelli Luigi
2002-08-25 21:42 ` Stefan de Konink
2002-08-25 21:54   ` Riley Williams
2002-08-25 22:31     ` Stefan de Konink
2002-09-01  6:28   ` Dan Olson
2002-09-01  9:48     ` Luigi Bardelli
2002-09-01 19:10       ` Rob Helmer [this message]
2002-09-01 19:06         ` Stefan de Konink
2002-09-01 19:29     ` Paul Nasrat
2002-09-02  9:44     ` Feher Tamas
2002-09-02 23:31       ` Gavin
2002-09-03  2:23         ` Gregg C Levine
2002-09-03  9:11         ` Feher Tamas
2002-09-03 16:59         ` Blaz Antonic
2002-09-03  9:23           ` Gavin
2002-09-03 17:17             ` Chad Page
2002-09-05 19:45               ` Robert de Bath
2002-09-05 20:17                 ` Francois Gurin
2002-09-05 20:18                 ` Dan Olson
2002-09-06  4:23                   ` Gregg C Levine
2002-09-10  5:44                     ` Robert de Bath
2002-09-10 18:55                       ` Dan Olson
2002-09-12 15:30                         ` Jacek Lipkowski
2002-09-17 16:33                         ` Seemanta Dutta
2002-09-17 16:33                         ` newbie...please help Seemanta Dutta
2002-09-10 21:47                       ` 286 xterm? kees
2002-09-05 21:02                 ` Chad Page
2002-09-03 16:17           ` Bardelli Luigi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20020901121020.A5462@namodn.com \
    --to=robert@namodn.com \
    --cc=Linux-8086@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox