kurt_dup2

that's an interesting thought iboymatt - turning off the AFP I'll have to think how that will affect all our other applications. Still, I'd have thought that I should be able to get my mac VW users to log into the file server via SMB when they want to do some VW work. I thought I had tried this but it had not worked, but I'll try it again and report back. Thanks for the interest, Kurt

Trying to unify the Macs and PCs in our office using a Mac OsX server has worked quite well so far, except for a natty little problem in the use of xrefs on vectorworks. Basically we find that an xref target and master set up using the PC machines works but the xref is not correctly resolved when opened on a Mac machine, seemingly because the server name is different. To start at the beginning ... We have had no problems with permissions or sharing of files for other applications using this server now that it has been properly configured. We have VW 10.5.0 running on both Mac and PC machines. The PC machines have windows 2000, the Macs have Mac OsX 10.3.2. We have noticed that the first part of the path to the master file when viewed with a PC machine initially appears to be //{PC windows Name of server}/Folder 1/Folder 2/LibraryMaster.mcd but once an external link has been relinked, on opening with a Mac, it now appears to be //{IP address of server}/Folder 1/Folder 2/LibraryMaster.mcd (when viewed again on a PC.) If anyone can give some advice on which networking protocols we should use to provide maximum external filename compatibility would be most helpful. Many thanks Kurt Haselwimmer

Dear everyone, having just been introduced to this resource I'm going to try it out to see if I can get some answers to those VW curiosities that 1) curiously make me lie awake at night and 2) those that could seriously undermine a current project to turn our entire manufacturing operation over from 2D to 3D. Second things first - and I am cuious to figure out why we are generating such large file sizes when modelling some of our component parts that we have drilled tapped holes in. We are getting some file sizes as big as 30MB for a part with, oooh, 15 M3 tapped holes in and I'm concerned by some of the other posts that I've seen here that when we build our sub-assembly and then top-level assemblies from parts like this we are going to end up with massive files. Any comments regarding A) putting a tapped hole into a block of metal (we tried a number of different ways but found that subtracting a tapped shaft was the most reliable.) B) how to yield reasonable file sizes when a number of such holes in A) are put into a component C) guidelines on the size of files to expect when you xref a number of component files to build a sub-assembly build. Any thoughts from those more experienced would be most helpful. Cheers !!