I don't mean to suggest you're "going wrong", Jim. In fact, I don't think you've gone wrong in your case, nor did I say your complexity was unnecessary. What I said is that this is not generally necessary...
Most users don't need to take these steps (there's a broad mix of users in this forum).
(Yes, I was describing mounting the image and why it takes so long: it's being scanned for validity.)
As far as the destination not mounting: did you receive any errors? The remote volume is mounted by resolving an alias to the mount previously established: this should cause the system to mount the network volume (using authentication from the keychain).
__________________
--Dave Nanian
|