IPX with Win32 ZDoom
Forum rules
IPX with Win32 ZDoom
I have an old(ish) DOS box that is networked via IPX with my windows machine (for Dooming). I've tested this setup with the standard doom2.exe/doom.exe stuff and it works fine (eliminating the possibility of network error). Also, ipxsetup picks up the second node, and executes ZDoom.
The DOS version of ZDoom works fine via ipxsetup (apparently, anyhow. It does not crash until the other system does). The Win32 version (1.2.2 or 47.cab) does not.
Is it possible to use IPX with ZDoom ?
Thanks!
Cheers,
Blue
The DOS version of ZDoom works fine via ipxsetup (apparently, anyhow. It does not crash until the other system does). The Win32 version (1.2.2 or 47.cab) does not.
Is it possible to use IPX with ZDoom ?
Thanks!
Cheers,
Blue
- Kappes Buur
-
- Posts: 4120
- Joined: Thu Jul 17, 2003 12:19 am
- Graphics Processor: nVidia (Legacy GZDoom)
- Location: British Columbia, Canada
- Contact:
This from the thread: modem support
Alas, the same holds true for IPX networking.randy wrote:Actually, there was never any modem code in Doom to begin with. It was all inside of sersetup.exe. Doom just had some stub routines that called into sersetup.exe to handle the connection.HotWax wrote:All of Doom's modem code has been ripped out from ZDoom. The only multiplayer support is now via TCP/IP.
And to be more accurate, the networking is actually UDP, not TCP, though most people probably don't know the difference, since they're both part of the Internet.
-
- Posts: 73
- Joined: Wed Jul 16, 2003 3:08 am
- Location: Imperial Moon Base: Thal Vaishet
- Contact:
What sucks, is that the Windows OS is not cross compatible, I wasted over 3 hours trying to figure it out, finally one of my friends tole me that you can't connect Win98 with WinXP. Thanks alot Bill Gates, you jerk!
I'll have to wait untill september to get the new computer my Mom's friend is giving me. But at least I can run 2 Win98 machines so I can set up a cool multiplayer HeXen game.
I'll have to wait untill september to get the new computer my Mom's friend is giving me. But at least I can run 2 Win98 machines so I can set up a cool multiplayer HeXen game.
- Sticky
- Posts: 836
- Joined: Mon Aug 04, 2003 12:29 pm
- Location: Denver, CO How do they get teflon to stick to the pan?
a jerk......
There is some way to do it, but it's tricky I think.
I dunno, I'll have to talk to my uncle and find out what he did... until then, don't give up hope!
I dunno, I'll have to talk to my uncle and find out what he did... until then, don't give up hope!
Thrasher wrote:What sucks, is that the Windows OS is not cross compatible, I wasted over 3 hours trying to figure it out, finally one of my friends tole me that you can't connect Win98 with WinXP.
Yeah, completely false. Not only do I play zDoom networked with my 98 machine and xp machine, I play other networked games too like q3a and diablo2 and several others.
- Kappes Buur
-
- Posts: 4120
- Joined: Thu Jul 17, 2003 12:19 am
- Graphics Processor: nVidia (Legacy GZDoom)
- Location: British Columbia, Canada
- Contact:
For USB network connectivity, I am almost certain that you need those:
http://www.dlink.com/products/?pid=134
http://www.dlink.com/products/?pid=134
Ummm....Thrasher wrote:What sucks, is that the Windows OS is not cross compatible, I wasted over 3 hours trying to figure it out, finally one of my friends tole me that you can't connect Win98 with WinXP. Thanks alot Bill Gates, you jerk!
/me turns around to gaze at his GF's Win 98 machine.
/me checks the cabling and hub connecting his machine to hers.
/me brings up his XP run prompt and types //prit/c to make sure he can still access her hard drive.
Yeah, I think you might just be mistaken.
Actually, there CAN be problems connection Win98 to XP. My 1 machine (of 4) originally refused to connect. All the addresses, etc were correct.
I think it has to do with how the browse master is set up. Anyway, that's how I fixed it. What you need to do is disable the browse master on the Win98 machine, reboot and try again.
I think it has to do with how the browse master is set up. Anyway, that's how I fixed it. What you need to do is disable the browse master on the Win98 machine, reboot and try again.
Windows XP has a networking wizard, and while I typically loathe use of Wizards, one of its options is to make a disk that will automatically configure the other machines, including Win98 machines, for the network. I found that using such a disk was the easiest way to get the machines to talk to each other.
I've had people come to LAN parties with XP and I have win98 on my machines. They were able to network but had to work at a few settings, I didn't pay attention because of distractions. Here's what the worthy doomer LordUnum had to say when I asked him about the process:
Hmmm... well to start, XP has a ton of built-in drivers for generic and
popular net adapters. Mine was detected automatically. Proceed as you
would w/9x (ensuring that the adapter appears in Device Manager).
Right-click on 'My Network Places' or click on 'Network Connections' in
Control Panel. If it hasn't been run before, click on 'New Connection
Wizard.' A dialog-box will pop-up asking for area-code and dialing info
(modem setup). That can be filled out or canceled. Of the listed
options, select 'Setup a home or small office network.' If one didn't
exist before, a 'Local Area Connection' will now be listed under
'Network Connections.'
Clicking on the 'Local Area Connection' will bring up the connection's
status which'll show basic info like throughput the length and speed of
connection (10mbps, 100mbps, etc.). Clicking on 'Properties' will
introduce a menu similar to that brought up when right-clicking 'Network
Neighborhood' in Windows 9x. Aside from indicating the PCs name and
workgroup (that info will be found in Control Panel => System under
Computer Name), itll be much like 9x again from here on out (make
sure TCP is installed, proper IPs indicated, etc.).
What I did in the command line at the LAN BTW was just use ipconfig to
release and renew IP info on the adapter. Why MS didnt include winipcfg
to neatly do this from the GUI like in 9x is beyond me.
Hmmm... well to start, XP has a ton of built-in drivers for generic and
popular net adapters. Mine was detected automatically. Proceed as you
would w/9x (ensuring that the adapter appears in Device Manager).
Right-click on 'My Network Places' or click on 'Network Connections' in
Control Panel. If it hasn't been run before, click on 'New Connection
Wizard.' A dialog-box will pop-up asking for area-code and dialing info
(modem setup). That can be filled out or canceled. Of the listed
options, select 'Setup a home or small office network.' If one didn't
exist before, a 'Local Area Connection' will now be listed under
'Network Connections.'
Clicking on the 'Local Area Connection' will bring up the connection's
status which'll show basic info like throughput the length and speed of
connection (10mbps, 100mbps, etc.). Clicking on 'Properties' will
introduce a menu similar to that brought up when right-clicking 'Network
Neighborhood' in Windows 9x. Aside from indicating the PCs name and
workgroup (that info will be found in Control Panel => System under
Computer Name), itll be much like 9x again from here on out (make
sure TCP is installed, proper IPs indicated, etc.).
What I did in the command line at the LAN BTW was just use ipconfig to
release and renew IP info on the adapter. Why MS didnt include winipcfg
to neatly do this from the GUI like in 9x is beyond me.
Read about what BrowseMaster does and then you'll see why this becomes a problem.
http://www.wown.com/j_helmig/browse.htm
Briefly somebody looks over all the machines and no wizard will fix this potential problem on the Win98 machine. This is mostly a problem for existing Win98 networks. The ordering of the network has a great deal of influence.
So some people get it working just like that and others tear their hair out.
There was originally a similar problem with Win95 and Win98 machines.
http://www.wown.com/j_helmig/browse.htm
Briefly somebody looks over all the machines and no wizard will fix this potential problem on the Win98 machine. This is mostly a problem for existing Win98 networks. The ordering of the network has a great deal of influence.
So some people get it working just like that and others tear their hair out.
There was originally a similar problem with Win95 and Win98 machines.