Another issue I've come across - Not sure why this didn't crop up before, but for some reason, starting yesterday, I'm getting disk not inserted errors now on occasion when attempting to rip a different disk from the command line.
In this screenshot you can see that my drive monitor queued the rip of drive G, but DVDFab throws an error for there being no disk in drive E (the drive that just finished and ejected prior to this run of DVDFab)
This is the specific command line that was called to initiate DVDFab:
As previously stated, I do have disk checking disabled for all drives, but I do know that DVDFab checks all drives on startup anyway. Is there a way to stop it from checking drives on startup, or at the very least to suppress this error message for a drive not related to what is being ripped?
I've also attached the log file for this run. I was away and came back to the error ~84 minutes after it first popped up which is why the log jumps from 0m 00.98s to 84m 41.86s because the entire process halts until continue is pressed. (Note that this disk failed to rip because it is damaged, but that is not relevant to the issue at hand)
In this screenshot you can see that my drive monitor queued the rip of drive G, but DVDFab throws an error for there being no disk in drive E (the drive that just finished and ejected prior to this run of DVDFab)
This is the specific command line that was called to initiate DVDFab:
Code:
"C:\Program Files\DVDFab 10\DVDFab.exe" /MODE "DVDMP4" /PROFILE "mkv.h265.10bit.Sub" /SRC "G:" /DEST "C:\users\Johnathon\Desktop\Ripped\In Progress\The Princess Diaries.mkv" /CLOSE
I've also attached the log file for this run. I was away and came back to the error ~84 minutes after it first popped up which is why the log jumps from 0m 00.98s to 84m 41.86s because the entire process halts until continue is pressed. (Note that this disk failed to rip because it is damaged, but that is not relevant to the issue at hand)
Comment