error -100 (device rejected command)

[rhall]

I recently purchased Retrospect Professional 6.0 but, when I tried to use it, it ejected my CD with an error of "error -100 (device rejected command)". I called Dantz technical support and they told me I'm not entitled to support without specifically purchasing it. Argh! My immediate reaction is to demand a refund, but I thought I'd try posting here first.

 

 

 

My CDRW is listed on the site as being qualified. It's a brand new Gateway computer with two CD's installed:

 

 

 

a.) DVD/CD-ROM: HITACHI DVD-ROM GD-8000

 

b.) CDRW: LITE-ON LTR-24102B

 

 

 

The CRRW (Lite-on) is the drive in question. Here are the driver specs:

 

 

 

Driver Provider: Microsoft

 

Driver Date: 7/1/2001

 

Driver Version: 5.1.2535.0

 

Digital Signer: Microsoft Windows XP Publisher

 

 

 

I'm using Windows XP

 

 

 

Retrospect sees my drive and all goes well when I try to do a backup until (I suppose) it's time to write to the disk. At that time, an error message pops up, the cd is ejected, and all comes to a halt.

 

 

 

Here is the contents of a Retrospect log entry:

 

 

 

---begin paste---

 

 

 

+ Retrospect version 6.0.206

 

Launched at 10/9/2002 3:52 PM

 

 

 

+ Executing Immediate Backup at 10/9/2002 3:59 PM

 

To Backup Set Backup Set A...

 

 

 

- 10/9/2002 3:59:56 PM: Copying Drive C (C:)

 

Trouble writing: "1-Backup Set A" (262144), error -100 (device rejected command)

 

Trouble writing: "1-Backup Set A" (262144), error -100 (device rejected command)

 

10/9/2002 4:05:02 PM: Execution stopped by operator

 

Remaining: 113965 files, 8.0 GB

 

Completed: 0 files, zero KB

 

Performance: 0.0 MB/minute

 

Duration: 00:05:06 (00:03:42 idle/loading/preparing)

 

 

 

Quit at 10/9/2002 4:05 PM

 

 

 

--end paste---

 

 

 

Any thoughts?

 

 

 

I'm figuring I'll give this a day or two to get worked out. If it works, I might remain a customer.

 

 

 

Thanks,

 

 

 

Ron

[AmyJ]

Make sure your firmware is up to date through the vendor. While in Retrospect, go to Configure > Devices > Environment. The 'Version' column will list your current firmware version. Retrospect requires a minimum version: 5S54

 

 

 

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.

 

 

 

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. We recommend using brand name media, such as TDK, Sony or Verbatim. However, you should check the vendor site for recommended media compatibility with the drive.

 

 

 

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.

 

 

 

Was ASPI installed correctly? Run ASPICHK (in the Retrospect Program Files folder) to make sure ASPI is "green" and all components are at version 4.60. If not, try a reinstall (ASPIINST.exe). If you still have problems, consult the Retrospect User's Guide or Adaptec's website.

 

 

 

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're still having problems after following all of the above steps, do the following: quit all other applications and terminate any nonessential tasks (Ctrl-Alt-Del) and turn off software compression (under the Options button).

 

 

 

If you still don't have any luck, I'd recommend the following hardware troubleshooting steps.

 

 

 

Try straightening out the internal ribbon cabling.

 

 

 

Try switching master and slave settings.

 

 

 

Try new internal cabling.

 

 

 

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.