Conference 501clb::pcdoom

I looked my system over and could not find protman.sys.  I did find protman.dos
and protman.exe.  When I ran protman.exe it said it could not find PRO0023E or
something like that.

Obviously, I have no idea what is going on.

The network card is a DE100.  

THANKS.

    
    
    Looks like WFW is not configured to support a network.
    
    Has the existing network connection between the two PCs ever worked
    before? Doesn't sound like it.
    
    You will need to go into WFW setup and configure it for the type of
    network card you have (DE100) and IPX protocol stack on _both_ PCs.
    This setup will load/create the PROTMAN.* files and PROTOCOL.INI (a
    text file that describes the "build" sequence for the NDIS drivers.)
    
    Note: WFW V3.1 does not include an IPX stack, V3.11 does FWIW.
    
    HTH,
    
    Jason...

Unless I'm mistaken (and it's very possible that I am),
the DE100 is incapable of running PROTMAN, as the 
design of the board doesn't require it. What you're
looking for is a DE203 or a DE205...

Geoff

    
    
    The original DEPCA did support NDIS (protman et al.).
    
    I've never tried NDIS on a DE100, but I'm pretty sure it would work.
    
    There was period where we were selling DE100s only and supporting NDIS
    under PATHWORKS. A current PW SPD would say for sure if you can run NDIS
    on that card.
    
    I could be wrong too, but that never happens (yea right 8^)
    
    Jason...

    ummmm... you guys are confusing each other.
    
    PROTMAN.SYS is the old way to bind NDIS drivers at CONFIG.SYS time.
    Any NDIS drivers, including all DEPCA/DExxx models.
    
    Now WfWg V3.11 doesn't do that at CONFIG.SYS time any more (neither
    does PATHWORKS V5.)   
    
    WfWg V3.11 does the PROTMAN stuff in the NET START command, using the
    PROTOCOL.INI in the Windows directory.
    
    PW V5.0 will setup it's own thing (unless you are using WfWg, in which
    case it uses that)
    
    If you have WfWg V3.11, DEPCA support is already in there.  Just talk 
    to the Network Setup app to get it configured.
    
    	Dave.

    
    That makes sense, thanks for clearing that up Dave.
    
    Jason...
    
    ps Isn't this a great business! Only takes a few months for your
    knowledge base to be out-of-date.

I reinstalled WFW 3.11 and setup the IPX protocol on both machinges, and we are
now playing 2 node DOOM games.  Cool.  I'm not sure what is different now, but
it work and we're happy.

Jim

I also installed DOOM V1.2,  we had 0.9!!  I think this may have had more to do
with it not working before than the protocol.

On a side note, this only works in Windows! If we try to NET START/USE from
DOS, I get error messages.  Would really like to run from DOS instead of Windows.

Jim

I have WFW311 on my PC and I am currently trying to setup Doom 1.4 to 
run across the network.

I have selected IPX/SPX Compatible network in the windows network 
setup program. I have device=c:\wfw311\ifshlp.sys in my config.sys.

I start the network in DOS by typing net start full as per .0. I can
then log into my network OK.

If I type net start /list only full and netbios is listed.

When I try to run network doom from the setup program, I get:-

---------------------------
DOOM NETWORK DEVICE DRIVER
v1.21
---------------------------
Communicating with interupt vextor 0x60
IPX not detected

and my PC locks up.

Help please...

JohnB

P.S. DOOM v1.2 has a similar problem.....

    Got our network running last night, and first things first we tried out
    doom. After much playing with IRQ's in the cards, it works and WAAHEEY!
    What fun, much smoother than over serial.
    
    We're still waiting for 2 of our housemates to get their computers so
    at the moment it's a 2 node network, but soon we'll have 4 players.
    Excellent.
    
    Can anyone suggest a good .WAD file for playing deathmatch. We've got
    ULTIM at the moment, which is very good fun, but we're starting to
    catch on to each others tactics now and need something new. Any
    suggestions, anyone?
    
    Thanks in advance.
    Dan
    
    re.-1
    	Looks to me like you simply haven't loaded your cards' IPX driver
    thingy. Doom doesn't require anything fancy to run over net. We just
    got it to work by running the following in order. Don't ask me
    technical garbage, I don't know it, and obviosuly these files are
    specific to our software but...
    
       C:\GAMES\DOOM> LSL - network support layer ?!
       C:\GAMES\DOOM> NE2000 - driver for NE2000-compatible card
       C:\GAMES\DOOM> IPXODI - IPX driver ?!
       C:\GAMES\DOOM> IPXSETUP -file ultim.wad t2.wad -deathmatch -nomonsters
    
    Does this help in any way?

    Be patient Dan, It'll soon be a 3 node network!
    

    Oh great! Your 386SX16 complete with starter handle and rubber band, I
    presume?
    
    ;-]
    Dan

    Har de Har, no stupid! I was referring to the imminent purchase of a
    486dx50 or dx2/66. Then it'll be your computer that'll need cranking up
    to keep up!

    rathole alert

    
         Awww, go for a Dx4 or for a little more get a pentium...
    
         Remember, Quake is coming...
    
                                                       Bye,
                                                        Mike.

    Hmm. I still think Doom can be faster over the network. I saw it on a
    mates and I'm sure it was quicker over his networks than ours. It still
    stutters some times.
    
    We both have the same cards, NE2000-compatibles, so is there a way of
    optimising network performance for doom? How can we make it run
    smoother? I seem to remember on our mates' network it was just as if
    you was playing standalone (ie. no slowing).
    
    One machine is a DX33, the other is a Cyrus Chipset 486 33 (effectively
    a 486SX25 in performance) .... is the processor difference to blame? I
    wouldn't have thought so....
    
    Any help greatly received.
    
    Dan

    Well thanks for the response :-)
    
    There's little else we can do about the network, and since the
    performance is limited by the slowest machine we can only presume the
    gitters when playing between the following machines is due to the Cyrus
    chipset making it the slower machine.... plus it has a basic graphics
    card compared to a simple but effective VLB card on the 33.......
    
    	<==---------------------------------------------==>
    	  |						|
    Intel 486DX33        			Cyrus 486-33
    4meg                                        4meg
    Cirrus Logic VLB grfx                       Trident 1meg SVGA
    
    The bigger the level, the slower it is, so the simple solution is to
    only play a small, uncomplicated level with -nomonsters option!
    
    I guess we'll just have to get 16 meg on each machine and play doom
    from ramdisc ;-)
    
    Hope this helps anyone contemplating network gaming....

Dan,
    There's little else you can do about the network, and since the
    performance is limited by the slowest machine I can only presume the
    gitters when playing between the machines is due to the Cyrus chipset 
    making it the slower machine.... plus it has a basic graphics
    card compared to a simple but effective VLB card on the 33.......

    The bigger the level, the slower it is, so the simple solution is to
    only play a small, uncomplicated level with -nomonsters option!
     
    I guess you'll just have to get 16 meg on each machine and play doom
    from ramdisc!


Hope this helps.

M@$sincere. 

    Thanks for that excellent suggestion, it seems to be the only way to
    go...
    
    :-) hehe, very good Matt....!

    
         RE: -.1
    
         Well, perhaps not...
    
         If you think the performance reduction is due to the graphics
            card you could always get a better card... It might be
            cheaper than the additional Meg and would definitely
            speed doom up...
    
         Also, did you try to get updated drivers? This might help
            also...
    
         Sorry, for not replying earlier, although I read this conference
            daily, I very rarely have the time to reply...
    
                                                         Bye,
                                                          Mike.

    Hmmm, I'm not getting a new card for mine since this GD5428 (or
    something or other) is all I need, and there's no talking my mate into
    spending money on his computer, he only ever uses it for Word for DOS !
    
    As for the drivers, they came with the cards which are new. The
    graphics card on mine is fine when you play standalone - indeed, the
    graphics on network game are smooth, they just 'pause' every now and
    then while Doom transfers various information between machines.
    
    It looks like it's going to be a case of 'grin and bare it', but I will
    endeavour to speed the bloomin' thing up!
    
    Cheers for the help,
    Dan

Hmmm....if you ask me, I think it may be a case of grommits in your 
thingamawotsits.  It's probably the tappets.  

Not that I know anything about computers, but I recon that it's due to the 
relative lack of performance of your housemate's computer.  It probably has 
enough trouble running Doom as standalone, let alone trying to cope with 
transferring data to and from your machine.  Also, are your network cards and 
link up to the job?  

Matt$tryingtomakeavalidinputtothisconf,butnotsucceeding.

    Dan,
    	Maybe you should wait until I get my computer, then we can play
    deathmatch without using Roach's non-Intel chip set and maybe the
    gameplay will be much smoother.
    
    Trev.

    re.23 - This seems a sensible suggestion
    
    re.22 - Although trying to be helpful, Matt, as usual it sounds
    complete tosh to me ;-)
    
    Dan

    One thing that I found makes doom run slow is not enough free upper
    memory.  You need at least 25K free upper memory (I don't think it has
    to be contiguous) to get the best performance.  At least this was with
    the old 1.1 version, it may not be relevant now, but it's something to
    consider.
    
    Ken
    

    
    We've just got this going over the network, but one thing is puzzling
    us.
    
    Once a player is dead, how can you restart without quitting and coming
    into the game again?
    
    Have I missed something?
    
    Steve.
    
    

    re: .26
    
    Press the spacebar?

    
    yep, the spacebar
    

    
    Thanx
    
    I'd tried every key apart from the ones which do something in the
    game!
    
    Steve.
    

This question is based on a doom related problem, but it's not specifically 
aimed at doom usage..

Can anyone recommend a decent network card, for not much dosh?  I don't know a 
lot about networking, but my housemate and I want to link our PCs so that we can 
play games like Doom, Microprose GP etc..etc.. head-to-head.

Any suggestions?  And where can I get them from???

Suggestions of British distributors only, please.

    I'd suggest you buy a copy of Computer Shopper. There are lots of
    companies offering 16bit NE2000 compatible network cards from 25 to 40
    quid. A little more if you want VLB instead of ISA. Some include driver
    software, some don't, and don't forget the cost of cabling and
    connectors. All vendors seem to offer the lot. I suspect it'll cost you
    about �100 +VAT for a two-machine setup.
    
    Cheers, Laurie.

That's including the two cards, is it?

Also, is it normal co-ax cable or something? (sorry, I really don't know NEthing 
about it)

The connection will have to be about 10-15 metres long, so I hope it's cheapy 
cable.  Also, do all network cards support all most software, or are there 
horses for courses?

    
    When Windows for Workgroups first came out MS was selling a 'kit' to
    two WfWg licenses, s/w, two Intel Ethernet cards and a length of coax
    cable. They may be selling something similar for WfWg V3.11. If so it
    could cover everything you need, plus faster Windows disk access.
    
    This was being sold in Canada - no idea if it is avalaible in the UK.
    
    Cheers,
    
    Jason...
    

Thenks everyone.....at least I've got something to work on, now.

    Well Ed Mason and myself had a whirl of a deathmatch last night!
    There's a level that comes with one of the many editors you can get for
    Doom (I *think* it was DoomEd, but I could be wrong) called MINE.WAD.
    
    In it there is a lovely open space area, in fact the whole level is
    pretty good for deathmatch purposes, but you'll need to put objects and
    starting points in since the original is blank.....
    
    Anyway, try having a good old fistycuffs! It is hilarious and, after
    learning a bit of technique, it can be quite interesting..... I even
    beat Ed last night, me with my fists and him with chaingun !!! At the
    end of the night, about 60 frags later, the room was utterly cluttered
    with dead bodies.... it was sooooo funny!
    
    I can't wait to get it on 3 or 4 player......... try it!

    It's only a pity that you can't tell if your opponent is really going
    to have a fist fight, or whether he is really holding a shotgun to your
    head!

    Dan is an imp.  Not only does he run around alot while using his hands,
    he occasionally pulls out his shotgun, just for a laugh.
    
    And I would just like to say in my defense, that when he beat me (when
    I had the chaingun), I had just killed him, and because of the previous
    fight my health wasn't looking too preety.  He'll disagree, but I don't 
    care!
    
    Anyway, the reason for this note.  
    
    I have wondered for a long time what happens if you stand in an area
    where a transporter 'comes out' as it were.  Well last night me & Dan
    found out!  Basically, whoever is transported thru kills totally and
    uttery whoever was stood in the way.  Its marvellous it really is!  As
    you die, you plumet towards the ground, only to be left to look at your
    own disembodied remains that arn't a million miles away from looking
    like the source of a brontasaurus burger.
    
    Ace!  Try it, it's got to be worth the laugh at least!!
    
    I also think (to enter my 2 peneth for the 'running fast' discussion,)
    that when I get my PC (with 16 Mg RAM) I'm just gonna create a ram disk,
    copy doom onto it, and run it from there!! HA!  And the D.Stealth 64
    will help too............
    
    Makes you wanna be sick really dunnit?
     
    Ed

I take it Trev's agreed to giving you a lift then.  Otherwise, you'll be waiting 
rather a long time for your nuclear-powered-Mclaren-horsepower-super PC, wont 
you!

    Ed, you always need an excuse. You had a chaingun, Dan was using his
    fisticuffs, you lost fair and square.

    This could get very nasty.  But I won't let it.
    
    Well, not here anyway.
    
    I'll mail you instead!

    tetchy.

    Have you ever watched an opponent run away from you on deatchmatch?
    
    Very funny, this body speeds away, and the legs stay still!!
    
    Greg

    This is true.
    
    But if yuo just stand there looking at each other, and one moves to the
    side, he still faces you, but his legs are doing overtime walking
    towards you!!!
    
    Perhaps they should fix this in Quake.
    And show acurately what each person is holding (weapon wise).
    
    Ed

    Sounds like a pseudo-bug left over from the wolfenstien days. No matter
    where you were, the dead nazi's feet were always pointed toward you!
    
    Carl

re: last few and...

> Sounds like a pseudo-bug left over from the wolfenstien days. No matter
> where you were, the dead nazi's feet were always pointed toward you!

This is due to the sprite implementation in Doom.  Each stationary thing has
one sprite, and only one -- i.e. everything still (guns, keys, ammo, lamps,
twitching guy on a stick, etc.) looks the same no matter which way you look at
it.  If they had added 4 more you could get a semblance of perspective (using
reversed sprites to fill out the 8 views), but they didn't.  So consider it a
feature.

To solve the enemy-holding-different-gun-but-I-can't-see-it problem they'd
have to build more sprite support into the .exe along with the network code to
indicate when a weapon is switched.

...so in other words, pray for Quake :-)


- jeff

==================================
DOOM NETWORK TROUBLESHOOTING GUIDE
==================================

AUTHOR: Murray Chapman
  DATE: 25th May, 1994


INTRODUCTION
------------

The purpose of this file is to help you diagnose problems when running DOOM
on a dedicated network.  Dedicated means that there is no network software
running, it is not connected to any other computers, and will be carrying
no traffic other than DOOM.

In other words, this file will help you if you have computers, ethernet cards,
and cable but don't know how to set it up.

I have no experience with Novell/LANtastic/TCP, etc, and hence can't help you.


DISCLAIMER
----------

I accept no responsibility for anything that might happen to you or your
computer.  I also make no guarantees about the correctness of this, or its
ability to produce anything that works at all.  You're on your own.


BACKGROUND
----------

DOOM requires an IPX network to run.  IPX is a very simple and very
popular protocol, so you shouldn't have compatibility problems with 99% of
network cards.

Definitions:

Node: A computer with a network card installed in it.

BNC: A type of cable and connector: cable is coaxial, often MIL-C-17D grade.
     The ends of the cable have connectors with collars, which slide over
     the socket and are held on by pins on the socket when you rotate the
     collar.  Cost: a 20 metre cable, complete with all adapters and plugs
     for a four-node system cost me about $US80.

Network Card: The card that slots into your computer.  It could be either
     8- or 16-bit.  It should have a round BNC socket on the back, and should
     be able to run IPX networks.  99% do.  Cost:  I picked up four second hand
     cards for about $US70 (that's less than $US18 each!)

Transceiver: A device which should be built into the network card.  It is
     the hardware that converts between the TTL logic levels used in your
     computer and the signal levels used on the cable.  If there is a round
     BNC socket on the back of your card, then you have an "internal
     tranceiver".

Packet Driver (PD): a small program, specific to your brand/model of network
     card.  It handles the raw interface to the hardware on your network
     card.  This packet driver provides a hardware-independant interface for
     software.

IPX driver: a small program which sits on top of a packet driver, which
    implements the IPX protocol.

Ethernet: A networking standard.  See:

    http://wwwhost.ots.utexas.edu/ethernet/ethernet-home.html

    for an extremely detailed breakdown.



A GENERAL NOTE ABOUT DEBUGGING
------------------------------

Occam's razor: reduce a problem down to the smallest system that still exhibits
the erroneous behaviour.

If you are experiencing problems networking, it makes sense to minimise all
the sources of possible errors.  For example, don't try debugging a 4-player
game if you can't get a two player game going.  Strip your machine down
to bare minimum that you need to run DOOM: no TSRs, no HIMEM, remove the
sound card and drivers, EVERYTHING!  This can't be stressed enough.  Don't
assume that YOUR soundcard couldn't possibly be causing a problem!

If the problem disappears, then you know it was one of those components.  You
can then add them back one at a time to find the problem.

A fundamental problem is that there isn't much middle ground for testing a DOOM
network: you must have everything right to get it to work.  If even just one
thing is wrong, it won't work, and it won't give you a clue about where
to look.


A DOOM NETWORK
--------------

Here is a two-node DOOM network, from a hardware/software point of view:

+---------------+					+---------------+
| DOOM -nodes 2 |					| DOOM -nodes 2 |
+---------------+					+---------------+
| DOOM LAUNCHER |					| DOOM LAUNCHER |
| ([IPX]SETUP)	|					| ([IPX]SETUP)	|
+---------------+					+---------------+
| IPX driver	|					| IPX driver	|
+---------------+					+---------------+
| Packet driver |					| Packet driver |
+---------------+					+---------------+
| Network Card	|					| Network Card	|
+---------------+---------------------------------------+---------------+
|		  C O N N E C T O R S	&   C A B L E S			|
+-----------------------------------------------------------------------+

3 and 4 player systems are just an extension of this, shown below.

You need to construct this system from the bottom up, as each level of the
system requires the lower level be present in order to work.  (Actually, DOOM
itself is automatically run by IPXSETUP, which can be launched from SETUP.)

Debug from the bottom up: make sure that each layer is working before you
attempt to install the next.


HARDWARE SETUP
--------------

H0. Remove all unnecessary hardware.  This includes sound cards.  Don't forget
    to tell DOOM via SETUP that you no longer have a sound card.  This is
    important.

H1. Install the network cards in the computers.  Make sure all the jumpers on
   the network cards are set to either the defaults, or (if you are certain
   the default setting will cause a conflict) a known safe setting.  Make sure
   that you plug a 16-bit card into a 16-bit slot.  8-bit cards should work in
   16-bit slots.

H2. Connect your computers up as follows:


 Two Node setup:

	=TTT----------------TTT=
	  T		     T
	NODE 1		   NODE 2


 Three Node setup:

	=TTT----------------TTT----------------TTT=
	  T		     T			T
	NODE 1		   NODE 2	      NODE 3


 Four Node setup:

	=TTT----------------TTT----------------TTT----------------TTT=
	  T		     T			T		   T
	NODE 1		   NODE 2	      NODE 3		 NODE 4

 Where:
  TTT is a BNC T-piece
   T

   - is 50 ohm (MIL-C-17D) ethernet cable with BNC plugs

   = are 50 ohm terminator plugs

  Please note that the terminator plugs are essential for correct functioning
  of the network.  Very important!  If for some strange reason you can't find
  terminator plugs, all you have to do is connect the two wires in the cable
  via a 50 ohm resistor.  The plugs are cheap, and make a nice clean job of
  it, so you shouldn't really have to do this.

  Total cable length should not exceed about 180 metres. (!)  Any longer than
  that and you might suffer dropout or pick up too much RF interference.


H3. Learn about your system.  Run MSD.EXE (Microsoft System Diagnostics),
   Norton Utilities, PC Tools, or any other program which will give you
   details about IRQ levels, shared memory, etc.  Also check all aspects of
   your CMOS.  Make sure that you note all addresses that are in use.


H4. If your network cards came with software diagnostics, run them.

  The diagnostics should be able to detect the presence of the cards in the
  system, and check their circuitry.  They will ask you for things such as
  IRQ level and DMA channels.  Make sure that the values you supply match
  any settings you made with jumpers during step H1.  Also make sure that
  they don't conflict with any other setting in your system.

  Remember that DOOM can only use sound cards on IRQ 5 or 7.  Make sure one
  of these is still free if you intend to run a sound card as well.

  The diagnostics might mention a "loopback plug".  This is merely:

				=TTT=
				  T
				NODE

  but the networks illustrated in step H2 above provide the same functionality.

  You might be able to set up an "echo server".  Set up one node to be an
  echo server, then try running "echo client" on the others.  If none of them
  work, then it's probable that at least the node that has been set up to be
  the echo server is at fault.  If at least one client passes the test, then
  the server appears to be working.  The diagnostics should give you statistics
  about the success or otherwise of the test.

  If you have a node that works and one that doesn't, swap the network cards.
  If the problem follows the network card, then either the jumper settings
  are incorrectly set, or the card is at fault.  If the problem doesn't follow
  the card, then the problem is with that particular computer.

  For a each node that you suspect isn't working, redo steps H1 to H4.


H5. Once you have done all of this, you can assume the following:

    The cards are functioning correctly.  The cabling has been done correctly.
    The network is functioning correctly AT THE MOMENT.  There is no guarantee
    that it will work properly under DOOM.


PROBLEMS?

  If it doesn't work, then try all combinations of jumper settings, all
  card/PC combinations, and test your cables, plugs, and terminators with a
  multimeter.
  
  If you can't get it to work no matter what you try, then try setting up
  a null-modem game.  These are much easier to set up and run.  DOOM only
  requires three connections: pins 2, 3, and 7.  Make sure 2 and 3 swap over
  between computers.  If you can't get this to work, then I doubt that you
  would be able to get network DOOM to work.


SOFTWARE
--------

S0. Strip your AUTOEXEC.BAT and CONFIG.SYS down to the bare minimum needed
  to run DOOM.  This includes all sound-card drivers, all TSRs, HIMEM,
  SMARTDRIVE, mouse drivers, etc.

S1. Find a packet driver (PD) specific for your computer.  There are a whole
   suite of them available in:

	oak.oakland.edu:/pub/msdos/pktdrvr/pktd11.zip

   and associated mirror sites.

   Older versions of the file (OLDIPX.ZIP) are available at ftp.uwp.edu and
   infant2.sphs.indiana.edu.  If you get really stuck, try contacting the
   manufacturer (ftp.3com.com, for example).

S2. Install your packet driver.

  This is extensively covered in the DOOM FAQ:

    infant2.sphs.indiana.edu:/pub/doom/text/*

  Typically, you have to run the packet driver .COM file with commands which
  tell it what hardware settings you have made.  For example, a 3com 503 card
  running on IRQ 5, interrupt 0x60, communicating via port 0x300 would be set
  up like this:


    C:\IPX>3c503 0x60 0x5 0x300
	    (a)	  (b)  (c) (d)

    (a) 3c503.com: a packet driver for the card, found in pktdrv11.zip
    (b) IO interrupt: 0x60 is standard, others are 0x62, 0x64, etc
    (c) IRQ level
    (d) IO port

  Your packet driver should report on whether the attempt was successful
  or not.  If you have run the wrong PD, it should report that it couldn't
  find the card.

  Note that some of these values will have to match the values set by the
  jumpers on the network card.  Make sure they match and don't conflict
  with any other settings in your system.  The 3c503 lets you set IO address
  and shared memory address via jumpers, but the IRQ level is software
  selectable.  pktdrv11.zip contains readme files which should help.

  If you can't get it to install, try changing the jumper settings on the 
  card, and restart at step H1.

  NOTE!

  An incorrectly installed PD is the source of most errors.  What do errors
  look like?

     (a) Your computer reboots/crashes/locks up.
     (b) Erratic/unpredictable behaviour within two minutes
     (c) nothing immediate

  (a) is easy to detect, (b) can be detected by making sure that you can
  still get a directory, change dirs, run programs, etc.  I had a problem
  whereby the system would freeze after about 15 seconds.

  (c) is interesting.  It might have appeared to work, but if you get problems
  later you might have to come back here.

  NOTE!

    Once you install a PD, you might not be able to remove it or change the
    settings without rebooting your computer.  Be prepared to do this many
    times!



S3. Install the IPX driver:

  C:\IPX>IPXPD

  IPXPD.COM (or the newer PDIPX.COM) is in pktdrv11.zip.  Some people have
  reported lockups at the "Looking for a node..." point with PDIPX.  Try
  IPXPD first.

  IPXPD will look for your packet driver.  An optional parameter (in our
  example 0x60) tells it specifically where to look for the driver.  If you
  don't supply the parameter, it will search from 0x60 onwards.

  It shouldn't report an error.  If it reports an error or hangs, that means
  that it had a problem detecting your packet driver, so you should go back
  to step S2.

  Running MSD (or Norton Utilities) at this point should report that it
  detected a network.  Don't worry if some of the details look like rubbish,
  as long as it says "IPX DETECTED".


S4. Attempt to launch DOOM:

  C:\DOOM>IPXSETUP

  This is for a two node system.  Note that all nodes must be running the
  same DOOM.WAD, and IPXSETUP must be run on all nodes with the same
  parameters.  (There are exceptions to this: you can run different sound PWADs
  on different nodes.  Occam's razor implies that you shouldn't be doing this,
  however.)

  If everything is ok, it should say something like:

  Looking for a node....
  Found a node!
  Communicating via .....

  ...and then launch DOOM.

  If it reports "IPX not detected", then step S3 didn't work,

  NOTE!
    If you abort the connection attempt, or IPXSETUP reports "Illegal game
    packet encountered during setup", then IPXSETUP will exit, leaving the
    socket open.   If you try to run IPXSETUP again, it will say:

      Open socket: 0xff

    and you will have to reboot to close it.  Don't forget to reload your
    PD and IPXPD.  If DOOM terminates normally, IPXSETUP closes the socket
    correctly, and you can relaunch DOOM via IPXSETUP or SETUP.


  If a node hangs on: "Looking for a node..........." (ad-infinitum)
  Then either the PD on at least one node didn't install correctly (go to step
  S2), or you have a problem with a cable.


FURTHER PROBLEMS
----------------

Consider what happens when you try to launch a game of network DOOM.  Each
node sends out small tentative messages over the network.  Once they have
agreed on who is which player, DOOM is launched.  Then what happens?
DOOM starts to run.  The VGA card gets thrashed.  The sound card gets thrashed.
The keyboard/mouse gets thrashed.  In summary, your bus is carrying a LOT of
information.  DOOM pushes your system to the maximum, and this could be where
the problem surfaces.  It's like idling your car, then flooring the
accellerator: your fuel system might handle an idle, but it might not be able
to handle being run at full speed.  Don't forget that your sound card isn't
active during the connect phase of IPXSETUP.

Once you see the "DOS4GW Protected Runtime System" message come up, you know
that DOOM considers that your network is capable of supporting the current
setup.  It *can* communicate correctly, given the right circumstances.  Write
down the IRQ, jumper, DMA, and port numbers for each node for future reference.

With all the problems below, try different combinations of nodes, different
number of nodes, different peripherals, different powers of computers.  Best
to try are two reasonably similar computers, with similar performance and
memory characteristics.  Try to work out exactly when the problem occurs.

If you have one node that crashes, the problem is almost certainly with that
node.  Take it offline, replace it with a different node, and see if the
problem repeats itself.

If your DOOM session hangs, then see which nodes will bring up the menu
(eventually) when you hit ESC. If a node can bring up the menu, then it
is probably working properly.  Look at nodes that can't bring up the menu.


SYMPTOM: DOOM hangs on "Listening for network start info"
Cause: most likely a problem with another, slower computer.  This node is
       ready to go, and is awaiting another node.
  Fix: check other node(s).


SYMPTOM: DOOM hangs on a blank screen
Cause: Protocol problem
  Fix: Wait.  If it doesn't continue, then whichever node was last to start
       is probably the culprit


SYMPTOM: DOOM runs extremely slowly.
Cause: Too many monsters
  Fix: add "-nomonsters" to the IPXSETUP command on all nodes
  Fix: Make all nodes play on low detail mode.

Cause: Too complex a level
  Fix: play a more simple level, such as "-episode 1 -map 8"
  Fix: Make all nodes play on low detail mode.

Cause: A really slow computer
  Fix: Make sure that you don't play with a 386SX-16! :-)

Cause: Cable too long
  Fix: Try a shorter cable.

Cause: Protocol errors.  Doom automatically detects when there is a problem
       a transmission. It "drops" erroneous packets, and waits for others.
       This causes DOOM to slow down.
  Fix: Try to isolate the problem down to a particular node.  Reinstall
       everything on that node.


SYMPTOM: DOOM slows down slightly for a moment, then resumes normal speed.
  Cause: One node is struggling; either it is doing a lot of work, or is
	 having problems with its card.
    Fix: More memory, faster computer.


SYMPTOM: DOOM hangs suddenly, can't get the menu up on at least one node.
  Cause: That node has crashed.  The problem is probably with that node.
    Fix: Re-install system on that node, from step H0.


SYMPTOM: DOOM hangs suddenly, but you can get the menu up on all nodes.
  Cause: Someone kicked a cable out!
    Fix: Check the cabling!


SYMPTOM: DOOM slows down, then crashes on one particular node.
Cause: A problem with the crashed node.
  Fix: Remove/replace that node, see if the problem re-occurs.


SYMPTOM: DOOM consistently crashes at a particular point
Cause: A network card is clashing with either the hard drive or the sound card.
  Fix: Change the jumpers on the card or the software settings.  Go to step
       H3.


DEBUGGING EXAMPLES
------------------

(A)
Two 386DX-33s. One with a SB-16, the other with a SB-16-ASP.  Both sound cards
were set to IRQ 5, and both were trying to run network cards on IRQ 5 as well.
3com 503 ethernet cards.  DOOM 1.2.

Changed soundcard IRQ jumpers to 7, notified DOOM of this via SETUP, and it
worked fine.

(B)
A 386DX-33/8Mb/SB-16/Sound Canvas and a 486DX-33/16Mb/Sound Galaxy were
networked, and worked fine.  Both had 3com 503 network cards.  DOOM 1.2.

Added a 486DLC-40/8Mb with a 3com 503 network card.  DOOM started ok, but
crashed whenever we tried to move too far.

Took the 386 off line, to see if it was a problem with the DLC or with 3 nodes
in general.  The problem remained, therefore it was with the DLC.

Checked the CMOS on the DLC.  Becuase it had a hybrid chip, it had some extra
setting.  There was a setting for "Hard Disk type 47 area", which was 0x300,
the same as the port for the network card.  I changed a jumper on the network
card so that the card used 0x310.  When installing the PD, I made sure I
specified 0x310.

The problem remained.

I remembered that in order to get DOOM to run on the DLC in the first place,
we had to switch off some shadow RAM.  Thinking there might be a memory
conflict, I changed the "shared memory" jumper on the network card from "DC00"
to "DISABLE", left the port at 0x310, and ran it.  It worked.


(C)
A 386DX-33/8Mb/SB8 3com 503 network card.  Would connect ok, but send the
network start info, but would then hang on a black screen.  The problem was the
old 8-bit Sound Blaster, which would only use DMA channel 1.  The network card
was software selectable to DMA channel 3.  Unfortunately, this didn't work,
so we removed the sound card, and this solved the problems.  DOOM 1.2.

(D)
A 486SX-33/8Mb/PAS-16 3com 503.  Would say "listening for network start info",
then print a string of garbage, then quit back to DOS. Solution: Eliminated
things from CONFIG.SYS.  EMM was probably at fault here.  DOOM 1.2.

(E)
486DX-33/16Mb/SB-16 3com 503.  Would hang on "listening for network start info"
Tried everything, eventually discovered that when we swapped the network card
for a slightly different revision board, it worked fine.  The board at fault
worked perfectly in a different computer.  DOOM 1.2.


NOTES
-----

I haven't got the time to maintain this file.  If you are interested, then
let me know.

Murray
--
-- Murray Chapman                               Zheenl Punczna            --
-- [email protected]                           [email protected]        --
-- University of Queensland                     Havirefvgl bs Dhrrafynaq  --
-- Brisbane, Australia                          Oevfonar, Nhfgenyvn       --

    Hey guys, a co-op game of Doom 2 is actually quite a lot of fun! Ed
    (MASON) and myself are slowly trouncing our way through the levels.
    We're at Dead Simple at the moment (that old favourite) but Ed got
    toasted last night so we gave up.....
    
    (Cripes I can't believe I admitted to liking co-op)
    
    Dan$deathmatch nutter

    Hi,
    I wanted to know if anyone knew how to call up one of my friends with
    the modem and set up a deathmatch between us.Oh by the way I wanted to
    do this with the shareware version.
     
          Thanks,
             Andy
              

    It's a no-no, Andy. You'll need to splash out �30 for the registered
    version.
    
    But you'll be so glad you did! And all the instructions for
    deathmatching via modem are included.
    
    Steev
    
    PS - An even better deal is to buy the Doom 2 CD which includes Doom 1
    as well.

    Steev, 
    
    Are you sure the FULL Doom 1 is on the CD, I thought it was just the
    shareware level 1.
    
    Greg

    Sure it's the full Doom! It also includes Wing Commander IV with free 
    VR headset and glove! And King's Quest 27 complete with Crown and 
    regional accents!
    
    Bloody good deal eh?!
    
    Steev
    
    PS - No, I am sure. The box even lists 'Three episodes from the
    original Doom'.
    

>>    PS - No, I am sure. The box even lists 'Three episodes from the
>>    original Doom'.

But when I tried to apply the ALIENS-TC to the DOOM 1 from the
CD, I couldn't (compained about not finding all files).  I'll
check the documentation tonight.

Skippy.

    You had installed Doom 1 onto your hard-disc, right?! You sometimes
    have problems writing to a CD-ROM ;-)))

    Does anyone know of a PWAD that is good for a 'Predator' type of level?
    It would need lots of dark areas and invisibility spheres.
    
    For those who need it explaining, it works like this:-
    
    It's a net game for 3 or more people. Somebody chooses to be the
    predator, the others are the hunters. The level needs to be fairly
    large and have lots of dark area and lots of invisibility spheres.
    
    It must be agreed that only the 'predator' can use the invibility
    spheres.
    
    The hunters work together to find the predator! When you're bored, you
    swap around and someone else is elected as the predator!
    
    A dark level helps, and its good to have the spheres spread out so that
    someone doesn't just sit around waiting for the predator to turn up.
    
    Any ideas, anyone?

    Sounds like you should get designing Dan!

    I've got one in the making (not much done)... you start off, and theres
    8 teleports, each with a weapon/item above it on a shelf. You choose
    which weapon you want to use by going through that teleporter. It's
    gonna be cool! I'm gonna make two versions, I think, both for
    deathmatch purposes.... one normal, one predator! Or maybe I'll just
    combine the two...... hmmm....

    I reckon you'll just have to have one invisible thing, say in the
    middle, so it's a sprint to get it, and it's only available once.
    
    Greg
                                                                  

    FWIW
    
    I recall reading of a "cheat" someone had designed which made his
    sprite invisible in deathmatch. Perhaps something like this could be
    built into the level when you design it. You wouldn't have to worry
    about invisibility spheres then.  3')
    
    	Nick.  

> I recall reading of a "cheat" someone had designed which made his sprite
> invisible in deathmatch. Perhaps something like this could be built into the
> level when you design it. You wouldn't have to worry about invisibility
> spheres then.  3')

If I recall, all of the DOOM.EXE's need to be patched for the 'invisible
sprite' trick to work.... ...so you gotta get access to the other computers
without that Doomer knowing about it.

Or trick 'em into downloading/unzippin/running the patch first.


- jeff

    To coin a phrase:
    
    	Pay attention dammit!  %^\
    
    I thought the original idea was that everyone knew they were playing a
    `predator' type game. No `trick' needed, you all agree to load this
    special patch. ='>
    
    Nick - who-hasn't-got-a-clue-what's-involved-in-an-exe-hack

> Pay attention dammit!  %^\

Oh okay! :-)

The hack/patch I mentioned will make someone COMPLETELY invisible, not
merely a semi-visible 'predator'.

Actually, there should be an easy way with DEHACKED.  Take the 'inviso-demon'
sprite and map it over the player 1/2/3/4 sprites, editing it to look like a
marine (or a predator, etc.), not the demon.

Then make the 'attack' frame for the now-semi-visible-predator sprite flash
the eyes just as it shoots!


- jeff

...and if yer really gung ho on this...

e-mail the author of Aliens-TC for how he hacked up the .exe to model the
different Aliens-esque weapons.

Using his tricks, you could do the 'frisbee' (similar to chainsaw), the
'shoulder-mounted-laser' (similar to rocket launcher but faster), set
explosive booby traps (invisible barrels that explode on contact), etc....

You could then make the 'monsters' look like the different marine characters
in the Predator movie, one with a chaingun, one with a knife, and put big bad
Arnold at the end for the hand-to-hand battle! :-)

And hack the opening screen to show a chopper flying low over hills, etc...



- jeff

    
    RE: Invisibility...
    
         You could also get DEHACK and change the duration of an invisible
            power-up to last like 10 or more minutes. Then design your
            level with only one, right in front of the person who
            wants to play predator.
    
         You could then design three or four levels in which the invisible
            power up cycles between each person... E1L1 player 1 gets
            inviso, E1L2 player 2 gets inviso... so on and so forth...
    
                                                    Think it'll work?
                                                     Mike.

    Well .63 sounds best to me.
    
    I think most of you have forgotten the base idea - only one person is
    the 'predator', the others work co-operatively to get him. This is just
    a network deathmatch, not an idea for a complete new 'theme' !!
    
    Incidentaly, there's an interesting new theme collection (much like
    starwars and Aliens-TC) on FLYTE, which is a mix of Predator, Aliens
    and Terminator. It *sounds* good, though I haven't been able to try it
    out yet.
    
    It's in FLYTE::USER1:[ARCHIVE.DOOM.THEMES.THEME12].
    
    Dan

    
    im crazy....  just bought a 12 port 10baseT hub ... all in the name of
    doom....
    
    i had 2 machines networked together, my roomate had two machines
    networked together....  now we have 4!!  yes :').
    
    question not really doom releated, but but are you guys running for
    network software?  i'm looking for something peer to peer, ipx
    obviously that doesnt consume lots of memory.  I'm currently running
    Novell personal netware, but for peer to peer, each machine needs to
    have server.exe running.  hows lantastic in this respect?
    

    We use Windows for Workgroups. :-)
    
    It's not bad at all, really. Better than that neos.net shareware doofer
    - which was crap and kept crashing all the bloomin' time. Plus, it's
    free (kinda - I mean it comes with the machines, so...).
    
    Need some help setting it up, or don't you have WfWg?

    
    i have WfWg but i got the idea that the real mode ipx drivers were
    rather lacking.  i need real mode ipx because i need connectivity at
    the dos lovel for other games like falcon, etc.  (does doom run under
    ipx in a dos shell?  didnt think it would).
    

    Well we're just using Novell Netware stuff..... ipxodi, netbios
    (required for those awkward games like WC Armada)...
    
    >>(does doom run under ipx in a dos shell?
    
    Hmm. Terminology in PC networking always confuses me, what does this
    mean? If you mean does Doom require IPX, yes, it does. If you mean from
    windows (sorry, WinDoze), I doubt it :-]

    
    well, what i meant was that if you use a virtual mode ipx driver in
    windows, do you get ipx connectivity that doom supports when you shell
    out?
    
    now... has anybody got this thing working on lantastic?  all i can see
    after installing this on 4 machines is that is supports ipx routing,
    not ipx....  if thats the case, looks like its back to novell personal
    netware...  i DO so like the lantastic interface though...  man, i had
    all my acl's set up and everything...
    

    
    unless i can find a packet driver for these cards....  3 3com, 1 pcmcia
    

    
    If you config WfWg for IPX (under Windows) and reboot and enter NET
    START WORKSTATION you should have a REAL mode IPX stack (usable by DOS
    and DOOM.
    
    I haven't done it but it should work for DOOM (I use this to do backups
    over Ethernet between PCs).
    
    HTH,
    
    Jason...

    
    hmmm....  thanks!  
    

    This question is in response to note 20.91 (how'd it get there?  %'} ).
    
    What is IFRAG and where can I get it?
    
    
    Cheers,
    		Nick.

    
    temporarily located at kdx200::u2:[rob]ifrag20.zip
    
    ill post the readme, but yes, it apparently CAN be used for other games
    besides doom, heretic and doom 2.
    

    
    i take it back, its for doom, doom 2 and heretic only.  there IS
    something else out there that will allow other games, but i dont know
    what it is.
    

    I'll pop this 'iFrag' onto flyte in the misc directory.
    
    Dan

    So anyone wants to try this internally so to speak?

    Is there a way of saving a networked game on Doom2, it's a bit of pain
    having to start from the beginning every time.?
    
    Giles

    Yup. One of you just saves the game. It's as simple as that (co-op I
    mean).
    
    I don't know about deathmatch - I suppose it'll work for deathmatch
    too. Try it.
    
    Cheers,
    Dan

    
    besides, you can start on any level you want in a network game.
    

    
    	Cheers chaps, I had managed to save a game but when I tried to 
    reuse it, it said I couldn't select a saved game. I'll give it another 
    try.
    
    Giles.

    Played this for the first time over a modem with my brother in Cornwall
    - several 100 miles away. Once we got it going it was just incredible.
    
    To both be playing in the same game area whe nhe was so far away was
    great. Not good for the phone bill though. The chat feature is
    invaluable, though you need to be able to type quick and keep and eye
    on the action at the same time.
    
    If you know the play area well it's goo fun being able to send a
    message saying 'cooeee, up here' then letting rip with a rocket shell!
    Bye the time he's swung 'round to see where you are just sees a large
    peice of ordinance coming his way.
    
    Clive, you've got Sportster modem too, give us a call if you feeling
    deprived of a deathmatch. 
    
    
    paul

    > Clive, you've got Sportster modem too, give us a call if you feeling
    > deprived of a deathmatch. 
    
    I will, but first I'd better get the second phone line fitted. Steph
    will kill me if I tie up the only phone line in the house for a hours
    fragging. I'll also get a chair with a safety harness so I don't hit
    the ceiling when you blast me with the Plasma Gun.
    
    Clive

RE: .81

  You have to start a saved game from the DOS prompt:
  
  IPXSETUP -loadgame X

  Where X is the number of the saved game (zero based!) i.e. 0-5 vs.
  1-6 on the save screen... that one got us till we read the manual!

  BTW, make sure no one is playing with the mouse/keyboard during a 
  net save.  We noticed lockups and mis-saved games (V1.666).
  Also, restoring a single player game on a net game does wild and
  wacky things to your screen memory!!  

    re .-1
    
    Cheers, that's the business.....
    
    
    Giles.

    Someone point me in the direction of a packet driver for an NDIS-type
    DEC EtherWORKS network adapter, so I can go about sorting an iFrag server
    for DEC :-).
    
    Cheers,
    Dan
    

    Try:
    
    http://www-nics.lkg.dec.com/
    
    or noted::etherworks

    Path:
    nntpd.lkg.dec.com!pa.dec.com!jac.zko.dec.com!crl.dec.com!crl.dec.com!caen!hookup
    p!usenet.eel.ufl.edu!usenet.cis.ufl.edu!usenet.ufl.edu!gatech!udel!news.sprintli
    ink.net!pipex!mantis!mantis!not-for-mail
    From: "Neil R. Bonner" <[email protected]>
    Newsgroups: rec.games.computer.doom.announce
    Subject: Network DOOM Traffic Analysis
    Date: 28 Mar 1995 22:55:18 +0100
    Organization: MEPTEC - Mobil Oil Corporation
    Lines: 60
    Sender: [email protected]
    Approved: [email protected]
    Message-ID: <[email protected]>
    NNTP-Posting-Host: sunforest.mantis.co.uk
    Mime-Version: 1.0
    Content-Type: text/plain; charset=iso-8859-1
    Content-Transfer-Encoding: 8bit
    
    Network DOOM Traffic Analysis
    ----------------------------------------
    Neil R. Bonner, ([email protected])
            Original Release: March 28, 1995
    
    There has been a lot of posts, discussions and misinformation regarding 
    what effect playing DOOM has on a network.  The conventional thinking
    is that, playing DOOM on a network will bring that network to its
    knees.
    
    While it is true that the first versions (1.0 and 1.1) of DOOM used 
    "broadcast" packets to communicate with other DOOM workstations, that 
    method was changed in version 1.2 to use "directed" packets.  Directed
    packets have less impact on LAN traffic than broadcast packets.
    
    id Software originally used broadcast packets because this method is 
    more efficient *if* all you're doing is playing DOOM on that network
    segment.  However, if other workstations are on the network trying to
    do real work... well then broadcast packets aren't such a good idea.
    
    The below table illustrates exactly how much network traffic is
    generated
    by DOOM in a 2, 3 and 4 player game.
        __________________________________________
        No. of Players   |   2   |   3   |   4   |
        ------------------------------------------
        Mb/second        |  0.04 |  0.12 |  0.24 |
        (bandwidth)      |       |       |       |
        ------------------------------------------
        Packets per Sec. |    35 |    70 |   105 |
        (per PC)         |       |       |       |
        ------------------------------------------
        Total Packets    |    70 |   210 |   420 |
        per Second       |       |       |       |
        ------------------------------------------
        Total Packets    |  4200 | 12600 | 25200 |
        per Minute       |       |       |       |
        ------------------------------------------
        Packet Size      |    72 |    72 |    72 |
        (bytes)          |       |       |       |
        ------------------------------------------
    
    This information was gathered using a packet analyzer on an Ethernet 
    (10Base-T) network with no devices other than 2 workstations running 
    network DOOM.  The numbers for 3 and 4 workstations were calculated 
    based on the actual observation of the 2 player game.
    
    This network utilization chart is the same for DOOM, DOOM II and
    Heretic.
    
    BOTTOM LINE: DOOM uses very little "bandwidth".  This is largely due
    to the fact that DOOM packets are very small (only 72 bytes).  It is
    interesting to note that there is three times more traffic generated 
    going from a 2 player to a 3 player game, and six times the traffic
    going from a 2 player to a 4 player game.  
    
    Even though DOOM uses little bandwidth, it does generate a lot of
    packets
    in a 3 and 4 player game.  Because of this, network DOOM players should
    be considerate of other network users before starting a 3 or 4 player
    network game.  Generally speaking, no one should be adversely impacted
    by someone playing a 2 player game unless the network is already 
    saturated with traffic.