DiscJuggler will report many different types of errors in the event log of the Status panel. Host adapters, device drivers, and drives report many types of errors. Unfortunately, DiscJuggler cannot give a detailed explanation of the hundreds of potential errors, but following is a list of the most common errors. For additional error message explanations, please contact Technical Support or visit the Support page at http://www.padus.com/support/.

Blank disc detected:

You have specified a blank disc as the source for a duplication process. Remove the blank disc and insert a disc with content desired the duplication process.

Buffer under-run:

This error is displayed for many different errors depending on the process. In general, it means that the writing drive is not receiving data fast and the writing process has failed. See Problems with Write Speed and Copying and Caching to Hard Disk in the Troubleshooting section.

Illegal field in command descriptor block:

If you are using a reading drive, it is likely that the drive does not contain a feature configured for use by the writing drive. If you see this message for your writing drive, the drive does not contain a feature configured for use in the writing process. In all cases, please see if an update is available for all drives' firmware.

Imperfect Audio Re-synchronization:

DiscJuggler was not able to perfectly duplicate the audio track using software algorithms, even though these imperfections will often not be audible to the human ear. If you have a high quality drive, you can move the re-synchronization slider in the Advanced panel to the "Native" setting to let the drive handle the audio re-synchronization. You can also try setting a lower reading speed. Causes could include a scratched or dirty disc.

Media is incompatible:

Error displayed when using blank media not compatible with a particular type of writing drive. Insert another type of blank media and check with the writing drive manufacturer to see which disc types are compatible.

Medium error:

The disc is use is bad. Try using another disc.

Device not ready:

A drive is not ready to perform the selected action. Try again once the unit has had an opportunity to detect the inserted disc. If you still see this error message, check your cable connections, termination, power to the units, and the seating of discs in drives. Make sure that auto-Insert notification is not interfering. Make sure that no other software capable of disc writing, such as packet writing software, are using drives.

Not enough space on target media:

The destination writing drive or hard disk cannot support the total size requested. With writing to disc, please make sure that the blank media in use supports the amount of data in use for writing. With writing a disc image file to hard disk, make sure that enough space is available and disc image files larger than 4 gigabytes in size are being written to file-systems supporting files over 4 gigabytes in size, such as NTFS.

OPC or PMA update error:

The blank media is either incompatible with the writing drive, or the disc has already been put to use. Drives first calibrate laser power by testing a small area of the disc and if this was done with the writing process being aborted or not started, the OPC area would already be used even though the disc shows up as being blank.

PCA (Program Count Area) area is full or unreadable:

The target disc is not completely blank or has a flaw in its structure. Try using blank media from another manufacturer, if possible.

PMA (Program Memory Area) area is full or unreadable:

The target disc is not completely blank, has a flaw in its structure, or is not rated for the selected write speed. Try using blank media from another manufacturer, if possible.

SCSI/ATAPI communication error:

There is a problem with the host adapter, device drivers, or cabling. Check cable and power connections. Check that you have the latest versions of device drivers supporting components and devices in use.

Unable to detect ASPI manager:

With Windows 2000/XP/2003, the Padus device driver was not installed by the installer, the system was not restarted after installation, or DiscJuggler must be reinstalled. With Windows 95/98/Me, the system contains an older or incomplete version of an ASPI device driver.

Write address is EFM area (already written):

The target blank disc is not completely blank or has a flaw in its structure. Try using blank media from another manufacturer, if possible.