132 - Response files nested more than 10 levels deep in <file name>

There is no limit to the number of response files you can supply to WL32 but there is a limit to how deeply they can be nested. This message indicates <file name> exceeds a nesting deeper than ten levels. Move the offending response files out of the tenth nesting level.

133 - Allocate memory attempt failed. Probably out of virtual memory.

This error is most often caused when CauseWay's virtual memory manager runs out of conventional and extended memory and disk space is very low. Free up more disk space or extended memory. When using Windows or OS/2, allocate more DPMI memory for the linking session. If you are using the CAUSEWAY=SWAP, TEMP or TMP environment variable, make sure it is not pointing to a disk with little free space.

134 - Resize memory attempt failed. Probably out of virtual memory.

WL32 failed to increase the memory associated with a previously allocated selector because there was no more memory available. This error is most often caused when CauseWay's virtual memory manager runs out of conventional and extended memory and disk space is very low. Free up more disk space or extended memory. If you are using an operating system that uses DPMI, make sure enough DPMI memory is allocated to your program. If you are using a TEMP or TMP environment variable, make sure it is not pointing to a disk with little free space.

135 - At least one object module file must be specified when linking.

One or more options and possibly an EXE file name, MAP file name, or library files were listed in the linker command line or response file. However, an object module was not listed. Supply at least one object module file name when linking.

Next Page

Previous Page

Go to Table of Contents

Go back to Devore Software & Consulting home page