From: "Vikas Kumar" <walburn@gmail.com>
To: Dennis Lubert <plasmahh@projectiwear.org>
Cc: linux-8086@vger.kernel.org
Subject: Re: Hardware requirements
Date: Mon, 15 May 2006 09:07:22 -0400 [thread overview]
Message-ID: <792c60620605150607q5ef19566u81fcb5676504d2f3@mail.gmail.com> (raw)
In-Reply-To: <1147695063.5703.10.camel@speedy.projectiwear.org>
Dennis,
Feel lucky that you have a hard drive !!
I ran ELKS on an 80C86 (8086 with CMOS) processor with a 720KB floppy
drive and 640KB RAM (my machine doesnt have a hard drive). So you have
enough, or should I say a very powerful configuration to run ELKS.
regards
Vikas
On 5/15/06, Dennis Lubert <plasmahh@projectiwear.org> wrote:
> Hello people,
>
> it looks like the project isnt really dead, thats cool. My mom recently
> called me and asked me if she can throw away my "old computer stuff" and
> among lots of stuff there was an old PC-D with the following Hardware:
>
> 80186 CPU
> 896kB of RAM
> 13MB HDD
> 5 1/4" 720kB floppy
>
> The question now is, if it could be possible to run that project on such
> a system, or if its desired to make it run on it. Im planning to get
> that stuff to my house during the summer. I also have a second system,
> but unfortunately some chips and stuff are missing, but it has a 80187
> FPU, maybe its worth repairing it (mainly the power supply is missing
> among most of the chips of the board)
>
> greets
>
> Dennis
>
> -
> 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
>
--
Capitalization is the difference between "I had to help my uncle Jack
off a horse.." and "I had to help my uncle jack off a horse.."
next prev parent reply other threads:[~2006-05-15 13:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-15 12:11 Hardware requirements Dennis Lubert
2006-05-15 13:07 ` Vikas Kumar [this message]
2006-05-15 15:07 ` Dennis Lubert
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=792c60620605150607q5ef19566u81fcb5676504d2f3@mail.gmail.com \
--to=walburn@gmail.com \
--cc=linux-8086@vger.kernel.org \
--cc=plasmahh@projectiwear.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