From: Dieter Kedrowitsch <dieter.kedrowitsch@gmail.com>
To: linux-8086@vger.kernel.org
Subject: Re: Console output corruption
Date: Wed, 10 Mar 2010 13:25:12 -0500 [thread overview]
Message-ID: <ba3128e11003101025medb7497j9c1b8d1bdb7ea263@mail.gmail.com> (raw)
In-Reply-To: <7A01080381764DE0B2C2FF7F21F4DF7E@linux104>
Hans, thanks for the reply.
Unfortunately my C debugging skills are pretty much non-existent.
It's a shame because it seems ELKS has the potential to be rolled into
a pretty neat little 8088 Linux OS.
I will poke around a little to see if I can figure it out, but I fear
without further assistance I will be unable to get this little beast
to behave and run smoothly on my 8088.
If anyone who is still following the list has the time and ability to
help me out, please feel free to chime in!
Thanks!
On Wed, Mar 10, 2010 at 12:53 PM, Hans <hans64@ht-lab.com> wrote:
> I guess a good place to start is cprintf.c located in the dev86\libc\conio.
> Unfortunately ELKS seems to have been abandoned by most if not all
> developers so I am afraid you will be on your own. If only I had some more
> spare time .......
>
> Good luck,
>
> Hans
> www.ht-lab.com
next prev parent reply other threads:[~2010-03-10 18:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-10 14:28 Console output corruption Dieter Kedrowitsch
2010-03-10 17:53 ` Hans
2010-03-10 18:25 ` Dieter Kedrowitsch [this message]
2010-04-18 14:50 ` Phil Goembel
2010-04-18 15:17 ` Mario Frasca
2010-04-18 15:45 ` Phil Goembel
2010-04-18 16:07 ` Mario Frasca
-- strict thread matches above, loose matches on Subject: below --
2010-04-18 16:34 Hans
2010-04-18 18:40 ` Phil Goembel
2010-04-18 20:04 ` Mario Frasca
[not found] ` <v2w5a4d65ae1004181614m86200731mcc4a1fcab0cc3a56@mail.gmail.com>
2010-04-19 1:12 ` Kirn Gill
2010-04-19 14:05 ` Mario Frasca
2010-04-19 14:35 ` Mario Frasca
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=ba3128e11003101025medb7497j9c1b8d1bdb7ea263@mail.gmail.com \
--to=dieter.kedrowitsch@gmail.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