Packed file corrupt
Cause: You attempted to load the program into low memory.
Action: Try loading the program using LOADFIX.
Note: LOADFIX loads a program above the first 64K of memory and runs the program.
Parameter format not correct
Cause: DOS and COMMANDS. One or more of the parameters entered for the command is not valid, is in the
wrong order, or is duplicated.
Action: Make sure that the character following the slash (/) is valid for the program being run, and that the
command syntax is correct.
Parameter value not allowed
Cause: DOS and COMMANDS. One or more of the parameters entered for the command is not valid.
Action: Make sure that the value following the slash (/) is valid for the program being run.
Parameter value not in allowed range
Cause: DOS and COMMANDS. One or more of the parameter values entered is too high or too low.
Action: Check your typing to see if you misspelled a parameter and if the parameter is within the valid range.
Parameters not compatible
Cause: FORMAT. You attempted to use two parameters that are not compatible with each other (/b and /v,
for example); the parameters specified do not apply to the drive or media.
Action: Review the FORMAT command. Correct the parameters and re-enter the command.
Parameters not compatible with hard disk
Cause: FORMAT. You have used a switch that is not compatible with the specified drive.
Action: Review the FORMAT command. Correct the parameters and re-enter the command.
Parameters not supported
Cause: FORMAT. You tried to format a disk using the /n and /t separately.
Action: /n and /t must be used together. Try the command again, using the correct format.
Parameters not supported by drive
Cause: FORMAT. This message occurs during initialization. An invalid parameter that cannot be supported on a
specific type of hardware was entered.
Action: Review the FORMAT command parameters for further information.
Parse error #
Cause: DOS. An error occurred on the command line.
Action: The "#" position in this message represents a number that corresponds to a particular error that caused
this message to be displayed.
The specific causes and actions for these errors are listed in this book in alphabetic order. Use the following
list to find the message that corresponds to the number displayed on your screen:
1. - Too many parameters
2. - Required parameter missing
3. - Invalid switch
4. - Invalid keyword
6. - Parameter value not in allowed range
7. - Parameter value not allowed
8. - Parameter value not allowed
9. - Parameter format not correct
10. - Invalid parameter
11. - Invalid parameter combination
Partition selected is not a Non-DOS Partition
Cause: FDISK. You selected the option to delete a non-DOS partition; however, the partition you selected is
not a non-DOS partition.
Action: Select a non-DOS partition, or press ESC to return to the FDISK main menu.
Partition selected is not a Primary DOS Partition
Cause: FDISK. You tried to delete a non-DOS primary partition; however, this option can be used only for DOS
primary partitions.
Action: Specify DOS primary partition, or press ESC to return to the FDISK main menu.
Partition selected (#) is not startable,
active partition not changed.
Cause: FDISK. The partition that you selected to be marked active is not a startable partition. The active
partition was not changed.
Action: Select another partition to be marked active.
Path name too long
Cause: COMMANDS. The path for the file you specified is longer than 127 characters.
Action: You might have to move to the directory containing the file you want to process before using the
current command.
Path not found
Cause: DOS and COMMANDS. A file or path named in a command or command parameter does not exist in the
directory of the specified (or default) drive.
Action: Retry the command, using the correct path and file name.
Path too long
Cause: COMMANDS. The path specified as a parameter was greater than 127 characters.
Action: Correct the path and try again.
PCMWIN can only add I/O cards, i.e. Fax/Modem, LAN, SCSI, Sound Card.
Cause: PCMCIA. You attempted to configure a non-I/O card on PCMWIN.
Action: Use PCMSETUP to configure memory cards.
Primary DOS partition already exists.
Cause: FDISK. A primary partition for DOS has already been set up.
Action: Return to the FDISK Options menu and select a different option.
PRINT queue is full
Cause: PRINT. You tried to add more than the limit of 10 files to the print queue; 10 files is the default. You
can set the limit to 32 files. See the PRINT command.
Action: Wait until a file is printed before you add another file to the print queue.
Printer error
Cause: MODE. The MODE command (option 1) was unable to set the printer mode because:
o An I/O error occurred.
o The printer is out of paper (or switch is off).
o The printer timed out (is not ready).
o The printer is offline.
Action: Determine which of the previous conditions caused the error message and correct it.
Printer out of paper error
Cause: PRINT. The printer is out of paper or not turned on.
Action: Turn the printer on, press the "Online" switch, or add paper and retry.
Probable non-DOS disk
Continue (Y/N)?
Cause: CHKDSK. The file allocation table identification byte contains invalid information. Either the disk was
not formatted by DOS or has become badly damaged.
Action: If you did not use the /f switch and you reply Y, CHKDSK will indicate its possible corrective actions
without actually changing the disk. Try running CHKDSK without the /f switch before using the /f and replying Y.
Problem with read
Cause: COMMANDS. There are bad sectors within the directory or file allocation table (FAT) structure. An
error occurred when accessing the directory.
Action: Try formatting the disk to make it usable again.
Problem with write
Cause: COMMANDS. There are bad sectors within the directory or file allocation table (FAT) structure. This is
a write problem.
Action: Try formatting the disk to make it usable again.
Processing cannot continue
Cause: CHKDSK. Your computer might have run out of memory, or the file allocation table (FAT) might be
damaged.
Action: If you continue to see this message, back up the information and reformat the disk.
Program too big to fit in memory
Cause: DOS. The file containing the external command cannot be loaded because it is larger than the available
free memory.
Action: Reduce the number in the buffers parameter in your CONFIG.SYS file (if you have specified BUFFERS),
restart your system, and reissue the command. If the message reappears, your system does not have enough
memory to process the command.
Please see the LEGAL - Trademark notice.
Feel free - send a 
for any BUG on this page found - Thank you.