I've been working for about a week at setting up a LAN between a DOS computer [DOSLANHIPPY] and my existing Windows LAN (consisting of three computers, a 98 [SCHLINGY], an Me and an XP ).

MS Client has been the best contender so far. It works with mapping UNC paths belonging to each of the Windows machines. However, DOSLANHIPPY does not show up on the other computers. It was setup following the directions given at http://fhctech.org/fhc/networking/dosclient.htm, if that helps.

I have tried Duke3d and Death Rally, and some kind of communication is taking place, but only one-way for the most part.

Duke3d crashes on DOSLANHIPPY when I try to run a network game, but SCHLINGY accepts its connection when it's waiting for a game (but hangs when DOSLANHIPPY crashes).

Death Rally connects and runs fine until the race starts. On SCHLINGY, both vehicles work fine, so it seems there's no problem with DOSLANHIPPY sending packets.

However, on DOSLANHIPPY, SCHLINGY's vehicle doesn't move, indicating there's a huge problem with DOSLANHIPPY receiving data.

I had only IPX installed initially. I've since installed TCP/IP and NetBEUI, but the only functionality that has changed is that I can now access the Me computer.

Anyway, enough with my life story. Is anyone able to help me out?

Cheers.

>Jimage

Both MS NWC 3.0 Server and Client installed using only TCP/IP??

http://www.wown.com/j_helmig/dosclien.htm

In Windows MSDOS Prompt or Command Prompt map a share:

net use * \\computername\sharename

Yeah. Client and server were both installed, but it turns out I needed to run 'share' then 'net share <drive>=<UNC> [/full]'. Now I can access the machine from Windows.

Initially, trying to access a subdirectory of Drive C on DOSHIPPY via Windows would lock DOSHIPPY up. I tried your suggestion to run 'net share' in Windows, and it seems Drive C on DOSHIPPY runs fine through that medium.

After that, I removed IPX and attempted running TCP/IP only. Filesharing works flawlessly, even through Network Neighborhood, but now I don't have an IPX driver installed to run games at all.

Making progress at least. Cheers.

>Jimage

Have you added IPX/SX support to both Windows and DOS, providing you use the Basi Redirector in DOS NWC3, then base memory usage should not be a problem, but it could be!. Alternatively look at Spartacom Lantastic:

http://www.spartacom.com/products/lantastic.htm

Just a thought, why not install OpenDOS7.01/DRDOS7.03 with the Netware add-on, instead of MSDOS, which would give you IPX support.

On the Windows PC install Novell Netware.

If you wish to keep MSDOS install the Novell Netware DOS Client.

I have never tried to communicate between "DRDOS Netware add-on or the Novell Client" and IPX in Windows so that may be worth exploring??

Yep, I'm using the Basic Redirector in MSC3, and originally IPX was installed in both Windows and DOS. I've also tried (prior to my previous post) DRDOS 7.something, but I wasn't in the mood at the time to mess around setting up NetWare support in Windows.

I threw another DOS machine on the network with a more or less identical setup to DOSHIPPY (both now running IPX only) in order to see if it was something about Windows interfering with the communication.

I ran Death Rally on both machines. They detected the IPX protocol fine. Each can detect and join a game hosted on the other. However, when I go to start the race, both machines sit there 'waiting for other players', indicating the communication issue is in the DOS setup, not Windows.

I also tried Duke3d, and it causes the same error on each computer now, so at least the problem is consistent. It announces it's 'Looking for network players." then spits out "GetPacket: ecb.ComletionCode = 0xfd" and returns to the DOS prompt.

I've been trying to find information about just setting up an IPX packet driver with which to run games (I'm not sure how this'll go with Duke3d, since it also requires NetBIOS). I can deal with rebooting to switch between filesharing and gaming if necessary. However, I haven't been able to find any conclusive information about doing this. Any ideas?

>Jimage

In XP I would say this is not feasible as it does not allow direct port access in the MSDOS Emulation.

In ME they have integrated MSDOS 8.0 to make it less usable, MSDOS Command Prompt is less usable.

W9x you could start in MSDOS mode and write a batch file to launch the network etcetc.

It is probably easier to create a MSDOS Boot Floppy for the Windows machine, and stick to standalone MSDOS, W98SE OEM Boot Floppies are a good starting point.

Good Luck

Woo! It's all sorted. http://members.ozemail.com.au/~nkingham/ipxdos.html explains how to do IPX networking in DOS. Basically, one runs LSL.COM, then the network card's ODI driver, and then IPXODI.COM. Bingo. Done. Functional.

It works on top of MSC3, but it pushes the conventional memory to its limit, so I've setup two different boot modes--one to run the filesharing network and another to run the IPX gaming network.

It works with Death Rally and Duke3d between Windows 98 and DOS marvellously, without tweaking the Windows machine one bit. I haven't tried it with Me or XP, but I'd say it should be similarly cruisy.

Thanks for the help, rogerashley.

DOS LAN Party time!

>Jimage