On Wed, 3 Dec 2014 08:09:40 +0100, "Jiri Malak" <***@gmail.com>
<snippo -- although "vdm" is mentioned, it is in relation to 32-bit
Win 7, and so not relevant to this discussion>
Post by Jiri Malak Post by Paul S. Person
There is also the other problem I reported: when wmake is run within
DOSBox, a wgml command line is produced, but the following whlpcvt
(yes, a DOS32 version of whlpcvt can be built and used) reports that
it cannot find the PTF file: IOW, wgml did nothing.
It used to run and at least try to process the document (succeeding on
some but running out of memory with others). I don't know about anyone
else, but I think our makefiles should continue to support building
with a DOS host (which is essentially what is happening when wmake --
or builder [yes, it is possible to build the 16-bit special tools, but
only from within DOSBox since the build eventually wants to use a tool
it has just built -- is run within DOSBox). But perhaps I am not
setting an environment variable properly here as well.
Oh, now it is a little clearer. You are building OW under NT VDM.
It is a little exotic configuration.
I don't think that it has much sense to run NT VDM based build on 32-bit
Idea of using DOSBOX and other emulators is to fix lack of DOS 16-bit
on some version of Windows and Linux only for wgml utility, all other uses
native 32/64-bit tools.
Which is why I am using it here. I am not using a VDM; DOSBox is my
VDM. Sorry for any conclusion.
This worked before your change, in the sense that wgml 4.0 launched
and tried to process the documents. Granted, it ran out of memory on
many of them, but at least it tried.
Here it is not trying at all. And I have discovered why. It's really
You should know that "d:" is OWROOT. The "real" OWROOT (c:\ow'ow) is
mounted as drive D in DOSBox. The command line:
does not work. No error message appears, neither in the DOSBox itself.
nor in stdout.txt nor in stderr.txt. The command line
does work: wgml launches.
So here is some information about DOSBox: it doesn't accept "/" as a
path character. At least, not in its default configuration. IIRC, this
was configurable under DOS, but there is no guarantee that it is under
DOSBox, and it would really be much simpler to fix the makefile to use
the correct slash and so work with DOSBox or other DOS emulators that
insist on being fed valid DOS paths.
As for the sanity of all this, certainly actually /building/ OW inside
a DOSBox would be an insane thing to do. But, if you read my other
post, you will see that the idea is to do all of the invocations of
wgml and whpcvt inside a single DOSBox, thus reducing the amount of
irritating DOSBox popups to exactly 1. Note that, even with the
document build off, buiding OW from scratch invokes wgml /12 times/:
twice each in three build directories of both browser and viper.
And, since wbrw and ide happen (by shear good luck) to be documents
that wgml 4.0 /will/ build successfully when invoked by wmake running
in DOSBox, the actual OW build can be done as stated in the other
The main build may indeed need to pop up DOSBox for each invocation,
if that is the only way to solve the "out-of-memory" problem; it
appears to work fine with c_readme in docs\nt (used because Win 8.1
will display the help file): every page reachable from the Contents
page displays without complaint. The DOSBox popups are quite
irritating, however and, for a full build, there will be quite a lot
of them. Hence the desire to prebuild the docs in a single DOSBox
"Nature must be explained in
her own terms through
the experience of our senses."