[Turbo Pascal] Q&A official thread

Yes.

I'm using the same concept in my library. This is a "system" call, but for now I'm using these functions as valid callable functions. In newer releases of my library I'll try to create an initializing function (something like a constructor) to point the original ClrScr and GotoXY to my _ClrScr and _GotoXY. These new functions are faster than the older functions that uses BDOS calls that are known to be slower functions.

[]'s
PopolonY2k

Hi Popolony2k,

Yes, 3.3 supports directories so {$I inc\....} works but breaks compatibility downwards because 3.0 can't handle subdirectories.

I tried it, but the code still fails. I downgraded my compiler to 3.0 but the code still crashes. Throwing the same error about IDE commands not working. I tried some other code that performs direct writes to vram and these work. These libraries are based on Kari's code.

PROGRAM MSXDOS;
{$I wrtvram.inc}
{$I fastwrit.inc}

Begin
      FastWrite('Hello World');
End.

Given that I am the only one that has these errors it has to be either something in my setup: the files I am using. These are constant factors between my real machine and the emulated version. My real machine has MFSCC+ card, the emulated machine has a sunrise IDE emulated.

I found that the issue might be European hardware related. When I switch openMSX to Boosted MSX2+ JP the code compiles and executes without crash!. The same for a TurboR in OpenMSX.

PROGRAM MSXDOS;

{$I types.pas}
{$I msxbios.pas}
{$I conio.pas}
Begin
      _ClrScr;
      repeat until keypressed;
       WriteLn(''Hello World');
       repeat until keypressed;
END.

This is also not flawless. After _ClrScr the screen is empty and the line Hello World I added is not displayed, but at least there is no crash.

Thanks!

If you're trying to use something like the Kali's FastWrite function in your program, please consider using my DVRAM.PAS (Direct VRAM) procedures/functions.
These procedures/functions have the same effect of fastwrite but are better because with a simple modification you can still use the same Write and WriteLn standard Pascal procedures.

Check the code below:

Program TestDirectVRAM;

{$i types.pas}
{$i dvram.pas}
{$I msxbios.pas}
{$i conio.pas}     { For _GotoXY function }

Var
       scrHandle : TOutputHandle;
 
Begin
 (* 
  * Open the text mode for direct access, enabling WriteLn and Write to access 
  * the VRAM directly instead using BDOS calls.
  *)
  OpenDirectTextMode( scrHandle );

  (* 
   * Use the standard ClrScr if you're having problems with European machines. 
   * This will be modified in the future and the standard ClrSrc will be pointed 
   * to the new _ClrScr, so all legacy code will work  fully without big changes.
   *)
  _ClrScr;

  WriteLn('Hello World');

  (*
   * If you're using the DVRAM to redirect the Write/WriteLn procedures to the 
   * library's fast VRAM handling the standard GotoXY won't work. Use the 
   * CONIO.PAS _GotoXY procedure instead. This will be modified 
   * in the future and the standard GotoXY will be pointed to the new _GotoXY,
   *  so all legacy code will work fully without big changes.
   *)
  _GotoXY( 10, 10 );

  WriteLn('Hello World');
  CloseDirectTextMode( scrHandle );   { Restore the original handlers }
End.

[]'s
PopolonY2k

Hi friend.

Thanks, I tried this config NMS8250 and I'm facing the same problems you reported here. I think that is related to slot selection. I'll try to fix this.

I think that is a good idea to create a new thread for discussing about PopolonY2k's framework fixes, new ideas and improvements.

[]'s
PopolonY2k

Hi Popolony2k,

I did an attempt to debug the old fashion way (Writeln() before and after each line of code) and I also had a my doubts about CallSlt. At least I am glad to see that my problem can be reproduced