TEMP
, TMP
, and TMPDIR
directories are set correctly. Most importantly, when using RAMFS.IFS
,
do not use a root directory because apparently RC chokes on that. I have the following
in CONFIG.SYS
:
IFS=J:\common\ifs\RAMFS64.IFS CALL=J:\common\ifs\RAMDISK.EXE Z: RUN=I:\OS2\CMD.EXE /C md Z:\temp SET TMP=Z:\temp SET TEMP=Z:\temp SET TMPDIR=Z:\temp
Same thing if you get unknown definitions or unresolved externals during compiling/linking. This is most probably due to outdated helpers.
.IDL
files, you may
have a problem with the nmake
version that is running. Several
people have reported that the nmake
that comes with the Warp 4.5
Toolkit does not set SMINCLUDE
correctly from the makefiles.
I am still running nmake
3, which comes with the Warp 3 Toolkit
and also with the IBM VAC 3 compiler.
Alternatively, look at idl\makefile
and search for
SMINCLUDE
. Uncomment the line that sets the environment variable
and set the variable to the proper values externally. Some people have
gotten the thing to work like that too.
The SOM compiler that comes with some versions of the Warp 4.5 Toolkit appears to produce very strange errors also, according to some user reports. I recommend using the Warp 3 Toolkit; see Required Tools.
src\shared\xwp.def
, which exports the functions from
XFLDR.DLL.
XWPDAEMN.EXE
, which
will automatically unload the hook DLL. Then, after the build, restart the daemon
by executing XWPDAEMN -D
(to circumvent the error message box which
comes up otherwise).
See config.in for details.
.PCH
files in your TEMP directory,
or comment out the PRECH
line in setup.in
to disable
precompiled headers altogether. I have also found that killing DDE4LOAD.EXE
(the VAC background process) helps sometimes, for whatever reason.