After a year and a half of tweaking and experimenting, I've finally got a streamlined DOS config that allows me to run any DOS game I want (607k free conventional memory) while running MS Client 3 in the background to allow filesharing across an MS workgroup. However, network gaming requires a separate configuration using an ODI driver, which conflicts with MSC. It works to an extent over MSC, but the communication drops out within seconds of any fast action. Everything works fine as it is, and it's simply a matter of running a batch file and rebooting the machine in order to switch between filesharing and network gaming. However, if I can manage it I'd like to minimise the amount of necessary rebooting. In addition, since I have far fewer hard drives at present than computers to put them in, my goal is to have many DOS boxes each booting from a small hard disk, or even, once I learn how, off the network. The games would be run from one or more servers elsewhere on the network. So, if it's possible, does anybody know how to setup: a) IPX gaming via MSC that doesn't crash out, and/or b) filesharing across a MS workgroup using an ODI driver, or c) some other approach that also allows filesharing and IPX gaming? Thankye muchly. >Jimage

If you want an alternative the only way I have found is to switch off NWC3 and install a packet driver for the NIC then install the IPX Packet Shim PDIPX, WATTCP can be used for IPConfig.. http://www.dosthealt.f2s.com/pdipx.com http://www.smashco.com/wattcp.asp

""After a year and a half of tweaking and experimenting, I've finally got a streamlined DOS config that allows me to run any DOS game I want (607k free conventional memory) while running MS Client 3 in the background to allow filesharing across an MS workgroup."" How did you get 607k free after running MS client 3.?? It sounds impossible with the amount of conventional memory ms client takes up. Can netware client in dos access microsoft shares???

Which files do I need for this WATTCP? That page doesn't explain things very well (though maybe I need to re-read it). I've searched around for more information, but it seems to be a fairly obscure utility. -==- "How did you get 607k free after running MS client 3.??" =--= This magic little utility: http://sorry.vse.cz/~roman/dimension/rdos/rdosumb/ Here's what my startup files look like: [fdconfig.sys] file=8 fcbs=1,0 device=c:\dos\driver\rdosumb\rdosumb.com * #1D dos=high,umb devicehigh=c:\dos\driver\fdxms.sys devicehigh=c:\net\ifshlp.sys devicehigh=c:\dos\driver\rdosumb\upload.com /e [autoexec.bat] c:\dos\driver\rdosumb\upload.com /d lh c:\net\net initialize lh c:\net\nwlink lh c:\net\net start http://jimsoft.spatang.com/dos/DOSBEAST-MEM-Apr-19-2006.TXT =--= "Can netware client in dos access microsoft shares???" -==- From what I can tell it requires a Netware server in order to access the network at all. But I haven't been able to get a Netware client running at all. Anybody else know whether it can be done?