home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Resource Library: Graphics
/
graphics-16000.iso
/
msdos
/
raytrace
/
dkb
/
dkbpro.doc
< prev
next >
Wrap
Text File
|
1991-05-24
|
3KB
|
68 lines
Notes for DKBPRO 2.12
-----------------------------------------------------------------------------
This is a 32 bit version of DKB 2.12. It has been compiled for 32 bit
protected mode with Intel's 386/486 Code Builder Kit. Please Note: It
*ABSOLOUTELY REQUIRES* the following:
80386SX, 80386DX or 80486 Based machine.
80387SX, 80387DX or the built in 80486 CoProcessor or a 487SX.....
AT LEAST 2 Megs of RAM, preferably 4Megs. (The more the better though,)
(it'll use it all. )
A Hard Disk Preferred. Since a Virtual Memory Manager is linked into the
program the disk can be used as swap space much like what Windows 3 (TM)
does to add additional "memory". (See DKBMOD.DOC for notes on how to modify
the amount of hard disk space that will be used by the Virtual Memory
Manager. This is *NOT* dynamic and must be adjusted according to your
individual systems available resources.)
The program *WILL NOT RUN* on 8088, 8086 or 80286 based systems!
If you get a message at startup about an incompatible extended program
in operation, *REBOOT* your machine IMMEADITATLY, --- dont continue!!!
File corruption can result if you continue!!! (This according to Intel
Doc's) Then re-start with a "bare" system.
The program will only run in harmony with relitivly new extended memory
applications. The other application *must* be DPMI 0.9 compliant for both
of them to operate at the same time. (Most arn't, disk caches, XMS->EMS
converters etc.) The program will not run with QEMM installed. If you
intend to be tracing only (I.E. "single tasking" so to speak) QEMM's
functions are un-needed anyway. DKBPRO *WILL* run in concert with QEMM
5.1 UNDER WINDOWS 3.0 in ** 386 ENHANCED MODE **. VCPI applications are
incompatible with DKBPRO.
Please let me know if you find any errors or quirky operation.
The Display option seems to work. It has only been tried on a Tseng
4000 based card and ATI VGA Wonder at this time however.
IBM.C port by John Gallagher.
I have also added a "Trace Time" to the statistics report at the
end of a run. It will report the number of *seconds* that the
actual trace took. (Excluding parsing and swap file setup) It
displays to the nearest second, the 10th's and 100th's will always
be 00. (I.E. XXXXX.00 Seconds).
Other than these differences DKBPRO is exactly the same as the DOS
version. It will however trace MUCH-MUCH larger image sources. It didn't
crash on me with the composite in ROMAN.DAT tripled, I have also mapped in
as many as 3 200+K GIF's in the same image. It has also parsed and traced
a 32,768 triangle fractal surface correctly. 3.3 Meg DAT file!
If you come up with any interesting huge models please let me know!
I am also interested (just for curiosity's sake) in anything that DOES manage
to crash the program. I have found it to be about 20% faster than the
MSC 6.0 DOS version, as well as about 40% faster than a Turbo C compile.
Thanks --- Bill Pulver
CIS: 70405,1152
GO COMART on CIS (CompuServe) for more Raytrace folks.
5/25/91