[Robo]

At work we are trying out a deployment system using a SuperDuper-created compressed .dmg of a system located on a read-only AFP network share. Unfortunately, SuperDuper fails when trying to use that .dmg as a source to clone to a local drive. If we mount the .dmg in the Finder, the resulting volume can be used as a source, but this is an extra step and results in a slower cloning process. If the network share is mounted as read/write, SuperDuper handles the .dmg clone just fine, but we want it to be read-only.

Any known reason for this? Is there any way to make this work without allowing write access to the drive? The network share is on OS X server so we have full control over the permissions and ACLs on the share, if there is a special ACL setting or something that can help..

Thanks,

Robin