Resource for corrupting a file?

[Jimbo2112]

System: NT4 server SP6, Mac OSX

Hi All,

I have a situation where every now and again a file that originates from the Mac on OSX which is moved to my NT4 server becomes corrupted. It has been an image (tiff or EPS) and this week it was a plain text file. It was fine one day and corrupt the next. When I say corrupt, I mean: will not open, copy, move or delete.

Possible issues:
*I tend to delete resource forks from the Mac on the PC.
*We have a nightly backup of files (very unlikely to be an issue)

The only way to fix the issue is to reboot the NT4 server which is not always an option.

Has anyone else seen this happen? Any suggestions?

Regards

Jimbo

 

[Zelandakh]

Why do you delete the resource forks?

 

[Jimbo2112]

Hi,

The resource fork files show as `._` type files in the PC environment. This can confuse people that are not PC literate where I work.

Is there an issue with deleting resource forks? Maybe I can make them invisible on the PC somehow?

Cheers

Jimbo

 

[jmgalvin]

OSX documents do not rely on resource forks like OS9 and erleir versions. They rely on extensions, like Windows and most formats like .jpg. .eps. .doc.etc are fully interchangeable between platforms.

I assume that your NT platform allows you to dtrip the forks for OS9 and earlier Mac documents, but you probably do not have to do this with OSX.

One thing to be aware of. Office X gives you the option of appending the extension. It's a check box on the save window. Once you check it, Office retains the setting on subsequent Save windows. You should make sure that users have that checked.

All other OSX apps that I've seem append the extension. If you take that Extension off, in a Mac enviroment, the machine will usually give you an error message of not understanding the application to open in.

Using OSX 10.3.8 on a G4