From: "Riley Williams" <Riley@Williams.Name>
To: Dan Olson <dano@agora.rdrop.com>, linux-8086@vger.kernel.org
Subject: RE: 768k XT?
Date: Wed, 11 Jun 2003 00:14:47 +0100 [thread overview]
Message-ID: <BKEGKPICNAKILKJKMHCAEEHPEEAA.Riley@Williams.Name> (raw)
In-Reply-To: <20030610133844.D98615@agora.rdrop.com>
Hi Dan.
> Hopefully someone knows, I have a Samsung XT clone that has
> 3 banks of 256k chips, so that would mean a total of 768k or
> memory. The BIOS memory check reports 640k, so I'm wondering
> if there really is 768k available somehow, or if it was just
> cheaper to use 256k chips and leave a few k unused.
I don't know that particular box, so can't comment there, but...
> 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.
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.
> Is anyone familiar with any other boards that allowed the use
> of 256k parts in place of the 64k chips in order to add some
> upper memory?
Other than the above, no.
> 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.
Best wishes from Riley.
---
* Nothing as pretty as a smile, nothing as ugly as a frown.
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.488 / Virus Database: 287 - Release Date: 5-Jun-2003
next prev parent reply other threads:[~2003-06-10 23:14 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 [this message]
2003-06-11 1:54 ` Dan Olson
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=BKEGKPICNAKILKJKMHCAEEHPEEAA.Riley@Williams.Name \
--to=riley@williams.name \
--cc=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