From: Paul Nasrat <pauln@truemesh.com>
To: linux-8086@vger.kernel.org
Subject: Re: ELKS port of Adventure - help needed :)
Date: Wed, 11 Dec 2002 22:51:06 +0000 [thread overview]
Message-ID: <20021211225105.GA10355@raq465.uk2net.com> (raw)
In-Reply-To: <200212112222.gBBMMA5G007271@eddie.loc>
On Wed, Dec 11, 2002 at 10:22:13PM +0000, Richard Wallman wrote:
> On 11 Dec, Richard Wallman wrote:
>
> > Possible a source code or bcc problem
>
> It's a bcc problem: strcmp doesn't return the right values.
Cheers that's a great pointer, oh well time to get my hands dirty...
> Paul: short answer = rewrite strcmp. Only "vocab.c" and "english.c" use
> that function, so just replace all references. sed is your friend. :)
Indeed - I'll hopefully have some time to do this tomorrow. I have the
bcc archives to hand so can look at previous versions to brush up my
asm.
Just got nice shiny 8086 laptop - but without floppy/serial. It's an
Olivetti Quaderno, I may be able to use a flash pcmcia disk on it to get
elks onto it, but we'll see. Else it's going to be pinouts from usenet
and some soldering (eep)...
Paul
next prev parent reply other threads:[~2002-12-11 22:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-10 13:07 ELKS port of Adventure - help needed :) Paul Nasrat
2002-12-11 8:19 ` Phil Goembel
2002-12-11 21:27 ` Richard Wallman
2002-12-11 22:22 ` Richard Wallman
2002-12-11 22:46 ` Richard Wallman
2002-12-11 22:51 ` Paul Nasrat [this message]
2002-12-11 23:59 ` Phil Goembel
2002-12-12 7:39 ` Paul Nasrat
2002-12-12 8:18 ` Paul Nasrat
2002-12-12 19:11 ` Adventure - the answer to what went wrong? Richard Wallman
2002-12-12 20:21 ` Harry Kalogirou
2002-12-12 20:52 ` Alan Cox
2002-12-12 20:27 ` Dan Olson
2002-12-12 20:29 ` Harry Kalogirou
2002-12-12 20:41 ` Dan Olson
2002-12-12 21:15 ` Alan Cox
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=20021211225105.GA10355@raq465.uk2net.com \
--to=pauln@truemesh.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