public inbox for linux-8086@vger.kernel.org
 help / color / mirror / Atom feed
From: Dan Olson <dano@agora.rdrop.com>
To: linux-8086@vger.kernel.org
Subject: RE: 768k XT?
Date: Tue, 10 Jun 2003 18:54:18 -0700 (PDT)	[thread overview]
Message-ID: <20030610185135.B98615@agora.rdrop.com> (raw)
In-Reply-To: <BKEGKPICNAKILKJKMHCAEEHPEEAA.Riley@Williams.Name>

>  > Has anyone ever run into this before?
>
> I've run into similar - in my case, a Kyoshui XT with 4x256k
> mapped as 640k of normal RAM and 384k of EMS RAM (permanently
> in the D0000-DFFFF address range.

Interesting, it's nice to know that someone else thought of such a thing,
and to know there there is always a chance.  Is there any indication
(durring the memory check or by any other method) that this memory is
present?

 > Technically, it's possible that one of the 256k banks has one
of > the address pins permanently tied either high or low, and thus
> that the extra 128k isn't mapped anywhere as a result.

Sure, that's actually what I suspect to be the case.

>  > Does anyone have any DOS utilities or ELKS utilities that
>  > would test for upper RAM even though the BIOS says it's
>  > not there?
>
> As far as RAM above 1M is concerned, the XT processors don't
> support it.

Sure, I'm just refering to the memory between 640k and 1M, if present.

	Dan

  reply	other threads:[~2003-06-11  1:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-07 19:36 ELKS on Laptops Juanjo Marín
2003-06-10 20:43 ` 768k XT? Dan Olson
2003-06-10 21:57   ` Chad Page
2003-06-11  1:46     ` Dan Olson
2003-06-10 23:14   ` Riley Williams
2003-06-11  1:54     ` Dan Olson [this message]
2003-06-14  9:57   ` jb1
2003-06-14 20:26     ` Dan Olson
2003-06-15  9:23   ` jb1
2003-06-15 18:24     ` Dan Olson

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=20030610185135.B98615@agora.rdrop.com \
    --to=dano@agora.rdrop.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