title
Products            Buy            Support Forum            Professional            About            Codec Central
 
Results 1 to 7 of 7

Thread: Reject - No CD after load Error

  1. #1

    Reject - No CD after load Error

    I'm getting a strange error all of a sudden for no apparent reason. After a CD is finished ripping, it gets ejected and accepted into the ripped pile. Then the autoloader tries to accept the CD a second time. Since the tray is empty, I'm getting a "Error on COM 1: No CD after load" message and the batch stops. What could be causing this issue? Thanks.

  2. #2
    Administrator
    Join Date
    Apr 2002
    Posts
    42,340

    Re: Reject - No CD after load Error

    Which autoloader do you have?

  3. #3

    Re: Reject - No CD after load Error

    It's a Mediatechnics with custom drivers from Brendon Hoar.

    Worked fine for 2 years. Now I started getting this error. Rebooted many times, reinstalled Batch Ripper software. No fix yet.

    Thank you.

  4. #4
    Administrator
    Join Date
    Apr 2002
    Posts
    42,340

    Re: Reject - No CD after load Error

    I do not know sorry.

  5. #5
    dBpoweramp Enthusiast
    Join Date
    Dec 2015
    Location
    Austin, TX, USA
    Posts
    50

    Re: Reject - No CD after load Error

    Can you be more specific as to which model autoloader?

  6. #6

    Re: Reject - No CD after load Error

    It is a Mediatechnics Fusion MX with Plextor PX-891SA drives. I've pretty much eliminated the possibility of it being a mechanical error...all commands working fine via the hyperterminal.

    There seems to be something off with the sequence of the software...as soon as a disc is successfully ripped and accepted, the software immediately reports "Reject: No CD after load." It is looking for a new disc before the loader has had a chance to load one...

    Very strange. Thanks for your help if you have any ideas about it!

  7. #7

    Re: Reject - No CD after load Error

    Well, after trying everything else, I finally went ahead and reinstalled windows completely. Problem solved. Strange that something got corrupted in the software that could not be solved by reinstalling...

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •