PM>I've got the source for Wolf 3d, and although I CAN get it to compile
PM>(using BC++3.0, the original host) it somehow compiles an EXE that's
PM>419-ish K. Whereas the shareware version's EXE is only 100-ish K.
I've never noticed it, but I'd guess the shareware version doesn't
include the additional maps, graphics, sounds, etc. that aren't needed
in the full version. If it makes you feel any better, the commercial
version of Spear of Destiny (basically the same was W3D) is also several
hundred K.
PM>When I exec the program the actual EXE appears to work fine, but I get
PM>bitmaps that are substituted for others, and crazy characters. Basically
PM>the engine works fine, it's just some problem with the bitmap files.
Curious. That's similar to what it does with TC30. I've been thinking
it was either TC30's huge bug, or the pseudo registers being trashed by
the different code that TC30 generates.
I've heard a lot of people say they can't get it to run properly. Only
a few have ever said they can get it to run correctly. I think a good
part of a the problem is the source is just what they could find that
was left of it, and they don't even know what version it was, etc.
PM>Sooo. Is this because I'm using the shareware graphics files?
Well... If you've #defined UPLOAD, it should properly configure stuff so
it can read the shareware version of the data files.
--- QScan/PCB v1.19b / 01-0162
---------------
* Origin: Jackalope Junction 501-785-5381 Ft Smith AR (1:3822/1)
|