Network drivers in the DOS world aren't quite like other DOS drivers.
Normally you only need one .exe to do the job, but with networking you will
need a few files: a packet driver for the hardware itself and, depending on
what protocol your software expects, maybe a TCP stack as well. The packet
driver is hardware-dependent and will have to be obtained through your
manufacturer, but the TCP stack (WatTCP or Trumpet, etc.) can be found
freely on the internet. I believe FreeDOS includes WatTCP if I'm not
mistaken.
Some network hardware won't have a packet driver interface available and
will instead have an NDIS driver. In this case, (I'm going by memory here
since I haven't messed with NDIS that much recently) you'll need a program
to do the NDIS binding, and I believe a Microsoft component (MSLanMan
maybe?) as well. More fleshed out instructions can be found online, but I
hope this helps.
------------------------------------------------------------------------------
Dive into the World of Parallel Programming! The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net
_______________________________________________
Freedos-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/freedos-devel
