From: CodeMonk on
Frank Kotler wrote:
> CodeMonk wrote:
>> Frank Kotler wrote:
>>
>>> Herbert Kleebauer wrote:
>>>
>>>> Frank Kotler wrote:
>>>>
>>>>
>>>>> And the
>>>>> monochrome screen is at B0000h, not B80000h, if you care...
>>>>
>>>>
>>>>
>>>> As far I remember, it's neither B0000h nor B80000. DOS programming
>>>> must be really dead when such essential values aren't correctly
>>>> remembered.
>>>
>>>
>>> Okay, refresh my memory...
>>>
>>> Best,
>>> Frank
>>>
>>
>> Both values contained an extra zero, but no big deal - it's like
>> 'mispelling' a word during an Instant Messaging session, they know
>> what you mean.
>
> If I'da meant "B000:0000" I would've said so. Are you guys telling me
> the tut is correct?
>
> Best,
> Frank

Actually that's my bust, I read the "B80000" and assumed I knew what
the actual issue was. Maybe next time I should read the whole thread
first. I return you to your regularly scheduled program. :)

- Scott
From: Herbert Kleebauer on
Frank Kotler wrote:

> >>>> And the
> >>>> monochrome screen is at B0000h, not B80000h, if you care...
> >>>
> >>> As far I remember, it's neither B0000h nor B80000. DOS programming
> >>> must be really dead when such essential values aren't correctly
> >>> remembered.
> >>
> >> Okay, refresh my memory...
> >
> > Both values contained an extra zero, but no big deal - it's like
> > 'mispelling' a word during an Instant Messaging session, they know what
> > you mean.
>
> If I'da meant "B000:0000" I would've said so. Are you guys telling me
> the tut is correct?

Isn't it b8000 for text mode (and a0000 for graphics mode)?
From: SpooK on
On Aug 14, 12:01 pm, Herbert Kleebauer <k...(a)unibwm.de> wrote:
> Frank Kotler wrote:
> > >>>> And the
> > >>>> monochrome screen is at B0000h, not B80000h, if you care...
>
> > >>> As far I remember, it's neither B0000h nor B80000. DOS programming
> > >>> must be really dead when such essential values aren't correctly
> > >>> remembered.
>
> > >> Okay, refresh my memory...
>
> > > Both values contained an extra zero, but no big deal - it's like
> > > 'mispelling' a word during an Instant Messaging session, they know what
> > > you mean.
>
> > If I'da meant "B000:0000" I would've said so. Are you guys telling me
> > the tut is correct?
>
> Isn't it b8000 for text mode (and a0000 for graphics mode)?

Correct... mostly. The base addresses are as follows...

MONOCHROME = B000:0000 (0x000B0000)
COLOR = B800:0000 (0x000B8000)
GRAPHICS = A000:0000 (0x000A0000)

From: Herbert Kleebauer on
SpooK wrote:
>
> On Aug 14, 12:01 pm, Herbert Kleebauer <k...(a)unibwm.de> wrote:
> > Frank Kotler wrote:
> > > >>>> And the
> > > >>>> monochrome screen is at B0000h, not B80000h, if you care...
> >
> > > >>> As far I remember, it's neither B0000h nor B80000. DOS programming
> > > >>> must be really dead when such essential values aren't correctly
> > > >>> remembered.
> >
> > > >> Okay, refresh my memory...
> >
> > > > Both values contained an extra zero, but no big deal - it's like
> > > > 'mispelling' a word during an Instant Messaging session, they know what
> > > > you mean.
> >
> > > If I'da meant "B000:0000" I would've said so. Are you guys telling me
> > > the tut is correct?
> >
> > Isn't it b8000 for text mode (and a0000 for graphics mode)?
>
> Correct... mostly. The base addresses are as follows...
>
> MONOCHROME = B000:0000 (0x000B0000)
> COLOR = B800:0000 (0x000B8000)
> GRAPHICS = A000:0000 (0x000A0000)

Then sorry Frank. I'm old, but not old enough to have programmed a
IBM PC with something older than VGA (at that time I used the
superior Atari ST).
From: opexoc on
On 14 Sie, 14:46, Frank Kotler <fbkot...(a)verizon.net> wrote:

> > Another question: Is it really necessary to enable A20 line to enter
> > PM?
>
> If you want to access "odd megabytes", yeah.

Actually, why "odd megabytes"? Why A20 line decide if odd megabytes
are available?



First  |  Prev  |  Next  |  Last
Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
Prev: NASM HelloWorld - DOS
Next: ELF loading