Board index » delphi » Patch turbo.exe with directvideo:=false?

Patch turbo.exe with directvideo:=false?

Hi!

Does some kind soul know of a patch for the turbo.exe-binary of TP6 or TP7  
in that the IDE will use the BIOS INT10h for its own screen interactions?
(=To run it on a 9110-PDA with an incompatible screen-memory layout)

If it is true that Borland's IDE has been compiled with TurboVision, then  
this would indicate they are currently just using a "directvideo:=true" in  
their own code.
I compiled a small sample program with TP6 and debugged to find out that  
TP simply generates a "MOV BYTE PTR [$0046],0" (..,1) for  
directvideo:=false (true), that is: The byte at address $46 is used as a  
flag and each screen output checks for its value to either call INT10h or  
a routine which blasts the string to the screen directly.

Scanning turbo.exe for something similar doesn't work however, as the  
d*mned TDEBUG fails on remote debugging turbo.exe (shame on you,  
Borland!).

-Any hints or brillant ideas how to achieve this?

Kai

--
Kai Rohrbacher, kairo AT maya DOT inka DOT de
(If you want to reply in private, please use this address)

 

Re:Patch turbo.exe with directvideo:=false?


Kai Rohrbacher <myelectronicdust...@gmx.de> said
Quote
>Hi!

>Does some kind soul know of a patch for the turbo.exe-binary of TP6 or TP7
>in that the IDE will use the BIOS INT10h for its own screen interactions?
>(=To run it on a 9110-PDA with an incompatible screen-memory layout)

Same reply you got in bptp : not a chance but you *may* stand a chance
with TP3.

--
Information on Newsgroup posted weekly on Sunday - read before writing!
Contains links to    |  http://www.pedt.serve.net.uk/faq/clpb-faq.txt
helpful information  |  http://www.merlyn.demon.co.uk/clpb-faq.txt
and some guidelines  |  ftp://garbo.uwasa.fi/pc/doc-net/faqclpb.zip

Re:Patch turbo.exe with directvideo:=false?


In article <7cLhq9Br...@gmx.de>,

Quote
Kai Rohrbacher <myelectronicdust...@gmx.de> wrote:
>Hi!

>Does some kind soul know of a patch for the turbo.exe-binary of TP6 or TP7  
>in that the IDE will use the BIOS INT10h for its own screen interactions?
>(=3DTo run it on a 9110-PDA with an incompatible screen-memory layout)

>If it is true that Borland's IDE has been compiled with TurboVision, then  
>this would indicate they are currently just using a "directvideo:=3Dtrue" i=
>n  
>their own code.

The problem is that Turbo Vision has its own screen handling routines
and does not use CRT.

Quote
>I compiled a small sample program with TP6 and debugged to find out that  
>TP simply generates a "MOV BYTE PTR [$0046],0" (..,1) for  
>directvideo:=3Dfalse (true), that is: The byte at address $46 is used as a  
>flag and each screen output checks for its value to either call INT10h or  
>a routine which blasts the string to the screen directly.

Note that the offset of the variable varies.

Quote
>Scanning turbo.exe for something similar doesn't work however, as the  
>d*mned TDEBUG fails on remote debugging turbo.exe (shame on you,  
>Borland!).

>-Any hints or brillant ideas how to achieve this?

Get a better system. I cannot imagine why anyone would write a system
that does not work on screen writes as they are the norm that one uses.

Are you sure that it works with BIOS calls? Or does it require DOS calls?

Osmo

Quote
>Kai

>--
>Kai Rohrbacher, kairo AT maya DOT inka DOT de
>(If you want to reply in private, please use this address)

Other Threads