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

Similar Messages

  • 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.

  • 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.

  • How open old Appleworks documents that appear as UNIX executable files?

    A few of my old Appleworks or Clarisworks files won't open with Appleworks 6, but show up as a "UNIX executable file." I have tried adding the ".cwk" extension, repairing permissions using Disk Utility, and using Finder>File>Get info>Open to choose Apleworks 6 (it already was selected) as recommended by Peggy. With ".cwk" extension, I then get "that file appears to be damaged and cannot be opened."
    Any other suggestions?

    Hi Cloyd G,
    welcome to Apple Discussions and the AppleWorks forum.
    The 'UNIX executable file' classification error appears to arise mostly from the lack of a suffix (.cwk) on the original file. If adding the .cwk suffix does not make the file readable by AppleWorks, and gives a 'file appears to be damaged' message, then it's likely that the file has indeed been damaged.
    If it's a word processor file, you could try opening it in a Text editor (such as Text Edit, supplied with OS X, or Text Wrangler, available free from Bare Bones Software). You'll get a large amount of junk (file meta data and formatting codes, etc.) with the text of your document somewhere in the middle. If you know a single word that is in (or is likely to be in) the document, a search using command-F should take you directly there. Copy the text and paste it into a new AW document.
    For spreadsheet files, you can try dragging the file and dropping it onto a new, empty spreadsheet document. The same technique may also work for database files. I've never tried or seen recommended the same texchnique for Draw or Paint files, but attemptng it should do no harm.
    Best of luck with this.
    Regards,
    Barry

  • Word documents appear as "unix executable files" and cannot be opened

    Hi: I am running 10.5.5 on my Intel Imac. The problem is that many old MS Word documents have suddenly flipped into documents with no file extension, but which are identified in the Preview window as "unix executable files."
    I've had this happen before, and all I had to do was add the .doc extension for them to become Word documents again. This time there is nothing I can do to change them over. I have tried opening them from Word, from Pages, from Text Edit, with no results. (I have also used all the possibilities available from Word as well).
    There doesn't seem to be any pattern -- random documents in the same folder, created at the same time and modified at the same time, appear as unix files, while the others seem fine. Any ideas?
    <Post Relocated by Moderator>

    This is the iWeb forum. You should post your question in the Leopard forum. But I'll give a try at a possible solution:
    1 - check the Finder preferences and make sure you have the option to show file extensions checked.
    2 - select one of the Work files, type Command+i and in the Info window go to the Open With menu and select Word as the default application. Then click on the Apply to All... button.
    OT

  • When I attempt to open a PDF file I saved from a website, I get the message "There was an error opening this document. The file is damaged and could not be repaired." Is there any way to correct this problem?

    When I attempt to open a PDF file I saved from a website using Safari, I get the message "There was an error opening this document. The file is damaged and could not be repaired." When I save the same PDF file using FireFox it opens up immediately. Is there any way to correct this problem with Safari?

    Back up all data.
    Triple-click the line of text below to select it, the copy the selected text to the Clipboard (command-C):
    /Library/Internet Plug-ins
    In the Finder, select
    Go ▹ Go to Folder
    from the menu bar, or press the key combination shift-command-G. Paste into the text box that opens (command-V), then press return.
    From the folder that opens, remove any items that have the letters “PDF” in the name. You may be prompted for your login password. Then quit and relaunch Safari, and test.
    The "Silverlight" web plugin distributed by Microsoft can also interfere with PDF display in Safari, so you may need to remove it as well, if it's present.
    If you still have the issue, repeat with this line:
    ~/Library/Internet Plug-ins
    If you don’t like the results of this procedure, restore the items from the backup you made before you started. Relaunch Safari again.

  • How do I open my old Appleworks documents which have turned into Unix Executable Files?  I would like to convert them into Pages documents.

    How do I open my old Appleworks documents which have turned into Unix Executable Files?  I would like to convert them into Pages documents.  I also have old Word Perfect documents which have become similarly unopenable.

    Best bet might be to try opening them using LibreOffice [free] and save them to .doc.
    Do you really want to save them as .pages files? You are jumping from the frypan into the fire. Yet another proprietary format that Apple has again deadended with no working translation.
    Peter

  • 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)

  • Unix Executable Files...why won't they open?

    I now have a new iMac and using Mavericks 10.9.3. I used TimeMachine to transfer my files (that contained these strange "Exec" files after I had updated to Mavericks on my previous iMac) a number of these files turned into something called "Exec" files (Black rectangular icon with green "exec" in the upper left corner). and randomly appeariing in diff software.  Have these files become corrupted? Should I trash them?
    Thanks for any help
    Julie

    In the Finder, click on these Exec files and press command+I. If the file is an AppleWorks document (even with no extension) it will tell you that. If it is a UNIX shell script with owner+group+world execute permissions, or a compiled executable from source code, it will state that it is a UNIX Executable File.
    In the Terminal application, you can use the file command to discern (usually) more accurately what these black Exec documents comprise. The filenames that I use below at random, were created on my machine.
    file -b dictx2
    Mach-O 64-bit executable x86_64
    file -b mvim
    POSIX shell script text executable
    file -b fubar.cwk            # Finder Get Info says it is an AppleWorks document, and opens nicely in LibreOffice
    data
    The decision to delete these depends on what they are, the purpose they may continue to serve, and in the case of word processing documents, content for retention consideration.

  • 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.

  • My PDFs with form fields get "There was an error opening this document. The file is damaged and could not be repaired." on anothers computer, PC and MAC

    Im creating PDFs through InDesign and using Acrobat Pro 9 to add fields.  I save them to allow ADobe Reader people to use them.  Everything works fine on Pro and Reader on my end with a PC as well as someone elses PC.  But one person using Mac said some forms work and some dont.  Those that dont get the error "There was an error opening this document. The file is damaged and could not be repaired."  Ive resaved them and made sure they work and same problem.  There is nothing overly coplex about the PDFs either, a date field at the most.  They are using Reader 9.1.
    I found out the other day that one person who can open them adds info to them saves them and send over to that other person and cannot open any of them after they have been edited, same error.  He even tried on a PC and still gets it.
    I dont know what to do.  I know it has to be on his end and not mine.  What else can I suggest to him??

    It sounds like they are using an earlier version of Acrobat or Reader, though you said Reader 9.1. If you add some features in AA9 that are new, it appears that earlier versions see the new features as damaged files. At least that is my guess. Try using Reduce File Size or PDF Optimize to save to an earlier version and see if that helps. The other option is that you are getting them messed up in e-mail because many client look at PDF files as ascii and do not encrypt them. In that case force the encryption. You can also send them in ZIP form.

  • 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 Files how to open

    I have a disc from a design company which contains many Unix Executable Files. I have no idea what the content files extensions are and some of the files are quite large. The cotents are important for my job. Is there any way I can open these files? A 5 hour internet search and I'm no closer to a solution, I'm just more confused. I am scared to just try adding a 'guess' extention as the contents I am hoping to find are ai, psd or other hi res but there could be text data. I am scared of destroying stuff. Can anyone help me please?
    Thank you,
    Amanda

    If the file follows the "proper conventions", in terminal use the file command.  In terminal, type the command file followed by a space.  Then drag one of the files into the terminal window.  You will see a line that looks something like,
    file path-to-file
    Hit return.  If it's a file that the file command can recognize it will tell you what it thinks it is.  It it isn't it will tell you it's just a data file.
    If it's a executable mach-o file file will tell you that and for which architecture.  But if you are getting these files from some non-Mac system the odds are pretty good they can't be executed in the mac environment because they won't follow the mac architectural coding conventions or they aren't even mach-o executables in the first place.  If they did come from a mac system and are executable, then without any documentation on each file you can only guess at what they may do (or screw up).  Many unix tools have a convention where if you just execute them without any arguments they may give you some minimum help info on what they do.  But it may not.
    Not one of those files documents what on that CD?
    If file does recognize the file, say as a pdf, or text, etc., then you probably can use mac tools to open them.  For example, if it's pdf (gif, jpg, etc.) open it with preview.  If text, open with textedit.

  • Unix executable file won't open HELP!

    I am having the same problem as one other person, my word folder has changed to a Unix executable file and I can't open the content in the folders anymore.  I was just using the folder yesterday and now they are now working.  Please help!

    I'm not sure if this is your problem. But I was futzing with a file, and  intentionally removed most of it's attributes, as reported by the mdls command.
    I was able to get enough of them back, for the file to be recognized by the finder again.
    This command lists the different importers.
    $ mdimport -L
    find the one that matches the filetype. Then run the following, where testfile is the file that you're having problems with.
    mdimport -g /System/Library/Spotlight/XXXXXX.mdimporter testfile
    I don't use Word, so I can't tell you the name of the importer file that you need. It may be possible to just
    run
       mdimport testfile
    Nils

  • Need help opening Unix Executable Files

    I've recently been given the task of updating various files containing instruction manuals. However, the person who created these files is long gone and no one seems to know what program they were created in. All I know is that they are listed as "Unix Executable File" when I click on the document. I've tried opening them in TextEdit and this does me no good. Does anyone know how I can determine what program these files were originally created in so that I can open them?

    Files that have no filename extensions (used by Windows and OS X, but not by OS 9) and have lost their Type and Creator codes (used by OS 9, but not by Windows or OS X), and are then written to a DOS-formatted disc by OS 9 and copied back to a Mac disc, are usually if not always misidentified by the OS X Finder as Unix executables.
    Your company's old files, created in applications that ran in OS 9, probably have never had any filename extensions. Their Type and Creator codes have evidently been lost; those are what OS 9 uses to link the files to the applications that created them. If the files have also been written by OS 9 to any disk or flash drive formatted for Windows, i.e. FAT16 or FAT32, they have also lost their resource forks. The resource fork is a portion of a Mac file that has no analogous structure in a PC file. When a Mac file that contains data in its resource fork is written by OS 9 to a PC-formatted storage device, there's no place in the Windows file structure for that data — so it is simply discarded. When the Mac file is later copied back onto a Mac-formatted storage device, its resource fork is gone along with whatever data it contained, and the file may for all practical purposes be destroyed. OS X handles writing Mac files to Windows-formatted drives more gracefully, but passing files back and forth between OS 9 and OS X via a Windows-formatted storage device is asking for trouble.
    I don't know just what practices have been used in moving these files from the Macs they were created on to the one you're trying to open them on now, but I suspect there has been some unwitting demolition in the process.
    If copies of these files are still stored on the old Mac on which they were created, and that Mac still works, get on it and double-click the saved copies of the files to open them in the program(s) that created them, and make notes of which application opens each of the files. Be aware that the folder structure containing the files may have to be preserved exactly as it is for the files to open properly — do not reorganize anything. It may be essential, for example, for a PageMaker file to be kept in the same folder as all the individual files that have been "placed" in it using the Place command in PageMaker. If any of those files are moved elsewhere, they may be missing from the PageMaker document when it opens. I've never used Quark or Freehand, so I don't know whether they have the same requirement, or other requirements that are less than obvious.
    Any of the old manuals that you're able to open in their original applications can be saved as PDF files using an invaluable OS 9-based "printer driver" called PrintToPDF. They can then be opened in Adobe Reader or Preview on your G5 running OS X, though you won't be able to edit them easily. If you require the ability to edit these files on the G5, rather than on the old computer using the apps that originally created them, you will need first to discover which OS 9-based application created each one, and then ascertain what if any current OS X-based application is able to open the file format used by that old application. In the case of PageMaker files, that will probably be Adobe InDesign or nothing. InDesign may also open old Quark files; I don't know. Aldus or Adobe Freehand files may be openable using Adobe Illustrator. These are just guesses.
    Dragging and dropping the files onto MS Word or TextWrangler may reveal, buried somewhere in them, the name of the application(s) that created them. I know a PageMaker file, opened as plain text, will always contain the word "PageMaker". As for other file formats, I'm not sure.
    Message was edited by: eww
    Message was edited by: eww

Maybe you are looking for