I kow this was the general consensus, but I reached out to the author of mTCP for this question: can I use etherDFS for a multi-node BBS?
I'm moving on to MSCLIENT...
But I'd much rather use mTCP (for TCP/IP) and XFS (for NFS v2) under MSDOS 6.22, but not sure how to "share" the packet driver? I've seen PKTMUX mentioned, but it seems like the use case is DOS + Win3.11 packet drivers.
I kow this was the general consensus, but I reached out to the author of mTCP for this question: can I use etherDFS for a multi-node BBS?
But I'd much rather use mTCP (for TCP/IP) and XFS (for NFS v2) under MSDOS 6.22, but not sure how to "share" the packet driver? I've seen PKTMUX mentioned, but it seems like the use case is DOS + Win3.11 packet drivers.
Nothing to stop you using PKTMUX with crynwyr drivers.
SHARE
VIDRAM ON (QEMM Option, extends base memory into the lower video ram.) PCNTPK -n INT=0x7a
PKTMUX 2 (I want to use it twice)
PKTDRV (expose driver on int 0x7b)
XFSKRNL 0x7b
... assorted xfstool commands ...
PKTDRV (expose driver on 0x7c)
RLFOSSIL
Share will be doing its thing, file locking is really doing its thing
on the
server though. Not had a problem with this setup, it just runs day
in, day
out. Using MS-SOD 6.22 in VirtualBox.
Share will be doing its thing, file locking is really doing its thing
on the
server though. Not had a problem with this setup, it just runs day
in, day
out. Using MS-SOD 6.22 in VirtualBox.
I haven't optimized memory yet but I'm left with 548k (ouch). XFS is just a hog and won't load high, so I guess I'll load everything else.
But, I've got network accessible storage AND TCP/IP to run RLFOSSIL now.
What version of QEMM are you running?
I couldn't get QEMM's OPTIMIZE to run properly with this setup. It'd
go
through the motions, say its done its thing and then when you tried to restart and check it out, the drivers wouldn't load into the locations optimize set them for. Result was even more loaded low.
j0HNNY a1PHA wrote to Spectre <=-
Same! Getting strange QEMM warnings, freezes, then no upper memory at
all, etc. and finally realizing ProxMox just isn't a great platform to
run DOS VMs... May have to switch to VirtualBox, which is kind of a
bummer because all my other stuff is on my ProxMox PVE and it would be super convenient...
Same! Getting strange QEMM warnings, freezes, then no upper memory at all, etc. and finally realizing ProxMox just isn't a great platform
Have you tried any of the other architecture settings? I've run DOS 6.22 and freeDOS in PXE, but not doing much more than running Microsoft
Word for DOS and a QWK reader.
Maybe there's something I'm missing, what architecture settings? I didn't
When you create a VM, there's setting for machine type under system (440bx or Q35) and under CPU you can pick the type. One of those settings might be more compatible.
Sysop: | Eric Oulashin |
---|---|
Location: | Beaverton, Oregon, USA |
Users: | 94 |
Nodes: | 16 (0 / 16) |
Uptime: | 04:14:44 |
Calls: | 4,789 |
Files: | 8,491 |
Messages: | 349,151 |