Hurtless by The FLamoots And The Dark Vision [web]
-----------------------------
HURTLESS General Informations
-----------------------------
0) Requirement
---------------
Hurtless requires a 386 compatible computer with 4Mo RAM, Hicolor SVGA card,
and GUS 512k (the SB mode is really unstable :-( ). It was designed for 486-DX2
66 computers !!! So we can't certify that it will run correctly on smaller
machines !
Turn OFF Surround on GUS 512K !!!!!
Avoid QEMM, and use HIMEM instead ;-) !!!
1) Wat is dat ?
----------------
Hurtless is the demo done by TFL-TDV for the Wired 95 event held in Mons on
3-5 november 1995.
The projected version was really bugged and unfinished, and got 9th place (on
17 demos presented there).
This is the final release ! May be an AWE 32 version will be spread in the
beginning of 1996, depending of the free time we'll get ;-) !!!
2) How to run it ???
---------------------
This demo uses VBE 2.0 as well as other SVGA features. The activation of some
routines is controlled via the SetUp in order to avoid some incompatibility
problems.
For example: GFX copro routines or HiColor DAC Switches are not 100% bug free
certified. GFX Detection routines may hang your computer in some cases ...
You can use UniVBE 5.1 or more , to get the VESA 2.00 compatibility !!!
(available on ftp.scitechsoft.com)
In the SetUp, you have 2 main parts:
- The Sound SetUp:
Auto (by default)
GUS (force GUS detection)
SoundBlaster (force SB detection)
(AWE32: not implemented in the current version)
=> Use these options when you have many sound cards in your machine for ex.
To force no sound, just select nothing :)
Disable SURROUND only if - you have a GUS with less than 1Mb on board
(the demo could crash after the intro-scroller),
- if you have a mono soundblaster or a mono
amplifier.
If you don't select Auto, nor GUS, nor SB, you get NoSound !!! Can be usefull
because Mikmod 2.03 SB routines are really unstable !!!
(Interpolation: not implemented in the current version)
- The GFX SetUp:
Detection: you can set it to ON/OFF. Set it to OFF, if you get problems like
computer hangs immediately, or just after the text message of the
beginning (This is because the routines can have an unstable
behaviour on new models of video cards... by ex. we got some probs
with Diamond Stealth 64 S3)
Fast Video Mem/Video Booster: this routine reduces parameters as wait states
or changes some things relatives to the video
addressing scheme, but sometimes this can
produce some incompatibility (computer hangs,
ugly flicks) ! So you can disable it !!!
In the current version, the routine is
available for the S3 and Cirrus Logic 54xx
series.
GFX Copro: this routine actives the use of GFX coprocessors when there are
present ! It may bugs on some video cards (computer hangs, doesn't
rewrite the background correctly)
In the current version, only the Cirrus Logic, Primus and Advanced
Logic copros routines are enabled.
Force 13h: In some parts, by default the demo uses optimised/customised
320x200x256 with 16 pages, which allows advanced buffering
techniques in order to obtain 100% without flickers screens and
faster animation. But the mode initializer can fail, resulting in
an uggly mode (black screen, wrong colors, or "crasy" clock).
So you can disable this feature with this flag.
Force 640x200x32k:
The "Mars" like part uses by default a 320x200x32k mode. The
problem is that this mode can not be run on every video cards
(ex. S3 Trio), so we need to use a 640x200x32k instead, which is
runnable on EVERY Hicolor Video cards (but 640x200x32k is slower
than the 320x200 :-()
known probs:
- On S3 Diamond Stealth 64, may be you need to turn OFF the
Video Card Detection to run the demo properly (ex. if you get
some strange red vertical lines during the text messy)
- On S3 Trio 32/64 and Diamond Stealth: force 640x200x32k !
If you have some ugly dots merged with the picture, try to
set the Video Booster OFF. If it persists, check if you haven't
120 ns DRAMS ( joke for Bismarck ;-) ).
- On S3 805, in the custom 320x200x256, the impair/pair rows are
inverted, so force 13h !!!.
- The use of UniVBE 5.1 reduces incompatibility problems !!!
- Without UniVBE 5.1, some modes can be decentralised, so don't
panic !!!
- On S3, you can try alternative VBE 2.0 ... ex: s3vbe20 available
on ftp.uni-muenster.de /pub/meschede
- better run the demo under HIMEM instead of QEMM (sometimes the
demo may hang in the water or in the scaled plasmas part)
If you want to disable VBE 2.00 features (like linear frame buffer, pmode
interface, ...) use the UNIVBE SetUp for ex.
3) Hidden Keys
---------------
Press ESC if you want to quit the demo
Press SPACEBAR to skip a part
Press +/- to see the CPU time eaten by each part (rasters or nb frames/sec)
4) I want to know more !!!
---------------------------
Report to the hurtless.nfo !!!!
-= Type One / TFL-TDV =-
[ back to the prod ]