Evo uputstva za Quake2, malo je staro, tada je bio aktuelan win95, ali možda će vam pomoći.
Veoma je detaljno, ali se nadam da to neće nikome da smeta.
Quake II - 2 player modem to modem
2 player Quake II via modem connection utilising TCP/IP.
Although Quake 2 doesn't contain serial code (modem / modem link) as most
previous Id titles featured, you can still establish this kind of link with
another player without connecting to the public Internet thus enabling you
to enjoy low ping fragfests with one other player.
What you need:
Win95 OS on each machine.
A registered copy of Quake II on each machine.
A copy of Microsoft Plus or DUN version 1.2
*IMPORTANT* One of the machines needs to have the MS dial up networking
server module installed from either the MS plus pack or alternatively be
running Dial-Up Networking version 1.2
1) On each machine open the network properties dialog box by right clicking
on "Network Neighbourhood" and then selecting properties from the drop down
list. Scroll down until you find your Dial-Up adapter entry, MS TCP/IP
should be bound to this adapter..if it's not bind it.
2) On each machine select the TCP/IP protocol that corresponds to the dial
up adapter (there will be two entries if you also have a NIC using TCP/IP
(as in the above example) and then click the properties button.
3) Select the "IP address tab" from the dialog and click the "Specify an IP
address" radio button. *Note: there is no need to worry about any of the
other tabs here, DNS - WINS - GATEWAY etc. etc. If you have an entry for DNS
or WINS that's cool - leave it alone, there's no need to touch it. We don't
need to worry about name resolution in this application so WINS and DNS
** NOTE ** If you already have an IP address in this field there is no need
to change it as long as the other player assigns an address that is unique
and knows what your address is if you choose to be the server.
4) Enter an IP address in the IP address field - e.g 192.0.0.1 for machine A
and 192.0.0.2 for machine B. These are class C IP addresses so in the next
field entitled "Subnet mask" make sure you have the appropriate entry for a
class C network - eg. 255.255.255.0
5) Click yes/apply or whatever and the machine will ask you to restart..do
what it asks.
6) At this stage each machine should have TCP/IP installed , bound to the
dial up adapter and feature a unique IP address and the correct subnet mask.
7) Time to connect - At this stage it is worthwhile establishing a voice
call to establish who's machine is going to be the Quake server as well as
which machine will act as the Win95 dial up server. Knowing this will save
time and heartache - loved ones are lost, armies are defeated and Quake II
virtual IP network deathmatches don't work as a result of communication
establishing these variables, hang up and proceed to point 8.
** IMPORTANT **
The person who decides to call the Win95 Dial-Up server should follow the
a) Make a new dial up networking connection by clicking on the "new
connection" icon found in the "dial-up networking" section of "my computer".
b) Give the connection a name and phone number e.g Recipient of skull
cracking - Ph# 9234 1234
c) After a new dial-up networking icon is generated which features the name
you just chose a couple of steps back, right click on it and then select
properties. In the "server types" tab make sure tcp/ip is checked and that
the server type is set to "PPP: Win95, Windows NT etc. Click on the TCP/IP
settings button and make sure that the IP address tab contains an IP address
that is unique to the one the server you will be dialling is using.
**IMPORTANT** Make sure that the "log onto network" check box is UNCHECKED.
"Sofware compression" can stay on and "Require Encrytped Password should
also be UNCHECKED.
8) The person who elected to be the Win 95 dial up server needs to launch
the server process by selecting - 'My computer > Dial up Networking and then
selecting the "Connections" drop down menu. Next select "Dial-Up server"
from the list and click on "allow caller access". Click the "server type"
button and make sure that no encrypted password is required and that the
server type drop down box lists "PPP: Windows 95, Windows NT3.5, Internet. *
Software compression can be on.
9) The server machine is now ready to answer. When the incoming call is
picked up by the server and the modems handshake, it is a good idea before
launching the game to ping each other to make sure the IP network is
actually talking. You can use the Windows 95 built in ping tool to do this
from a DOS prompt.
10) The computer that elected to be the Quake II server should invoke the
game and select "multiplayer" from the main menu. Select a map that you're
happy with and let the game begin.
11) The caller should also start Quake II and select "mulitplayer" from the
main menu. If the Quake II server has initialised on the other persons
computer you should see an available game in the server list. Simply connect
and play away.
Note: It is important to remember that in the above example we have used
TCP/IP for our Virtual Private Network as Quake II currently only
understands this protocol (IPX protocol expected in upcoming point release).
You will have noticed from some of the diagrams above that IPX can also be
used across this type of connection. Most games that no longer contain
direct serial connection functionality can utilise this kind of Windows 95
connection by simply using the inbuilt network multiplay code.
EXPECTED Q2 PERFORMANCE:
Results will obviously vary for everybody depending on location, telephone
exchange quality etc. but here is an example of what we have seen lately.
USR Sportster 33.6 Internal modems on each computer.
Both machines 166mhz Pentiums with Voodoo video.
Average client ping 95-110 ms. (makes for quite a good game with Quake 2's
integrated client prediction.
- - - - -
NOTE: I've received a couple of emails from people who set up their machines
to be the Win 95 Dial-Up server and then discovered when attempting to
connect to the Internet after playing that they could connect but could not
browse to sites etc. If your ISP assigns an IP address automatically to your
client when you connect and you have included an IP address in your TCP/IP
properties under the network control panel applet for the dial up adapter
then you will experience this problem.
Why does it happen?: When you manually assign an IP address to the DUN
adapter TCP/IP properties in the network control panel applet it is treated
as a global entity. This means that even if you have "Server assigned IP
address" checked in the DUN connection you use to connect to the Internet,
the IP you assigned in the network control panel applet will be used instead
resulting in the problem described above.
-=- 73 de YU1IS -=-