 |
 |
Word docs -> unix executables?
|
 |
|
 |
|
Dedicated MacNNer
Join Date: Feb 2000
Location: New Haven, CT
Status:
Offline
|
|
A user moved files via the Finder from an external HD to his G5 running Panther. Most of the files came across without a hitch. However, some of the MS Word docs were changed to "unix executable files" or at least that's what the Panther Finder thinks they are. BBEdit can open them and the info is recovered 100% but I'm wondering what happened.
I Googled the phenomenon and discovered others have seen the same event. No clear thread as to cause . . . . .
any ideas???
-gfitzy

|
|
|
| |
|
|
|
 |
|
 |
|
Addicted to MacNN
Join Date: Oct 2001
Location: Yokohama, Japan
Status:
Offline
|
|
Add .doc to the end of the filenames and they will be recognized as Word documents again.
|
|
|
| |
|
|
|
 |
|
 |
|
Dedicated MacNNer
Join Date: Feb 2000
Location: New Haven, CT
Status:
Offline
|
|
actually, no, this doesn't work. At least not for these files. Also, doing Get Info and trying to make the Finder use Word doesn't help either. Word bails saying the file can't be opened.
-gfitzy
|
|
|
| |
|
|
|
 |
|
 |
|
Addicted to MacNN
Join Date: Aug 2004
Location: FFM
Status:
Offline
|
|
|
|
|
|
| |
|
|
|
 |
|
 |
|
Dedicated MacNNer
Join Date: Feb 2000
Location: New Haven, CT
Status:
Offline
|
|
no go, doing so changes the Finder info including the file's icon, but the changed doc crashes Word when it tries to open it. Also, doubling clicking the file itself launches BBEdit NOT Word even with the correct Word file type and creator info.
Please note, I've recovered the data, that's NOT the problem. I'm trying to figure out what happened on the user's machine do to this so I won't have to bail him out again.
-gfitzy
|
|
|
| |
|
|
|
 |
|
 |
|
Dedicated MacNNer
Join Date: Feb 2000
Location: New Haven, CT
Status:
Offline
|
|
cause found!!!
This is a recently detected Wintel MS Word worm/Trojan, http://securityresponse.symantec.com...xploit.37.html
On a Panther box with v10 of Norton Antivirus running the beastie is detected and quarantined, it is not repairable. In my case the user must have moved these files onto a Windows machine recently.
-gfitzy
|
|
|
| |
|
|
|
 |
 |
|
 |
|
|
|
|
|

|
|
 |
Forum Rules
|
 |
 |
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
|
HTML code is Off
|
|
|
|
|
|
 |
 |
 |
 |
|
 |
|