home *** CD-ROM | disk | FTP | other *** search
-
-
-
- Preliminary Documentation for PARSETUP 1.1
-
- PARSETUP is a Parallel Printer Port device driver for id
- Software's DOOM (tm) and DOOM II (tm) which will allow two
- computers to play across a LapLink or InterLnk parallel cable.
- This file is a quick and dirty substitute for real documentation.
-
- Connect your computers together using a LapLink or InterLnk
- cable (see CABLE.DOC for wiring diagram). Install PARSETUP.EXE
- into a directory on your PATH. PARSETUP is designed to work with
- both DOOM and DOOM II, and will invoke whichever program resides
- in the current directory when PARSETUP is started, i.e. running
- PARSETUP from the directory containing DOOM2.EXE will cause
- PARSETUP to launch DOOM II instead of DOOM. Alternatively, you
- can install a copy of PARSETUP into each of your DOOM
- directories, at the cost of a little extra disk space.
-
- Once installed, use PARSETUP just as you would use IPXSETUP
- or SERSETUP. In addition to the standard DOOM command line
- switches, PARSETUP understands the following:
-
- -player1
- Forces console to be player 1 (Indigo) to override the
- automatic player choice. Player 0's machine is the "master" and
- sends the network start information at the start of the game.
- This can sometimes be helpful when systems of vastly different
- speeds are linked together for DOOM, or if you just want to
- manually decide which player will be Green and which will be
- Indigo.
-
- -port
- Specify the base I/O port for the printer in C-style hex
- notation. Possible values are 0x378, 0x278, and 0x3bc.
-
- -irq
- Specify the IRQ setting used by your printer port. Can be any
- value in the range [2..7].
-
- PARSETUP defaults to I/O port 0x378, IRQ 7 which corresponds
- to LPT1: on most systems.
-
-
- Troubleshooting
-
- Q: I connected my computers together with a cable, but all I
- see is "wrote: PLAY0_0" scrolling endlessly up the screen. What's
- wrong?
-
- A: There are a couple of problems which can cause this. You
- might have the wrong kind of cable; the wiring of the cable used
- for PARSETUP must have AT LEAST the connections listed in
- CABLE.DOC. Extra wires probably won't hurt, but too few wires or
- wires which connect the wrong pins will prevent PARSETUP from
- communicating across that cable. Once you have verified that your
- cable is wired correctly, you can test the cable using the
- InterLnk program which comes with recent versions of MS-DOS.
-
-
- Q: OK, I did all of the above, but when I try to play I
- *still* get an infinite list of "wrote: PLAY0_0" strings on my
- screen. What gives?
-
- A: Since you verified that the port address and cable
- connection are both OK in the earlier steps, the next problem
- area involves interrupt request (IRQ) settings. A printer port
- can be configured to generate an Interrupt ReQuest on one of the
- available IRQ lines, usually IRQ7. In most systems, the interrupt
- capability of the printer port is unused. For this reason,
- systems are often configured such that network cards, sound
- cards, mouse cards, or some other peripheral makes use of this
- "unused" printer port IRQ line. This situation is bad news for
- us, since two separate cards on a PC expansion bus cannot share
- the same IRQ level. Thus, if your network card or your
- SoundBlaster is set to use IRQ7, and your printer port card tries
- to use IRQ7 also, the result is a conflict and PARSETUP probably
- won't work.
-
- To correct this, make a note of the IRQ settings on each
- card plugged into your PC's expansion bus, as well as the actual
- IRQ setting used by your printer port. If you do find a conflict,
- you must change one of the cards to use a different IRQ. NOTE:
- Some motherboards with built-in printer ports allow you to
- enable, disable, and change the printer port IRQ settings using
- jumpers on the motherboard or in the BIOS SETUP. Check your
- computer documentation for more information.
-
- Once you have reconfigured your expansion cards to avoid IRQ
- conflicts, retry PARSETUP.
-
-
- TO REPORT BUGS:
-
- Email questions, comments, and bug reports to asre@uiuc.edu
-
-
-