Chapter 15:   TROUBLESHOOTING

FIRST STEPS

If you have problems using CauseWay, first try linking and running a one-line program that simply prints "Hello" on your computer screen. This will help establish if the problem is a basic incompatibility with CauseWay and your system setup, or if the error may lie elsewhere (e.g. a third party library). Please report your results when contacting technical support for further help. As a first step to resolving a problem, technical support usually requests your link or response file, a MAP file (WL32 /m option), and the CW.ERR file if any. Technical support frequently requests detailed information about the machine environment that is having the problem.

The remainder of this chapter provides a description of error and warning messages that you may encounter when using CauseWay. Suggested solutions to correct the errors are included where possible.

DOS EXTENDER ERROR MESSAGES AND RETURN VALUES

DOS extender error messages are displayed by the CauseWay DOS extender when a CauseWay application is running and encounters a serious problem that it cannot recover from. The DOS extender then terminates the application with the appropriate return code, displaying a dump of register values, and writing system information to the file CW.ERR. The WL32 linker itself is a CauseWay application and some of these errors can occur when using WL32 to link your application if the error condition is present.

01 - Unable to resize program memory block.

Generated if DOS reports an error when CauseWay tries to resize its real mode memory block. As the block is always shrunk, the only possible cause of this is corrupted memory control blocks (MCBs). Reboot the system to correct this error.

02 - 386 or better required.

Generated if CauseWay is run on any machine with a processor below a 386SX. To correct this error, run the application on another machine or upgrade the machine's processor.

Next Page

Previous Page

Go to Table of Contents

Go back to Devore Software & Consulting home page