From: Peter Jay Salzman <p@dirac.org>
To: phrostie <pfrostie@yahoo.com>
Cc: linux-msdos@vger.kernel.org
Subject: Re: Doom in Linux HOWTO
Date: Sun, 8 Dec 2002 10:12:48 -0800 [thread overview]
Message-ID: <20021208181248.GA29890@dirac.org> (raw)
In-Reply-To: <01KPSFYJFKG494LYS0@SMTP00.InfoAve.Net>
because he wanted to detail doom under dosemu. :) sometimes this kind
of reason is simply enough when you're talking about linux.
btw, lxdoom is totally outdated. that project has merged with 2 other
doom port projects and has formed prboom.
i think doom legacy is the best; you have mouse look up and down (like
quake) and can jump.
pete
begin phrostie <pfrostie@yahoo.com>
> sorry i'm late getting into this but why can't you run either:
>
> lxdoom-svga 1.4.4-7
> Svgalib binary for lxdoom
> or
> lxdoom-x11 1.4.4-7
> X binary for LxDoom
>
> do they not have needed features?
--
Fingerprint: B9F1 6CF3 47C4 7CD8 D33E 70A9 A3B9 1945 67EA 951D
next prev parent reply other threads:[~2002-12-08 18:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-08 14:35 Doom in Linux HOWTO Stas Sergeev
2002-12-08 16:55 ` Stian Sletner
2002-12-08 19:36 ` phrostie
2002-12-08 18:12 ` Peter Jay Salzman [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-01-07 18:53 Stas Sergeev
2002-12-08 20:10 Stas Sergeev
2002-12-08 3:38 Stian Sletner
2002-12-08 4:47 ` Bart Oldeman
2002-12-08 4:58 ` Stian Sletner
[not found] ` <20021208043551.GA23189@dirac.org>
[not found] ` <20021208045400.GD15769@sletner.com>
[not found] ` <20021208061926.GA26833@dirac.org>
[not found] ` <20021208063342.GF15769@sletner.com>
[not found] ` <20021208064541.GA27112@dirac.org>
[not found] ` <20021208065503.GA25194@sletner.com>
2002-12-08 19:19 ` Peter Jay Salzman
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=20021208181248.GA29890@dirac.org \
--to=p@dirac.org \
--cc=linux-msdos@vger.kernel.org \
--cc=pfrostie@yahoo.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.