3rd Party Plugin problem (unix executable file)

I have a few 3rd party plugins for final cut pro, but for some reason my computer will not accept them as the file type seems to be wrong.
Does anyone happen to know how to make "unix executable (exec)" files readable, so i can install these plugins.
A work friend has an older mac (G4 tower, not an intel like mine) and the plugins work fine for him. Very frustrating!

I have tried everything. Double clicking just asked to choose application and dragging the file into the /Library/Application Support/Final Cut Pro System Support/Plugins/
FxPlug plugins go here: /Library/Plug-Ins/FxPlug/ didnt work either. I got an error message (-32)
Im guessing it doesnt work on my mac because its a intel. Looking at the company website, i dont think that they have released a newer version for the intels.
Think im gonna give up on this issue, but thanks for everyones help and advice. If i ever solve this problem, i will make sure i create a new post to let you all know.
Thanks.

Similar Messages

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.

Problems after opening "Get Document" Unix Executable file

After importing documents from my Dell computer to macbookpro and opening a file called "Get Document" which is a Unix Executable file, I now have dozens of these type of these type of files in "Places":
file://localhost/Users/sacredsprings/%25B0%2580%25A9%25C0SR
I had Linux installed on my Dell, and having read a few threads think it may be to do with that. Can I just safely delete all these files?

Sometimes ZIP files are made into self-expanding .exe files. When run on a PC, they will unzip without needing any unzipping software. They will not do this on a Mac, but Stuffit Expander may work with them
<http://www.stuffit.com/mac/expander/>

Unix Executable files within apple programs, problem???????????

Sometime ago i was using logic pro 7,and saving my project folders on an external drive,,,all of my folders turned into EXE files and couldnt be read,,
Now ive wiped my internal drive,,reloaded the install disks,,used disk warrior,
If i highlight any icon such as logic,iDVD,garage band,,or any other,,"show package contents" ???? click contents then open the "MacOS" folder,, A black Unix Executable file is here,,,,in all programs,!!!!!!!!!!
I have tried to find out if this is normal as i lost a huge amount of project folders,,,,but there is nothing or no one i can find to resolve this issue,
i would just like to feel safe as im not much of a computer wizard,,
anyone got an idea? yours confused,, steve

I have tried to find out if this is normal
Yes, it is.
(48530)

Unix Executable Files Problem

My husband moved from PC to Mac and had the Apple Store transfer his libraries to it - including picture files. Every time he opens iPhoto he is told that there are 14 files not yet imported. However, they can't be imported and on inspection turn out to be Unix Executable Files. Each time he does this another Recovered File folder appears in his picture folder on the HD.
I've tried to find out what the files are - but, of course, can't open them. I suspect that they maybe Clip Art from his PC version of Microsoft Office. They can't be deleted. If I put a Recovered File folder in Trash and Empty Trash, it just turns up in the Picture Folder again!
While not a disaster, it's very irritating. Is there anything he can do?

Quit iPhoto and right click (control click) on your iPhoto library (by default in the pictures folder) and select the show package contents command - find the folder names import (or importing) and drag it to the desktop, close the iPhoto library and launch iPhoto - you will be fine
Open the import(ing) folder on the desktop and see if there is anything you want to save in it - if there is import them to iPhoto and then trash the import(ing) folder
LN

Export Results in Unix Executable Files Instead of .jpg

When I try to export an album to a folder, the exported files are in "unix executable file" format instead of .jpg
How do I fix this?
Mac OS X (10.4.6)

Harley:
Welcome to the Apple Discussions. In the file export window have you selected jpg or "original format" and have the Add extension checkbox checked?
Do the exported files have a extension? If so and it's jpg, then select on and bring up the Info window for it (Command-I). Then under default application select Preview and click on the Apply to all.. button. If you prefer to use a 3rd party editor like Photoshop or PS Elements then select that and click on the Apply to all... button. But the files should have an extension.
Do you Twango?
G5 Dual Core 2GHz, 2G RAM, 250G HD; G4 Dual 1Ghz, 1.5G RAM, 80G HD, Mac OS X (10.4.6) 22 LCD Display, 200G & 160G FW HDs, Canon S400, i850 & LIDE 50, Epson R200

How do you install and delete 3rd party plugins from Logic 9?

I have been trying to install RX2 from iZotope with no success. I can authorize it in the standalone version but not in logic. I had a previous demo version of it installed and everytime I went to authorize it would point to the earlier version and not authorize and run in demo. I removed a number of files pertaining to it from HD & User/ Library/ Preferences and Audio/ Components and tried reinstalling. Now it doesn't even show up in the plugin list. Can anyone tell me how to clear this up? Also, how to deal with 3rd party plugins. What can I say, no problems with Reaper! Appreciate any help with this. Thanks

The Isotope website isn't very clear about it.. It seems to indicate the Windows version is 32 and 64 bit where as the AU version is 32bit and will work/is compatible with Logic 64bit.. which it will as it will run under the 32 to 64bit bridge... when Logic is run in 64bit mode..but as i said, it's hard to tell one way or the other.
The thing is, if you simply reinstall it.. and then run Logic first in 32bit mode and then in 64bit mode.. it should show up.
Where are you looking for it in Logic?
Does it show up in the AU Plugin Manager? (after, that is you have reinstalled it)

Leopard, ps cs3 and 3rd party plugins

help again please.
I have PS CS3 and numerous 3rd party plugins but as soon as I installed the new OS 10.5 I get the msg. one or more plugins are currently unavailable on your system. They worked before the upgrade of os10.5. I even upgraded to 10.5.1..The plugins I can't get are Nik color efex pro complete and Nik sharpener pro complete. The Nik website states they are compatible. Other 3rd party plugins like Fluid Mask 3, Genuine Fractals and Flaming Pear all work. Help if you can please. I already have a msg. to Nik software for help but have not gotten an answer from them..
Thank you.
sincerely
karen

To use your Nik Software products on a new Intel-based Mac Computer with Photoshop CS3, simply follow these three easy steps below:
1. Quit / Exit out of Adobe Photoshop CS3 and navigate to the Adobe Photoshop CS3 application file which is typically at the following location: Macintosh HD | Applications | Adobe Photoshop CS3
2. Highlight the Adobe Photoshop CS3 application file icon and press Command + I (+ I) to open File Info.
3. On the File Info window (as shown on the right), check the box next to "Open using Rosetta", then close the window.
That’s all there is to it. Photoshop and Nik Software filters will work without a problem.

InDesign 3rd party plugin update to CC2014 failed

Dear Community,
I have a following problem: We have developped a 3rd party plugin for different InDesign versions (5, 5.5, 6). The new requirement is to build a new project configuration for InDesign CC2014 in VS 2013. So, I created new configuration by using the settings from InDesign 6 configuration, then I adjusted necessary pathes to sdk and project variables but now I get the following error by trying to compile the project:
1>------ Neues Erstellen gestartet: Projekt: iMatch (iMatch-Plugins\iMatch), Konfiguration: ReleaseCS2014 Win32 ------
1> VCPlugInHeaders.cpp
1>C:\Program Files (x86)\Adobe\Adobe InDesign CC 2014 SDK\source\precomp\common\ShukHeaders.cp(19): fatal error C1083: Datei (Include) kann nicht geöffnet werden: (File cannot be opened) "boost/config.hpp": No such file or directory
========== Alles neu erstellen: 0 erfolgreich, 1 fehlerhaft, 0 übersprungen ==========
I checked the file ShukHeaders.cp by other sdk versions and it has the same include, so I dont understand what could be wrong.
I would very appreciate if somebody could give me an advise that could help me to solve the problem or perhaps a small workaround how I can create new project configuration properly.
Thank you in advance.

The same problem was solved here:
Re: D:\InDesign CC\Adobe_InDesign_CC_Plugin_SDK0108\source\precomp\common\ShukHeaders.cp(19): fatal erro

Can I rearrange AU 3rd party plugin's nested folder structure??

Is it possible to organize 3rd party AU plugins by TYPE rather than by Brand? Even better, can they be integrated into the menu of Logic's included instruments/effects? It's hard to sift through say, all your samplers, or all your synths, when they are organized by Company names, and separated from Logics own instruments. I would love to see Kontakt and Sampletank alongside EXS24. And all my compressors together in a list, as opposed to them all being nested individually.
I haven't seen this mentioned anywhere, but was thinking maybe someone figured out a way to change the structure. Thanks!

I'm sorry, I don't think I explained this clearly enough:
My problem is NOT that the plug-ins won't show up in my Library after I set the path to a particular folder in Motion's Preferences.
My problem is that there is no longer even an option anymore to set the path to a particular folder in Motion's Preferences! It was there before, and now it has just disappeared! I don't know how to get it back. When I open Motion's Preferences pane now, in the General section, the sections are as follows:
Startup
Interface
File Browser & Library
Content Library & Templates
Media
Keyframe Editor
Normally, the "3rd Party Plugins" section is right below the "Content Library & Templates" section, but it's not there anymore...
I apologize for any confusion caused by an earlier post and hope my problem is more clearly understood now. Thanks!

Disappearing "3rd Party Plugin" option

I recently tried to change the search path for 3rd party plugins to my After Effects plugins folder (Applications > Affter Effects > Plug-ins). They still wouldn't show up when I'd open Motion and navigate to the 3rd Party folder in the Library. So I gave up and didn't bother with it any more.
I was more distracted by the fact that none of my Replicators or Particle Emitters were showing up, so I re-installed (or possibly installed for the first time, this is a work computer, so I didn't do the initial installation) the Motion Content and they all appeared as expected. Now, here's what's confusing me:
When I go into Motion's Preferences now, there is no longer even an option to set the path for 3rd Party Filters and Plugins (under the Content Library & Templates section)...
Anyone know how I can fix this and get my plugins to work? I didn't have any trouble doing it on an ancient G4 Powerbook, but for some reason a fully-loaded MacPro is being difficult with me.
Thanks for any help.

I'm sorry, I don't think I explained this clearly enough:
My problem is NOT that the plug-ins won't show up in my Library after I set the path to a particular folder in Motion's Preferences.
My problem is that there is no longer even an option anymore to set the path to a particular folder in Motion's Preferences! It was there before, and now it has just disappeared! I don't know how to get it back. When I open Motion's Preferences pane now, in the General section, the sections are as follows:
Startup
Interface
File Browser & Library
Content Library & Templates
Media
Keyframe Editor
Normally, the "3rd Party Plugins" section is right below the "Content Library & Templates" section, but it's not there anymore...
I apologize for any confusion caused by an earlier post and hope my problem is more clearly understood now. Thanks!

Old Quark files are now Unix Executable Files

I made hundreds of archive CD's with Mac's running OS 9 back in 1990's. They contain Quark files and .tif's. I've referred back to these CD's many many times over the years with no problems. My new iMac has the intel processor. I pop an archive CD in and all the files (with no extensions like "tif" or ".qkd" or ".eps") are now "Unix Executable Files" that won't open.
I simply add an extension to the images files (like ".tif") and they work. HOWEVER, it's not so easy with the Quark files. I add ".qkd" to the file name and it still remains a Unix file.
I launch Quark and try to open the file through the finder and it doesn't work. I took an archive CD to a friends house whose on a G5 and the CD worked properly with no extensions needed to be added.
So I figure the problem is with the Intel/PC based processor. I shouldn't have sold my old G5.
One forum claimed that a program called "File Buddy" did the trick for him. Does anyone have any other ideas other than me buying a non-Intel Mac.
I love our new iMacs but I need these archive CD's to work!
Thanks

I automatically run OnyX once a week for maintenance, but it didn't help this situation.
Those chores won't reset the LaunchServices database. Go to the Maintenance heading and click on the Reset tab. Turn on the check box for "LaunchServices database" (all other check boxes off). Click the Reset radio button and then Execute. Restart your Mac.
OS X will automatically rebuild the database according to the applications on your hard drive, giving preference to Apple applications as they would be when you first install OS X. So if you have the Acrobat Reader set up to open PDF files, you'll have to do that again as they will be set back to Preview.
Actually it's .qxd not .qkd for Quark XPress file extensions.
That's it! I knew .qkd was wrong, but Quark 6.x won't show you the old extensions when you save a file, and I couldn't remember it (been using InDesign steadily for a while now).

CS4 and 3rd party plugins - icons disappear

I'm having problems with CS4 on Vista 64bit with 3rd party plugins. I'm aware that 64bit issues exist but even on the 32bit CS4 Photoshop's toolbar icons disappear once Nik, OnOne etc are installed. I've left CS2 installed as well on the same system and this works fine.
This could be a problem with for the 3rd party developers of course but obviously CS4 has changed something.
I have Vista 64bit with 8gb RAM. Disabling the GPU functions doesn't help nor does running CS4 in XP compatibility mode. Removing the plug ins is the only way to resolve the problem.
Just wondering if anyone else has hit this problem and even better found a solution to it.

I think I can recall the behavior being confirmed for Nik and they are working on a fix/ update. The situation may be the same for other tools/ vendors, so you'll probably have to live with it for a moment or resort to using older versions of PS...
Mylenium

Word Docs have become Unix Executable Files!

The subject says it. This has happened on both my wife's iMac G5, and my MacBook Pro. Some, not all, of our Word docs, (both using 2004, running OS X.4.7) have had their icons turned into a gray console, and in "Get Info" identify themselves as "Unix Executable File." When opened in Word, I get the option to open as if it were a foreign file, and typically, it opens with all formatting gone, and all kinds of bizarre characters at the beginning (and sometimes end) of the doc.
Now, I can salvage the data, it seems, but is there some way to simply undo this damage without manually going through every file?
I must say, this is exactly the kind of junk that I would expect to find on a PC. This is a stunningly bad problem, by far the worst I've experienced in almost 15 years of using Macs. I would assume that Apple is aware of this, and that they can:
1) Explain what happened.
2) Explain a quick and easy fix.
Thanks to anyone (from Apple or otherwise) who can do 1 and 2 above.

Jeffois,
The first command I gave to you will render the directory in question, and all nested directories, inaccessible. The second command will make the diretories accessible again.
There is a possibility that there are files in this directory structure which are not owned by you. Not likely, but I must make the assumption that these could be encountered when I give such commands "in the dark" as it were. In such a case, you would see an error regarding these files, thus the warning.
You can return your directories to accessibility using the second command, regardless of errors you might encounter. If you do encounter errors, I will post a different form of the same commands that will work.
Be prepared to deal with this problem any time you transfer files from a Windows-formatted volume. This is not a Windows problem, but rather one of differences between the two file systems. If you see a file show up with the executable icon, you might want to remove the execute bit right away. Unfortunately, there is no way to do this in the GUI, so you must resort to using Terminal.
This shouldn't be too much of a problem. Just open Terminal, type this text with a traling space:
<pre style="overflow:auto; font-family: 'Monaco'; font-size: 10px">chmod a-x</pre>
then select all of the new files and drag them all into the Terminal window. This will create a rather long command line that includes the full path to every file you dragged in. Just press <RETURN>, and "POOF," no more execute bit!
Scott

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.

3rd Party Plugin problem (unix executable file)

Similar Messages

Maybe you are looking for