I had an SP go bad on our array and everything transferred
to the second SP except for one volume. I attached the
unknown volume to the good SP and found the volume in
Windows 2000 server again. I re-shared the volume out as a
windows and a Macintosh volume and found dates wrong and a
host of other resource fork related issues. How do you
repair the corruption from the windows side?

On 10/21/03 3:45 PM, "Bob" <(E-Mail Removed)> wrote:

> I had an SP go bad on our array and everything transferred
> to the second SP except for one volume. I attached the
> unknown volume to the good SP and found the volume in
> Windows 2000 server again. I re-shared the volume out as a
> windows and a Macintosh volume and found dates wrong and a
> host of other resource fork related issues. How do you
> repair the corruption from the windows side?

Hi Bob!

Windows doesn't recognize the resource forks although storing Mac files on
NTFS volumes will preserve them. You have minor tools on a Windows server to
edit file type and creator codes for Mac files, but that's about it. I
suspect your information is gone due to corruption.

I would suggest simply restoring from a backup to a known good Mac volume.

Hope this helps! bill
--
William M. Smith
(Microsoft Interop MVP)