VOGONS

Common searches


First post, by j0hnny a1pha

User metadata
Rank Newbie
Rank
Newbie

I'm attempting to get NFS v2 file sharing client via XFS, and mTCP TCP/IP stack, running under MS-DOS 6.22. Using my packet driver for RTL8139 (RTSPKT.COM), I CAN get either/or running, but not at the same time. I'm running DOS only, not Windows 3.11.

I've been reading that PKTMUX may be able to help here -- from the XFS docs:

 If you're using PKTMUX,  because you must  multiplex more then one Packet Driver  application, the  best solution is  to load PKTMUX at XFS's multiplexor interrupt:

ne2000 0x60 // or other shim
winpkt 0x60 // for XFS
xfskrnl 0x60
pktmux 2 62 // 2 channels, at interrupt 62
pktdrv 63 // for your first PD application
pktdrv 64 // second
win // start Windows

I don't need to load Windows, so I omitted WINPKT/WIN parts, but I still can't make this work (XFS and mTCP each work when loaded individually, but not together using PKTMUX). What am I doing wrong?? Thanks for any help.

Last edited by j0hnny a1pha on 2024-02-29, 16:01. Edited 1 time in total.

Reply 1 of 1, by j0hnny a1pha

User metadata
Rank Newbie
Rank
Newbie

Solved, with the help of some folks in MS-DOS BBS community!

FYI -- I'm running MS-DOS 6.22, XFS and mTCP -- on a ProxMox PVE.

in autoexec.bat:

REM - Load Packet Driver, Multiplexer, XFS, TCP/IP with mTCP
RTSPKT 0x7a
PKTMUX 2
PKTDRV
DHCP
PKTDRV
xfskrnl 0x7c
xfstool init client sm=255.255.255.0 gw=192.168.1.254 csum=off
xfstool mount f: openmediaserver:/export/Test
xfstool show

In mtcp.cfg, I had to change the packet driver location to match RTSPKT's location: 0x7a

I haven't done any real memory management yet, but i've got about 548k conventional memory free (ouch) -- but I've got a network accessible drive (i needed NFS, even though EtherDFS is a smaller footprint) and TCP/IP.