is fine but 256k is to
little for compass.
Thanks and if i have another question you'll see it here
:)
Greetz,
Antal
-Original Message-From:
[EMAIL PROTECTED] [EMAIL PROTECTED]To: [EMAIL PROTECTED] [EMAIL PROTECTED]Date: Thursday,
September 02, 1999 11:55 PMSubject: BDOS
Hi
It depends on some other things.
Are you using DOS 1 or DOS 2 ?
What is the current slot setting and where is this memman segment located ?
Do you have two memory mappers ? This gives some problems in DOS 2.
[EMAIL PROTECTED] wrote:
Hi,
Does BDOS use the standard TPA segments if you use
Hi,
Does BDOS use the standard TPA segments if you use the
BDOS call random block read to read a file ?
The reason i ask is that whenever i want to load the file in a
segment switched by my memory manager (memman) the
data is not present! It seems BDOS switches back the standard
TPA segment
At 11:47 PM 9/2/99 +0200, you wrote:
Does BDOS use the standard TPA segments if you use the BDOS call
random block read to read a file ?
From the DOS2 Program Interface Specification: (section 2.5)
"Any disk transfers will be done to the RAM segments which are paged in
when the function
for that and the (some?) BDOS-routines set back the page to the
'original' page. Dos2 mapperselectroutines are as fast as possible, the
only
thing they do is write the value to the mapperport and back it up somewhere
in the memory. The latter is not done when directly accessing the I/O ports
and I don't know
However, there is a restriction on the slot the RAM must be in:
"environment strings and disk transfer areas must be in the mapper RAM
slot."
I think "the mapper RAM slot" means the main mapper (primairy mapper
slot).
On turbo R, this is the internal mapper, on other MSXes this is the
From the DOS2 Program Interface Specification: (section 2.5)
"Any disk transfers will be done to the RAM segments which are paged in
when the function call is made, even if they are not the original TPA
segments."
So, if Memman tells DOS2 which segments are selected (I assume it does),
this is
] manager (memman) the data is not present ! It seems BDOS switches back =
] the standard TPA segment and
] places the data in the standard TPA segment whenever loading. After that =
] my segment is placed back... ?
]
This is indeed the case with MSXDOS2. MSXDOS2 always loads data to the
sp
[EMAIL PROTECTED] wrote:
"environment strings and disk transfer areas must be in the mapper RAM
slot."
...
Is there a workaround for this problem ?
no
you must allocate a primary mapper segment for your disktransfers or use
a TPA segment for that purpose. And copy the data to another
Hi,
Does BDOS use the standard TPA segments if you use the BDOS
call random block read to read a
file ?
The reason i ask is that whenever i want to load the file
ina segment switched by my memory
manager (memman) the data is not present ! It seems BDOS
switches back the standard TPA
:MHGVCPM MSX1 00h - Program terminate
: CPM MSX1* 01h - Console input
: CPM MSX1* 02h - Console output
:
: What do those asterisks ('*') indicate?
:
:LH Those are non-CP/M-compatible MSX-DOS Bdos-calls.
:
:
: No, that can't be it: CP/M has functions 01H (Read Console
Greetings, ~Grauw...
MHGVCPM MSX1 00h - Program terminate
CPM MSX1* 01h - Console input
CPM MSX1* 02h - Console output
What do those asterisks ('*') indicate?
LH Those are non-CP/M-compatible MSX-DOS Bdos-calls.
No, that can't be it: CP/M has functions 01H (Read
12 matches
Mail list logo
