DiskDupe Error Codes

101 Disks are Done

This is a normal message indicating that all the disks are done.

102 User Esc

This is a normal message that occurs when the user presses the [Esc] key to stop duplicating disks.

201 Bad NEC CMD

This usually indicates a hardware problem with your computer.

202 Bad Address Mark

This normally occurs when reading a master disk that is bad, but can also indicate that the drive or disk type is set incorrectly. If your drive has been used for several months, it might need cleaning.

If are using the Pro or AutoPro version and the number of Retries is set too low, disks that would normally pass with the default settings of "2, 10, 5, 100" might be rejected. For example if "2" were selected for each setting, and three retries occurred the disk would be rejected. NOTE: A number must be selected for each category. If just one number is entered, for example "1", DiskDupe does not assume the other settings are "1" as well. The settings may be initialized with zeros, causing this error as well.

It can also occur if the drive or disk type is set incorrectly. If you are using a double speed drive set up as a regular speed drive (or vice versa) in the Drive List (under Setup|Drives) then you might see this message.

With two-cable SDS drives this message can occur if the head 0 cable is connected correctly but the head 1 cable is not or if the cables are reversed.

With single cable SDS drives on the Allegro controller this error message sometimes occurs when the "C1 SDS CONFIG" jumper is set incorrectly. If it is set to YE DA then try setting it to ALF or vice-versa.

203 Write Protect

If the disk that you are trying to write to has a write protect tab on it, you will get this error, unless you are using Relay mode.

It can also occur with an autoloader if the diskette is not being fully inserted in the drive. Remove the cover of the autoloader and visually inspect the insertion of the diskettes using the ALTALK program if you have it.

This can also occur when more than one drive are connected to the same cable on a controller. Never connect two drives to the same drive select (position) on the drive cable.

With two-cable SDS drives this error can occur if the head 1 cable is on upside-down.

204 Record not Found

This usually occurs when reading a master disk that is bad but can also occur if the wrong disk type is selected. See error 202.

If the drive you are using has a Y-E Data interface and the P1 jumper is on the wrong jumper block, this error can also occur.

205 Bad DMA

Usually this indicates that there is a conflict between the floppy controller and some other device in the computer that is using DMA.

Common sources of DMA conflicts:

1) SCSI hard drive cards (Adaptec 1542) 
2) LAN cards configured to use DMA 
3) Soundcards 
4) Power management feature on laptops

In the specific case of the Adaptec 1542 SCSI controller it is necessary that the floppy controller used with DiskDupe supports FIFO buffering. The Allegro and the CompatiCard IV are examples. The new Adaptec 1542CF controllers come with an 82077 floppy controller, which also supports FIFO buffering and works fine with DiskDupe.

Network cards should be jumpered to use polled I/O rather than DMA.

Soundcard conflicts can often be avoided by moving the soundcard or the floppy controller to another DMA channel.

If you get this error message using a laptop then try turning the power management features off.

With SDS controllers make sure that the DMA channel for the Head 0 controller (usually 2) is different from the DMA channel of the Head 1 controller.

If you get this message using an Allegro controller try changing the jumpers on the Allegro to use another DMA channel. Avoid using DMA 2.

If you get this error using a CompatiCard IV then try using another DMA channel on the CompatiCard. Refer to the CompatiCard manual for the corresponding DIP switch settings for SW-1.

The DMA Burst Mode for the controller must be turned on or set to Auto for double speed high density drives. This is set in the Controller List (highlight the controller and then pick Edit). Make sure that your controllers are configured correctly in the Controller List.

With 2XSDS drives you can try going into the computer's CMOS setup and increasing the bus speed and/or the DMA speed. Some older computers are shipped with the bus and DMA speed set too low for 2XSDS drives.

206 DMA Boundary

This usually indicates a hardware problem with your computer. It could also be caused by a software program gone astray. Try rebooting the computer and taking out all memory resident programs.

If you are using any version of OS/2, including WARP, try running DiskDupe with the /DMAWINOFF switch (Dos only), i.e. enter DISKDUPE /DMAWINOFF (Dos only) to run the program.

207 Bad CRC

  • This usually occurs when reading a master disk that is bad but can also occur if the wrong drive type or disk type is selected.
  • If you get this message writing to the final tracks of a diskette then it is likely that the heads on the drive are dirty or misaligned or that the disks are of poor quality. This can also happen when the disk type (density) is set incorrectly, especially with 5.25" diskettes.
  • Sometimes this error occurs if the ribbon cable for the floppy drive is too long or too close to the computer monitor or if the pull-up resistors on the drive or the controller board are of the wrong value.
  • Some drives tend to have problems writing to preformatted diskettes because they cannot overwrite the format information. The older Sony drives are known for this problem. Try using blank media and set "Format" to "Always" in the job menu. If your media is preformatted then try degaussing it. (To degauss small quantities of disks you can use an inexpensive Bulk Tape Eraser, which can be purchased at Radio Shack).

208 Bad NEC

This usually indicates a hardware problem with your computer or floppy controller.

If you get this error on a laptop then try turning off the power management features.

209 Bad Seek

  • If you are using an Allegro I SDS controller with an SDS drive, this can occur if the Allegro is jumpered for a NORM drive interface instead of YE DATA. See the Allegro manual for installation instructions.
  • If you get this error at the beginning of a copy then it is likely that loose or misconnected drive cable or power connector is causing the problem, although sometimes you can get this error right away if the stepping rate for the drive does not suit the drive (see below).
  • If this message occurs at the end of a copy then it is probably either that the stepping rate is set too fast for the drive, there is a problem with the stepping motor for the drive heads, or the track zero sensor for the drive is faulty or mispositioned. Check and make sure that the heads of the drive are not catching on anything (such as the power cable or the diskette jacket).
  • In DiskDupe 5.0 the step rate can be set for the drive by editing the drive in the Drive List (under Setup|Drives) and choosing the Advanced option from the Drive Setup. Usually the Auto setting works best but you can also set the step delay to a particular time. 6ms is usually (but not always) a good value for 3.5" drives, 12ms for 5.25". Try both increasing and decreasing the stepping rate and then running Drive Test from Setup|Drives.

210 Timeout

  • This error can occur for several reasons: The drive that DiskDupe is trying to use does not exist, there is no power to the drive or the disk does not have an index hole. It can sometimes also be cause by an address conflict (see Error 802, Controller not Responding).
  • It can also occur with an autoloader if the diskette is not being fully inserted in the drive. Remove the cover of the autoloader and visually inspect the insertion of the diskettes using the ALTALK program if you have it.
  • With SDS drives this error can occur when the head 1 connector is incorrectly connected to the SDS floppy controller. It can also occur if the SDS (head 1) controller does not have its interrupt disconnected or if the index signal from the drive (pin 8 of the floppy connector) is not getting to both controllers. On the Allegro I controller make sure that the INDEX jumper is set to SDS for SDS drives. See error 824.
  • If you are using a secondary controller card, such as an Allegro card, this can occur if the interrupt is not being serviced quickly enough. Try changing the interrupt from the default value of 6 to 5.
  • DiskDupe cannot read disks with a sector interleave greater than 4. If a particular diskette causes this problem then recopy its files to another diskette with normal interleave using Dos DISKCOPY and use the new diskette as the master for DiskDupe. This error can also occur when DiskDupe is run on a computer that is not completely compatible.

211 Bad Window Margin

  • The diskette has failed the window margin test on the floppy controller board and has been rejected. Window margin testing is only supported on certain controllers.
  • If you are using a 4XSDS (1200 RPM), you will have to turn the Window Margin feature OFF. Currently Window Margin is not supported with 4XSDS drives.

212 SDS Head 1 bad DMA

  • The diskette has failed the window margin test on the floppy controller board and has been rejected. Window margin testing is only supported on certain controllers.
  • If you are using a 4XSDS (1200 RPM), you will have to turn the Window Margin feature OFF. Currently Window Margin is not supported with 4XSDS drives.

213 Bad SDS NEC

This usually indicates a problem with the computer or the SDS (Head 1) floppy controller.

214 Bad Address Mark on SDS Head 1

Normally this error message indicates that side 1 of the diskette is unreadable on a particular track.

If this error occurs consistently on the first track of several disks then this is an indication that DiskDupe can read the data from the head 0 controller but cannot read the data from the head 1 controller. Make sure that the drive is jumpered for the correct mode and drive select.

If you are using a two cable SDS drive make sure that both cables are the same: either both cables are straight or both cables have a twist. On the Allegro controller this message occurs if the head 1 cable of a two cable SDS drive is left unconnected.

If you are using a Tracer 3 autoloader with a Y-E Data 2XSDS drive, the JP-2 jumper needs to be in the 2-3 position.

215 SDS Head 1 Record Not Found

he data on Head 0 of the SDS drive was readable but the data on head 1 was not.

216 Bad CRC on SDS

The data on Head 0 of the SDS drive was readable but the data on head 1 was not.

217 Disk bad after user interrupt

The TSR has informed DiskDupe that some problem was encountered with the diskette so we will take their word for it and reject the diskette.

301 Bad Compare

  • This is an error that normally occurs only when comparing disks. It indicates that DiskDupe rejected a disk because there were data discrepancies between it and the master.
  • With certain computers and controllers this error message can occur when duplicating and this is usually indicative of a DMA problem (especially with Compaqs and machines with SCSI controllers, soundcards, or network cards that are jumpered to use DMA). See error 205, Bad DMA.
  • Sometimes this error can be caused by a floppy cable being placed too close to a noise source (such as a monitor). In this case you will also see error 207 (bad CRC) on some disks. Try using a shorter cable.
  • This error can occur when using an Allegro controller and the Write Protect Disable feature is ON with an unmodified drive.

302 Bad CRC only verify

When the user asks DiskDupe to perform a CRC only verify of some diskettes the DiskDupe asks for the CRC value to check for. If the disk CRC does not match this value this error message is reported.

This feature is not yet supported in DiskDupe.

303 Bad sectors were skipped

Bad sectors were encountered on the master disk, and every attempt at recovering the data was made. Normally a master with a bad sector is rejected, but with The Skip Bad Sectors option enabled DiskDupe will attempt to make a copy of the master anyway.

401 Unknown COM Error

DiskDupe is having trouble using the com port. If possible try another com port or check the serial card. Also try a "clean boot" (i.e. boot the computer from a floppy disk and then try running DiskDupe).

402 Autoloader is not Responding

  • Usually because the wrong com port or autoloader type is chosen. Try another com port in the Autoloader List under Setup. Use the test button on the autoloader list to see if the autoloader will respond.
  • Can also be caused by the autoloader power switch being off, by a bad serial cable, or by com port drivers (i.e. mouse drivers) eating up the response from the autoloader (the autoloader calibrates but then DiskDupe reports the error 402). Try booting from a floppy diskette and then running DiskDupe. If the problem goes away then some com driver is to blame.
  • If you get this error when trying to access a drive that is not in an autoloader then setup the drive to use no autoloader (under Setup|Drives).
  • If using DesqView, make sure in the DV setup, "Uses Com ports" is Yes.
  • If you are using Com1, make sure that the com port is jumpered as Com1. If it is jumpered as Com2 or 3, Dos will still find it and be able to send commands to it, but DiskDupe won't.
  • If the autoloader is silent and you get an error 402 "Autoloader not Responding" then try USE CTS NO, found in the Autoloader List (pick Edit for the autoloader of interest).
  • If you have the ALTALK program, try this:

In ALTALK pick T for talk and then try the following sequence: 
[C] X [S] 07 [I] X [S] 0B [A] X [S] 07

Send: 
[C] for calibrate 
[I] for insert 
[A] for accept disk 
[R] for reject disk

Receive, One byte: 
X for okay 
E for error 
? for unrecognized by autoloader

Send: 
[S] for status

Receive, Two bytes: 
07 for no disk in drive 
0A or 0B for disk in drive

First Byte: 
If it is not zero then an error has occurred. 
1, 3, 5, 7, 8, 9, B, D, or F indicate a disk jam 
2 indicates that the input hopper is empty. 
4 indicates that a command is out of sequence.

Second Byte: 
0 through 7 indicate that there is no disk in the drive. 
8, 9, A, B, C, D, E, or F indicate that a disk is in the drive. 
0, 1, 4, 5, 8, 9, C, or D indicate that the hopper is not seated.

If there has been an error then you have to send a C for recalibrate to clear the error before the autoloader will accept further commands.

  • If the autoloader does not respond to ALTALK then take the autoloader to another computer and connect it with another serial cable and try running ALTALK again.

403 Bad Autoloader Command

  • Turn the loader power off, wait five seconds, turn it back on and try again.
  • If DiskDupe copies the first disk but then reports an Error 403 Bad Autoloader Command then go into the Autoloader List, highlight the autoloader on interest, choose Edit and turn off the "Use Full Status" option. This is a common problem with older Mountain loaders.

404 Com Port not Responding

If you are using Desqview make sure that "Uses COM ports" is set to "yes". Otherwise make sure that the com port that you have chosen in the Autoloader List works.

406 Printer Com Port not Responding

Can occur if you have the printer type set to a serial type printer, like the JP350, and it is hooked up to a parallel port instead.

407 Input Lost

DiskDupe was unable to recover the serial communication bytes from the autoloader fast enough. Turn of the autoloader, wait five seconds, turn it on again and then try running DiskDupe again.

408 Parity Error

The com port has reported a parity error. Try using another com port or a new serial card.

409 Com Framing Error

Turn the loader power off, wait five seconds, turn it back on and try again.

501 Unknown Autoloader Error

An unknown error has occurred with the autoloader. Turn the loader power off, wait five seconds, turn it back on and try again. Also check the loader cabling.

502 Hopper is Empty

The autoloader input hopper is empty.

503 Disk Jam

  • A disk has become jammed in the autoloader. Remove it before continuing.
  • If DiskDupe reports this error even though there is no disk stuck in the autoloader then it is possible that one of the disk present photo sensors is not functioning correctly. First try turning the autoloader off and on again. If that does not work and you have the ALTALK program, use it and choose T for "talk directly to loader" from the menu. The screen should then display "type [Ctrl][C] to exit". Type a "D" for diagnostics and the autoloader should present a menu of diagnostics choices. Pick "P" for "display photocells" to get a real-time display of the status of the photocells. Check the various photocells by blocking them one at a time with a piece of paper, especially the one mounted in front of the drive and the one mounted by the exit slot. If there is no response from one of the cells then try cleaning it with compressed air.
  • Also try turning off the "Use Full Status" option for that Autoloader. Go into the Autoloader List, highlight the autoloader on interest, choose Edit and turn off the "Use Full Status" option.

504 Output Bin is Open

Some Mountain autoloaders have a removable output bin that has to be in place for the autoloader to function.

505 Labeler is empty

This error message applies to the ADC Copymaker Plus (LLP). The printer has been sent a label file but no disk. Press the pause key on the autoloader.

506 Input hopper is empty

This error message applies to the ADC Copymaker Plus (LLP). The input hopper of the printer is empty. Refill the hopper and then press the pause key on the autoloader.

507 Output hopper is full

This error message applies to the ADC Copymaker Plus (LLP). The printer output hopper is full. Empty it and then press the pause key on the autoloader.

508 Loader is paused

This error message applies to the ADC Copymaker Plus (LLP). To resume press the pause key on the autoloader.

509 No Disk in Printer

DiskDupe has ejected a disk but the disk has not arrived at the inline printer. Check to see that a jam has not occurred.

511 Bad disk in good bin

A bad disk has been placed into the output bin.

602 File not Found

  • You may be trying to use an image, set label, or serial file that does not exist or that is in a different directory from where DiskDupe is looking. DiskDupe assumes that all of these files are in a common directory with the image files.
  • To create a new file select the File|New menu. To view an existing file select File|Open. In either case the file dialog box will show at the bottom what directory the files are in.
  • Can also occur while trying to create an image when Compare is chosen instead of Duplicate from Job|Go.

603 Path not Found

This can occur if you have erased the subdirectory that a file was in.

604 Too Many Open Files

If you get this error, check your CONFIG.SYS file to see if there is line that says FILES=30(or greater). If not, add this line and reboot your computer before trying DiskDupe again.

605 File Access Denied

This can happen if you have marked a file as read-only and are trying to create a new disk image file with the same name. Use the Dos command (ATTRIB -R filename) to unmark the file. It can happen on a network if someone else is using the same image file. If two people are trying to make copies of the same disk image file, mark it as shareable. On Novell networks you can do this with the command FLAG DISK1 SRO.

If the DISKDUPE.DAT file is marked as read only then whenever changes are made to the configuration then DiskDupe will report an "error 605 writing configuration file, changes not saved". This is normal.

616 Cannot Remove Current Directory

You cannot remove the directory that you are currently in.

617 Cannot Rename Across Drives

You can only rename files that are on the same physical drive or partition.

700 File Error. Disk read error

  • This usually indicates a serious problem with your hard disk, but could also indicate that the image file chosen is not intact. Try making a new image file.
  • Sometimes users that are unfamiliar with the DiskDupe will get this message if they pick a non-image file as a source with the intention of copying the file directly to the destination diskette. DiskDupe is designed for disk to disk (or image to disk) copy and does not support a direct copy of Dos files. It is possible to copy files to a Rambodisk from Dos and then run DiskDupe to make a copy of the Rambodisk to a floppy.

701 Disk is Full

Your hard disk is full. Quit DiskDupe and delete some unused files before trying again. To avoid this error make sure there is enough XMS or EMS memory available to buffer a full diskette.

702 File not Assigned

This error can occur if you have erased the Temp File name under Options. Specify C:\DISKDUPE.TMP

703 File not Open

Error messages 703, 704, and 705 will only occur if a software program has gone astray. Try taking out any memory resident programs and rebooting the computer.

704 File not Open for Input

See Error #703

705 File not Open for Output

See Error #703

706 Invalid Numeric Format

A disk image file or the DISKDUPE.DAT file has been damaged. If you get this error message when you first start DiskDupe, copy the DISKDUPE.DAT file from the original program disks into the \DISKDUPE subdirectory on your hard disk. If it occurs when reading from an image file, make a new image file of the disk.

750 Disk is Write Protected

This can occur if you are running off DiskDupe on a floppy drive when DiskDupe tries to save its data files or if DiskDupe tries to write over a disk with a write protect tab. DiskDupe will not work properly when run off of a floppy disk; a hard disk or Ram disk is required.

751 Unknown Unit

Make sure that you specified a valid hard disk letter like C:. If you are hooked up to a network, make sure that you are logged in.

752 Drive not Ready

Make sure that you specified a valid hard disk letter like C:

753 Unknown Command

There is a problem accessing the hard drive.

754 CRC Data Error

Indicates a problem reading data from the hard disk.

757 Unknown Media Type

The hard drive controller has reported an unknown media type error.

758 Sector not Found

The hard drive controller has reported a sector not found error.

759 Printer out of Paper

This error messages occurs when Labels are selected and the printer is not ready to accept jobs.

760 Write Device Fault

DiskDupe is having trouble accessing the hard disk.

761 Device Read Fault

DiskDupe is having trouble accessing the hard disk.

762 Hardware Failure

DiskDupe is having trouble accessing the hard disk.

780 A Virus was found

A virus was found on the hard disk.

801 Configuration File not Found

DiskDupe cannot locate the file DISKDUPE.DAT. or DISKDUPE.DA5 Make sure this file is in the current subdirectory or in a subdirectory on your path statement.

802 Controller is not Responding

  • A controller that is not functioning correctly has been selected under Setup. If you have a secondary controller, check its configuration.
  • Try running Auto-Set from the Controller List in DiskDupe before and after installing a new floppy controller. Normally a computer has only one Primary Controller at address 3F0 and additional controllers are put at the 370 and/or 360 addresses. When the new controller is removed (with the computer power off) if Auto-Set detects a controller at these addresses or if the computer locks up when Auto-Set is run then determine which card is causing the conflict and re-jumper it to use another address or move the floppy controller to another address to keep it from conflicting.
  • If Auto-Set locks up the computer then enter the floppy controller addresses manually in the Controller List.
  • Do not install a new floppy controller card that is jumpered to use the Primary address (3F0) unless the Primary controller for the computer (for A: and B:) has been disabled.
  • If you are trying to run an SDS drive with two controllers then make sure that the second controller (for head 1 of the drive) has its interrupt disconnected and that its address is entered in the controller following the Head 0 controller in the Controller List.
  • Can also occur if a controller is not setup to use IRQ 6, which is the normal floppy drive interrupt request signal. Although DiskDupe supports other IRQs, we recommend using IRQ 6 since it has a high service priority. Look at the controllers documentation for information on what interrupt it is using. Most controllers by default use IRQ 6.

803 Drive is not Responding

  • This is the expected error when the floppy cable is disconnected. Try another floppy cable. Most likely the drive number is incorrect in the Drive List or there is a cabling problem. Try selecting Auto-Set from the Drive List to see where DiskDupe finds the drive.
  • If you are working with an SDS drive with two cables make sure that the head 0 controller is connected to head 0 of the drive and that the SDS controller is connected to head 1.
  • If you are using an Allegro I controller make sure that the C1 SDS CONFIG. jumper is set for the type of interface you are using: NORM for normal drives and two-cable SDS drives, YE DA for factory Y-E Data SDS single cable drives, and ALF for the single cable ALF interface. (If you have jumpered the card for software select of the C1 connector and you are using a Y-E Data SDS drive then make sure you have run the SDSCON.EXE program to configure the connector).
  • With single cable Y-E Data 2XSDS drives make sure that the jumpers on the drive are set correctly. There should only be jumpers on M1, DC and DS0.

804 Not a RamboDisk

The drive letter set for the Rambodisk is not a valid RamboDisk or is not formatted to the correct capacity. Reboot your system and check the drive letter for the RamboDisk, which is displayed when the driver loads. Make sure that the Rambodisk is formatted to some capacity (like 720Kb) and that it is accessible from Dos as a drive letter (like D:). Type RAMBODSK /? from the Dos prompt for help.

805 Not a Valid Image File

  • This occurs when you specify a source file that was not created by DiskDupe. It can also indicate that the disk image file is damaged. Try creating a new disk image file.
  • If an error occurs when creating an image file, even if it is an autoloader error, then the image file will not be finished and will not be valid.
  • Sometimes users that are unfamiliar with the DiskDupe will get this message if they pick a non-image file as a source with the intention of copying the file directly to the destination diskette. DiskDupe is designed for disk to disk (or image to disk) copy and does not support a direct copy of Dos files. It is possible to copy files to a Rambodisk from Dos and then run DiskDupe to make a copy of the Rambodisk to a floppy. Type RAMBODSK /? from the Dos prompt for help.

806 Unknown Image Version

This message commonly occurs when two different versions of DiskDupe are used to copy from a common set of image files. Image files are always forward compatible but not always backwards compatible. Otherwise this could be a sign that the image has been corrupted.

807 Can't Determine Disk Type

The auto-sensing feature under Disk can not tell what type of disk is being used. This usually means that the disk is unreadable but it can also occur if the drive or disk type is configured incorrectly in DiskDupe.

Try setting the disk type manually.

808 Wrong Disk Type

  • Check the type of disk that is set under the Disk menu- usually it is best to leave the disk type set on "Auto".
  • The only cross-format configurations that DiskDupe supports are the three listed in the Help|Contents under "Disk Conversions". In most cases the disk size of the "Source" should be the same as the "Destination" regardless of the amount of data on the master.

809 Set Destination to a Drive

You may get this error if, for example, you are formatting a disk and have destination set to an image file.

810 Controller not a Compaticard IV

The CompatiCard IV is an enhanced controller that has a special driver in DiskDupe. Try the Auto-Set option in the Controller List under Setup.

811 Controller not an Enhanced 82077

Try setting the controller type to Standard.

812 Not Enough EMS Memory

This could indicate a problem with the actual memory chips in your computer.

813 Not Enough XMS Memory

This could indicate a problem with the actual memory chips in your computer.

814 Bad set File

Your set file has been damaged. Try creating a new set file (File|New).

815 User Interrupt TSR not Installed

  • If you are using a copy protection program like Az-Tech's Everlock or BBI's StopCopy make sure the copy protection TSR is installed before you start DiskDupe, then go into Job|Options to activate it.
  • If you are not using a TSR, make sure User Interrupts is off under Job|Options.
  • DiskDupe looks for the TSR at interrupt vector 60 (hex).

816 SDS Controller not Responding

  • The controller for the head 0 side of the SDS drive is responding but the controller for head 1 is not. Check the address of this controller and make sure it is the address listed for the last controller in the Controller List. If it is not then enter the correct address in this menu or try running "Auto Set". If something is conflicting with the controller then you might need to move it to another address. See error 802.
  • Also make sure that the interrupt on the SDS controller is left unconnected.

818 File is Bad

  • Can occur if an image, DiskDupe.DAT, or serial file has been corrupted. Remake the file, but keep a backup of the corrupted file just in case this is not the problem. Image files have built in Cyclical Redundancy Checks which help maintain data integrity, so if the data read in does not correspond to its CRC calculated value this error may occur.
  • Can also occur when DiskDupe is buffering data to an area of the hard drive that is bad. If this problem is encountered, a possible solution might be to run SCANDISK which comes with Dos 6.0 or running an equivalent program that checks your hard drive for bad spots.
  • Can also occur if you are using some sort of disk caching program, such as LanCache that comes with Lantastic 6.0. If this is the case try performing a "clean" boot, i.e. boot the computer from a floppy disk or press the [F5] key when your computer is booting up, if you have Dos 6.0, and then try running DiskDupe.

822 Setup Error (command line)

DiskDupe has not recognized one of the command line switches used, which is indicated with a ^ symbol in the error dialog box.

823 First disk needs to be write-protected

When running in Relay mode the first diskette must have a write protect so that it can be recognized as a master.

824 SDS Head 1 not Responding

  • The drive SDS drive head 0 is responding but the drive head 1 is not. Check the connection between the head 1 board on the drive and the controller.
  • Some SDS drives are designed to operate with controllers (such as the ALF and Allegro controllers) that do not need to see an index pulse at both heads so it is possible to find a drive that has does not have its index pins connected together for both heads. If you are using an SDS drive with two boards (the so-called "pancake" SDS drives) then make sure that the pin 8 of the first board (index) is connected to the pin 8 of the second board by checking this connection with a continuity meter.
  • If you are using the Allegro I board with a SDS drive then you only need to make sure that the INDEX jumper is in the SDS position.

825 Unknown auto-loader type

If you are using a CopyBus loader, try turning it off and waiting 5 seconds before turning it back on.

827 Cable Bad or Upside-down

  • Warning! If you have a Media Logic AccuCopy drive do not reverse the drive cables. This error can occur for a number of reasons, so it is imperative not to assume that drive cable is indeed upside down, since reversing the cables will DAMAGE your drive!
  • If you get this error message using a Multi-Disk II controller make sure that the controller type is set up correctly in the Controller List under Setup.
  • The 34 pin ribbon cable for the floppy drive is in question or else the drive select jumper is in the wrong position.
  • For the Y-E Data 2XSDS single cable drive the jumpers should be on DS0, DC, and M1 only, even though the drive is at position 1. All other drives should be jumpered to use DS1.
  • The ALF and Y-E Data SDS single cable interfaces only work with a straight cable.

829 SDS cable is bad or upside down

This error message can occur with SDS drives for the same reasons listed for error 827.

830 No SDS Controller Setup

  • DiskDupe cannot find the SDS controller listed in the Controller list. If you are not using an SDS drive then set the Drive Speed to 1X in the Drive List (highlight the drive of interest and choose Edit).
  • If you are using an SDS drive then the SDS controller should be the last controller in the list and it should have no interrupt (IRQ 0). Try choosing Auto-Set in the Controller List under Setup to see if DiskDupe can sense the controller.

831 SDS drive cables are reversed

  • This error message can occur on two cable SDS drives if the drive cables are reversed.
  • When you attach an SDS drive (or any drive) to the C2 connector on the Allegro I or II without telling the software to use the C2 connector this error message will occur.

833 Side 0 has side 1 data, bad cable or setup

  • This error message can occur if the drive has been setup as a 1x or 2x drive and it is really a SDS or 2xSDS drive.
  • This error message can occur if the drive cable is connected incorrectly or if the drive is jumpered incorrectly.

835 Controller not an Allegro

  • If you are using an Allegro controller and you get this message then there may be an address conflict (see error 802). Make sure the Allegro has been properly entered into the menus on the Controller List.
  • If you get this message using some other type of controller then enter in the controller type in the Controller List.

844 Drive alignment is bad

A drive alignment problem has been detected which may require servicing. A misaligned drive will produce disks that are perfectly readable by it, but may not be readable on a properly aligned drive. Misaligned drives are one of the major causes of creating "bad" disks, which is why we recommend checking the alignment frequently.

845 Controller doesn't support this data rate

  • An attempt was made to copy a disk to a drive that does not support that disks data rate. For example, trying to copy a 1.2MB 5.25" image to a 1.44MB 3.5" HD drive.
  • This can also occur if the drive you are using has been set up incorrectly. For example, if you are copying to a a regular 1.44MB drive and the drive speed has been set to the incorrect RPM (360, 600, etc.) you will also get this error. To check if this is the case, go into Setup|Drives and edit the drive to find out.

902 Out of RAM Memory

DiskDupe ran out of conventional memory. Try exiting out of DiskDupe and starting up again. If the computer has extended memory then make sure that a memory manager is loaded (like HIMEM.SYS or QEMM) so that XMS memory is available to DiskDupe.

903 EMS Error

This could indicate a problem with the actual memory chips in your computer.

904 XMS Error

This could indicate a problem with the actual memory chips in your computer.

905 User Interrupt Error

The user interrupt TSR reported an unknown error.

906 Buffer Memory has been Corrupted

Indicates that the image file has changed or that the memory in your computer might be bad. Try setting the "EMS/XMS Limit" in the Setup menu to "Not Used/Not Used" (Dos only). This message can also occur if the image file has been corrupted. Try remaking the image file. Also be sure to scan for viruses.

907 Code Memory has been Corrupted

Indicates that there might be a problem with a TSR writing over the DiskDupe code. Also try scanning for viruses.

909 DMA Setup Error

  • There has been a conflict between the DiskDupe software and the memory manager of the computer (usually when running under Windows). Try starting up DiskDupe using the /DMAWINOFF command line (Dos only) switch by typing DISKDUPE /DMAWINOFF from the Dos prompt (Dos only). This setting gets saved in the DISKDUPE.DAT file so it does not have to be reentered each time afterwards.
  • If /DMAWINOFF doesn't work try /VDMA=NONE or /VDMA=MEM (Dos only). The default is /VDMA=BUF, which normally works the best.
  • When running from Windows, try increasing the DMA buffer size by adding the line "DMABufferSize=100" under the [386Enh] section of the Windows SYSTEM.INI file.





Need Help?


Call us at (925) 689-1200 to speak with a technician.

Need Help?

DiskDupe is a legacy technology and no longer fully supported. We have provided We have provided some troubleshooting information help you address common issues. If you are unable to find the answer you are seeking, please contact us at (925) 689-1200 and we will do our best to help you.