WinQuake v1.0 (Final)

| Installing and running WinQuake |

In order to run WinQuake, you must first have Quake installed. Assuming Quake is installed in the standard directory, c:\quake, unzip the WinQuake zip file into c:\quake. The following files from the zip file must be present in order for WQ to run:

winquake.exe
pmpro16.dll
pmpro32.dll
wdir16.dll
wdir32.dll
wdirnop.com
wdirnop.pif

Then you can run WinQuake by making c:\quake the current directory, typing "winquake" and pressing the Enter key. Alternatively, you can use wq.bat to run WinQuake. The wq batch file requires one parameter describing how to configure WQ for performance; just type "wq" to get a list of the six options. The first of the six options is

wq fast

This is the same as typing "winquake"; this runs WinQuake in an aggressive configuration that is likely to yield the best performance if it runs successfully on your system, but which has a risk of causing WinQuake or even your system to crash if there are bugs or incompatibilities in your video or sound drivers. Alternatively, you can use

wq safe

to run WinQuake in a conservative configuration, likely to run on almost all machines with no problems, but possibly with slower graphics, fewer high-resolution modes, and delayed sound. Or you can run

wq verysafe

to run WinQuake in a very conservative configuration that is pretty much guaranteed to run, but will probably have slow performance, and will have no sound. Two other options are

wq fastvid

which has maximum video performance, but greater sound latency (delay until the sound is heard), and

wq fastsnd

which uses more conservative video modes, but low-latency sound.

(One odd note is that DirectSound has much lower-latency sound than wave sound, but is currently quite a bit slower overall. Thus you may find that "wq fastvid" is actually faster, by as much as 5-10%, than "wq fast"; however, it may not feel faster, because the sound will lag.)

Finally, you can use

wq max

which is the same as wq fast, but turns on DirectInput, which provides more responsive mouse control, but does not work properly on all systems.

Note that DirectX is not required for WQ to run, but WQ will automatically take advantage of DirectSound and DirectDraw if they are present. If DirectSound is not present, there will generally be considerable sound latency (sound will become audible several hundred milliseconds after the event that caused it). Note also that there are currently no true DirectSound drivers for Windows NT, so WQ will always run using wave output on NT, and will consequently have lagged sound. See below for information about obtaining DirectX if you do
not have it.

Note that VESA VBE modes aren't required for WQ to run, but WQ will automatically make VESA modes available if they're present. Your BIOS may already have VESA VBE 2.0 support built in, but most BIOSes don't. Worse, some BIOSes do have VESA VBE 2.0 built-in, but have buggy implementations, which may prevent you from being able to run the faster configurations of WQ. An easy way to get reliable VESA 2.0 support is by obtaining SciTech Display Doctor; see below for further information. WQ can also use VBE/AF 1.0 and greater modes; again, SciTech Display Doctor is the commonest way to get VBE/AF support.

Note that winquake -dedicated completely replaces the old winded dedicated Win32 server, which is now obsolete.

WinQuake normally uses half the physical memory in your system for its heap, but not less than 8.5 Mb and not more than 16 Mb. You can override this with "-heapsize n", where n is the amount of memory to allocate for the heap, in Kb.

To use the joystick, you must bring down the console by pressing the tilde ('~') key, and type "joystick 1"; you can disable the joystick with "joystick 0" at any time. The joystick setting remains in effect for subsequent WinQuake sessions until changed, so you only need to do joystick 1 once to enable the joystick. If the joystick somehow causes problems that keep you from being able to run WinQuake at all, you can start WinQuake -nojoy to complete disable the joystick for that session.

For further information please refer to the readme file that comes with this package.