public inbox for linux-8086@vger.kernel.org
 help / color / mirror / Atom feed
From: Dan Olson <dano@agora.rdrop.com>
To: Chad Page <cpage@silcom.com>
Cc: linux-8086@vger.kernel.org
Subject: Re: 768k XT?
Date: Tue, 10 Jun 2003 18:46:02 -0700 (PDT)	[thread overview]
Message-ID: <20030610184345.P98615@agora.rdrop.com> (raw)
In-Reply-To: <Pine.GSO.3.96.1030610145609.20032B-100000@beach.silcom.com>

I could look for documentation I guess, but I'm not familar enough with
DOS debug to know how to test for memory (I presume just writing to that
address and seeing if there's anything there afterward).  I have a VGA
card in it now but could use anything I suppose.  It's most likely that
the memory is linear but that may not be the case.  I was also wondering
if there might be a register somewhere that turn the RAM on/off.

	Dan


On Tue, 10 Jun 2003, Chad Page wrote:

>
> 	Use DOS debug to see if there's memory between segments a000 and
> b000/b800, depending on the video type.  It might also have an MMU of some
> sort, but that would be rather unlikely.
>
> 	- Chad
>
>
> On Tue, 10 Jun 2003, Dan Olson wrote:
>
> > 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.  Has anyone ever run into this before?  Is anyone familar with any
> > other boards that allowed the use of 256k parts in place of the 64k chips
> > in order to add some upper memory?  Does anyone have any DOS utilities or
> > ELKS utilities that would test for upper RAM even though the BIOS says
> > it's not there?  Thanks.
> >
> > 	Dan
> >
> > -
> > 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
> >
>
>

  reply	other threads:[~2003-06-11  1:46 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 [this message]
2003-06-10 23:14   ` Riley Williams
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=20030610184345.P98615@agora.rdrop.com \
    --to=dano@agora.rdrop.com \
    --cc=cpage@silcom.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