Mac OSX Leopard and server connections

Devin Asay devin_asay at
Fri Feb 5 16:11:45 CST 2010

On Feb 5, 2010, at 2:19 PM, Dan Soneson wrote:

> Hi everyone,
> I have a rather odd problem using rev applications on Mac OSX  
> Leopard, connecting to a server on my network. I connect to a server  
> with an Applescript command: do theScript as Applescript. I can do  
> this just fine. But if I unmount the server  by dragging it's icon  
> to the trash, then remount from within Rev eventually Rev reads the  
> name of the server differently. Let's say the name of the server is  
> "George". I can connect to "George" several times, but eventually  
> Rev or Leopard appends a digit to the name of the mounted volume.
> Originally, the path to file "Textfile.txt" on the server named  
> "George" will be "/Volumes/George/Textfile.txt" However, after a few  
> connections (don't know how many or exactly when this happens), the  
> path to the file becomes "/Volumes/George-1/Textfile.txt". Oddly  
> enough, the icon on the desktop for the volume is still "George".  
> However, any reference to the file "Textfile.txt" from within Rev  
> now will fail, since Rev reads the connection as "/Volumes/George-1/ 
> Textfile.txt" but is still looking for "/Volumes/George/ 
> Textfile.txt"!  This gets somewhat frustrating, since I never know  
> when it will happen, and once it does, I can no longer transfer  
> files back and forth between the server and the computer.
> Has anyone seen this behavior? Do you have a workaround or a  
> suggestion to get around this problem? I never had the problem  
> working with pre-Leopard operating systems on the Mac, but it is now  
> cropping up since all our computers in a lab are now running Leopard.
> Another issue may be that the physical server (now running OSX Snow  
> Leopard) has several share points, each of which may be mounted as  
> individual volumes, one of which is the aforementioned "George".  
> Mounting and unmounting several of these share points may bring  
> about the re-numbering issue. Rebooting the individual computer  
> doesn't seem to help either.
> Thanks for any suggestions.


Maybe not a complete answer, but a clue: When OS X mounts volumes with  
the same name the way it keeps them separate in the Volumes list is by  
appending a number to the duplicate name. I have sometimes seen cases  
where the OS somehow doesn't get the message that a volume was  
ejected, and if it is remounted the volume name appears with a number  

Open the terminal and type 'ls /Volumes' to see a list of all mounted  

Maybe what you need to do is check for the existence of the volume  
before you try to mount it?



Devin Asay
Humanities Technology and Research Support Center
Brigham Young University

More information about the use-livecode mailing list