Originally Posted by
sredmyer
Those are GREAT thoughts Brendan. So I guess I am right in assuming there is no way at this time for the CLIs to tell cdgrab.exe to skip certain drives?
The CLIs (if you mean the load.exe, unload.exe, etc.) do not interact with cdgrabe.exe at all. The batch ripper core calls all of those independently.
Originally Posted by
sredmyer
As a posible work around, what would happen if the load.exe cli simply never returned from a request to load a particular drive? Would the entire system hang or would that instance of cdgrab.exe just hang waiting? Is there a timeout?
If the configuration file (DefaultCmdLine.txt) does not include a watchdog line as defined in the documentation taken from this post ( http://forum.dbpoweramp.com/showpost...85&postcount=8 ):
Code:
--watchdog="120000" (for batch ripper: will end task the loader command if not finished after X milisecond time)
By avoiding use of the --watchdog "special" command line option (it is special in that it really isn't sent on to the load.exe, but is a flag for the batch ripper.exe to change its behavior), my own drivers are able to hold a drive hostage (e.g. if I'm using multiple one-drive robots at a time - I put up a dialog when the input bin(s) become empty and ask the operator to fill them before hitting OK) while continuing to allow the other drives to be served by their robots independently.
So yeah, just preventing the load from returning takes the drive out of commission. But of course, that means the file can only be taken out of commission during the load process, which might address your main concern.
Originally Posted by
sredmyer
I really hope I can work this out. With four of these changers (8 drives) going at once I get some really impressive discs per hour rates.
Tell me about it.
-brendan