On Tue, 6 Jun 2000, Bob Baird wrote:
> Currently I have a specialized application program running under DOS. I
> have acquired a project that requires the output of the program to be sent
> over an Ethernet connection.
>
> I think Linux may be a good choice for an OS to solve some security and
> server issues (FTP server, Telnet server, SMTP server, HTTP server) and so
> forth. Also, it seems to allow accessibility to a BSD 4.3 compliant TCP/IP
> stack permitting (packet or streaming methods: TCP, UDP, IP, ICMP, and ARP),
> so as to permit quite a bit of flexibility for building features.
>
> I am interested in running this pre-existing DOS application under DOSemu.
> What are the limitations of DOSemu? Is there a FAQ sheet besides a thorough
> technical description of the DOSemu program interfacing to Linux *AND* the
> system hardware? My DOS application program directly interfaces to hardware
> system resources, comprising DMA, IO memory and interrupts through the PCI
> bus.
System hardware calls are translated to Linux calls for whatever hardware
DOSemu and Linux support. It is also possible to pass on hardware calls,
IRQs, etc. directly, but this only makes sense if your hardware is not
supported/used by Linux, and hence these direct accesses don't interfere
with the OS.
Check out the documentation on www.dosemu.org, specifically the HOWTO, the
README and the technical README. Specifically you may want to check out
sections 2.1.11 and 15 of README.txt: DOSEmu has support for virtual
TCP/IP (so that you e.g. can run a DOS telnet client), IPX and packet
driver code.
Then just try and see if it works for you. Good luck!
Bart
