Errors
I get the message "Running in restricted mode", then the application fails to find default.cfg.
Quake III can't find the baseq3/pak0.pk3 file. Quake will not give an
error message if the pack file is missing, it will just run in restricted
mode, and look for demoq3/pak0.pk3. If it can't find the demo pack, it
will again not complain, but just tell you that it could not find the
very first file it expected -- which happens to be default.cfg.
Make sure baseq3/pak0.pk3 still exists in your install directory and has not been moved or renamed.
If this file is in place, the error is most likely caused by your Quake III wrapper script being overwritten. Your install directory should contain both a "quake3" file and a "quake3.bin" or "quake3.x86" file. The "quake3" file should be a small shell script and the other is the Quake III binary executable. If the script shows a size of 916340, the script has been overwritten with the binary. You'll need to mv
#!/bin/shWhen I try to run the game from the CD, I get:
# Needed to make symlinks/shortcuts work.
cd "/usr/local/games/quake3"
quake="./quake3.x86"
"$quake" $* exit $?
+set fs_cdpath /mnt/cdrom <-- command line seta fs_cdpath /mnt/cdrom <-- config fileI can't set in_dgamouse to 1.
#!/bin/sh # Needed to make symlinks/shortcuts work.Quake III won't recognize my mouse wheel.
cd "/usr/local/games/quake3"
quake="./quake3.x86"
"$quake" $* exit $?
ls -l /dev/3dfx grep 3dfx /etc/conf.modules ldconfig -v | grep glide ldconfig -v | grep GLMake sure that you have the proper version of the SDK installed. In the /usr/local/glide/bin directory, use "detect" as normal user, and, if it doesn't work, then try as root. If it works as root only, /dev/3dfx is either missing or has wrong permissions. Next, use "test3Dfx" as a normal user and then as root. If this does not work, your Glide library might have the wrong version, wrong permission, can't be handled by ld, or may not even be installed. Next, you might want to try a Mesa demo like demos/gears. If this works with your 3dfx in fullscreen, then any remaining problem will be Q3A specific. If Mesa renders in software mode in a window, then Mesa is not compiled for Glide and 3dfx. Screenshots are broken.
Your machine name should be listed with its ethernet IP address instead of with the loopback address, like this:127.0.0.1 localhost 10.1.1.1 franknputer1 10.1.1.2 franknputer2 10.1.1.3 franknputer3Thanks to Craig Block for this informationCouldn't get a visual ...WARNING: could not set the given mode (3)You have to have a 640x480 modeline in e.g. your /usr/X11R6/blib/X11/XF86Config. If you try to use 532x384 or below, you also need those lines. You can try+set r_mode 4 (or 5 or above).Below is a sample. Do not copy these, as they vary depending on your monitor. Chances are you have a modeling, but have not listed it in the SubSection "Display":modes# 640x400 @ 70 Hz, 31.5 kHz hsync Modeline "640x400" 25.175 640 664 760 800 400 409 411 450 # The Colour SVGA server Section "Screen" Driver "svga" Device "G400" Monitor "Optiquest V95" Subsection "Display" Depth 16 Modes "640x480" "800x600" "1024x768" "1152x864" ViewPort 0 0 EndSubsection EndSectionYou also have to have the following if you are using GLX:Section "Module" Load "glx.so" EndSectionBack to Questions