Error messages

The following error messages can be generated by Ramdrive 1.0 while setting up your ramdrives:

BAD CHARACTER:

An invalid character was found on this line. Only numbers, uppercase letters, commas, spaces, underscores, semicolons, $, " and % are valid characters, unless in a string.

BAD COMMAND:

The command is not recognised by Ramdrive 1.0. You have most likely made a mistake entering the command name.

UNEXPECTED CHARACTER:

The command should be separated from its first parameter by a space. Some other character was found between the command and the first parameter.

UNEXPECTED END OF LINE:

An end of line character (155) was found when not expected. This is usually caused by a comma with no parameter after it.

BAD PARAMETER:

There is a mistake in this parameter. Either an invalid character was found, or if it is a string, the closing " is missing.

TOO FEW PARAMETERS:

You have not given this command enough parameters. Check the manual for the correct number of parameters.

TOO MANY PARAMETERS:

You have given this command too many parameters. Check the manual for the correct number of parameters.

WRONG NUMBER OF PARAMETERS:

You have given this command the wrong number of parameters. Check the manual for the correct number.

EXPECTING ,:

Either there's a comma missing, or there's a stray space on this line. A command's parameters should be separated by commas.

NUMBER TOO BIG:

The number is greater than 65535. Only numbers between 0 and 65535 inclusive are allowed.

BAD BINARY NUMBER:

The binary number you have entered is wrong. Binary numbers are made up of 0's and 1's preceded by a % and can have a maximum of 16 digits.

BAD DECIMAL NUMBER:

The decimal number you entered is wrong. Decimal numbers are made up of digits between 0 and 9, have no prefix, and can have a maximum of 5 digits.

BAD HEXADECIMAL NUMBER:

The hexadecimal number you entered is wrong. Hexadecimal numbers are made up of digits between 0 and 9, and uppercase letters between A and F inclusive, are prefixed with a $ and can have a maximum of 4 digits.

BAD PARAMETER TYPE:

Parameters can be either strings, numbers or constants. Not all commands accept all types of parameters. You have given the command a parameter type it wasn't expecting (i.e. a number when it was expecting a string). Check the manual for the correct parameter type.

BAD CONSTANT:

The command does not recognise this constant. Check the manual for the constants recognised by this command.

PROCESSING STRING:

An error was found in this string. Strings should be surrounded with double quotes (").

MISSING ":

The close quote for the string is missing. Strings must be surrounded by quotes.

2ND ADDRESS MUST BE HIGHER THAN 1ST:

The second parameter passed to the LOAD_ADDR must be higher than the first.

NOT ENOUGH SPACE DEFINED:

There is not enough space between the first and second parameters to the LOAD_ADDR command for the Ramdrive 1.0 code and any ramdrive set up so far. Either reduce the number of ramdrives, decrease the first parameter to LOAD_ADDR or increase the second parameter to LOAD_ADDR. You need to allow 1042 bytes for the Ramdrive 1.0 code plus 23 bytes to store the configuration information for each ramdrive you have set up. If only 1 parameter has been given to the LOAD_ADDRs command and it is less than 20224 then the top range will default to 20223, otherwise it will default to 65535.

OUT OF SPACE:

There is not enough space as defined by the LOAD_ADDR command to add another ramdrive. If you need to add another ramdrive then you must increase the space defined with LOAD_ADDR. Each ramdrive needs an additional 23 bytes for its configuration information.

BAD ADDRESS:

The addresses specified in the LOAD_ADDR parameters are invalid. These addresses should not overlap the area RAMDRIVE.OBJ loads into (20224 to 35365 inclusive), change the values of the parameter so that they don't overlap the RAMDRIVE.OBJ area. This error will occur if either (or both) of the parameters to LOAD_ADDR are within this area or if the first parameter is less than 20224 and the second parameter is higher than 35365.

NOT ENOUGH FREE BANKS:

You do not have enough extended memory banks to create this ramdrive. If you have more extended banks available then increase the BANKS command parameter, otherwise use a smaller ramdrive.

IOCB x NOT AVAILABLE:

This error occurs if the second parameter passed to the XIO command is 4. IOCB 4 is reserved for use by the Ramdrive 1.0 set-up code.

NOT A RAMDISK:

You have tried to either write protect or unprotect a drive that isn't a ramdrive. Only ramdrives can be protected or unprotected in this way.

ERROR xxx READING SECTOR sss:

Where xxx is the error number and sss the sector number. An error occurred while Ramdrive was trying to read this sector from this drive.

ERROR xxx WRITING SECTOR sss:

Where xxx is the error number and sss the sector number. An error occurred while Ramdrive was trying to write this sector on this drive.

OFSET LARGER THAN OR EQUAL TO SECTOR SIZE:

The 3rd parameter to the MODIFY_SECTOR command must be between 0 and the sector size-1 inclusive, (i.e. 0 and 127 for single density, 0 and 255 for double density, etc.). Reduce the value of this parameter.

OFSET + NUMBER LARGER THAN SECTOR SIZE:

The 3rd parameter plus the fifth parameter to the MODIFY_SECTOR command must not be bigger than the size of the sector, i.e. for single density sectors these values must not add up to more than 128.

BUG ALERT!:

BUG ALERT! IN DECINT:

BUG ALERT! IN CMDTBL:

You should hopefully never see these error messages, but if you do then you have found a bug in Ramdrive 1.0. If this happens then send me copies of your RAMDRIVE.CFG and RAMDRIVE.CPY files along with your system's details (computer type, extended RAM size, bank size, number or banks, DOS used, OS used, any modifications you have installed, etc.) and I'll fix the problem for the next release.

ERROR xxx OPENING RAMDRIVE.CFG:

ERROR xxx OPENING RAMDRIVE.CPY:

Where xxx is an error number. Either the RAMDRIVE.CFG or the RAMDRIVE.CPY files are not on the disk, or they couldn't be read. Check in your DOS's manual for the meaning of the error code, or insert the correct disk.

ERROR xxx OPENING filename:

Where xxx is an error number and filename the name of a file. An error occurred while the COPY_FILE command was trying to open this file. Check your DOS manual for this error's meaning.

ERROR xxx READING filename:

Where xxx is an error number and filename the name of a file. An error occurred while the COPY_FILE command was trying to read this file. Check your DOS manual for this error's meaning.

ERROR xxx WRITING filename:

Where xxx is an error number and filename the name of a file. An error occurred while the COPY_FILE command was trying to write this file. Check your DOS manual for this error's meaning.

ERROR xxx DURING XIO:

Where xxx is an error number. An error occurred while this XIO command was being carried out. Check your DOS manual for this error's meaning.

ERROR xxx DURING NOTE:

Where xxx is an error number. An error occurred while Ramdrive 1.0 was attempting a note command. Ramdrive 1.0 will attempt a note when a PROMPT, COPY_FILE with 3 parameters, or a COPY_SECTOR or MODIFY_SECTOR command whose last parameter is a string, is found. This is done so that if the disk with the RAMDRIVE.CFG or RAMDRIVE.CPY file is removed from the drive, then Ramdrive 1.0 can detect this and ask you to replace it after the command has executed.