home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
D!Zone (Collector's Edition)
/
D_ZONE_CD.ISO
/
docs
/
domohel2
/
domohel2.txt
next >
Wrap
Text File
|
1994-12-06
|
13KB
|
342 lines
DOOM Modem Help Version 2
-------------------
GENERAL INIT STRING
-------------------
Having problems with DOOM 1.2 serial? I tried several modems and
configurations. The below init string seemed to provide the most
consistent results across the widest number of modems. DOOM requires
a 9600 bps connect speed. A 2400 baud modem won't work. There are
some utilities which claim to allow 14.4 connect speeds, but I have
not been able to get the modems to respond properly after using them.
(I prefer to wait for an official patch from ID).
AT &F S46=0 &K0 &Q0 &D2 &W
AT Z H0
--------------------------------
SPECIFIC MODEM BRAND INIT STRING
--------------------------------
Here is the much requested specific modem list. If you have PROVEN
connection methods and init strings, please send them to me so I can
expand the list.
Modem: Init:
---------------------------------------
Infotel 14.4 &F0 \N1 &D2 S37=F8
Nuvotel IFX 14.4 &F \N1 &D2
UDS V.3223 &F \N1 \Q &D2
UDS Fastalk 32BX &F0 \N1 &D2
Microcom AX &F \N1 \Q0 &D2
I will add to this list as soon as I get ABSOLUTE verification on other
modems. Keep in mind, sometimes even these settings have to be tweaked
in order to work with different modems (see specific settings below).
We have had some modems provide incredible smooth play when "tweaked"
properly. If you have one you are confident with, please send me the
modem vendor, version, and init string.
------------------
CONNECTION METHODS
------------------
Bascially, there are four effective ways to connect and play DOOM dialup:
1. Connect via the DOOM SETUP program.
2. Connect via command line options with the DOOM SERSETUP program.
3. Connect via a communication program and then with SERSETUP
4. Connect with redirected DOS commands and then with SERSETUP.
-----------------
DOOM SETUP METHOD
-----------------
a. Edit your MODEM.CFG file. Change the first line (MUST be the first
line) to provide the proper init string for your modem.
b. Run the program SETUP in your DOOM directory. Choose "Play network/
modem/serial..."
c. Choose Modem.
d. Tab to fields and set as desired. The most important fields are
your COM port number.
e. Finally, one side must "CALL" (supply phone #) and the other player
must "Wait for Call".
f. After pressing F10, Your screen should clear. Both sides should see
the init string sent to there modem AND an exact match response. If
you lock up no modem response or ERROR, you need to check your
connection and modem init string.
g. Next, one side will dial the number. The receiving (waiting) player
should see "Waiting for Call..." displayed.
h. Upon ring, the receiving modem should issue an ATA and the modems
connect.
i. This is the most common lock up point. The modems connect, but the
game never detects the other player. Did both sides connect at a
true CONNECT 9600? Did you see the connect message from your modem?
(Look at modem command X4). Are both modems in direct mode? (Look at
modem command \N1 or &Q0). Is there a flow control or break option
causing a problem? (Look at modem commands &K, \Q, \G, \K, &R). The
modem commands are described in more detail in a later section. Also
check the IRQ settings for your COM port. Is everything reporting
correctly? You can run the utility MSD (comes with Windows) to get
precise information on your COM ports and their IRQs).
j. After each side detects and connects, the screen will clear and the
blue ribbon will display across the top. The normal DOOM startup and
initialization will take place.
k. Finally, each side display a message indicating it is SENDING or
LISTENING for the other player. The same troubleshooting points above
apply here. This is the next point of common lock up.
l. The last point where a lock up is encountered is right after the game
"starts". Each player is frozen. Look here for not enough flow
control options set.
m. Occasionally, I have run into CONSISTENCY FAILURES and
NETTICS > BACKUPTICS. I currently have no solution for consisitency
failures -- although it does seem to be more prevelant with specific
modem combinations. The NETTICS > BACKUPTICS seems to be due to
over-zealous modem tweaking. Put some flow control back in and let
the program and/or modem throttle the data.
----------------------------
COMMAND LINE SERSETUP METHOD
----------------------------
a. This assumes you have read the standard connection information and
edited your MODEM.CFG file, etc.
b. The caller should start SERSETUP. For example:
SERSETUP -com1 -dial 555-1212
c. The receiver should start SERSETUP. For example:
SERSETUP -com1 -answer
d. Of course, you would specifiy YOUR COM port and the correct number to
dial. Additional options can be specified, but just stick with the
basics when troubleshooting. See the DOOM README info for more on
command line options.
----------------------------
COMMUNICATION PROGRAM METHOD
----------------------------
a. This assumes you have read the standard connection information and
edited your MODEM.CFG file, etc.
b. Each side should start a communication program like Qmodem or Procomm.
Each side should manually issue the AT commands to set the modem. For
example:
AT &F \N1 &D2
c. The caller should dial the receiver. For example:
ATDT 555-1212
d. When the phone rings, the receiver should issue the AT answer command.
For example:
ATA
e. After the modems connect, exit the program (try to leave the connection
up or leave DTR high. You may have to alter the &D2 to a different
value to cause the modem to stay connected).
f. Each side should start the SERSETUP. For example:
CD \DOOM
SERSETUP -com1
g. Of course, you would specifiy YOUR COM port and the correct number to
dial. Additional options can be specified, but just stick with the
basics when troubleshooting. See the DOOM README info for more on
command line options.
-----------------------------
REDIRECTED DOS COMMAND METHOD
-----------------------------
a. This jewel came from Cris Williams (75300,2704) on Compuserve. It
does indeed work when other methods fail.
b. This assumes you have read the standard connection information and
edited your MODEM.CFG file, etc.
c. These examples assume COM port 1 and a phone number of 555-1212. Alter
according to your setup and real phone numbers.
d. Both sides issue the MODE command to the modem from the DOS (i.e. C:)
prompt:
MODE COM1:9600,N,8,1,P
e. Both sides issue a redirected ECHO command to set the modems to place in
direct mode and disable compression, etc... For example:
ECHO AT&F &Q0 &D2 > COM1
f. The caller should issue the dial sequence. For example:
ECHO ATDT555-1212 > COM1
g. When the phone rings, the receiver should issue the command:
ECHO ATA > COM1
h. Both sides should start SERSETUP. For example:
SERSETUP -com1
----------------------
COMMAND MODEM COMMANDS
----------------------
Here are the most common settings and what they do:
&F - This fetches the factory default in most modems. Always a
good starting point. Modems with multiple factory settings
may require a qualifier (i.e. &F0)
S46=0 - This register setting disables compression on many v.32 and v.42
modems. You might also try S46=136 or %C0.
&K0 - Disable flow control between the modem (DCE) and your PC (DTE).
This was one of the most common problems -- You should look
at flow control options more closely if you connect and just hang
WITHOUT the screen clearing and displaying the blu