Has anyone else had problems with  some Turbo Pascal code not loading on
the latest high speed machines.  I am getting error 200 (divide by zero)
messages from some code.  On some machines this happens every time  and
others some of the time.  The code  in question has been working fine
for years. WHOHAS.EXE behaves in exactly the same way.

Has anyone else had problems with  some Turbo Pascal code not loading on
the latest high speed machines.  I am getting error 200 (divide by zero)
messages from some code.  On some machines this happens every time  and
others some of the time.  The code  in question has been working fine
for years.  WHOHAS.EXE behaves in exactly the same way.

Has anyone else had problems with  some Turbo Pascal code not loading on
the latest high speed machines.  I am getting error 200 (divide by zero)
messages from some code.  On some machines this happens every time  and
others some of the time.  The code  in question has been working fine
for years. WHOHAS.EXE behaves in exactly the same way.

Now think again.

 124) Curing Crt initialization runtime error 200 on fast machines

 149061 Jul 19 1998 ftp://garbo.uwasa.fi/pc/link/tsfaqp.zip
 tsfaqp.zip Common Turbo Pascal Questions and Timo's answers, linked

   All the best, Timo

....................................................................
Prof. Timo Salmi   Co-moderator of news:comp.archives.msdos.announce
Moderating at ftp:// & http://garbo.uwasa.fi/ archives 193.166.120.5
Department of Accounting and Business Finance  ; University of Vaasa
mailto:t...@uwasa.fi <http://www.uwasa.fi/~ts/>  ; FIN-65101,  Finland

Pascal Start-Up Error 200 on fast PCs when using the Crt unit is a VFAQ!

Read the many earlier postings in the comp.lang.pascal.borland (Frank H,
Roger D, ...) and borland.public.turbopascal newsgroups (you can use
DejaNews), including the comp.lang.pascal.borland mini-FAQ, and Prof.
Salmi's FAQ  ftp://garbo.uwasa.fi/pc/link/tsfaqp.zip #124, and/or see
http://www.merlyn.demon.co.uk/  clpb-faq.txt  pas-time.htm  pas-linx.htm
Some collected patches are in http://www.merlyn.demon.co.uk/zipfiles/
Another fix is to avoid all use of the Crt unit, or, if accurate delay is
not needed, to compile with TP5 or TP6.

 iw> Folks

 iw> Has anyone else had problems with  some Turbo Pascal code not
 iw> loading on the latest high speed machines.  I am getting error 200
 iw> (divide by zero) messages from some code.  On some machines this
 iw> happens every time  and others some of the time.  The code  in
 iw> question has been working fine for years. WHOHAS.EXE behaves in
 iw> exactly the same way.

 iw> Ian Stone

Not again! NOOOOOOOO!

In article <aea_9808152...@mnet.pubnix.ten>, Frank McCormick <has.no.ema
il.acc...@f819.n514.z17.mnet.pubnix.ten> writes

Unit Fdelay;             { Use this before CRT }

interface

const dfix:word=1;       { call delay() dfix times }

implementation

uses dos;

procedure oldints; assembler; { "variables" in the code segment }
          asm dd 0,0 end;

Procedure error;
begin
  runerror(200);
End;

Procedure Int0; assembler;
          asm
          cmp cx,55       { If CX<>55 we are at some other point }
          je @ok
          sti
          call error
@ok:
          shr dx,1        { divide dx:ax by 2 }
          rcr ax,1
          shl Dfix,1      { multiply Dfix by 2 }
          iret            { return to the DIV (286+) }
          end;

{ Int21h handler removes the int0 handler (as well as itself) from the
  memory when CtrlBreak vector is set by CRT right after calculating
  the delay counter. Note DS does NOT point to the data segment when
  this is called }

Procedure Int21h; assembler;
          asm
          cmp ax,$251B
          jne @old               { Not setint 1Bh? }

          push es; push si; push di
          mov si,offset oldints
          xor di,di
          mov es,di
          cld
          segcs; movsw
          segcs; movsw           { restore int 0 }

          mov di,$21*4
          segcs; movsw           { restore int 21h }
          segcs; movsw
          pop di; pop si; pop es

@old:     db $2e,$ff,$2e         { jmp far indirect cs:[oldints+4] }
          dw offset oldints+4
          end;

type tr=record int0,int21:pointer; End;
     pr=^tr;

begin
  GetIntVec(0,pr(@oldints)^.int0);
  GetIntVec($21,pr(@oldints)^.int21);

  SetIntVec(0,@int0);
  SetIntVec($21,@int21h);
end.