Hello, Rugxulo pointed me at a custom FreeDOS release that has some networking support. I haven't had time to look at it closely. But, initial quick and simple tests showed support for VirtualBox and VMware (bridged NIC).
> On Jul 31, 2016, at 8:32 PM, Louis Santillan <lpsan...@gmail.com> wrote: > > A couple weeks late. Apologies. > > I like this goal. The current FD 1.2pre 22 doesn't seem to have any > networking subsystem packages installed. For me, this affects our > direction. Michael Brutman has additional applicable analysis about > DOS networking here [0]. > > WatTCP/Watt-32: Lots of apps. Mostly older, unmaintained apps. 16 & > 32 bit apps and libraries. Not a lot recent development or > maintenance. OpenSSL support (which affect modern apps). > mTCP: Few apps. Recent (well) written apps. 16-bit only. Currently > (semi-?)actively developed graciously by Michael. No SSL/TLS support. > picoTCP4dos: One app (FDNPKG) for DOS, maybe others for other > platforms could be ported. 16-bit only (as ported by Mateusz, I see > potential for a 32-bit djgpp port) as of yet. No apparent SSL/TLS > support, yet. > > As for the Emulators and their hardware support, > VMWare: Supports AMD PCnet [1]. > VirtualBox: Supports AMD PCnet [2]. > QEMU: Supports AMD PCnet [3] as well as NE2000. > Bochs: Supports only NE2000 [4]. > > Personally I'm a VirtualBox and/or QEMU user and formerly a Bochs user. > > As for drivers, the picture seems complicated (at least to me). The > only reference to open source DOS network drivers are the crynwr's > [5]. The amdpd.zip [6] file seems to have a PCnet driver with an > ambiguous license (AMD Trade Secret + Russell Nelson GPL?). There's a > NE2000 [7] driver as well. Somehow they're all OSI certified. > There's lots of them. They're intended to compile with TASM/Turbo > Make first, MASM second. NASM, OWASM, JWASM porting/support would be > nice. > > A nice generic WatTCP/mTCP DHCP config in autoexec.bat is easy to > setup if you're using David Dunfield's DHCP [8][9]. It can write both > config file formats. I do something like: > SET MTCPCFG=C:\DOS\MTCP.CFG > SET WATTCP.CFG=C:\DOS > LH C:\DRIVERS\PCNTPK INT=0x60 > C:\DRIVERS\DHCP.COM P=60 /F /M > C:\DRIVERS\DHCP.COM P=60 /F /W C:\DOS\WATTCP.CFG > > > > [0] http://www.brutman.com/Dos_Networking/#Some_notes_on_networking_software > [1] http://www.stankowic-development.net/?p=6674&lang=en > [2] https://en.wikipedia.org/wiki/VirtualBox#Device_virtualization > [3] https://en.wikipedia.org/wiki/QEMU#Emulated_hardware_platforms > [4] https://en.wikipedia.org/wiki/Bochs#Emulated_hardware > [5] http://www.crynwr.com/drivers/00index.html > [6] hA couple weeks late. Apologies. > > I like this goal. The current FD 1.2pre 22 doesn't seem to have any > networking subsystem packages installed. For me, this affects our > direction. Michael Brutman has additional applicable analysis about > DOS networking here [0]. > > WatTCP/Watt-32: Lots of apps. Mostly older, unmaintained apps. 16 & > 32 bit apps and libraries. Not a lot recent development or > maintenance. OpenSSL support (which affect modern apps). > mTCP: Few apps. Recent (well) written apps. 16-bit only. Currently > (semi-?)actively developed graciously by Michael. No SSL/TLS support. > picoTCP4dos: One app (FDNPKG) for DOS, maybe others for other > platforms could be ported. 16-bit only (as ported by Mateusz, I see > potential for a 32-bit djgpp port) as of yet. No apparent SSL/TLS > support, yet. > > As for the Emulators and their hardware support, > VMWare: Supports AMD PCnet [1]. > VirtualBox: Supports AMD PCnet [2]. > QEMU: Supports AMD PCnet [3] as well as NE2000. > Bochs: Supports only NE2000 [4]. > > Personally I'm a VirtualBox and/or QEMU user and formerly a Bochs user. > > As for drivers, the picture seems complicated (at least to me). The > only reference to open source DOS network drivers are the crynwr's > [5]. The amdpd.zip [6] file seems to have a PCnet driver with an > ambiguous license (AMD Trade Secret + Russell Nelson GPL?). There's a > NE2000 [7] driver as well. Somehow they're all OSI certified. > There's lots of them. They're intended to compile with TASM/Turbo > Make first, MASM second. NASM, OWASM, JWASM porting/support would be > nice. > > A nice generic WatTCP/mTCP DHCP config in autoexec.bat is easy to > setup if you're using David Dunfield's DHCP [8][9]. It can write both > config file formats. I do something like: > SET MTCPCFG=C:\DOS\MTCP.CFG > SET WATTCP.CFG=C:\DOS > LH C:\DRIVERS\PCNTPK INT=0x60 > C:\DRIVERS\DHCP.COM P=60 /F /M > C:\DRIVERS\DHCP.COM P=60 /F /W C:\DOS\WATTCP.CFG > > > > [0] http://www.brutman.com/Dos_Networking/#Some_notes_on_networking_software > [1] http://www.stankowic-development.net/?p=6674&lang=en > [2] https://en.wikipedia.org/wiki/VirtualBox#Device_virtualization > [3] https://en.wikipedia.org/wiki/QEMU#Emulated_hardware_platforms > [4] https://en.wikipedia.org/wiki/Bochs#Emulated_hardware > [5] http://www.crynwr.com/drivers/00index.html > [6] http://www.crynwr.com/drivers/amdpd.zip > [7] http://www.crynwr.com/drivers/pktd11b.zip > [8] http://www.classiccmp.org/dunfield/dos/index.htm > [9] http://www.classiccmp.org/dunfield/dos/dhcp.zip > >> On Sun, Jul 17, 2016 at 4:36 AM, Jerome E. Shidel Jr. <jer...@shidel.net> >> wrote: >> Hello all, >> >> As you you may already know, we have been working on the FreeDOS 1.2 >> release. >> One thing I would like to see make it into the release is some networking. I >> don’t think it would be >> practical to have a universal setup for each and every machine and NIC at >> this time. But, it >> may be possible to have the installer automatically do this for some of the >> known virtual machines. >> For example, it may be feasible to setup and configure VMware, VirtualBOX >> and QEMU to do >> networking. But, I don’t have the time to figure it all out. This is where >> all of you come in. >> >> >> If you can provide the detailed information for these platforms and Jim >> approves, I may then be >> possible to include it. >> >> Here are the main and mostly obvious requirements. >> >> All files and drivers must have an acceptable license and can be >> redistributed. Public Domain, >> GPL, BSD or another open source or unrestricted license. No encumbered >> commercial drivers >> (such as NOVELL Netware, 3COM, NetGear, ….. ). >> >> DHCP setup only. >> >> Links to (or provide) any drivers and files that are required. >> (It would be nice if they were in a FDNPKG compatible package) >> >> Completely setup configuration files for the platform. (all INI, CFG files, >> etc) >> >> List of any current 1.2 repo packages that may be needed (excluding BASE >> packages). >> http://www.ibiblio.org/pub/micro/pc-stuff/freedos/files/distributions/1.2/repos/pkg-html/ >> >> Preferably, any files that are not in a package (like the config files) are >> placed under >> \NET\VMWARE, \NET\VBOX, \NET\QEMU or other appropriate directory for the >> platform. >> >> Also, please do not provide a customized config.sys or autoexec.bat. It >> should be possible to >> place all environment settings and load drivers from a \NET\STARTNET.BAT >> file. >> >> Thank you, Jerome >> >> (Without your support, there is no way any type of pre-configured networking >> will make it into the next release.) > > ------------------------------------------------------------------------------ > _______________________________________________ > Freedos-devel mailing list > Freedos-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freedos-devel ------------------------------------------------------------------------------ _______________________________________________ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
