Closed maxz closed 8 months ago
You've ran it as redumper dump cd ...
both "dump" and "cd" are commands. "dump" means just dump cd (but don't split to multitrack) and "cd" command is actually a meta command that executes "dump" "protection" "refine" "split" "info"
So what was executed in the end was:
"dump" "dump" "protection" "refine" "split" "info"
Second dump from here will fail as previous dump has already created files based on a timestamp which remains the same throughout the execution.
You probably want just to dump a cd so for that you either execute:
redumper cd ...
or just
redumper ...
as the default mode is cd.
Ah. I've run successful dumps before. But I began automating my redumper use and wanted to specify the operation explicitly as far as it makes sense. I though CD itself was on another level as dump.
Thanks for the clarification on the commands.
I see, if you're building something more advanced, you can use all the underlying commands directly. Just want to mention that depending on a disc type, the command list will be different, example: https://github.com/superg/redumper/blob/main/redumper.ixx#L178
Redumper complains about an already existing dump when specifying the
dump
argument although there were no files at all before starting redumper.With
--overwrite
it obviously works. But I would expect it to work without overwrite if no files with conflicting names exist apart from anything that redumper itself creates.Log without explicit name or path:
ls .
after the error:Log with name and path:
ls BUG_IMAGE_PATH/
after the error: