I recently had to restore from a DDS3 backup after a striped disk failed and when I was done I noticed that a bunch of my mac programs were now just documents that I could not run.They were still the same size but I guess the attribute that told the system what specific type of file it was was somehow lost.Is there any way to reset that attribute or tell the system to run it anyways?

It was a bog standard NTFS backup done using the backup program that came with Windows 2000 server. I kinda blame myself actually for not stuffing the files. I find they preserve a lot better.The restore was done using the same program.

I use Win2k server "Services For Macintosh" to provide appleshare directories, these then use NTFS streams to store the finder and resource information. If it knows how to do NTFS streams it should have saved recovered the files correctly.

How are they mac files?Normally, if you are running a mac and you click on the program the installer for said program starts and the installer does the rest.If it does help, I do have ResEdit.Yes, I had the server running so that it handled mac files properly however I have gotten the odd hiccup once or twice where the mac suddenly forgot what several JPEG files were and I had to manually open them by first opening Picture Viewer before it remembered that they were images.

If you open them with ResEdit do they still have their resources? Perhaps they just lost their Creator and file type.

I don't remember how Services for Macintosh works. I know it uses ntfs streams for the resource fork, does it keep a database similar to the "Desktop" database somewhere? or another stream for the creator, type and other attributes?

If the file type was lost you could use my favorite, FileTyper to make a droppable type changer (DropType? can't remember what it calls them) to drag your apps onto and change the type back.

Yes, I use Appletalk to connect my macs to the server.Anyways, I tried opening it with ResEdit and it tells me it has no resource fork and opening it will create one.So it looks like at least the resource fork is all messed up.