Wish the freaking thing worked... - rmark

I am maintaining an image database with about 30,000 JPG files on both Mac and PC without any insurmountable problems. Sure, there is room for improvement, but it certainly meets most of my needs. I too wish that Extensis were more responsive. But then I wish that Apple and Microsoft were more responsive.

Reply to This

Tuesday, December 23 2003 @ 06:59 PM PST

Wish the freaking thing worked... - ewelch

Actually, there is an easy fix for the path problem. Extensis' solution is to turn off SMB and use Windows Mac services with a Windows Server. Not a reasonable requirment by a long shot. Mac a Mac ONLY see the Windows servers and no other shares on the network? What were they thinking!

But I have a script that fixes it. If you know Applescript, the solution is right there on your computer. Pull down the script menu. The only script in there will fix the paths, you just have to give it some input. I rewrote the script to do most of it automatically. I just have to choose whether to fix the paths in the current gallery or in the whole catalog.

Some things to know.

On PCs it writes the server name into the path. Mac's using OS X don't, they put the share name at the front of the path. For example, at work, our server's name is CRS-DEV. The Share name is WORK. So the path is CRS-DEV:Work:Image:Diamonds for example. The Macs write Work:Images:Diamonds. So I have to put the CRS-DEV at the front using the script. And in our environment, don't know if this is the case everwhere, but I suspect that it is, you have to put two colons in front of the server name. I guess that's how it identifies it as a server? Anyway, the script has to write the path like this:

::CRS-DEV:Work:Images...

Write the script so it puts the minimal required change on the front of the path. For example:

The default script asks you what the old one is. In my case, I would type:

Work:

Then it asks what to replace it with:

::CRS-DEV:Work:

is what you would replace it with.

Hope that helps.

Email me at work and I can send you the script. (I'll be back Jan 2, 2004.)

Reply to This

Wednesday, December 24 2003 @ 07:51 AM PST