This section lists fatal error messages generated by the DOS Microsoft Programmer's WorkBench (PWB.COM). PWB errors (U13xx) prevent PWB from starting up, or returning from a build or operating-system shell.
| U1350 |
Could not execute PWBED.EXE |
| |
PWB.COM could not find or load PWBED.EXE. |
| |
Make sure your system has the following configuration:
 Make sure PWBED.EXE can be found on the path specified in the PATH environment variable and that there is sufficient memory to operate PWB.
Check that your environment contains the recommended settings from the NEW-VARS.BAT file created by the SETUP program when you installed PWB.
|
| |
PWBED.EXE is the executable file for the PWB editor and environment. PWB.COM processes the command line on start-up and handles all system-level commands when building projects and executing Shell, User, Print, and Compile commands. |
| U1351 |
out of memory |
| |
There is not enough available memory to complete the operation. |
| |
Some possible causes for this error are
You may have too many TSR programs installed. Remove some TSRs.
A previous command may not have released memory when it terminated. This can happen if you attempt to run a TSR from within PWB.
You may have too many active command shells. Leave the current shell with the operating-system Exit command.
|
| U1352 |
COMSPEC not defined |
| |
The COMSPEC environment variable is not set. |
| |
PWB requires COMSPEC to be set to the full pathname of the operating-system command processor. |
| U1353 |
error reading script file |
| |
PWB.COM encountered an error while reading the file that contains a script of commands to execute during a shell or build operation. |
| |
This can be caused by a CTRL+BREAK or a disk error while reading the script file. |
| U1354 |
could not execute |
| |
PWB.COM was unable to execute the given command. |
| |
Some possible causes for this error are
The executable file for the command was not found.
The pathname of the command was not found.
The operating system denied access to the file: it is in use by another program.
There is not enough available memory to execute the command.
A previous command may not have released memory when it terminated. This can happen if you attempt to run a TSR from within PWB.
The environment is corrupt.
The executable file is corrupt.
|
| U1355 |
Bad Command or Filename |
| |
An operating-system command or executable program could not be executed. |
| |
The command may be spelled incorrectly, or it does not exist on the path specified in the PATH environment variable. Make sure that your environment contains the recommended settings from the NEW-VARS.BAT file created by the SETUP program when you installed PWB. |