Might this be the same issue as the Turbo Pascal 7 issue? For that a simple hexedit replace was sufficient

EZ wrote on 2026-09-14, 20:12:

Might this be the same issue as the Turbo Pascal 7 issue? For that a simple hexedit replace was sufficient

Not exactly, but related. The patches you are talking about are to fix the binary output from Turbo Pascal (or Turbo C ), and can be found here: Fix "Error 200" (Divide by zero) - by Snover and Stiletto (updated!).
What I am looking for, are patches to fix Turbo C itself.

Does it not work as it is? I’ve never noticed any issue.

Ringding wrote on 2026-09-16, 19:36:

Does it not work as it is? I’ve never noticed any issue.

The editor seems fine, but I'm having issues with code built with it. I wanted to learn how to write DOS TSRs. Code written for Watcom and DJGPP, my usual compilers, work fine. The examples I found for Turbo C seem to affect my IO controller - my hard disk gets unmounted when I run them, requiring a PC reset.

For example, PCPilot is often mentioned as an example of how to write a TSR using Turbo C. It causes my disk to unmount. Pretty much all the example TSR programs on Simtel's Turbo C section do the same.

* PCPilot: http://cd.textfiles.com/sourcecode/msdos/c/pcpilot.zip
* Simtel Turbo C: https://ftp.sunet.se/mirror/archive/ftp.sunet … /msdos/turbo_c/

I was hoping there was some patch to fix Turbo C 2.01, but if there isn't, I will give up on it and stick to Watcom and DJGPP.

AFAIR, on Turbo Pascal the offending bit (error 200) was the crt unit and I remember finding a source-patched crt unit.

Maybe on Turbo C the same delay loop that throws error 200 is in the same library (crt), so you can find a patched library.

Turbo C was succeded by Turbo C++, and you can compile C code using Turbo C++. So you can try compiling your code using a later version (Turbo C++ was released as freeware, so it can't be too hard to find).

Zup wrote on 2026-09-17, 05:01:

Turbo C was succeded by Turbo C++, and you can compile C code using Turbo C++. So you can try compiling your code using a later version (Turbo C++ was released as freeware, so it can't be too hard to find).

I get the same error when compiling with Turbo C++ - I don't think they updated their C library much after moving to C++.

Turbo C++ also has another problem on my computer - the editor hangs if I have any CDROM driver loaded.

Anyway, for all intents and purposes, I have gone back to Watcom for 16-bit DOS programming.

I cannot find a single piece of functionality in this software that does not work on my P4 2.8 GHz.

Ringding wrote on 2026-09-22, 19:56:

I cannot find a single piece of functionality in this software that does not work on my P4 2.8 GHz.

Can you try running PCPilot that was compiled with TurboC?

* PCPilot: http://cd.textfiles.com/sourcecode/msdos/c/pcpilot.zip

Yes, I even compiled it myself.