RJay,

I do the same thing, where I have scripts to mount the network volumes 
rather than use alias'.

I find that sometimes the drive is not mounted in the Finder, but it is 
under /Volumes. If you restart the Finder, then the drive then shows 
up. If the drive is not there and you run the script again, then the 
drive still does not show up, but under /Volumes you have {drive}_1. 
Restart the Finder and one shows up, but not the other.

I think some of the issue is within the Finder as well. If it is 
restarted every couple of days on machines where a user is always 
logged on, seem to help a great deal if there are a lot of drives 
mounted and unmounted each day.

Lloyd

On Apr 10, 2007, at 10:00 PM, MACSCRPT automatic digest system wrote:
> Subject: problems with volume mounting
>
>
> I've written some simple little scripts for our Mac workstations to 
> mount volumes from our Xserve i.e. --
>
> mount volume "afp://XX.X.XX.XXX/volumeName" as user name "username" 
> with password "" (x's represent IP address)
>
> I've also used --
>
> mount volume "afp://username:[log in to unmask]"
>
> I've also run these inside a Finder "tell", but apparently isn't 
> necessary and doesn't make a difference in the following behavior.
>
> These are put in the user's script folder in their Library and run 
> from the Scripts menu. All has worked fine until upgrading to 10.4 
> recently. Now, most of the time we have to run the script twice before 
> it mounts the volume in question. The first time it's run, the machine 
> acts like it's running the script but the volume doesn't mount and it 
> generates no error messages. Running it again mounts the volume.
>
> But this doesn't happen every time you run one of these. Sometimes it 
> mounts the volume the first time you run the script. Also, it always 
> works with the first volume you mount... in other words, if you have 
> no server volumes mounted at all, the first script you run mounts that 
> volume fine, but any subsequent scripts you run to mount other volumes 
> usually fail on the first run.
>
> Does anyone have any ideas what may be causing this? All this is 
> happening on OS X 10.4.8 using G4s and G5s.
>
> Thanks for any suggestions,
>
> RJay