Hi again, > So on the driver side, PKT and ODI drivers fade out, which only > leaves NDIS2. Which means we are stuck with MS Client / LAN Manager > Client. Unless there is some new free networking software for DOS. ... > MS Client's protman (PROTMAN dot DOS / EXE) to configure a) the NDIS > driver of the card and b) the free DIS_PKT shim and then MS Client's > NETBIND.COM to bind these two... ... > Wishlist (it's nearly christmas, OK?) Let Arachne directly talk to the > NDIS driver. Or better: Let there be a free external TSR TCP/IP kernel > (stack) that communicates directly to the NDIS driver, so everything > else could use this kernel.
This would only help Arachne, not the rest. Why not write a free replacement for NETBIND and PROTMAN? I am sure only a fraction of their functionality is actually used to send configuration parameters to DIS_PKT. And Arachne and other DOS apps are happy with the packet driver side of DIS_PKT, so there is no need to teach them how to talk with NDIS directly. So basically I agree with Tom: > Teach DIS_PKT to talk directly to NDIS, and you are done. > probably easier (and much more useful) then teaching Arachne NDIS ... > Pointless. Noone will ever talk to this (hypothetical) TCP/IP kernel > this millenium ;) Eric ------------------------------------------------------------------------- SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace _______________________________________________ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
