CydandClaude Fable 5
63312e07f9
- BORLAND/: Borland C++ 4.52 (chosen over 4.5 by byte-match: CODE/RP/CW32.LIB
is identical to 4.52's install lib). BCC32/TLINK32/TLIB/MAKE run natively on
Win11; CODE/BT/OPT.MAK is the shipped BTL4OPT.EXE's exact flag recipe
(extender = Borland PowerPack DPMI32, not Phar Lap TNT).
- restoration/source410/: the literal 1995-form reconstruction of the missing
BT game source (never mixed into CODE/). Round 1-3 state:
* 6 of 10 surviving original TUs COMPILE CLEAN under the period toolchain
(BTMSSN, BTCNSL, BTSCNRL, BTTEAM, BTL4MODE, BTL4ARND) - first builds
since 1996.
* BT_L4/BTL4APP.CPP pilot reconstruction: 12/12 functions, Fail() lands on
its binary-recorded line 400 exactly.
* BT/BTCNSL.HPP: console wire IDs recovered from the binary's ctors
(Killed=9, Damaged=10, ScoreUpdate=13, DeathWithoutHonor=15 [T1];
TeamScore=12 flagged [T4]).
* MUNGA/: 8 engine-header backfills back-dated from the BT412 WinTesla tree
(VDATA numbering decomp-verified; AUDREND's OpenAL-era virtual removed -
the period compiler is the drift detector).
* Tooling: backdate.py (WinTesla->1995 header transform), compile410.sh
(per-TU verification sweep under authentic OPT.MAK flags).
* README: corrected roadmap - MECH.HPP is the capstone grown with the mech
TU reconstructions; BTREG.CPP green = the header-family milestone.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
65 lines
2.4 KiB
Plaintext
65 lines
2.4 KiB
Plaintext
RWINI.TXT
|
|
===========
|
|
|
|
This file explains switches used in the WORKSHOP.INI
|
|
file that control driver behavior (WORKSHOP.INI is
|
|
in your Windows directory).
|
|
|
|
A number of display drivers don't implement some
|
|
off-screen operations correctly. This file documents
|
|
specific workarounds for some of these driver problems.
|
|
Most of the workarounds were tested on a variety of drivers
|
|
and don't cause additional problems. However, some of these
|
|
workarounds have side effects on other drivers, or they
|
|
significantly affect the performance of the operation. These
|
|
workarounds are controlled by switches in WORKSHOP.INI.
|
|
Place all of the switches under the section [Resource Workshop].
|
|
|
|
|
|
RWS_OwnFloodFill=1
|
|
------------------
|
|
Some drivers don't perform flood fill correctly. Either the
|
|
operation fails, or vertical bars are placed on byte
|
|
boundaries in the image. If when using the paint can tool
|
|
you see either of these symptoms, use this switch to correct
|
|
it. Note that this switch is slower than the driver code.
|
|
|
|
RWS_Own16Color=1
|
|
----------------
|
|
If you are creating 16-color bitmaps with custom colors
|
|
(for example, a gray-scale image), you must turn off the
|
|
"Save with default device colors" option in the
|
|
Options|Editor options dialog box. If, after doing that, the
|
|
color table returns to the default colors after saving, use
|
|
this switch to correct the problem.
|
|
|
|
RWS_Own256Color=1
|
|
-----------------
|
|
If you're creating 256-color images with custom colors and
|
|
the colors return to the default, use this switch to correct
|
|
the problem.
|
|
|
|
RWS_ColorCopy=1
|
|
---------------
|
|
Some drivers don't perform GetDIBits properly when the
|
|
source device dependent bitmap is monochrome and either
|
|
less than 8 pixels wide or an odd number of pixels wide.
|
|
You can determine if this problem exists by creating a
|
|
new 6X6X2-Color image. If the initial image is black,
|
|
your driver has this problem. This switch copies the
|
|
monochrome image to a color image before calling GetDIBits.
|
|
|
|
NoDriverHacks=1
|
|
---------------
|
|
When using 256-color drivers, Resource Workshop displays
|
|
a grid on all zoomed images. Use this switch to turn off the
|
|
grid. If Workshop crashes when an image is zoomed, turn the
|
|
switch off and report the problem to your driver manufacturer.
|
|
|
|
bAutoH=0
|
|
--------
|
|
Use this switch to suppress the Add File To Project dialog
|
|
box when creating new .RC projects.
|
|
|
|
========= END OF FILE RWINI.TXT =========
|