Mount c drive with option -freespace (default value = 250, which seems to be too less).

that is odd if it works with the linux version.

I'm not exactly sure how the -freespace option is supposed to work. I could not find any documentation on it.

I tried:
mount c <path> -freespace

That did not work. I also tried:
mount c <path> -freespace 1000
and
mount c <path> -freespace=1000

neither of those worked either. How exactly is freespace supposed to be used?

Sorry, correct word is -freesize

the readme is a valuable thing to read...

Okay, I tried -freesize 1000, and I still get the error message

I found the documentation for mount in the ReadMe file. That is all well and good that the ReadMe contains the mount documentation.

It would seem more intuitive that is someome typed mount /? at the command prompt that it might list these features. One also might expect there to be documentation when they use the help command as well.

That's what intro is for, it tells you in the big blue box when you start dosbox. I'd also say that reading the ReadMe should be the most "intuitive". One might expect people to first read the documentation and/or turn to it when they have problems with something. If you had done this you would have realized it's freesize versus freespace....

Back to the problem, are you using similar mountings on OS X than on linux? Could you write them here? If turbo c++ isn't on the same place on on the emulated c drive it might behave like this.
Example: if turbo is on ~/dos/turbo and
on linux you do
Mount c ~/dos
and on os x you do
Mount c ~/dos/turbo
that might be a problem.

On both systems, I created a directory called CDrive in my Documents folder and I mounted the C drive in DOSBox to that directory. I used an ISO image to run the installation program for Turbo C++ from DOSBox itself to install the program.

On both systems the Turbo C++ program is located in C:\TC\BIN

Hmm, there goes that theory 🙁
Sounds as if you did all that correctly.

Next step would be running a debugger enabled dosbox.

How would someone run a debugger enabled dosbox?

./dosbox
😀
Seriously you just need to compile dosbox yourself and enable debug in the configure step.

AFAIK, TC++ 3.0 fails to start and displays the error "Disk full! Not enough swap space." when it fails to create its swap file for any reason. I suspect that you're still on DOSBox's Z: drive when you start TC.

TC needs to have C:\TC\BIN\;C:\TC\INCLUDE\;C:\TC\LIB\ added to the path, so it can be run from anywhere; and its default behavior is to create its swap file in the root directory of the current drive. So, after you've mounted a C: drive, you must change to that drive before starting TC, or you will get the error when it attempts to create its swap file on the Z: drive.

You can change TC's swap drive to something specific instead of "current"; the setting is under: Options, Environment, Startup.

I had C:\TC\BIN added to the path. I did not have C:\TC\INCLUDE and C:\TC\LIB, and it doesn't seem like one would need to as those paths should only be needed during compiling and linking, plus everything works on Linux with only C:\TC\BIN in the path.

I just found out that I can get Turbo C++ to run after all. I have to make sure to switch from the Z drive to C drive and then type the tc command. I'm not sure if that's how I got things to run on Linux, and I don't have Linux running right now to check.

That you beed to switch drives is what ripsaw wrote 😉

Of course you'll want the LIB and INCLUDE dirs in the path... or are you really planning to use TC without compiling anything?

Heh, I'll take your word for it that you discovered about switching away from Z: without reading my prior post; but I also mentioned *why* you have to do that, and how you can configure TC to get around that.

The include and lib paths don't need to be in the system path environment. Those paths are configured in the IDE for the project being developed.

Yes, reading ripsaw8080 post is what allowed me to discover that I needed to switch to the C drive. I didn't think I needed to do that on Linux. I just checked and I do get the same error message if I don't switch and stay on the Z drive. I guess I must have switched to the C drive on Linux before running the program, and never realized it.