![]() ![]() This is a confusing process and takes a while to get used to. program output) before you can type into the IDE on the monochrome monitor. Second, as DOSBox will only process keypresses if the main window gains focus, you will need to click the mouse in the color monitor (e.g. The IDE is now monochrome and features such as syntax highlighting will be limited to keywords. CTRL-F9 to exit) overrides that of Turbo Pascal (Ctrl-F9 to run), so you might want to use the IDE’s menu, or change the DOSBox key assignments. This is a very convenient way of debugging as you can see both the codes and the output at the same time, compared with having to swap between the two screens. As you step through the program, numbers will be written to the color monitor (right window). In the screenshot above, the IDE is shown in the monochrome monitor (left) and the program output on the color monitor (right). To test it, run Turbo Pascal 7.0 (or Turbo C 3.01) with a simple program and step through it, line by line: However, it is presently ignored and I simply get light grey text color, which is not a big problem in any case. For it to work, you will also need to check your EMM386 declarations (if any) and make sure that region B000-B7FF is excluded, or just remove EMM386 altogether.Īccording to the documentation provided by the patch author, to start DOSBox in dual monitor mode, you must specify the -display2 parameter, followed by the color you want (white or green): dosbox.exe -display2 greenīefore the latest Windows 11 update, the color setting used to work for me. ![]() With this, the DOSBox console window has been repurposed to be the monochrome terminal (named as the secondary display) and log messages (if useful) must be retrieved from the log files. What the patch does is essentially modifying the DOSBox to report via BIOS that a Hercules card is present, and then capture writes to the B000-B7FF region (used for text on monochrome monitors), interpreting these writes and display the corresponding text onto the DOSBox console window using the pdcurses library. You can also download the complete set of files here. It was not until recently that I came across a patch for DOSBox on vogons which supports exactly this feature, and decided to give it a try. Some only support very specific Hercules + CGA combination and Hercules + VGA will not work. Not all BIOS or motherboards support this option. x use n KB for the code and data memory poolĪ Hercules card is difficult to procure, even in the early 2000s, and for years I could not get this option to work. e * use n pages of expanded memory for swapping d dual monitor mode, IDE uses other monitor Option is any of the following: (/x- = turn option x off): Srcname is any ASCII file (default extension assumed) This option can also be specified from the command line (/D), as described in the help text for TC /? (Turbo Pascal does not support BP /? or TURBO /?, although command line arguments are described in details in online help): Syntax: TC ] ] MDA/Hercules) and a Color Graphics Adapter (CGA), then enabling this option will allow the IDE to be displayed on the monochrome monitor, and the debugged program to be executed on the color monitor. If you have a dual monitor setup, specifically a Monochrome Display Adapter (e.g. There is an interesting option called “Dual monitor support” located in the Options > Environment > Startup dialog of Turbo Pascal 7.0 and Turbo C++ 3.01. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |