I have not compiled Windows binaries since about 1998, when I switched away from that platform. All binaries are old, and they may not work in modern Windows, and I have no idea how to make them work there. This information describes their usage back then in 1998, and it is provided in the hope it may still be useful.
In general, the programs run normally in Windows MS-DOS prompt. They use a memory manager (or extender), and so they are not limited by MS-DOS 640KB limits. If any trouble, you may consult the djgpp FAQ. A few things must be taken into account.
The programs come without the memory manager, and they use the resident memory manager host in your PC. The most common nowadays is Windows (dpmi), and so it is best to run these programs in Windows MS-DOS box without exiting Windows. The programs can use some other memory managers in MS-DOS as well. If you don't have any memory manager, you can get CWSDPMI.EXE from djgpp (see faq).
The programs are linked with a floating point emulator which is used in case you don't have the floating point processor (however, the programs can be very s-l-o-w without FP hardware). In some cases the programs may fail to see that you don't have FP hardware. In that case you should give a MSDOS command
It may be that graphics don't work in your system: We're dealing with hardware periferials, and portable programming may be impossible. Be sure that all files needed by graphics (e.g. fonts) are in the same directory as the program (or that the program knows where they are!). It may be that to optimize the graphics or to make it work, you have to issue a specific SET command to the graphics driver, e.g.
SET GRX20DRV=VESA gw 1024 gh 768 nc 256
giving the driver name, screen width, screen height and the number of colours. The drivers available currently are
ati28800 cl5426 et4000 mach64 stdega stdvga VESA
For further details, see djgpp FAQ.
Original message written 5/3/97, update message added 15/3/05