Navigation:  PBShell >

PBShell Errors

Previous pageReturn to chapter overviewNext page

 

Fatal errors produce an error message box, as follows:

 

No source file specified

 

The absolute minimum command line consists of one source file name.

 

File <source/resource> not found

 

Either: The primary source file (or current source file if no primary is specified) does not exist, either as passed or with an assumed .BAS extension (if no extension specified).  Or: The current source file (or primary source file) has an .RC extension, triggering a resource compilation, but the resource script file was not found.

 

Could not execute <executable_spec>

 

This is an unexpected error in executing the compiled program when using the /E or /X options.

 

Cannot execute a DLL

 

This error will occur if you use the /E option for a source file that includes a #COMPILE DLL directive. If the /X option is used for such a source file, the /X option will be ignored and the completion dialog will be shown after compilation instead.

 

Cannot execute a resource file

 

The /E option was specified with a resource script name as the primary source file.

 

No PB compiler found

 

If no #COMPILER directive was found in the primary source file and neither PBWIN.EXE or PBCC.EXE was found. If a #COMPILER directive was specified, no compiler of the correct type was found. Check that either PBSHELL.EXE is in the same directory as the compiler or that the registry entry is correctly set.

 

Could not determine which PB compiler to use

 

Two or more PB compilers were found and it could not be determined which was the correct one to use. To resolve this error, put PBSHELL.EXE into the same directory as the required compiler.

 

Integrated Debugging Environment not found

 

Could not find or start the PBEDIT/CCEDIT IDE when the /D switch (compile & debug) was specified.

 

Could not get the IDE menu handle

 

Problem setting up the PBEDIT/CCEDIT IDE when the /D switch (compile & debug) was specified.

 

Could not modify the IDE file menu

 

Problem setting up the PBEDIT/CCEDIT IDE when the /D switch (compile & debug) was specified.

 

Resource compiler not found - RC.EXE

 

It is expected that RC.EXE resides in the same directory as the PB compiler.

 

Could not create pipe for resource compiler

 

The output of RC.EXE is captured via a pipe. This error indicates an unexpected problem opening this pipe.

 

Could not execute RC.EXE

 

It would be unexpected to get this error, since the existence of RC.EXE has already been verified, but there was a problem shelling to the resource compiler.

 

Pipe buffer overflow compiling resource

 

There was an unexpected quantity of output from RC.EXE. Normally, RC.EXE produces no output or one line only to indicate an error (though the new RC, unlike the old one, always produces some output).

 

Failed to create <resource_name>.RES

 

There was no other error, yet the .RES file cannot be found after running RC.EXE - strange!

 

Resource converter not found - PBRES.EXE

 

It is expected that PBRES.EXE resides in the same directory as RC.EXE and the PB compiler. This error is only shown if there is a primary source file which includes the #RESOURCE metacommand, clearly signalling your intention to produce a .PBR file.

 

Failed to create <resource_name>.PBR from <resource_name>.RES

 

This is the only check on PBRES.EXE operation. The .RES file was created successfully, PBRES.EXE exists, but no .PBR was created. Maybe the shell failed. This error is only shown if there is a primary source file which includes the #RESOURCE metacommand, clearly signalling your intention to produce a .PBR file.

 

Could not initialize DDE

 

Problem communicating back to the editor via DDE after a source compile or resource compile with an error.

 

Could not create DDE service handle

 

Problem communicating back to the editor via DDE after a source compile or resource compile with an error.

 

Could not create DDE topic handle

 

Problem communicating back to the editor via DDE after a source compile or resource compile with an error.

 

Could not complete DDE transaction

 

Problem communicating back to the editor via DDE after a source compile or resource compile with an error. Note that if the editor is not running, this does not produce an error - the DDE transaction is simply abandoned.

 

Could not run #PRECOM command: <command_line>

 

The SHELL to the specified #PRECOM command failed with an error.

 

Could not run #POSTCOM command: <command_line>

 

The SHELL to the specified #POSTCOM command failed with an error.

 

Warning: Include path not found

 

This last is not a fatal message box error.  If if occurs, this shown in place of the normal "compiling" messages, extended to at least 3 seconds duration.  This message indicates that no include path was found in the registry and that no include path was obtained from the PBWIN.INI file. Therefore, no include path has been passed to the PB compiler (or the resource compiler) and this is the probable cause of any subsequent "file not found" error from the compiler.