public inbox for xconq7@sourceware.org
 help / color / mirror / Atom feed
From: "Erik Jessen" <ejessen@adelphia.net>
To: <pessolo@freemail.it>, "'Hans Ronne'" <hronne@comhem.se>
Cc: <xconq7@sources.redhat.com>
Subject: RE: HW requirements
Date: Sun, 11 Jan 2004 00:25:00 -0000	[thread overview]
Message-ID: <000501c3d7da$918068e0$6401a8c0@Win2k> (raw)
In-Reply-To: <16384.37380.662950.518268@gargle.gargle.HOWL>

How many people use VT100 any more?

Erik

-----Original Message-----
From: klaus schilling [mailto:510046470588-0001@t-online.de]
Sent: Saturday, January 10, 2004 4:00 PM
To: Hans Ronne
Cc: Erik Jessen; xconq7@sources.redhat.com
Subject: Re: HW requirements

Hans Ronne writes:
 > As I said, 24 MB of RAM is required. I don't think disk space or CPU
speed
 > is an issue on any machine that can run Xconq. The only serious
limitation
 > on machines that people still use today is the poor graphics support
in
 > pre-NT versions of Windows (98 etc). Which is a OS problem, not a
hardware
 > problem.

but there's still the curses version which does not require anything
beyond 
a vt100 display

Klaus Schilling


  reply	other threads:[~2004-01-11  0:25 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-07  2:40 New Action: change-type Eric McDonald
2004-01-07  2:47 ` Erik Jessen
2004-01-07  3:30   ` Eric McDonald
2004-01-07  2:51 ` Lincoln Peters
2004-01-07  4:04 ` Hans Ronne
2004-01-07  4:31   ` Eric McDonald
2004-01-07 20:08   ` klaus schilling
2004-01-07 20:17     ` Eric McDonald
2004-01-07 20:26     ` Hans Ronne
2004-01-07 20:47       ` Eric McDonald
2004-01-07 21:22         ` Eric McDonald
2004-01-08  6:28           ` Erik Jessen
2004-01-08 16:26             ` Eric McDonald
2004-01-10  5:49               ` Erik Jessen
2004-01-10 16:42                 ` Eric McDonald
2004-01-10 17:57                   ` Hans Ronne
2004-01-10 18:59                     ` HW requirements Erik Jessen
2004-01-10 19:44                       ` Hans Ronne
2004-01-10 23:31                         ` klaus schilling
2004-01-11  0:25                           ` Erik Jessen [this message]
2004-01-11  3:44                             ` Jim Kingdon
2004-01-11  7:25                               ` Erik Jessen
2004-01-11  7:45                                 ` Eric McDonald
2004-01-11  7:52                                   ` Erik Jessen
2004-01-11 21:19                                   ` Jim Kingdon
2004-01-11  0:31                           ` Hans Ronne
2004-01-08  3:48         ` New Action: change-type Hans Ronne
2004-01-08  4:28           ` Eric McDonald
2004-01-08  6:39             ` Hans Ronne
2004-01-08 16:46               ` Eric McDonald
2004-01-11 16:48 HW requirements Feneric Brown
2004-01-11 17:02 ` Erik Jessen
2004-01-13 10:42   ` Bruno Boettcher
2004-01-11 16:52 Feneric Brown
2004-01-11 18:10 Feneric Brown
2004-01-11 20:05 ` Jim Kingdon
2004-01-11 18:12 Eric W. Brown
2004-01-12 17:19 ` Eric McDonald
2004-01-13 15:59 Eric W. Brown

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='000501c3d7da$918068e0$6401a8c0@Win2k' \
    --to=ejessen@adelphia.net \
    --cc=hronne@comhem.se \
    --cc=pessolo@freemail.it \
    --cc=xconq7@sources.redhat.com \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).