Newsgroup: it.comp.lang.pascal
Titolo: error 200 (division by zero) piccola spiegazione

riporto questo messaggio:
Mandato da........: F1LXJ
Indirizzato a.....: ALL   @WW
Tipo/Stato........: BF
Data/Ora (ARRIVO) : 11-Nov-1999 * Ore 21:03 LOC
Data/Ora (ORIGINE): 11-Nov-1999 * Ore 08:05 GMT
Bid (Mid).........: 1356-F1LXJ
Messaggio numero #: 744940
Titolo (Soggetto) : My clock badly TIC on CELERON
Complements of information on the problem of the Pentium II and Celeron
All programs developed by Turbo (Borland) Pascal risk to block on a
Pentium II and celeron by producing an error 200 (division by zero).
With MSDOS 6 and more, on PC celeron A.
It is the case of JVFAX 7.1
Reason :
There exists a bogue in unites it CRT Borland (low code level).
To calculate periods of the program Turbo and Borland Pascal with a
precision
of 1 milliseconde on machines with a tic of clock of 55 millisecondes,
they count the number of time that the process can to execute a buckle in
a tic of clock and divide this figure by 55.
Unfortunately, the new Pentium II, and Celeron can execute more 65 536
buckles
by milliseconde.
When the obtained figure is divided  by 55, an overflow produced in the
instruction division 16 bits, as indicated by the error 200 (division by
zero).
Contournement of the problem :
It has been developed a utilitarian that can be used to rectify this problem
in all program.
TO note nevertheless that all timing or period calculated  by the program
not
will be more executed during the correct period.
The program tplfix.exe corrects the problem.
Effectively after having pass JVFAX 7.1  to the blender (TPLFIX) the program
functions without this planted, but as the timing is no longer executed
during
the good period, the quality of images is  finds some  strongly degraded.
On the other hand if I boot the PC with a IBMDOS 3.31, and that I use the
version not to modify JVFAX 7, not only it functions correctly, and the
quality
of images are more than suitable.
It is to tell that the PC functions in mode 80086,  it is therefore possible
to
force the clock tic to 55 millisecondes.
Who can tell how to make ?
         赏屯屯屯屯屯屯屯屯屯屯屯屯屯屯屯屯屯屯屯屯屯屯屯屯屯屯屯突
         喊鞍鞍鞍鞍鞍鞍鞍鞍鞍鞍鞍鞍鞍鞍鞍鞍鞍鞍鞍鞍鞍鞍鞍鞍鞍鞍鞍昂
         喊圹圹圹圯鞍圹圹圹圯鞍赏屯屯屯屯屯屯屯屯屯屯屯屯屯屯屯话昂
         喊鞍鞍鞍圯鞍鞍鞍鞍圯鞍�        de Serge F1LXJ        喊昂
         喊鞍鞍佰莅鞍鞍圹圹圯鞍�QTH:Annoeullin 59 Nord JO10LM 喊昂
         喊鞍鞍圯鞍鞍鞍鞍鞍圯鞍�F1LXJ @ F1FBB.#
FOU.FNPP.FRA.EU
喊昂
         喊鞍佰莅鞍鞍圹圹圹圯鞍�PMS:TSTHOST 1.43c/TNC20/TF27b 喊昂
         喊鞍鞍鞍鞍鞍鞍鞍鞍鞍鞍韧屯屯屯屯屯屯屯屯屯屯屯屯屯屯屯及昂
         喊鞍鞍鞍鞍鞍鞍鞍鞍鞍鞍鞍鞍鞍鞍鞍鞍鞍鞍鞍鞍鞍鞍鞍鞍鞍鞍鞍昂
         掏屯屯屯屯屯屯屯屯屯屯屯屯屯屯屯屯屯屯屯屯屯屯屯屯屯屯屯凸
         �151.59.30 
F1...@F1TUJ.AMPR.ORG
 email 
f1...@nordnet.fr
�         韧屯屯屯屯屯屯屯屯屯屯屯屯屯屯屯屯屯屯屯屯屯屯屯屯屯屯屯图
   ------  Fine del messaggio # 744940 di F1LXJ  per ALL    @WW      ------
1:IK4ICZ BBS (LC=*) >

Sinceramente ho capito poco di quanto detto, non per l'inglese che capisco
bene, ma per i contenuti...Cmq ho lo stesso identico problema, solo che mi
si presenta solamente compilando programmi tramite Turbo Pascal 7, mentre
per quanto riguarda Turbo Pascal 5.5 non mi da alcun problema...Con il 7
invece mi si bloccano tutti i programmi che compilo o debuggo e che
utilizzano le CRT....
mi spiegate per favore cosa devo fare ?

 wrote in message 81hr7e$8dv$1...@nslave1.tin.it...
