7cd
Subj : Re: cputs does not work in graphics-modi ?
To   : borland.public.cpp.borlandcpp
From : R.Wieser
Date : Sat Sep 10 2005 12:41 pm

Bob Gonder <notbg@notmindspring.invalid> schreef in berichtnieuws
9vk4i1demqcoiga5k91kisfcrl5h8fggr1@4ax.com...
> R.Wieser wrote:

Hello Bob,

> >And that seems to be the problem : the system forces restrictions that
are
> >not correct for the screen-mode I've choosen.
>
> "Not correct"  now, or back when the compiler was new?

Would be a bit difficult for me to look to "back when" would it not ?

But do you think that mode 12h (driver=vga, mode=vgahi) would have changed
in between ?   As far back as I can see mode 12h has allways been 80x30 text
....

> If you are choosing a screen mode that doesn't support those
> functions, then there is no surprise that they don't do what you want.

You're assuming something I didn't.   But it actually does not matter :
if/when I would be able to select a mode unknown to the system (by means
offered by that same system) I should be able to inform it of the settings
it should use for that mode.   And I don't get the idea that that is
possible ....

> One way is to use new, better than the old, versions of the compiler
> and OS.

Am I hearing a Gates-adept here ?   "new versions are better than old
version, whatever the reason" :-)

> Or, in this particular case, to use graphics functions on your
> graphics screen instead of tyring to use text functions on a graphics
> screen.

I'm sorry ?   The bios console-output works without any problems (after I
set the "directvideo"-switch you've shown me to 0x00), only the compiler is
currently limiting the cursor-movement.   Is that a good reason to "just
ditch it" and use a (as far as I consider it) work-around ?

As for  work-around ?  I can use INT 10h, ah=02h to move the cursor
whereever I want it to go (and use the normal console-output commands).
But I'd rather not.

Regards,
  Rudy Wieser

.

0