Dos Runtime Error 200
Contents |
games running before you start asking questions. Topic locked 3 posts • Page 1 of 1 Fix "Error 200" (Divide by zero) - by Snover and Stiletto, with thanks turbo pascal error 200 to edelbeb by Snover » 2002-7-26 @ 00:40 If you're trying to play
Runtime Error 200 Patch
an old game and it was written in Turbo Pascal, chances are, on any machine over 200MHz, you will get an runtime error 2001 Error 200 (Divide by zero error). This program corrects the problem by patching your executable. From the readme... ctbppat v1.2 © Andreas Stiller [April 2000]ctbppat fixes programs coded in Borland Pascal that cause runtime error 2004 runtime error 200 on systems with clock speeds of over 200MHz. This error occurs due to incorrect initialisation of the DELAY counter.ctbppat is also a universal EXE scanner, monitor, and patcher. It supports the usual EXE formats -- MZ for DOS; NE for OS/2, DPMI, and Windows 3.11; and PE for 32-bit environments -- and can detect the language with which the file was created. Running "bppatch *.*
Runtime Error 201
/s [/p]" will list all file formats in the current directory.If you use the switches /NE, /MZ, or /PE, ctbppat will be restricted to the respective EXE format. This will increase the speed with which it can analyse files. Running in pure DOS mode with SmartDrive (if possible) will also increase analysation speed.If ctbppat finds an executable made with Borland Pascal 7.0, it will examine the file further to determine if it uses an original or changed CRT unit, whether this unit is already patched, and whether the DELAY function is called at all. (If it is not, patching is unnecessary.)Depending on the result of this examination, ctbppat may offer to patch the file. If the DELAY function is used, it can be fixed by using a different delay routine that should function properly up to ~4GHz.To do this, the BREAK routine in the CRT unit is shortened and the delay code patched into the free space.If DELAY is not used, the divisor is simply increased to 65535. This will prevent DELAY from operating; however, this will ensure that the program is able to run (theorhetically) on a 300GHz CPU.If the CRT unit has been changed, but contains the same incorrect initialisati
these compilers when run on a Pentium-class computer faster than about 180mhz. Borland (now Inprise) has no officially-supported fix for this but several unofficial fixes have appeared on various Pascal programming forums and newsgroups. Some are to patch the runtime error 100 CRT unit in your compiler (so you can produce programs free of the problem) and others tp7p5fix are programs to patch executable programs that have the problem (in which case you do not need the source code or the means to re-build the problem program). A patcher for existing problem programs written by AndreasBauer
encounter this Runtime Error. Runtime Error 200 Symptoms Like any other Runtime Error, Runtime Error 200 lets itself be well known via a pop up alert. This “bug” seems to pop up in DOS http://wiki-errors.com/runtime-error-200-%E2%80%93-the-pascal-error/ based programs that were faster than 200MHz and could make an already slow machine even http://pedrowa.weba.sk/docs/Delphi/Pascal/Fixes%2520for%2520Pascal%2520'Run%2520Time%2520Error%2520200'/download.html slower and/or inoperable. Runtime Error 200 Causes The Runtime Error 200 problem is generated in the initialization routine’s internal workings. What happens is a code will actually measures the “running time” of what is called a busy wait loop. While doing so it calculates how many times a call must be made for a delay in the correct runtime error amount. When the computer moves too fast and the loop takes zero ticks and the calculations come up as “Division by Zero’ or Runtime Error 200. Solving Runtime Error 200 There are two ways in which you can go about solving Runtime Error 200 problems. The first way is to use a patch in order to get the program to work, but this is risky. If you do this be sure you are runtime error 200 using a reputable website in order to get the patch as some patches are really nothing more than viruses in disguise. Another solution is to run a TSR, or Terminate and Stay Resident, utility. Steps: Run the TP75.EXE and allow loading into TSR memory. Run your DOS program and avoid the error message. Repeat steps one and two each time you access DOS as the TSR will not be active unless you load it each time. See Also Personal tools Namespaces Article Search Our Products Main Page Applications .Net Framework Error AOL Browser Errors Installer Errors Internet Explorer Macro Errors Media Player MS Outlook Network Errors Outlook Express Windows Live Articles DLL Errors Exe Errors Ocx Errors Operating Systems Windows 7 Windows Others Windows Vista Windows XP TuneUp Tips Browser Tuneup Computer Tuneup Pages About Us Cat List Support Contact Us Help Center How to Uninstall Refund Policy Legal Disclaimers Privacy policy End User License Agreement (EULA) Terms of use Copyright©2012wiki-errors.com.All rights reserved. Disclaimer: This website is not affiliated with Wikipedia and should not be confused with the website of Wikipedia, which can be found at Wikipedia.org. This website should be used for informational purposes only. About Wiki-Errors Contact us Help Center Privacy Policy Terms of use End User License Agreement(EULA) Refund Policy How to Uninstall Disclaimers Sitemap
the delay factor to the maximum possible value. Note: this program speaks only German, but English docs are included. Note: This program is recommended by Borland. Use: if your program is program.exe , enter the command tppatchprogram.exe Warning: This patch will cause delay to run too fast on computers that are significantly faster than Pentium II with about 233MHz. Some programs require correct timing, for those this patch may do more harm than help! Other programs should work fine with this. Technical details: A patched program will test if the computer is too fast. If no it proceeds with calculating the delay factor as usual. If yes the factor is instead set to the maximum possible value. Program makes room for the required additional code by rewriting two variable assignments directly before the patched region with shorter code that is functionally equivalent. (If you don't see that it's equivalent after looking at the assembler code, note the registers that are used!). t7TplFix.zip patch program for Run Time Library file of Turbo Pascal 7.01 Program patches the file TURBO.TPL, the run time library file of Turbo Pascal version 7.01. Use: replace your file TURBO.TPL with the one generated by this program, then recompile your pascal sources. Technical Details: applies the same patches as in bp7patch (c't magazine), but uses the bugfixed Pascal version 7.01. No other files are changed, no other undocumented modifications are done to the CRT unit (unlike in the other distributed RTL files, see some of the other solutions below). NewDelay.pas unit with delay replacement and error trap (maybe newer version available here) This unit comes as pascal source. It contains two things: a new delay procedure that prevents the overrun by using a 32 bit delay factor instead of only 16 bit. a trap procedure to catch the runtime error as it occurs. It will still occur internally, but catched before the program aborts, then it's skipped and the program continued. That's a nasty trick, I don't like it, but it seems to work. Additional feature: tries to make a program behave nice during delays if it runs in a multitasking environment. This will of course delay to be a too long and a bit different each time. If you don't like it, disable it in the source. Use: In your program sources include this unit first, crt second, then all other units and then recompile your programs. bppatch.zip Solution by German computer magazine c't July 97 page 232. This file contains several different solutions: a patch program for executable files (discussed in the magazine), modifie