The installation packages on the
download page require that you have also a datafile for the game on
your memorycard. Both shareware and full version work. Please do not
me where to find the datafiles. QuakeWorld uses the same datafiles from
the same directory as Quake, so there is no extra installation
procedure for QW other that it requires the full version of the
1. Find a suitable datafile (either shareware, or the full version form original PC version)
2. Create "quake1" folder to the root of your memorycard
3a. If you have the full version, just copy the "ID1" directory to "quake1" directory.
3b. If you have only a shareware .pak file, create "ID1" folder to "quake1" directory and the copy the shareware pak-file there
4. If you want to have cdaudio aswell, create "cdaudio" folder to the
"quake1" folder. Then put the audio files as .mp3 to the "cdaudio"
folder, remember to rename the files from 1.mp3 throught 10.mp3. I
don't know what bitrate is the best, but I have used 256kbps and it has
impact of 0.1 fps to the performance. If you do not have the required
audio files, the background music is just not played.
5. install the Symbian P.I.P.S. c-runtime library, and the install the suitable version of quake.
from version 1.04 onwards, the game supports command file parameters
via file. The file is either "cmdline.q1" for quake, or "cmdline.qw"
for quakeworld. If you want to use command line parameters, just create
the required file(s), and place them to "quake1" folder. Use Google to
find out what parameters the game support, but ofcourse not all
parameters are applicaple. The command line parameters make it possible
to play mods, tested with the official mission packs "Scourge of
Armageddon" and "Dissolution of Eternity". To play the mission packs,
copy "hipnotic" or "rogue" folder from the original mission pack cd to
the "quake1" directory and use command line parameters "-hipnotic" or
Also, please note that in GLquake the brightness slider does not work.
You can adjust it via command line parameter by supplying something
like this "-gamma 0.7". For GLquake it is also possible to enable full
screen antialiasing with -fsaa command line parameter ( will degrade
If everything is in place, you are ready to rock now.
Seems that a nasty defect slipped to the initial release, the game might not work correctly on all languages. If you are having problems to get the game up and running, change the phone language to english.
1. get hold of suitable datafile (original cd or shareware/demo)
1.1 if you have n95-1, update the firmware to atleast 2.x.x otherwise it does not have enough memory.
2. install P.I.P.S and the QuakeII engine. If the phone complains
something about the certificate, check your settings in application
manager. It should be configured to allow installation of all sis files.
3. install datafiles (using for example the usb-mass storage mode)
3.1 create "quake2" folder in the root folder of your memory card.
3.2 inside "quake2" folder, create another folder "baseq2"
3.3 now copy the pak file(s), video folder and players
directory from the original cd to "baseq2" folder. If you have only the
shareware file, put it to "baseq2" folder. NOTE: with shareware .pak, the screen will stay black for about 30 secs
4. (optional) install audio tracks
4.1 create "cdaudio" folder in "quake2" folder
4.2 copy exactly 10 audio tracks (mp3) to cdaudio folder
and name them 1.mp3 through 10.mp3. If you don't have all the tracks
correctly named there, cdaudio wont't play
5. command line parameters can be set through "cmdline.q2" file
which should be placed to "quake2" folder. The file should be saved as
ASCII, and only the 1024 first characters of the first line are read.
Generally, mods that should work. However, mods that require a separate
game dll do not. Same applied to multiplayer games. The engine
installation package contains ported versions of vanilla ctf, xatrix
and rogue, so the official mission packs and ctf do work correctly. The
installation procedure for mods is similar to the base package, but
instead of putting files into "baseq2" you should put the into
"modname" directory under "quake2". To start lets say xatrix, put "+set
game xatrix" (without quotes) to "cmdline.q2" command line file.
Needless to say, you need the datafiles for the mod to be present
Also, the opengl video driver behaves slightly differently with
brightness settings. As it has coloured lighting, you need to use
console/autoexec.cfg to change the "brighness".
example(in the console):
intensity 1.6 (the intensity of bright colors, higher numbers means more)
gl_modulate 1.4 (lower settings makes all shadows darker)
If anything goes wrong, you could try to look for "q2_log.txt" in the "quake2" folder in order to see what went wrong.
In the end, you should have similar directory/file structure as in
these images (the phone seems to map itself as drive G: on my windows
machine, you mileage may vary)
Quake 3 Arena
1. Install Quake 3 Arena to your PC from the original Quake 3 cd
2. Update the game with the latest available update (ftp://ftp.idsoftware.com/idstuff/quake3/win32/q3pointrelease_132.exe)
3. Locate the baseq3 folder in the game installation directory on the PC
4. Create "quake3" folder on the memory card/mass storage drive on the phone (using usb mass storage mode with PC)
5. Copy the baseq3 folder from the game installation directory on the PC to quake3 folder and LEAVE ONLY FILES ENDING WITH .PK3
and delete everything else. Any other files from the PC version will probably screw something at this point.
The directory/file structure should be like this on the phone:
| | pak0.pk3
| | pak1.pk3
| | pak2.pk3
| | pak3.pk3
| | pak4.pk3
| | pak5.pk3
| | pak6.pk3
| | pak7.pk3
| | pak8.pk3
6. Install P.I.P.S 1.3(or later if available) to the phone (pips_nokia_1_3_SS.sis)
7. Install Quake3 to the phone (q3a_v100_armv6_fpu_hwa.sisx)
8. If you want to use bluetooth mouse or keyboard in the game, install hidsupport aswell (hidsupp_v100.sisx)
You should now be able to start the game (takes some time to start,
with the shell still visible, so please be patient). If something goes
wrong, the game writes a log file (q3_log.txt) to the quake3 directory,
in the case of error
you might want to contact me and send a few last (20) lines of the log file with a description of the error.
The first thing to do in the game is to reconfigure the ingame keys. The default keymappings do not correspond to the real
phone keyboard in any way. Other than that there are few hardcoded keys that cannot be changed:
console key - * on the phone keypad, the green call key on the internal
E90 kb, windows button on Logitech DiNovo mini, and the left softkey on
the Nokia KB
esc - the right softkey
The # key on the phone keypad can be used to navigate to the next menu item in the ingame menus
Full screen antialiasing(FSAA) can be controlled from the graphics options, the default is OFF
Multiplayer should work out of the box, however I strongly recommend
that please configure the access point to be used in the ingame network
settings(restart of the game required). When the access point is
configured, the game
will automatically use that connection. Also, running a local server on
the phone requires that you have configured the access point to use. If
the game can not use the access point for some reason, it's switched
back to none
Configuring bluetooth mouse and/or keyboard for Quake 3 Arena
If you want to play with bluetooth keyaboard and/or mouse, you need to
configure them first. You should have installed the hidsupport package
for that. In the application shell, you should see the "hidcfg"
application, locate and launch it.
The ui of the hidcfg application is rather simple, just navigate to
select the device number you want to configure and press the joystick,
or choose the "Choose device" option from the menu. Depending on the
device you want to
use, it might be necessary to set "Authenticate" to yes in which case
you will be asked a PIN code for the device. If you don't know the pin
code of the device, you could try 0000. The authenticate setting needs
to be set _BEFORE_ you select the
actual device, it does not do anything if you do it afterwards. Most of
the devices I have tried do not require the "Authenticate" option to be
You should always try with the authentication option as "No" first, and
if the device refuses to work with it, try again with authenticate set
Selecting the device is rather straighforward, just select "Choose
device", make your device discoverable(usually some button on the
device) and then select it from the list. If you don't see you device
on the list, just try again. Some devices might ask a PIN
code even if the "authenticate" setting is set to "No", in that case just enter the PIN.
If the device configuration was succesfull, your device name should now
be visible on the list, if not the device was not configured properly
-> please try again with different authentication settings.
When you have succesfully configured your devices, it's OK to quit the
application. Also the configuration needs only be done once, until you
want to use different devices, or the device has been used with some
MAKE ABSOLUTELY SURE THAT THE
"Nokia Wireless Keyboard" (nor any other manufacturer supplied "driver") application is NOT RUNNING
in the background as it will screw everything up
Now just start the game, and press some keys on the KB, or move the
Mouse and they should automatically connect to the phone(mouse cursor
should now move, and you should be able to navigate the menus with the
While I cannot quarantee that your specific hardware works, most of the
devices that use the standard Bluetooth HID protocol are likely to
some devices seem to try
to connect very few times (like the Nokia KB). If that is the case, you
may need to cycle the power on the device(this does the trick with the
Nokia KB), and press some keys again while the game is running.
It's normal that the
bluetooth connection indicator disappears after a while when in hidcfg
or when quitting it. The connection is not actively maintained. A game
like Quake3 listens to incoming connections from input
devices, the connection is set up when you are running the game and press/move the input device.
Mouse/KB cannot be used to operate the S60 UI
Devices known to work:
Logitech DiNovo Mini - bluetooth keyboard/mouse combo
Nokia SU-8W - bluetooth keyboard
Apple - bluetooth mouse (exact model not known, use passcode 0000)
Logitech mouse - bluetooth travel mouse (v270 I believe)
iGo - bluetooth keyboard
Microsoft - bluetooth mouse (exact model not known)
Trust MI-5700rp - bluetooth mouse