Copy & md5 Shell Script

[lab601]

hi dustin, i dont see a link for the command line version. if i try to extract the script from the app version and run it it fails. is there a link to the command line version?

thanks, great script!

[Dustin Cross]

David,

In the first post is a link to SandustTools which is just a simple GUI that launches the command line app. Inside that little app you can find the script.

Or at the bottom of the first post you can download just the script. CopyScript_20110701.zip‎

Hope that helps.


Dusty

[lab601]

thanks, i missed that somehow...is it as up to date as the script that runs in the beta2 of the gui link that's posted?

[Dustin Cross]

David,

The version in the CopyVerify app is very different because it is written to use Pashua. Pashua is what is used for the GUI.

The version in SandustTools app is the most up-to-date. There might be a couple minor changes in the copyscript in SandustTools and the stand alone CopyScript.


Dusty

[Sean Tabler]

Dustin,

I have been looking for a fast/simple/reliable/free, copy and checksum app for a little while now. I am new to the idea of checksuming copies rather than just simple drag and drop for backing up media. This tool you (and everyone who has giving input and changes) have created is great! I can't wait to put it through the paces. Thanks for the app and all the knowledge I gained reading this thread.

-Sean

[Ian Pinder]

Hi there.
I don't know if you are really still working on this, but I wondered if I could ask something about it.

I have just been trying this out on some memory cards, to see how feasible it would be to use it at work, and while I imagine it works well with r3d files where each mag has its own unique name, I have noticed that if I drag and drop a volume such as EOS_DIGITAL, then it would overwrite anything previously copied from a card with the same name, without any warning. On the face of it, this seems a little too risky for certain types of media.

Is there a way for it to be adapted so that I can enter a new "reel" name for each transferred card, and possibly ask it to refuse to overwrite any existing transferred media.

Thanks so much for making this, and I hope I can get it to fit into the things I need to do at work.

Kind regards

- Ian

[david_winters]

I've been using this app for a while now and love the simplicity. For DSLR shoots I create a new destination folder for each card.

[Dustin Cross]

Ian,

I always rename the Mags like that before downloading. EOS_DIGITAL to EOS_DIGITAL_01


Dusty

[Ian Pinder]

Hi Dustin.
Thanks for the response. I have messed around with some scripting (a long time ago), and I was wondering how difficult it would be to implement an incremental folder creation function (just say from "0001" onwards, based on what is already in the destination folder) into what is already there? I obviously don't really expect you to do this, especially if it would not really be of any use to you for your own work.

I think perhaps the renaming of the cards before transfer might well be the best solution for this.

Could I also ask you one question about how the script/app handles existing data at the same path? If I had already transferred a volume "001" and then attempted the same volume name again with different media contained on it, what would the script be set to do? Would it merge the new media into the existing folder name? Would any files with the same filename be overwritten, ignored or warned against?

Sorry for all the questions. Thanks so much for your generosity with this. Is there any donation scheme set up for your work?

Kind regards,
- Ian

[Elliott Balsley]

I think numbering the volume name before transfer is a good idea. But Ian has an excellent point — if you accidentally name a volume a number that's already been used, and the script overwrites the previous one, that could be catastrophic. Hopefully it will add a unique name to the new one.