Corrupt Resource Fork Issues

[J Lyle Petro]

Hi,
I work in the prepress department with about 25 Macintosh computers
varying from Beige G3's running OS 8.6 to Mirror Door G4's running OS
X Jaguar. We are running into real scary problems when it comes to
corrupted files on our Win2K server. We recently switched to Win2K on
our server from Novell 4.11. The problems we experience all relate to
saving over existing files on the server. In Photoshop, when
re-saving a file, occasionally the resource fork becomes corrupted,
causing a lock-up or freeze on a Mac which tries to place the graphic
file using either Quark Xpress or Multi-Ad Creator. The fix is
simple, open the file up in Photoshop, then re-save the graphic to a
local drive, then copy the newly saved graphic via the Finder over top
of the one on the network. Recently this corruption has started to
show up in Quark Xpress and Multi-Ad files on the network. The
symptoms of this problem is that the file cannot be seen from the Mac
side (but can from a PC). When a user on the Mac side tries to
re-create the ad (which has to be done over) and tries to use the
original file name, he/she is told that a file with that name already
exists. I suspect that this once again relates to corruption of
resource forks on re-saving of files. Has anyone else experienced
this prolbem and if so, do they have any suggestions for possible
solutions. Thanks for you time.

Lyle Petro
Application Specialist/Scanner
Saskatoon StarPhoenix
(e-mail address removed)

 

[William M. Smith]

Hi,
I work in the prepress department with about 25 Macintosh computers
varying from Beige G3's running OS 8.6 to Mirror Door G4's running OS
X Jaguar. We are running into real scary problems when it comes to
corrupted files on our Win2K server. We recently switched to Win2K on
our server from Novell 4.11. The problems we experience all relate to
saving over existing files on the server. In Photoshop, when
re-saving a file, occasionally the resource fork becomes corrupted,
causing a lock-up or freeze on a Mac which tries to place the graphic
file using either Quark Xpress or Multi-Ad Creator. The fix is
simple, open the file up in Photoshop, then re-save the graphic to a
local drive, then copy the newly saved graphic via the Finder over top
of the one on the network. Recently this corruption has started to
show up in Quark Xpress and Multi-Ad files on the network. The
symptoms of this problem is that the file cannot be seen from the Mac
side (but can from a PC). When a user on the Mac side tries to
re-create the ad (which has to be done over) and tries to use the
original file name, he/she is told that a file with that name already
exists. I suspect that this once again relates to corruption of
resource forks on re-saving of files. Has anyone else experienced
this prolbem and if so, do they have any suggestions for possible
solutions. Thanks for you time.

Your Mac volume on your server may be corrupt. Have you tried deleting and
then recreating the Mac volume? Deleting a Mac volume is the same as
removing a Windows share. You're not deleting data, just the volume/share.

Also, what service pack level are you running? The latest is sp4.

Hope this helps! bill

 

[Pete Rentmeester]

Your Mac volume on your server may be corrupt. Have you tried deleting and
then recreating the Mac volume? Deleting a Mac volume is the same as
removing a Windows share. You're not deleting data, just the volume/share.

Also, what service pack level are you running? The latest is sp4.

Hope this helps! bill

We are having this same file. The server share seems to be fine. The work
around we found was the same as your where we saved to the desktop and
copied back to the server. I recently found a fix from Bare Bones Software.
"Super Get Info". You can get this as a demo to test and it is a $20
purchase. What seems to be happening (at least on our end) was a resource
fork corruption. Expecially on the first time the file was opened or save on
the new server. After the file was saved correctly on the new server the
problem seemed to disappear. When the file corrupted Super Get Info (SGI)
allows you to create a resource fork profile. Then it is a drag and drop
conversion to the correct file time (Quark, Freehand, etc) and everybody is
happy.
I believe (Now this is just a guess) that the Novell server compression is
the instigator of this problem. If you don't transfer your data via a Mac
(Novell to Mac to W2K) ver (Novell to W2k) the Mac files have resource fork
problems.

My 2 cents
Pete