Free dos software for linux

FreeDOS aims to be a complete, free, 100% MS-DOS compatible operating system. Mostly achieved except Windows compatibility - Windows standard-mode works on FreeDOS, but 386-mode / WfW 3.11 does not.
Main features:
- Easy multiboot with Win95-2003 and NT/XP/ME
- FAT32 file system and large disk support (LBA)
- LFN support (on command line with 4DOS, which is now freeware: 4DOS for OS/2 is even open source)
- LBACACHE - disk cache (harddisks in CHS and LBA mode, diskette)
- Memory Managers: HIMEM, EMM386, UMBPCI
- SHSUCDX (MSCDEX replacement) and CD-ROM driver (XCDROM)
- CUTEMOUSE - Mouse driver with scroll wheel support
- FDAPM - APM info/control/suspend/poweroff, ACPI throttle, HLT energy saving...
- XDMA - UDMA driver for DOS: up to 4 harddisks
- MPXPLAY - media player for mp3, ogg, wmv... with built-in AC97 and SB16 drivers
- 7ZIP, INFO-ZIP zip & unzip... - modern archivers are available for DOS
- EDIT / SETEDIT - multi window text editors
- HTMLHELP - help viewer, can read help directly from a zip file
- PG - powerful text viewer (similar to V. D. Buergs LIST)
- many text mode programs ported from Linux thanks to DJGPP
- GRAPHICS - greyscale hardcopy on ESC/P, HP PCL and PostScript printers
FreeDOS was previously known as "Free-DOS" and originally as "PD-DOS." For a little trip down memory lane: In 1994, I was a physics student at the University of Wisconsin-River Falls. Most of my work for school had been done using DOS - writing programs, dialing up to the university computer, network, analysing lab data, etc. I really loved DOS; I did everything with it. I had a 386 desktop system in my dorm room and an XT laptop that I would carry around with me to do work "on the go".

GRUB for DOS is a rebuild of the GNU GRUB boot manager for DOS, and can be run under real mode DOS. It also has many new features.
For example, it can be booted through BOOT.INI of Windows (grldr) and kexec of Linux (grub4lin).
The disk emulation feature is another enhancement over GNU GRUB, and can be used to run legacy DOS/Windows9x systems with floppy or hard disk images.
Main features:
- Can be launched by NTLDR
- Can be launched from linux with kexec
- Can create ramdisks
- Can use file as well as partition as the source of the ramdisk
- Can be used as a no-emulation-mode bootable CD-ROM boot image
- Has a "Chinese" special build that can display chinese help message at the console
- Add device (md) that can map a specified range of memory as a ramdisk
- Add device (rd) that reflect the memdisk loaded by inited
- Can chainload KERNEL.SYS from FreeDOS
- Can chainload NTLDR from Windows NT/2K/XP
- Can chainload IO.SYS from MSDOS, Windows 95/98/ME
Enhancements:
- Some commands and options were added or changed.
- A few bugs were fixed.

KOPS project is a two-dimensional gravitational shootyerfriend game.

This is a port from the DOS version. It features parallax scrolling with a full digital soundtrack and sound effects.

A Pentium-class processor or better is recommended.

You control your ship with five keys; thrust (move forward), turn left, turn right, fire main gun and fire special gun. Both main and special guns can be upgraded by picking up power-ups that appear around the level from time to time.

When you pick up a main gun power-up, your gun is replaced instantly. Your main gun also has unlimited ammo. If you pick up worse gun than you already had, tough luck.

Torus is a simple game inspired by Torus for DOS. The object of Torus is to clear falling toruses by aligning toruses with the same color on one of several protruding pipes (the game concept is similar to Tetris(R)). It is written in C++ with Qt and STL. Torus for win32 is written in C++ with VXCL.

whouses Perl module is an impact analysis in a clearmake build environment.

SYNOPSIS

Run this script with the -help option for usage details. Here are some additional sample usages with explanations:

whouses foobar.h

Shows all DOs that make use of any file matching /foobar.h/.

whouses -recurse foobar.h

Same as above but follows the chain of derived files recursively.

whouses -exact foobar.h

Shows all DOs that make use of the specified file. The -exact flag suppresses pattern matching and shows only DOs which reference the exact file.

Whouses provides a limited form of "impact analysis" in a clearmake build environment. This is different from traditional impact analysis (see TRUE CODE ANALYSIS COMPARED below for details). In particular, it operates at the granularity of files rather than language elements.

Whouses is best described by example. Imagine you have a VOB /vobs_sw in which you build the incredibly simple application foo from foo.c. You have a Makefile which compiles foo.c to foo.o and then links it to produce foo. And lets further assume youve just done a build using clearmake.

Thus, foo is a derived object (DO) which has a config record (CR) showing how it was made. Whouses analyzes that CR and prints the data in easy-to-read indented textual format. For instance:

% whouses -do foo foo.c
/vobs_sw/src/foo.c =>
/vobs_sw/src/foo.o

The -do foo points to the derived object from which to extract and analyze the CR; it will be implicit in the remaining examples. The output indicates that foo.o uses foo.c, or in other words that foo.c is a contributor to foo.o. If we add the -recurse flag:

% whouses -r foo.c
/vobs_sw/src/foo.c =>
/vobs_sw/src/foo.o
/vobs_sw/src/foo

We see all files to which foo.c contributes, indented according to how many generations removed they are. If we now add -terminals

% whouses -r -t foo.c
/vobs_sw/src/foo.c =>
/vobs_sw/src/foo

Intermediate targets such as foo.o are suppressed so we see only the "final" targets descended from foo.c.

We can also go in the other direction using -backward:

% whouses -b -e foo
/vobs_sw/src/foo<<less