{"id":9981,"date":"2025-03-19T03:00:00","date_gmt":"2025-03-19T07:00:00","guid":{"rendered":"https:\/\/www.both.org\/?p=9981"},"modified":"2025-03-20T09:07:27","modified_gmt":"2025-03-20T13:07:27","slug":"old-school-programming-with-turbo-c","status":"publish","type":"post","link":"https:\/\/www.both.org\/?p=9981","title":{"rendered":"Old-school programming with Turbo C"},"content":{"rendered":"
\r\n
\r\n \r\n <\/i>\r\n <\/a>\r\n 1 <\/span>\r\n<\/div><\/div>\n

These days, retrocomputing<\/em> is a popular topic. It\u2019s fun to explore old systems and experience what it was like to run classic systems like DOS. DOS had a lot of great applications and games, which is why it had such staying power during it\u2019s time. A growing trend is retroprogramming<\/em> where developers create programs on these retro systems using classic tools, with all the limitations that go with running an operating system from the 1980s.<\/p>\n\n\n\n

During the 1980s and in the 1990s, one popular development platform for building DOS applications was Borland Turbo C<\/em> and Turbo C\/C++<\/em>. Some years ago, Borland released both of these (plus Turbo Pascal<\/em>) for free via their \u201cMuseum\u201d website. Later, Embarcadero acquired Borland, but maintained the Museum, now under the name \u201cCode Central.\u201d You can still find these classic programs on the CC website, but you\u2019ll need to set up a free account to download them. Both Turbo C 2.01 and its successor, Turbo C\/C++ 1.01, are listed on the CC popular downloads<\/a> page, for example.<\/p>\n\n\n\n

Borland C\/C++ 1.01 runs great on FreeDOS, although you may need to disable APM with FDAPM \/off<\/code> at the command line. Note that the four arrow keys may produce a \u201cdouble tap\u201d effect, as though you hit an arrow key twice, depending on your system. This is due to a mix of how the keyboard BIOS worked in later systems and how Borland’s TurboVision managed keyboard input. Using the arrow keys on the ten-key keypad instead is one workaround. If you use QEMU, you can also add -global i8042.kbd-throttle=on<\/code> to the QEMU command line.<\/p>\n\n\n\n

Exploring Turbo C\/C++<\/h2>\n\n\n\n

Released in February 1991 (but with a 1990 copyright date) Borland\u2019s Turbo C\/C++ was a modern development system. More than just a compiler, Turbo C\/C++ provided an integrated development environment in a small package.<\/p>\n\n\n\n

\"Turbo<\/figure>\n\n\n\n

Turbo C\/C++ included a comprehensive help system with a searchable index. For example, if you wanted to write a program that involved text windows with colors (defined in conio.h<\/code>) you could bring up the help index and press C<\/strong> to jump ahead to the topics starting with that letter, including the \u201cc<\/strong>onio.h\u201d entry. Navigate to the topic you want to learn about using the arrow keys or tab, and hit Enter to see details.<\/p>\n\n\n\n

\"Showing<\/figure>\n\n\n\n

The comprehensive help system also included code samples. Continuing with my previous example, you could navigate to the \u201cwindow\u201d topic to show its syntax, notes, related items, and a programming example.<\/p>\n\n\n\n

\"Program<\/figure>\n\n\n\n

Application development<\/h2>\n\n\n\n

Writing programs in Turbo C\/C++ is a breeze. The IDE follows the PC user interface guidelines that made many DOS applications feel immediately familiar: hit the Alt key to activate the menu, or Alt and a highlighted letter to open a menu, like Alt+F to open the F<\/strong>ile menu. Navigate through menu items using the up\/down arrow keys, or between top-level menus with the left\/right arrow keys. Press Enter on a menu item to use it.<\/p>\n\n\n\n

Write your program in the editor and you can compile it using the C<\/strong>ompile menu. If the build was successful, you\u2019ll see a \u201cSuccess\u201d message, then you can run your program with the R<\/strong>un action to see if everything works correctly.<\/p>\n\n\n\n

\"Compiling<\/figure>\n\n\n\n

You can do all of that without leaving the IDE. That\u2019s peanuts in today\u2019s development environments\u2014but consider that Turbo C\/C++ comes from an era when computers measured memory in megabytes<\/em>, like 16 MB or even 32 MB if you had a lot of money to invest in a computer. Similarly, computers of that age might have had a hard disk that was around 100 MB. My computer in 1990 had an 80 MB hard drive, which I later upgraded to 120 MB in 1991. Yet the Borland IDE\u2014including the compiler, libraries, debugger, tools, and help system\u2014required only about 5.8 MB of disk space.<\/p>\n\n\n\n

A test program in Turbo C\/C++<\/h2>\n\n\n\n

Writing DOS programs in Turbo C\/C++ is otherwise the same as any other DOS compiler. Note that due to when it was released, Borland C\/C++ 1.01 on supports \u201cANSI C\u201d programming; the original ANSI C standard was ratified in 1989 and published in 1990, so Borland was an early adopter of ANSI C on DOS.<\/p>\n\n\n\n

A neat feature in DOS was direct access to video memory using the conio.h<\/code> family of functions. This allowed programs to manipulate the screen very quickly, such as to create text windows and menus. With conio.h<\/code> on Turbo C\/++, you could call the window<\/code> function to define a region on the screen to use as a \u201cwindow,\u201d and set text color with textcolor<\/code> and background colors using textbackground<\/code>. If you defined a window and set a background color, the clrscr<\/code> function would clear the window with that background color. Other functions defined input and output on the console, like getch<\/code> to read a key from the keyboard buffer.<\/p>\n\n\n\n

Here\u2019s a sample program to define a small window on the screen, filled in white, then print some red text. This demonstrates several features available through conio.h<\/code> and provides a quick-start to write your own DOS programs:<\/p>\n\n\n\n

Note that the Borland conio.h<\/code> implementation doesn\u2019t reset the text window to the full screen upon exit. You need to restore the text window on your own; I\u2019ve written a clearscreen<\/code> function to make that easier.<\/p>\n\n\n\n

#include <conio.h>\n\nvoid clearscreen()\n{\n    window(1,1,80,25); \/* default win *\/\n    textcolor(7);\n    textbackground(0);\n    clrscr();\n}\n\nint main()\n{\n    clearscreen();\n\n    \/* make a window *\/\n\n    window(30,10,50,15); \/* left, top, right, bot *\/\n    textbackground(7); \/* white *\/\n    clrscr(); \/* win *\/\n\n    \/* print some text *\/\n\n    textcolor(4); \/* red *\/\n    cputs(\"hello world\");\n\n    \/* done *\/\n\n    getch();\n\n    clearscreen();\n\n    return 0;\n}<\/code><\/pre>\n\n\n\n
\"Running<\/figure>\n","protected":false},"excerpt":{"rendered":"
Explore retroprogramming on FreeDOS with this popular freeware IDE.<\/p>\n","protected":false},"author":33,"featured_media":3514,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_lmt_disableupdate":"","_lmt_disable":"","footnotes":""},"categories":[340,150],"tags":[267,152],"class_list":["post-9981","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-freedos","category-programming","tag-freedos","tag-programming"],"modified_by":"Jim Hall","_links":{"self":[{"href":"https:\/\/www.both.org\/index.php?rest_route=\/wp\/v2\/posts\/9981","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.both.org\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.both.org\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.both.org\/index.php?rest_route=\/wp\/v2\/users\/33"}],"replies":[{"embeddable":true,"href":"https:\/\/www.both.org\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=9981"}],"version-history":[{"count":2,"href":"https:\/\/www.both.org\/index.php?rest_route=\/wp\/v2\/posts\/9981\/revisions"}],"predecessor-version":[{"id":10010,"href":"https:\/\/www.both.org\/index.php?rest_route=\/wp\/v2\/posts\/9981\/revisions\/10010"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.both.org\/index.php?rest_route=\/wp\/v2\/media\/3514"}],"wp:attachment":[{"href":"https:\/\/www.both.org\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=9981"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.both.org\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=9981"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.both.org\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=9981"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}