File type changed to Unix Executable File

Hello:
I restored a corrupt Word file from a back-up drive (files are backed up using a special rsync that splits data and metadata forks. I did not assemble the two forks before copying the file back to the production volume) into a production folder in a local machine. Now when I browse the volume from my networked computer all Word files without extensions show up as Unix Executable Files. I've cleared the Launch services in the networked machine with no results. If I browse from other networked computers file types are set correctly. The problem seems to be with this specific networked machine. What an I do to restore file types as they should be? Please, note the problem seems to be with the client machine not the file server.

Thanks, Kappy. I've tried that but I get an error message saying "An error ocurred while changing...because not enough information is available." Could that mean that the action cannot be done because these files don't have extensions? When I go ahead and select to use Word to always open the file it only takes effect on that file. But the file remains a Unix Executable file.
Could anyone provide any further help with this issue?
Message was edited by: Karkula

Similar Messages

Files changing to unix executable files in leopard!

I'm having files show up as UNIX EXECUTABLE FILES in Leopard. these are Quark Xpress files and a few tiff files.
These were backup files sent from a client on a Mac, there were compressed using Zip software. Also the same files that were not compressed are DOCUMENT files.
What is happening that Leopard can not recognize these files?
I tried removing "com.apple.LaunchServices" files

I found that a number of Windows files copied across to an external HFS+ hard disk from a Windows PC using MacDrive showed as Unix executables.
It turned out that they files had Execute permissions set for all users.
You can change the "Execute" setting using chmod in the terminal, but a simpler solution is to install FileUtilsCM, a free context menu control available from http://www.abracode.com/free/cmworkshop/file_utils.html
It offers a variety of high level controls, including remove file type and creator; remove resource fork; clear "execute" Unix attribute.
I found this fixed the problem for my files. The "clear execute" control fixed the file type, and the "remove type & creator" command converted the type back to Plain text from Document.
I don't know if it will work for your problem, but could be worth a try. Works in Leopard 10.5.1 for me.
Slightly more control is available from Super Get Info from Barebones http://www.barebones.com/products/super/index.shtml
That's not free, however, but it does allow you to set the file type and creator.
DN

HELP! Indesign changes to Unix executable file

I have a Mac Xeon Dual core quad pro running an older Mac OSX and have recently bought a Macbook running OS 10.6.
On my old mac I use Indesign / Illustrator / Photoshop CS3 (no money to upgrade yet) and all works fine.
This week I transferred some Indesign files to my laptop to work in another office. The files show up as Unix executable files. They have the correct tags on the end of filenames and work fine on the old mac. Indesign and Illustrator have also been crashing on startup and I have had to dump out prefs twice now.
Illustrator files show up as Unix executable file as well and all have a grey icon.
I migrated everything over from the old mac to the laptop.
It is driving me mad as I have to trust that I can work on this out of the office.
If I upgrade to a newer version of the programmes will it solve the problem?
Any help gratefully received please!
PS I am a designer, so please use simple language - I do not have a lot of techie knowledge about macs
Thanks!

Thanks, Kappy. I've tried that but I get an error message saying "An error ocurred while changing...because not enough information is available." Could that mean that the action cannot be done because these files don't have extensions? When I go ahead and select to use Word to always open the file it only takes effect on that file. But the file remains a Unix Executable file.
Could anyone provide any further help with this issue?
Message was edited by: Karkula

HT2128 How do I recover old files that are labeled "Unix Executable File?"

Some files that were transfered from and older mac are labeled "Unix Executable File." How do I resd these files?

There is a terminal command called file which will give you a hint of what the file is.
/Appliactions/Utilities/Terminal
me ~$ file pki
pki: directory
me ~$ file pulse-cookie
pulse-cookie: data
type file space drag & drop the file onto the terminal, press return.
Robert

Can't open recovered files, which are now Unix Executable Files

My external hard drive, where I kept my Final Cut Pro documents, recently died. I hired someone to recover the data. Now, when I try to open them in FCP 6, however, I get the message "File Error: Wrong Type". It says they are "Unix Executable Files". Looking back in this forum, none of the previous solutions have worked for me--like adding .mov to the file extensions, for example.

ah, the subtle difference between a movie or media file and a project file.
Thanks for posting your solution, hardly anyone ever does that around here. And congrats on the rescue! We rarely hear of a successful data recovery on media files but this was a data drive, yes? You could help future users who suffer catastrophic drive failures by posting your contractor and the cost if you want to share that information.
bogiesan

Unix executable file- in backup email files

Hello,
I've searched the discussions and found a few posts that resemble my question but nothing exactly/ nothing suggested has worked so far.
I have entire email files backed up to a LaCie drive- 2 actually. All of the email backup icons have been changed to "Unix executable file"- the icon is a grey box with "exec" on it.
The promising side is that the files are still large- 301 mgs, etc- so I would think there is still information in the file.
I've tried going into "Info" and changing "open with" to entourage or thunderbird. Or even Excel to see if I could get a tab delimited file and convert. Nothing has worked so far.
I've seen this before with other types of backup files as well. I haven't changed operating systems, have only been working on Macs, this has happened both on a wireless ethernet disk and a firewire drive.
Any suggestions? Thanks!
jz

Hi,
Never fear! Your original MacOS disks should include the developer tools. They call it xcode these days. By default it should install extra command line utilities in /Developer/Tools. So really the command should look like:
/Developer/Tools/SetFile -t 'TEXT' -c 'CSOm' your_mbox
You can add /Developer/Tools to your $PATH variable to avoid the extra typing. But you can do that later. Just replace your_mbox with the path to one of your Eudora mail boxes that you've copied back to your harddrive.
Cole

Opening a Archival UNIX Executable file

I am currently using Maverick 10.9.2 . I am trying to open an archive file amd folder. The problem is that when I download the file, it appears as unix executable file and it cannot be opened. I have read in past posts that if the file does not have extension, it may become a unix executable file. I have changed them to .DOC, but no luck. Also when I tried to download the file later, the format changed to documents, but still could not be opened. Is there a problem because it was archived? If you have insight this problem as well, I would appreciate if you could let me know. Thanks in advance.

I'm assumimg that the file is either a zip, tar, gnuzip, or bzip2 archive. Remove the file extention from the file and move it to your desktop. From the Finder.app > Go menu > select "Go to Folder...", in the text box type- /System/Library/CoreServices . Drag the Archive Utility.app on to the dock. The Archive Utility.app icon will now appear in the dock. Drag the archive file onto the Archive Utility.app icon and the archive should be uncompressed and appear on your desktop.

AppleWorks 6.0 Files Listed As Unix Executable Files. Unable To Open.

A client of mine backed up a number of AppleWorks 5 & 6 files last week on a PowerMac w/ OS X 10.3. I reformatted the HD, upgraded the OS to 10.4 and attempted to reinstall AppleWorks 6.0. It would not allow installation. So, I installed OS 9 Classic. Still would not allow me to install AppleWorks. Then, I installed iWork '08, having read that it would open AppleWorks files. iWork would only open a hand full of the files. The remaining 90% of the files are listed as "Unix Executable" files.
Have the files been corrupted in the move?
Any ideas on how to open/recover these files?
Thanks,
stc

If one device used during the process was not an HFS one, the AppleWorks documents may have lost their resourceFork.
Are you sure that the files are named with the name extension ".cwk" which is quite required under Mac OS X?
Then, I installed iWork '08, having read that it would open AppleWorks files.
This is right and wrong.
Iwork components are able to work this way:
Pages may open AppleWorks 6 WP document, not the AW5 ones
Numbers may open AppleWorks 6 SS document, not the AW5 ones
Keynote may open AppleWorks 6 Presentation document, not the AW5 ones
Nothing may open the DB, Paint and Draw AW documents.
There is no reason that you can't install AppleWorks on a machine running 10.4.
I installed AppleWorks 6.0.4 last week on a machine running 10.4.11.
So, at this time it seems that the main problem is to understand why you are unable to reinstall AppleWorks 6.
If you wish to know if the documents are in good health, you may attach one to a mail and send it to my mailbox.
Click my blueName to get my address.
Yvan KOENIG (from FRANCE lundi 25 août 2008 19:12:51)

Tugsten E2 /unix executable file

My laptop is a MAC power book G/O.S.10.4.11.
My external hard drive crashed. I recovered the info.The back up i had from last version of my desktop palm shows only the file mame i gave it -NON RECOGNIZABLE ICON. I'm not able to open it, when i drag the file into the palmdesktop icon it doesnt read it. On the File info says:
KIND:unix executable file
I opened the file on microsoft word-officce 2004 and just appear like programming caracters.
I think I just need to add the file extesion in order the palmdesktop software read the file.
Do you know what the extension is?, or How to make readable opening it with the palm desktop sofware?
Post relates to: Tungsten E2

Hey!, I've re-installed palm desktop program and it didn't read the file.
In Mac, when a file is not readable, show's you a blank icon or in this case is showing a grey icon with green letters saying EXEC. That's why I think what I need is to add the correct extension to the file in order to be recognized by palm desktop folder.
I'll appreciate your help.
Thank you.

CDF type to Unix Executable File

When downloading a Comma Delimited File Database, Safari saves the download as a "Unix Executable File" and my database (Filemaker) will not recognize the file type. What is the problem (or solution)? Thanks in advance

There is no extension. What appears is the file name with an unusual (for Mac) icon. This was not the solution, but thank you. I have subsequently tried the download on two other machines with the same result. The question remains why does Safari (or Mac OSX) change a comma delimited file to an Unix executable file. I did discover that by opening the file in textedit and saving it, Filemaker will then work the file. That is only a workaround, not a solution.

Photoshop .psd files converted to Unix Executable files

I'm an illustrator and I store my art on CDs and DVDs. After a period of time my files are converted from Photoshop .psd files to Unix Executable files and I can't open them. What can I do to get my work back??? -and keep this from happening in the future. Why does it do this????
Thanks for any help.

The file sizes range from 22.2 MB to 67.9 MB.
Size isn't the issue then. Linc was asking that question because we see that with other file types. Older fonts in particular, which have all of their data in the resource fork. If that gets stripped, you end up with a zero byte file.
Does that mean I'll have to go through the Adobe authorization process for Photoshop again?
If the version of Photoshop you're currently using is already activated, then no. Either way, it has nothing to do with .psd files showing as UNIX executables.
In Windows, any file that doesn't have an association to a program is displayed as a white, dog-eared piece of paper with the Windows logo in the middle. That's Windows' way of saying, "I have no idea what this is." In OS X, (except for those files which actually are UNIX executables), displaying them as such is OS X's way of saying the same thing.
I thought I was home free when the icon changed to a thumbnail picture of the illustration, but PS refuses to open it saying it is not a Photoshop file. ???
Now that is weird. As of Snow Leopard, Apple put the old Type and Creator codes to rest. It will read them as a last resort to try and identify an older file, but none of Apple's applications add them to any file they save. For better compatibility with Windows, and OS X's own underlying UNIX core, file extensions have taken their place. So adding a .psd extension should have worked. Without playing with one of your files, I couldn't tell you why Photoshop declared it wasn't a valid .psd image.
On a side note, Apple added Uniform Type Identifiers to OS X to keep things separate. A big problem in Windows is that multiple apps may use the same file extension. EPS is a big one in printing. So you have Photoshop, Illustrator, Freehand, Quark and others all using .eps for Encapsulated PostScript files. However, Windows can only associate one application to any given extension. So if Illustrator happens to be the one tagged to .eps files, it will try to open any file ending in .eps, no matter what program actually created it. OS X keeps them separate with Uniform Type Identifiers. So even though multiple files may have .eps file extensions, the extra metadata keeps track of what program it actually belongs to.
This is what is part of the LaunchServices database, and was why it was my first suggestion. If that database is wonky, you'll see weird things like this. Have you tried clearing it yet?
The files are fine when newly burned to CD. It is only months, or years, later that they become Unix Executable Files. This has happened to just about all of my CD backups and it's frustrating to think that CD backup doesn't work across newer OSs and Photoshop upgrades. I suspect that may be the problem, but it just shouldn't happen.
That shouldn't make a difference. I've got a bunch of very old files created in Photoshop back from OS 8 on CD. No file extensions, as nothing did at the time. Just Type and Creator codes. They all open fine in PS CS5.5 in Snow Leopard, though the native Photoshop files do need to have a .psd extension added.

Wav Files renamed... now they are UNIX EXECUTABLE FILES

Hello everybody!
I ran a script in terminal to batch rename something like 2K+ .wav files following an .csv list.
The list contained 2 columns, A: the original name and B: the new desired name.
for the ones interested the script is here:
http://discussions.apple.com/thread.jspa?threadID=1886783&tstart=0
I ended up having the same 2k+ wav files perfectly renamed but the finder sees them as UNIX EXECUTABLE FILES.
Now all my audio apps can open them fine but the thing is that I need them to be listed as audio files in finder so I can preview them with QuickLook in the finder.
Anyone knows how to do this?
Renaming again using a different app (like Automator) did not work, file types and creator codes are blank. I have a utility that changes them but I don't know wich is the correct filetype and creator code....
Maybe you can shed some light on this issue....
Solved it myself. stripped the file of its extension. then replaced the extension.... worked!
Thanks!
Message was edited by: fhpetrone

Nevermind, I found this helpful page: http://www.thegaragedoor.com/roadcrew/samplerates.html.
btw, you could have found that same page on the B&B site, since that's where it came from:
http://www.bulletsandbones.com/GB/Tutorials/SampleRateBitDepth.html

Fonts problems (unix executable file)

Hi,
I've a mac os x 10.4.11(tiger) G5 and a new mac os x 10.5.2(leopard)Imac both connected on a server.
I've many differents fonts on the server. On the G5, I can take all the fonts on the server, put them on my desktop and they will keep their extensions. On the Imac, when i do the same, only the *.ttf et *.otf are recognized, and all the others (font suitcase, postscript type 1 outline font, etc...) are known as unix executable file (0 ko). So, i've to go on my G5, create a zip file of the fonts, open my zip on my desktop's Imac (not on my server, because same problem) and then I've all my fonts with the right extension.
My font software is (on my both mac) is Linotype FontExplorer X Version 1.2.3.
What I've to do, to proceed in the same way on my Imac as on my G5, and not create a zip?
Thanks

I knew this sounded familiar. Mark Douma posted this on a very similar thread a while back.<hr>Notice the "__MACOSX" folder in the expanded archive? That's evidence that the original archive was created using the built-in "Create Archive" function of the Finder, but that the archive on your end was expanded using Stuffit Expander 8.0.1 or earlier.
ZIP files don't normally support resource forks, so when you create a zip file of fonts, the program needs to some method of preserving this information. In Stuffit Expander versions 8.0.1 and earlier, it used its own method to preserve this information (before creating the final zip file, it would first encode each included file as a MacBinary (.bin) file).
Unfortunately, the built-in "Create Archive" feature of the Finder (BomArchiveHelper.app, actually) uses a different method, one which you're seeing evidence in the "__MACOSX" folder in the images shown. Inside that folder are the "other halves" of the files you want to use.
There are two possible solutions:
1) Instead of using Stuffit Expander to expand the .zip files, use the built-in feature of OS X. To do this, select a .zip file in the Finder, and choose Command-i to open a Get Info window. In the Open With section, make sure that "BomArchiveHelper.app" (Tiger and earlier) or "Archive Utility.app" (Leopard) is set to open the archives. If it isn't, click the pop-up menu, choose Other, and navigate to the /System/Library/CoreServices/ folder and choose the appropriate application for your version of OS X. Then click the Change All button to apply this to all .zip files. Then locate the original .zip and expand it once again.
2) Update your version of Stuffit Expander to version 8.0.2 or later. Allume changed the method it used to preserve information in zip files to match that of the Finder's method in Expander 8.0.2 and later. After updating, locate the original .zip file and expand it once again.
There may also be an advanced way of salvaging these files shown toward the end of the following movie.
The following movie shows the predicament (I haven't had a chance to add sound or text, but it should hopefully be self-explanatory).
Notice the version of Stuffit Expander used to expand the archive is 8.0, which exhibits the same problematic behavior you're seeing:
http://homepage.mac.com/mdouma46/images/zipFilesAndFonts.mov (~8.0 MB).
Hope this helps.... <hr>
Essentially, it's all in how the fonts were compressed or sent. Trying to send Mac fonts as direct attachments in an email will almost certainly ruin them. As Mark stated above, how they were zipped and then unzipped can also create empty fonts.

Time machine out of my control-Unix Executable file

Time machine did not show up on my desk top today. When i tried to access it thru Go/Network I got a box that said SMB/CIFS/file system authentication.
When I accessed the files on the time machine they don't open because they are "Unix Executable files" instead of the type that they really are. What happened to my access to the time machine?

One thing to double check is that the computer name (in the sharing preference panel) is exactly the same as it was when the backups were made. Sometimes that is all it takes to have Time Machine continue with incremental backups.
In your case, however, it may be that you would need to change the new computer's ethernet MAC address to the same as your old computer, and that could be a problem if you don't still have that computer.

Folders turn to 0 KB unix executable files in FAT32 drive

I two external drives in FAT32 format. Suddenly, what were once folders have now become 0 kb unix executable files, with a 12-31-1969 timestamp. One of the drives now doesn't mount.
This is a slightly different problem that when FILES do the same thing. I haven't found any ideas on the case of folders.
TestDisk tells me the disk geometry is bad (check sum doesn't match). If something that was once a folder now isn't, that would explain why the checksum is bad - optimistically, the files are still on the drive somewhere, but I can't get to them. Is there a way to change the file type from unix file back to directory? As far as I could tell, chmod will only change file types.
DiskUtility's Repair Disk gives me the error: Unable to read directory (Input/output error). The underlying task reported failure on exit.
DiskWarrior is no help, as these are FAT drives.
A change in these directories would easily explain why the directory structure is unreadable.
How do I set these unix executables back to folders, and how do I repair the directory structure??
Thank for any ideas!

Nasty. Your best bet is to use data recovery software to extract & backup whatever files you can, then completely reformat it.
http://www.cgsecurity.org/wiki/TestDisk
http://www.macworld.com/article/143139/2009/10/recovererased_harddrive.html
http://download.cnet.com/Data-Recovery/3000-2094_4-10298807.html
.

File type changed to Unix Executable File

Similar Messages

Maybe you are looking for