Finder reliability copy/move large files
Finder reliability copy/move large files
- Subject: Finder reliability copy/move large files
- From: "Scott Sandeman-Allen (RSCorp)" <email@hidden>
- Date: Sat, 18 Sep 2004 12:40:20 -0600
Hello everyone,
I don't use AppleScript much but recently needed to re-organize about 80 gb of digital photos for two
Folk Music Festivals (Edmonton & Calgary, Alberta). Some fairly simple tasks i.e. rename files, group
them by photographer etc. I later found an Exif OSAX that allowed me to sort out some duplicate
named, but different files for them. Most worked nicely because the images were processed in small
batches.
I had no problem getting a sript to work, or rather a series of srcipts. When it came time to burn
CDs and DVDs (lots of them!), it seemed apropriate to extend the suite to group all images into
burnable sized bytes. I wrote one variation to group by CD size, then extended it to group the CDs
into DVD sized blocks. Nice, simple... till I tried to run them on the full lot.
I tried a couple of differnet strategies. In all of them, the finder hangs after moving between 4,000
and 8,000 pictures (1-3.5mb each). For safety of originals, I tried copying first, then I simply
tried moving the files (after making a copy). I tried setting a 'timeout' value, I've tried pausing
with a loop construct. I even tried 'try' wrapped around a few of these constructs.
I also tried building a list of images to move, then moving them in batches. I've also simply scanned
for source images, then moved each one, one at a time. In all cases, I have asked Finder to return
frist a list of files within the sub-folder structure, then the file size and finally to move the
file. Each of these is in
In all cases, Finder simply hangs on me at some point (sometimes I have to restart the machine too).
I'm running this on a G5 with 512mb/160gb and 10.3.5, so the hardware should not be a problem. I'm
also _not_ doing anything else on the machine. Watching the Activity Monitor, half of the memory is
available, the disk is averaging 500kb/s but ranging from 250-900 kb/s.
Any thoughts on how I can increase the reliability of using the finder for this? Or should I just
scrap it and write it in something else?
Thanks,
Scott
PS. I guess I could do something with the command line and bypass finder all together for the move,
never tried that. Hmmmm.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Applescript-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden