From: Stas Sergeev <stssppnn@yahoo.com>
To: linux-msdos@vger.kernel.org
Subject: Re: increase base memory
Date: Mon, 16 Dec 2002 04:45:19 +0300 [thread overview]
Message-ID: <3DFD302F.1060806@yahoo.com> (raw)
Hello.
kandan bala wrote:
> I came to know the dosemu reserves A000 segment
> reserved for graphics.
> Is it possible to shift OR change another segment
> for graphics.
Ralf Brown memory.lst states:
--------V-MA0000000--------------------------
MEM A000h:0000h - EGA+ GRAPHICS BUFFER
Size: 65536 BYTEs
So it was always there. QEMM have a
program called "vidram", which allows
to use that region as a base memory
by the cost of not being able to diplay
graphics, but vidram will not work
under dosemu because qemm itself doesn't
work under dosemu.
> Is it logically correct.
But how are you running your program
at a pure dos at first (i.e. not
under linux/dosemu)? If your program
works only with QEMM's vidram or something
similar, then your program is broken
at a first place.
Dosemu allows you to use both UMB and
HMA, so there should be no disadvantages
against the pure dos (except that QEMM
with all its wonderfull tricks can't
be used).
> and running a cobol application.
I don't know what cobol was used, but
if it is a MicroFocus cobol, they
provide a DOS extender for it called xm,
wich will let the program to use all
the memory available for DPMI.
Increasing the base memory above 640Kb
is definitely the bad idea, as it is
used very rarely even in a pure DOS
and will cost you the inability to
display graphics.
next reply other threads:[~2002-12-16 1:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-16 1:45 Stas Sergeev [this message]
2002-12-16 5:31 ` increase base memory Sergey Suleymanov
-- strict thread matches above, loose matches on Subject: below --
2002-12-17 16:17 Stas Sergeev
2002-12-16 21:07 Stas Sergeev
[not found] <no.id>
2002-12-16 19:19 ` John Elliott
2002-12-16 20:01 ` Bart Oldeman
2002-12-16 18:09 Stas Sergeev
2002-12-17 5:39 ` Sergey Suleymanov
2002-12-16 1:12 kandan bala
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=3DFD302F.1060806@yahoo.com \
--to=stssppnn@yahoo.com \
--cc=linux-msdos@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