FS LOAD Error Messages

Invocation Errors

PRO/5 setup and switch translation:

pro5: <value>: duplicate switch

Program name given twice. Typically, this indicates an error in arguments. Occasionally, it indicates a control character embedded in the command line.

pro5: <value>: name too long

Program name used on startup too large for name space. The limit is 64 characters.

pro5: <value>: duplicate/conflicting switch

A "-m" or "-w" was given twice.

pro5: <value>: bad memory specifier

Value following "-m" or "-w" option not an integer value or is too large for PRO/5.

pro5: <value>: invalid switch

Neither PRO/5 nor the filesystem recognize the switch given.

Filesystem Configuration Errors

All errors returned by the PRO/5 filesystem during its configuration are in the following form:

<error message>

 fs load err=<val0> (val1)

 pro5: unable to initialize filesystem

 Where the <val0> is a Business BASIC error number (with one added) such as:

cannot open config file <filename>

 fs load err=13 (-2)

 pro5: unable to initialize filesystem

This indicates the filesystem was unable to open the file name <filename>, generating a BASIC !ERROR=12 in the process. The underlying error in opening the file was from the host (-2), returning an error 2 from the host filesystem or "C" library. In this instance, this is a UNIX operating system error 2 (ENOENT) (The file/directory does not exist.)

Error Messages

cannot malloc file system data

Out of memory in the filesystem. The error is usually caused by too large an allocation of one or more: ALIASES, STBLEN, CIBS, DEVS, and FCBS.

cannot malloc disk table data

Out of memory in the filesystem.

cannot open config file <filename>

Cannot open the file named <filename>. The "fs load err=" value will give the reason for failure.

alias table overflow

Out of space in the alias table. The alias table defaults to 12 entries, each entry containing a BASIC device description. The default may be increased using the ALIASES=<num> command in the configuration file.

alias table string overflow

An ALIAS line contains more than four fields. The line may contain extra spaces.

BASIC Errors

pro5: unable to allocate channel table

The system ran out of memory when PRO/5 was attempting to allocate its channel table.

pro5: unable to allocate workspace

The system ran out of memory when PRO/5 was attempting to allocate the requested workspace, or a workspace of 64 pages (16KB), if no memory size was specified.

fs load err=<val0> (<val1>)

 pro5: unable to open channel 0

PRO/5 encountered an error attempting to open the channel 0 device. Typically, the <val0> will show one of the following:




PRO/5 cannot find the config.bbx file or cannot find your workstation driver as specified in config.bbx.

This implies the absence of a DSKSYN statement in config.bbx, which disables a disk drive. The most common instance is not disabling a floppy drive A or B.


The device to open for channel 0 was directly named using BBTERM= but cannot be opened because the alias is not located in the configuration file, or the alias points to an invalid device name. This error may also occur when the SQL.INI referenced in the config.bbx file's SQL= line does not exist or is not in the current working directory.




The system does not have enough free memory. The STBLEN value may be too low to hold the config.bbx file or the aliases= needs to be increased.


The terminal type referenced by the alias of the TERM= environment variable cannot be found in the termcap file or TERMCAP= environment variable.


The terminal type does not have one of: "co#" (number of columns) or "li#" (number of lines) or $TERM=unknown. This causes the terminal driver to overflow memory limits attempting to allocate memory for the screen buffer.


PRO/5 has encountered an error it was not designed to translate. Either the operating system has created a new error code or is using a pre-existing error code in a new and unexpected context. Typically, this is seen in MS-DOS 5.x, and equivalent systems where the installer has not started the file sharing with the SHARE command.


This error is issued when PRO/5 detects an attempt to exceed the maximum user count for the installation or an unauthorized attempt is made to access PRO/5. An unauthorized access can occur on either a UNIX operating system network where two or more systems having the same PRO/5 serial number installed attempt to connect to a PRO/5 Data server, or on a Novel Network where two or more servers have the same PRO/5 serial number registered in their binderies. In these cases, one of the copies of PRO/5 must be removed from the server and, in the Novell case, from the bindery. The error can also be issued on a Novell Network where the PRO/5 serial number has not been registered with the bindery on the Server. In this case, log in as supervisor and invoke PRO/5. PRO/5 will register the serial number with the bindery. For additional information, refer to The Novell User Map section in the Installation and Configuration Guide.


Copyright BASIS International Ltd. BBj®, Visual PRO/5®, PRO/5®, and BBx® are registered trademarks.