On Fri, Dec 29, 2023 at 1:54 PM Jerome Shidel via Freedos-user < freedos-user@lists.sourceforge.net> wrote:
> When the default “start” option is provided, FDNET will only attempt to > start networking support under VirtualBox and VMware. On real hardware and > other virtual platforms, it will just provide that error message and exit. > > The reason for this is simple. It is known to work under those virtual > machines with the available open source drivers (by various authors) which > included with the FDNET package. > OK, that makes sense. I thought it was misinterpreting something (as I'm not running a physical system) or I needed a different QEMU invocation. I did get networking up and running under QEMU. After running PCNTPK after boot, it worked fine: C:\NET\FDNET\pcntpk int=0x60 C:\NET\FDNET\dhcp At that point, everything worked fine TCP/IP-wise. I think I'll add something like "call C:\LOCAL.BAT" to :End in FDAUTO.BAT and then put my local startup customizations there to avoid changing the dist FDAUTO.BAT too much. Thanks much! -- andrew fabbro and...@fabbro.org
_______________________________________________ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
