Bios

new topic     » goto parent     » topic index » view thread      » older message » newer message

Ben Van Poppel writes:
> I'm a beginner in Euphoria. I am also blind, and the first thing that I=

> noticed with Euphoria programs is they don't talk. The reason is that t=
he
> text is written directly to the screen and not through bios. =


That's strange. Euphoria calls a WATCOM C routine to perform all
text output to the screen. That routine is documented as using the
system BIOS. Calls to Euphoria's puts() and printf(), when directed
to the screen, use this C routine. The standard Euphoria editor, ed,  =

calls puts(). It never pokes values directly to screen memory.

A tiny percentage of Euphoria programs call display_text_image() in image=
=2Ee. =

It *does* poke values directly to screen memory. David Cuny's
editor uses pokes and calls to display_text_image(). It would
therefore give you problems.

Euphoria runs in 32-bit protected mode, and switches to 16-bit mode
to do system calls, such as text output. I wonder if this =

DOS-extended nature of Euphoria could somehow be upsetting =

your screen-reading software.

Regards,
  Rob Craig
  Rapid Deployment Software
 =

new topic     » goto parent     » topic index » view thread      » older message » newer message

Search



Quick Links

User menu

Not signed in.

Misc Menu