Borland Pascal 7 Runtime Error 200
CRT.ASM unit included with these compilers. DOS based programs that were compiled using these buggy versions of the CRT unit will generate the RTE200 error dos runtime error 200 when started on a CPU that is faster then 200 Mhz (though some non-Intel CPU's tp7p5fix would avoid the error up to 350 Mhz). One solution is to recompile the source code using a later version of Pascal, turbo pascal or a fixed CRT.ASM unit. Obviously that's only possible if you have the source code available. The more common solution is to patch the .EXE file to disable the bug. There are several programs that allow this. The one I recommend is PatchCRT by Kennedy Software. This one is more compatible then most others, including TPPatch (which is less effecent, and uses German results and error text). I'd suggest keeping PatchCRT.exe in your path, so that you can run it from any directory simply by typing it followed by the name of the .EXE to be patched. PatchCRT will only be able to patch .EXE files which have not been compressed by an EXE compressor, such as aPACK, Diet, LZEXE, PKLite, Petite, UPX, etc. If PatchCRT fails to patch the .EXE, there is a good chance it is because the .EXE has been compressed. The best tool I have found to uncompress .EXE files is UNP. This has worked for about 80% of the compressed .EXE files I have encountered. The nice thing about UNP is it runs well under Windows. My second choice would be CUP386, but this works best in a plain DOS environment without any extended memory manager (including himem.sys or emm386.sys) installed. I have used this tool to uncompress several .EXE's which UNP was unable to do. Once you have sucessfully uncompressed a compressed .EXE file, you should then be able to run PatchCRT on it to remove the RTE200 bug. If all the above fails, the other option is to run a TSR (Terminate and Stay Resident) utility that will provide a kluge to the division by zero issue by catching this error as the .EXE is being run, and telling DOS to ignore it. The best TSR I have found to do this is TP7p5fix. Simply run the TP7P5.EXE to load the TSR into memory, and any programs being run in that DOS window will avoid the RTE200. Keep in mind that once you close this DO
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 to edelbeb by Snover » 2002-7-26 @ 00:40 If you're trying to play an old game and it was written in Turbo Pascal, chances are, on any machine over 200MHz, you will get an Error 200 (Divide by zero error). This program corrects the problem by patching your executable. From the readme... ctbppat v1.2 © Andreas http://www.pcmicro.com/elebbs/faq/rte200.html Stiller [April 2000]ctbppat fixes programs coded in Borland Pascal that cause 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 http://www.vogons.org/viewtopic.php?t=93 environments -- and can detect the language with which the file was created. Running "bppatch *.* /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. Thi
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 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