Autosaved as Unix Executable Files after editing font size?

When I open a .txt file in TextEdit, and change the font, in the Finder I see a new Unix Executable File appear, with (Autosaved) after the file name. This is in addition to the original .txt file - so there are now 2 files of the same name showing.
However, when I manually save the file, the Unix exe file disappears from the Finder, leaving the newly saved .txt file.
Is this normal? If not, please let me know what else I can try to fix it. I've already tried both suggestions in this thread & neither of them worked.
Thanks!

Ok I noticed that TextEdit preferences shows an option to "delete the automatic backup file" so that's why it's disappearing...
...but what happens if TextEdit quits on me unexpectedly (which it has before)? Will I be able to open the autosaved Unix executable file with TextEdit or will it be "unrecognized?"
If anyone can give me confirmation that their autosaved files are Unix exe files and/or if they've been able to open the Unix exe backup files in the program they were created from, that would help.

Similar Messages

How can I restore my Microsoft Word Documents which became Unix Executable Files after my Macbook Pro Crashed?

After my MacBook Pro suddenly crashed, we had Best Buy's Geek Squad attempt to save the files. According to them, they were successful in doing so and put all of the saved files in a folder on my desktop which they labeled "Backup". The problem is, all of the files are in a Unix Executable format. When you double click on any of them, they pull up the terminal and that's it. After researching the issue and trying to grasp what was going on, I learned that you can open these files in Text Edit and sometimes find the file extension (.png .jpeg .amr .qt) that belongs at the end of the filename in order for it to be pulled up. In doing this, I had some success restoring some photos, audio files, and videos. However, no luck at all in restoring any of my Microsoft Word documents or even finding out which Unix Executables are Word documents. I've even tried to add .docx to various files just to see if I would luck out. Nope . Any help would be SO SO greatly appreciated!!!

Just to make sure, your Mac meets Snow Leopard's requirements?
Mac OS X v10.6 Snow Leopard - Technical Specifications
Yes, Lion does require that you have Snow Leopard installed so you have access to the Mac App Store.
And you do need to be running v10.6.8 in order to upgrade to Lion > http://www.apple.com/macosx/how-to-buy/
When you verified the startup disk using Disk Utility, what were the results?
Wouldn't hurt to do that again. From your admin account launch Disk Utility. Select MacintoshHD in the panel on the left then select the First Aid tab. Click: Verify Disk (not Verify Disk Permissions).
If the startup disk needs repairing, boot from your install disk to make repairs > Using Disk Utility to verify or repair disks
While you have the DU window open, check Capacity & Available at the bottom of the window. Make sure there is a minimum of 15% free disk space.

After Mavericks upgrade fonts on server appear as Unix executable files

Hello:
I upgraded two machines to Mavericks. An iMac and a Macmini both were running 10.8. We store files and fonts on a Windows server. Before the upgrade the fonts appeared as aspected on the server in the Finder, after the Mavericks upgrade they appeared as Unix executable files ( Only on the iMac ) the fonts display correctly on the MacMini. Both machines mount the server the same way and the fonts do work correctly if downloaded to the local machine.
Anyone have an idea why they would appear correctly on one machine and not the other.
appreciate any input.
thanks,
Rick

Gary Looft wrote:
They show up as Unix executable files
Kurt is very likely right, but we need more info to try to fix it.
Server details?
What version of Mac OS X can view the fonts?
What protocol do they use?
What protocol do you use?
If they connect to the server with a different protocol from you (eg, AFP vs SMB), try switching to the same protocol. That may very well not solve the problem, but it's the first step.

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.

Old Font Files in Leopard showing up as Unix Executable File

Is there any way I can make the computer be able to use and open the font files that now are being seen as Unix Executable Files even though they worked just fine as fonts before I upgraded to 10.5. I've tried putting new file extensions on them, or telling them to be opened with font book. I'm not sure what else to do, we have hundreds if not thousands of fonts that we need and that our customers need us to be able to use.

Thanks soo much everyone for all the help.
I've installed reset permissions, reset LaunchServices using OnyX, rebooted, and files are still "unix executable" to start with. I then used FileUtils app to "Clear Executible Status," which makes them open in txt editor, and say they are 0kb in size. I then renamed the extentions, playing around with a bunch of different types, and no luck at all with any of them.
Here is a screen shot (http://180bydesign.com/uploads/Picture5.png) of my folder (at top) with a list of fonts, and fontbook.app (at bottom) when I try to add a font from that location. No luck.
PS - here's something weird... I had a friend w/ Tiger send me a font suitcase which he zipped, and it did same thing, but then he zipped it twice (wierd, I know) and it worked! I unzipped the first one, then unzipped the second file within that first one, and WALLA, the suitcase actually looked and acted like a font. This doesn't help at all with all the other saved files, but it certainly helps. I might open a pc & try to double zip all the old ones & see if that does the trick.

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/>

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.

Unix Executable Files

after upgrading to Tiger 10.4.3, all my files that did not have a file extension (in particular all my fonts) are now Unix Executable files and unusable. is there any thing that can be done?

My boss if having the same problem! I however, am not. We have identical G5's, but our older G4's are slightly different with slightly different OS's and software. My boss has OS 10.1.3 and OS 9.2.2, also i have newer versions of photoshop and quark on my G4 than my boss does.
The file types he is having the issue with are .eps files from photoshop and illustrator, and quark files that don't have the extensions already. He was told by Support that the issue may be stemming from the fact that when he worked on his older mac, he booted up in OS 9, where as I always booted up in OS X and used OS 9 virtually.
We are trying to transfer the files directly now, while his older mac is booted up in OS X to see if that solves the Unix problem. But now we are running into the issue where, once the computers are hooked up by firewire, the process is freezing. Does anybody have any advice for us? We need HELP!!!
Thanks!
JdJ
Macintosh G5 Mac OS X (10.4.2) Old Mac - G4, OS X 10.3.2 & OS 9.2.2
Macintosh G5 Mac OS X (10.4.2) Old Mac - G4, OS X 10.3.2 & OS 9.2.2

Old Photos - Unix Executable File

Trying to help a friend - he has a bunch of photos on his Mac that are six years old. He can't open them. He sent me one - it shows up as a "Unix Executable File" (whatever that is?). The read/write accesses are OK. File is about the right size (350K). iPhoto 6 won't open them. Is there a way to open/convert these files?
Thanks, Nick

Nick:
Do the files have the jpg extension on them? If they do, select one and type Command-I. In the Info pane there's an Open with menu. In that menu select Preview as the default application to open it with. Then click on the Apply to all button. See if that won't get them to respond as they should.
Do you Twango?
TIP: For insurance against the iPhoto database corruption that many users have experienced I recommend making a backup copy of the Library6.iPhoto database file and keep it current. If problems crop up where iPhoto suddenly can't see any photos or thinks there are no photos in the library, replacing the working Library6.iPhoto file with the backup will often get the library back. By keeping it current I mean backup after each import and/or any serious editing or work on books, slideshows, calendars, cards, etc. That insures that if a problem pops up and you do need to replace the database file, you'll retain all those efforts. It doesn't take long to make the backup and it's good insurance.

Opening unix executable files

What application in Leopard can I use to open unix executable files?

It seems to be a file type that is given to any file (of any sort) that has had its Execute permission set. Plain text, TIFF and font files are all showing this oddness.
You can open them via the right (command) click context menu for the file and use Open with, or use GetInfo in the same menu to set the opening program, provided you know what sort of file it's likely to be.
You can remove the Execute permission using the Unix chmod command in the Terminal, but a simpler solution is to install the FileUtilsCM context menu (free) from http://www.abracode.com/free/cmworkshop/file_utils.html
See thread http://discussions.apple.com/thread.jspa?messageID=6125826&#6125826 for related info.
DN
Message was edited by: dcnicholls

UNIX EXECUTABLE FILES (S.O.S. I've lost my data!!)

Hey! This is what happened.
I bought my mac and I used it perfectly. After 6 months I decided to format the computer. I stored all my data in an external hard drive. I installed everything I needed, and when I transpassed the external drive's data to the MAC I got a bunch, a lot of EXEC or Unix executable files. I tried changing the extension but it says error, file corrupt or something. I'm really worried, HELP PLEASE!!!
Thanks!!!

To save complete system data in a movable and relocatable form,
and have it seen as a system again, it should be either archived
as a disk image (disk utility can do this) and then reimported to
the computer later, or as a clone. Free-running clone utilities of
widely known worth include Carbon Copy Cloner, & SuperDuper.
{You can clone the data off the computer, and then clone it back}
An external drive for storage should be formatted in a Mac
friendly format; though a windows format may work in a pinch.
I think the files you have, were changed due to a different one
on the external drive than the computer's OS would prefer.
Now that these files have been copied (by drag and drop?) to
another drive, they may be broken beyond repair or reuse.
The files not related to running the OS X or the apps may be
recoverable, since you probably had work or projects saved
and they may have copied over OK from the computer to an
external drive...
Sorry, that I do not have an easy answer for this; perhaps another
reader may find they have a more adequate answer given the
circumstances you now face.
Best regards, in any event...
Good luck & happy computing!
{ edited }

How to sync two excel files, the content is the same in both files after edit.

I have two excel files, which are data and edit by multi users, how can I sync the master files to the copy files after edit?
Is this operation required VBA? marco?

Hi,
Your request could be done via VBA code. Here are two ideas.
One:
Syncing the data from master file to the copy file without opening copy file. Sample code
Private Sub Worksheet_Change(ByVal Target As Range)
If Target.Count > 1 Then Exit Sub
Dim cnn As Object, SQL$, s$
Select Case True
Case Target.Value = ""
s = "null"
Case IsDate(Target.Value)
s = "#" & Target.Value & "#"
Case IsNumeric(Target.Value)
s = Target.Value
Case Else
s = "'" & Target.Value & "'"
End Select
Set cnn = CreateObject("ADODB.Connection")
cnn.Open "provider=microsoft.jet.oledb.4.0;extended properties='excel 8.0;hdr=no';data source=" & ThisWorkbook.Path & "\test folder\Book2.xls"
SQL = "update [Sheet1$" & Target.Address(0, 0) & ":" & Target.Address(0, 0) & "] set f1=" & s
cnn.Execute (SQL)
cnn.Close
Set cnn = Nothing
End Sub
Two:
Saving the master file as copy file before closing. Reference:
https://msdn.microsoft.com/en-us/library/office/ff194765.aspx?f=255&MSPPError=-2147217396
If you have any further question about coding, I recommend you post the question to the MSDN forum for Excel
http://social.msdn.microsoft.com/Forums/en-US/home?forum=exceldev&filter=alltypes&sort=lastpostdesc
The reason why we recommend posting appropriately is you will get the most qualified pool of respondents, and other partners who read the forums regularly can either share their knowledge or learn from your interaction with us. Thank you for your understanding.
Regards,
George Zhao
TechNet Community Support
It's recommended to download and install
Configuration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office
programs.
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected].

Final Cut Pro Unix Executable file??? what do i do?

Hey All,
So I wanted to dig up an old movie i edited in 2003 so i took out the old IMac. I found the Final Cut Pro 2 sequence on there but because all the footage (capture scratch, etc.) is saved to an external hard drive i need to reconnect the material to the sequence. i hooked up my WD My Book drive to my G5 to find the clips and sure enough i backed them up on this hard drive (37 gb worth) awhile ago but for some reason all the clips say they're Unix Executable Files? Why did this happen when i backed them up instead of them staying as Quicktime files?
So here are my questions...
Tonight when i go home I want to be able to open up the FCP sequence on Final Cut Pro Studio 2 (fcp7)...will this be possible to open up an FCP 2 sequence that many versions later?
Also, please tell me why the quicktime clips did this? When i do File-->Get Info-->change open with Terminal to Quicktime they play but how will i get them to reconnect to FCP?? Do i need to go one by one and add .mov extension??
I'm very confused...i would rather not have to do the editing on the 2003 machine..i'd like to get it to work on my newest computer (27inch imac).
Can i attach a newer external that the clips are on to the old mac?
Thank you,
Jenna

..will this be possible to open up an FCP 2 sequence that many versions later?
Yes.
Do i need to go one by one and add .mov extension??
Use my [Automator Action|https://files.me.com/nikholmes/0ge9cr] which will rename them for you -Just choose the correct folder in the "Start At" section. Link is a direct download from my iDisk.
Can i attach a newer external that the clips are on to the old mac?
Of course.

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

Why did all my files suddenly become UNIX Executable Files?

After reformatting my hard drive and installing Panther server, I restored the Retrospect back up of files to my home directory. Unfortunately, all the files that didn't have suffixes (eg: .doc, .xls, .pdf, etc.) suddenly had their icons replaced with an icon of a black console with the word "exec" typed in. And their kind was lost and all became: UNIX Executable File.
Ever since this Panther server has been acting eratically.
I have been able to resurrect the affected files by opening them in their native application and resaving them with the proper suffix. But there are thousands of files and dozens of applications that could have made each file.
Is there a way to resurrect these files without having to open and resave every single file in its native application one at a time? Could these thousands of UNIX Executable Files be causing problems for Panther server?
Thanks for your input.
Gregg

Hi TropicalReef,
At some point during your backup/restore process the executable bit was set on your files. This should not cause a problem with the overall performance of the operating system. But to some extent this is a security risk. There are a number of GUI applications that can change file permission. I recommend you download one and remove the executable bit from your files. Read the developers documentation carefully. Changing file permission especially in batch mode can be very dangerous.
The easiest way to make you files double clickable is to add the appropriate suffix to the file name. Again there a number of shareware and freeware apps that will do this. Check MacUpdate and VersionTracker.

Autosaved as Unix Executable Files after editing font size?

Similar Messages

Maybe you are looking for