is where your gaming and hardware needs are met. Be all that
you can be or get out of the game! This won't be a forum for
techno-geeks to find more ways to impress their non-technical
friends, it's for plain folk who need help to better their
gaming experience. But don't blame us if you blow your machine
sky high; we're offering tips, not the Bible on computers.
The mailbag is alive and well - send in those questions to
Subject: Quake 3 Point Release issues
We found many readers at our forum and
in TechTips Mailbag needing help after the release of the 117 Point Release for Quake 3. If you don't have it yet, hop on over to Fileplanet
and download it. Here are some of the questions:
Whenever I try to join a server, it says "server is protocol 45". WTF?
If you are using GameSpy then take a look at the
"Rule" area onve you have hilighted a server. In there you will see the listing for Protocol and for Version. Server version is the
number 116 n and 117 etc... Each of those is assigned a protocol number. 116n is protocol 43 and 117 is protocol 45. Therefore, the error
message you are getting means you need to upgrade to the Point Release 117 in order to play on that server.
I have installed the 117 Point Release and now I get teh message
There seems to be a small bug here. Although not absolutely confirmed as the fault of
the Point Release (possible user install error) it is related to any attempt to install it. It seems as though the q3key file loses your cdkey somewhere
in the install. If you receive this message, check your q3key file (make sure in Windows Explorer you have set Option to show all files) and make sure
your cdkey is still in it. Otherwise, try reinstalling the game and the 117 Point Release.
When I try to play Quake 3 online I get the message "couldn't load default.cfg". (this
is not just Point Release related, but a common question)
This message means you need to install the maximum install from the cdrom.
Dual or Single CPU?
If I have a load of ram, a superfast 3d card, and a fast pIII, is there much
difference in having a dual cpu for Q3A? Should I do it?
The use of dual processors would be more efficient and provide better performance most
likely. Of course that may depend on what dual CPU's..... But overall, there can be a significant improvement in performance of some applications in
using dual processors.
For example; picture that each processor has it's own L2 cache. They also work parallel,
doing simultaneous instructions. It is said that there is a 30 - 60% increase from using one processor. However, you did not mention what OS you are
using. It is proclaimed that NT is the best OS for dual processors so I hope you are not contemplating this decision using Windows 98.
You might want to check out the links at Motherboard
Homeworld and see what goes into running dual processors by examining how the motherboard uses them. I also found a quite interesting article written by Vikingl
about his experience with Dual K7 500 AMD processors and a Voodoo3.
System good enough?
I am planning on upgrading my second computer to play games on my lan.
I don't want to make a top of the line system, but one that will run Q3,
with nice graphics. I was thinking of a 500 Celeron, 128 megs of ram,
Voodoo 3000. Any input would help. Thanks
That system sounds just fine. It will be inexpensive and efficient enough to run Quake 3 nicely. Make sure not to skimp on the
motherboard. That is the center of everything to your computer. You get what you pay for and will regret a cheap purchase later. I highly recommend
Abit boards for Celeron systems. They are easy to setup and run like a dream. And BIOS upgrades are also simple and Abit-USA
gives great instructions.
Ski_Man on the PlanetQuake Forum
I have Win98, NT, and Caldera Linux.
Maxtor 15 gb master ata66
West Digital 6 gb slave ata33
What configuration and software should/can I use to load all three and have the choice of which to use?
Well, you got several choices. You can use LILO ("man lilo" in Linux) to manage them all, which is probably the best bet since it's expandable for whatever settings you want to use, and also plays well with Linux and the other bootloads if you have a need to use WinNT's. Caldera also comes with a copy of Partition Magic 4 in there somewhere on the CD. If you downloaded it, you won't get it. I dunno about people who repackage Linux, it's legal to do and considered a valid means of distribution if you don't want the "goodies" like a manual, but they won't include it either. I think the install files for that are on CD2. (I thought the installer prompted you as to if you wanted to use BootMagic?)
You can find a ton of documentation (ok, a mini-howto) over at http://metalab.unc.edu/pub/Linux/docs/HOWTO/mini/LILO.
Lemme crack open mine and help you out a bit.
(BEGIN /etc/lilo.conf) (anything that I write will be in ()'s from now on)
# LILO configuration file
# generated by 'liloconfig'
# Start LILO global section
boot = /dev/hda
compact # faster, but won't work on all systems.
delay = 3000
(ok, BOOT is what drive you are booting from. I boot from /dev/hda, the first and only drive in my system. Compact reads several sectors at once, but if your system dies when trying to do it, don't do it. It's experimental. Delay is the time before it uses the default OS, in my case, Linux. The delay is measured in deciseconds, so if you want it to wait five seconds before defaulting, you would use "50".)
# VESA framebuffer console @ 1024x768x64k
vga = 791
# Normal VGA console
# vga = normal
# VESA framebuffer console @ 1024x768x64k
# VESA framebuffer console @ 1024x768x32k
# VESA framebuffer console @ 1024x768x256
# VESA framebuffer console @ 800x600x64k
# VESA framebuffer console @ 800x600x32k
# VESA framebuffer console @ 800x600x256
# VESA framebuffer console @ 640x480x64k
# VESA framebuffer console @ 640x480x32k
# VESA framebuffer console @ 640x480x256
(This allows you to set your resolution for your screen in console mode. You can leave this out if you never are in console mode. It also lobs about a second off X windows loading time in Caldera if I remember correctly. You probably don't want to mess with this since Caldera is a X based Linux. My consoles run at 1024x768 since I like to contribute to my adolescent blindness problem)
# ramdisk = 0 # paranoia setting
(Not needed. I don't have a bootable network card or a ramdisk device)
# End LILO global section
# Linux bootable partition config begins
image = /mnt/boot/vmlinuz
root = /dev/hda2
label = linux
(alrighty, the image tag tells LILO where it can find your kernel. You can name the kernel anything. If I compiled a kernel called NataliePortman and put it in /mnt/boot/, I could make a new section for this kernel with a different label and boot different kernels depending on what I needed to do. the root tag tells LILO what drive partition the root "/" partition is on. the label flag is what I type to boot with that kernel. You are allowed to duplicate this into new sections if you change the label to run multiple kernels)
read-only # Non-UMSDOS filesystems should be mounted read-only for checking
(oops, this should be before all that commentary, but when I start up, I like to have my drives read-only until it's done launching daemons. This is because fsck likes read only and because one of my family members would always turn off my computer if it started to boot into Linux and I was annoyed at the constantly trashed filesystem. The drives are
automatically remounted as read-write before you are allowed to log in. This would also be the section for aliasing IDE cdroms to SCSI if you were going to burn CDs)
# Linux bootable partition config ends
# DOS bootable partition config begins
other = /dev/hda1
label = wintendo
table = /dev/hda
# DOS bootable partition config ends
(the other tag says "if they didn't give me anything I can boot to, automatically try booting to this". If Linux ever died (it never does), this partition would be automatically called. You can see that I have labeled it "wintendo" and that it is virtually identical to the Linux drive except it doesn't call a kernel)
I don't know about booting WinNT. Hopefully, just duplicating the Win98 settings, changing the labels and partitions will do ya.