|
|
wave sound, but is currently quite a bit slower overall. Thus you
|
than "qwc fast"; however, it may not feel faster, because the sound
|
Finally, you can use
|
which is the same as qwc fast, but turns on DirectInput, which
|
provides more responsive mouse control, but does not work properly
|
on all systems.
|
automatically take advantage of DirectSound and DirectDraw if they
|
are present. If DirectSound is not present, there will generally be
|
milliseconds after the event that caused it). Note also that there
|
are currently no true DirectSound drivers for Windows NT, so QWCL will
|
sound. See below for information about obtaining DirectX if you do
|
Note that VESA VBE modes aren't required for QWCL to run, but QWCL will
|
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
|
the faster configurations of QWCL. An easy way to get reliable VESA 2.0
|
further information. QWCL can also use VBE/AF 1.0 and greater modes;
|
support.
|
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
|
To use the joystick, you must bring down the console by pressing the
|
joystick with "joystick 0<enter>" at any time. The joystick setting
|
remains in effect for subsequent QWCL sessions until changed, so
|
joystick somehow causes problems that keep you from being able to run
|
joystick for that session.
|
-----------------------------------
|
QWCL crashes or won't run
|
-----------------------
|
it using "qwc safe" or "qwc verysafe". Or you can use command-line
|
switches:
|
This will almost certainly solve your problem; however, it may result
|
result in fewer or slower high-res video modes, and the mouse may be
|
each of the command-line switches until you identify the one that
|
possible.
|
If the above command line does not fix your problems, try:
|
which forces QWCL into silent operation with bare-bones video support
|
APIs are used instead). Again, if this works, try removing switches
|
until you identify the needed one.
|
is caused by outdated or buggy DirectX drivers or code, and can
|
frequently be completely fixed simply by installing the latest
|
Microsoft-supplied version of DirectX, which you may be able to find
|
| All times are GMT -7. The time now is 12:08 PM. |
|
Powered by vBulletin® Version 3.8.8
Copyright ©2000 - 2025, vBulletin Solutions, Inc.
©2000-, AI Media Network Inc123