There is an MS support downloadable hot fix that has to be run to allow the installation on the AMD Bulldozer architecture.
Borland c 64bit update#
Microsoft provide various downloadable hot fixes that update the registry to activate the VM. The installation of XPMode is automated (after activation of the Windows 7 Pro VM).
Borland c 64bit full#
It can be toggled between a Window and full screen.
Borland c 64bit 32 bit#
XPMode is a free downnload from Microsoft that installs a free version of Windows XP 32 bit in a virtual machine on Windows 7 Pro with full sharing of the cutpaste/copy buffer, USB, drives, screen and network card (web access). NTVDM by the way is a feature that can be activated on Windows 10 Pro but it yet to be seen what exactly can be done with it there. It runs Windows XP 32 which of course provide 100 percent transparent compatibility via its NTVDM with DOS 16 bit real mode, 16 bits protected (Windows 3.1), and DOS 32 bit extenders. Your best (but not only) solution for running all that is probably XPMode on Windows 7 Pro. There are plenty ready to run ISO images for FreeDOS, one worth mentioning is Seagate Seatools for DOS which is being distributed with the FreeDOS kernel.
Once you get a FreeDOS running in a VM you can simply SYS the VHD and start it anywhere. Regarding the creation of a FreeDOS virtual machines, pickup the tools from Microsoft SysInteral. FrameworkPascal (written in the old version of Watcom) provides a 32 bit extender. BTW, there is version 5.02 with some fixes (in case your version is exactly 5.0).Īs for a compiler, Open Watcom seems to me to be the best choice in your situation.
Borland c 64bit install#
Run Virtual XP or VirtualBox and install Borland C++ inside. This is the autoexec.bat that I use (smartdrv is a bit pointless in this case so I commented it out with "rem" prefix). I had to increase buffers, stacks, and files to avoid a stack overflow problem with this setup. This is the config.sys that I use that seems to work with Win 7 virtual machine. It's a bit awkward to import / export files to / from the virtual machine. I still have the original floppies and started with those on an old system that has a floppy drive. At Microsoft's support site, they have links to a bootable ISO file for MSDOS 6.22. You could try to create a virtual machine with MSDOS on it, but you'd have to find a way to install MSDOS 6.22 on the virtual machine. Why can't you run the Borland compiler using FreeDOS? Your best course of action is still to use a modern IDE and compiler.If you can find an old Microsoft Compiler, like 16 bit C / C++ 1.52 (which is included on the 32 bit C / C++ 4.1 cd-rom), or C 8.00 or earlier, it runs using a dos extender or in a 32 bit dos console window. It's a simple Windows C/C++ IDE - I haven't really used it, but it's worth a look if you like simple tools as much as I do. You could also choose to use the C/C++ compiler available from MinGW I use that one too some times, though usually only the pre-processor. I use this compiler for some things I write and I have confirmed that an EXE created with it will execute on Win 8.1 64-bit. Once you use Turbo C to write and debug your program you could then compile it with this newer compiler. This link Borland C++ Compiler version 5.5 will get you the Borland C/C++ 5.5 compiler and linker and a few other tools - Borland C++ 5.5 for Win32 Copyright (c) 1993, 2000 Borland - this is essentially what Turbo C grew up to be (but with no IDE). You cannot convert an already-compiled program.Īs Bill said, if you have the source code (and I think you do) then you can use a newer compiler to compile for the newer systems.Īs many have suggested to your many other questions, Visual Studio Express may be the right tool to use.Īnother option is to simply use a newer, but still rather old, compiler.