error-100

[lcwing]

I have been using 5.15 for a couple of years with few problems. All of a sudden I get error-100 (device rejected command) when I try to backup.

 

 

 

I bought and tried using a new CD and I get the same error message. I ran ASPICHK per an article in the knowledgebase; I have not added anything new onto my computer which might disrupt my CD drive (and yes, it's a supported drive-Sony CRX140E-DL).

 

 

 

I can also use other programs on the drive (DirectCD)--and no, this nor any other program is open when I am using Retrospect.

 

 

 

Retrospect recognizes the drive when I go to Configure/Devices, and will verify my backup set. I just can't backup anymore!!! Help!!#@$%

[AmyJ]

An error -100 is reported by the hardware itself and can be an indication of many things. I've listed below some things to check for when getting these kinds of errors. This is a relatively common error and I suspect that with a little troubleshooting you'll be able to isolate and fix the problem.

 

 

 

You can look into the following:

 

 

 

Have you tried other brands of discs? Often problems like this are due to drives that are picky with regard to brand of media you use.

 

 

 

Try *temporarily* uninstalling any other CD-writing utilities, in case extraneous drivers are conflicting with Retrospect. If you are using DirectCD, this can cause a conflict; I've included directions below on how to disable some functions of the software that may interfere with Retrospect.

 

 

 

Turn off the Auto Insert notification for Windows. This feature makes the operating system automatically mount a CD on the desktop when you insert it, but can interfere with Retrospect. To disable it, right-click on your CD drive in the device manager.

 

 

 

Is this Windows NT or 2000? If so, enable NT SCSI Passthrough to bypass ASPI: From the Retrospect Directory hit Ctrl-Alt-P-P. Under "Execution," check "Enable NT SCSI Passthrough." Click OK. Quit and relaunch.

 

 

 

If you still don't have any luck, I'd recommend the following hardware troubleshooting steps. Unfortunately you haven't said whether your device is SCSI, ATAPI or Firewire, so I'll send troubleshooting instructions for the three possibilities:

 

 

 

Try straightening out the internal ribbon cabling.

 

 

 

Try switching master and slave settings.

 

 

 

Try new internal cabling.

 

 

 

Try updating the firmware on the device if possible (see the drive manufacturer's website).

 

 

 

Are the drivers for the IDE controller current? Try updating them with an approved update from your PC vendor.

 

 

 

Finally, try bringing this drive to another PC and trying the backup. If it works here, you could be having a problem with either the ATAPI bus on the original machine or with the PC itself.