[ QBSP v29 Binaries for DOS                               ]
[ compiled with DJGPP v2.0 / GCC v2.7.2                   ]
[ brought to you by Thomas Zajic aka ZlatkO ThE GoDFatheR ]

Some notes:

1) Most important one first (DUH! ;-) - this version of QBSP compiles .MAPs
   to v29 .BSPs (ie. version byte [first byte in the .BSP] 0x1D), which can
   only be used with the registered version of Quake (and, theoretically only,
   SW versions v1.xx - IF they had not completely removed external .BSP
   support in these versions, just like good ol' DooM)! If you need help
   compiling the v28 binaries though (for SW versions v0.9x), feel free to
   e-mail me ... but then again - why would you?! If you like the game, just
   buy it! :-)

2) CWSDMPI.EXE (the DPMI host required to run this package) should be somewhere
   in your PATH or in the same directory as QBSP & Co. - I recommend using
   CWSDPMI release 2, it should be available on any SimTelNet mirror (on
   ftp.cdrom.com, look for csdpmi2b.zip in the /pub/simtelnet/gnu/djgpp/v2misc
   directory).

3) If you encounter any bugs, don't come cryin' to me - it's *Carmack's*
   source, *I* only did some modifications for DOS (the makefile and some .h's)
   and compiled the whole stuff. ***IMPORTANT*** If QBSP is "exiting due to
   signal SIGSEGV" (ie. segmentation violation) with that nice register dump,
   this is most probably NOT A BUG - it just means that QBSP desperately needs
   more (virtual) memory! To make QBSP shut the hell up & get back to work,
   you might want to try this (worked fine for me):

   a) start CWSPARAM.EXE from the same directory as CWSDPMI.EXE - you'll be
      asked some questions about how to configure CWSDPMI.EXE internally
      (nevermind if you don't know what this all means, JUST DO IT! ;-).

   b) "Full name of paging file?" - Your paging file should preferably be
      on a drive with a sufficient amount of free space (I've put it on a
      drive with about 490 MB free, so I don't expect any difficulties here,
      dunno about the absolute minimum required though). As this is only a
      temporary file (used during program execution), there's no reason to
      worry about wasting space (unlike Windoze's 386SPART.PAR ;-).

   c) Skip the next three questions by simply pressing <ENTER> ...

   d) "Paragraphs of memory for extra CWSDPMI internal heap?" - With a setting
      of 1024 you should be on the safe side. I have yet to come across a .MAP
      that doesn't compile with this ... care to write one? ;-)

   That's all there is about it - if it still doesn't work for you, tough luck!
   Note that you only have to run CWSPARAM.EXE once (unless you want to change
   some stuff again, that is), CWSDPMI.EXE will remember & use these settings
   from now on.

4) I'm not responsible for *anything* these binaries do to *anything* and/or
   *anybody* - it was *you* who downloaded the .ZIP, it was *you* who unzipped
   it, and it was *you* who ran the progs, okay?! If you're afraid of viruses,
   let me tell you that F-Prot v2.23a says there are none.

5) Copyright stuff ... yeah, right - as if I was a lawyer or something! :-)
   Anyway, I've seen the Linux/NT/Win95 compiled binaries on ftp.cdrom.com
   as well, so I don't think I'll go to jail for the DOS version.

Have fun!

Thomas aka ZlatkO ThE GoDFatheR
<thomas_zajic@hp-austria-om1.om.hp.com> OR <thomas_zajic@hp.com>