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)

Similar Messages

  • 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

  • Photoshop files show as unix executable files

    Hi,
    I've have a back-up drive with all my old files (the past 15 years). After I copied them over I noticed that most of them showed up as unix executable files. The most of the Quark files I was able to repair by adding .qxp. When I add the appropriate extension to my Photoshop files, (.tif, .eps) and then try to open them, PS won't recognize the files. Is there a fix to this. Unfortunately the originals have disappeared with a drive that crashed.
    Thanks for any help.

    Adding file extensions for unique application-types will work fine as long as there's an entry for LaunchServices to reference to - add the .qxd extension will "make" them Quark files, for example. The more generic types are going to be the problem, as there are many applications listed in LaunchServices that can open TIFF and EPS files. If you had files that you could absolutely identify as raw Photoshop files, adding a .psd extension would most likely work for those.
    Maybe I just need to let all those files go...
    Since it seems that only the resource fork has been munged, the files are probably fine - just missing the resource fork with the Type/Creator code and the preview info that Photoshop stores there.
    -Doug

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

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

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

  • Help! FCE project files converted to unix executable files

    I recently added a USB external drive and put my FCE project files on it. When I rebooted, the files now are unrecognizable by Final Cut Express as project files. In the finder they are now recognized only as unix executable files. Is there any way to reverse this problem. I really can't afford to lose all that work! Thanks

    How is the drive formatted? If it's not Mac formatted you may have a problem. It may be recoverable. How many project files are you talking about? What about the media?

  • 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

  • Backup files are now Unix Executable files

    I backed up my iPhone on my laptop (pc) but when i but transferred all my iPhone backup files to my iMac there was a couple of folders that are now Unix Executable files which are coincidentally are the same backups that I cant use to restore my iPhone without receiving an error message.
    Also, is there a program that I can use to read the history.mapsdata file? 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).

  • Quark files show as unix executable files.

    I have a strange issue. This is an all mac enviornment. The iMac's are running 10.4.11, and Quark express 6.0 One of the iMac's show the quark files as unix executable files. All of the other mac's can open the files without any issue.
    On the iMac that has an issue, some of the folders show up as unix executable files as well. Also, there is a network share that is a log in item that should auto mount when the user logs in, it no longer mounts automatically. The only way to mount the share is by navigating through finder.
    I was able to open one of the quark files by using open, then save the file using save as. this appended the file extension. I also enabled file extensions in finder, and manually appended the extension and they still would not associate with Quark. The file I did a save as does associate with Quark but it is the only one.
    I repaired disk permissions and that did not help. Anyone have any ideas on this one?

    I also couldn't find the download link for xsupport on the link you provided.
    Looks like they have changed their business model. I just copied the URL out of the aboutbox of my copy of the Xsuppport toll but didn't crosscheck it.
    Does that give any indication on what the problem is?
    Not really, perhaps a corrupted or unreadable (by permission) .DS_Store file in the folder where your Xpress files reside, but then again that should affect other clients as well.
    Which leads to the question:
    When some clients have the correct mapping document <-> Quark Xpress and one (or more) other(s) don't, do you connect with different users to the server or are the users always the samr but the connection made from different machines?
    If youuse different users to connect, then the problem very like is on the server side (addess rights, etc). If the same user has different results on different machines, the problem's most likely a local one. In which case you coud try all of ManiMenu's clean and deep clean actions.

  • Mac olm outlook files exported as unix executable files

    Hi There,
    I had to export all my mail in outllook 2011 on my MacBookPro due to size limitations with my company exchange account.  When I tried to import the exported file, I noticed it was identified as "unix executable file" & outlook could not import it.  I have tried to change the file extension but my Mac continues to handle the file as "unix executable file".  I am in complete panic as my entire email archive is contained in this exported file & I am unable to access it.  Any help is appreciated.  Thanks. 

    I just tried it and my .olm file is simply a blank document with no application assigned to open it. You need to do a Get Info on the file and select the application to open the file. You might have better luck getting your question answered at the Microsoft Office for Mac Outlook forum - http://answers.microsoft.com/en-us/mac/forum/macoutlook.
    Good luck,
    Clinton

  • Unix Executable Files need to be Imported to ITunes

    I have numerous sound files that are listed as Unix Executable Files in Finder. I can Play the sounds within Finder, but cannot seem to import them into ITunes. I read in another thread to simply add ".mp3" (or some other suffix) and then import. I don't know what the suffix should be, but I have tried .mp3, .aiff, and .wav, with none working. Are there other types of sound files I can try? Is there a way to make them become .mp3 (or something usable)? I have them stored on the HD, but would like to be able to share them or burn them to CD. Any help is appreciated. Thanks.
    quicksilver power pc   Mac OS X (10.4.8)  

    I got them from another Mac user when I first bought my Mac. Unfortunately, I no longer have contact with him, so no way to ask where he got them from. I know he had never owned a PC, but that doesn't mean they weren't originally from one. Thanks for the help.
    quicksilver power pc   Mac OS X (10.4.8)  

  • 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

  • Opening a Unix Executable File

    I am a Mac newbie, switching from PC. I do embroidery digitizing and downloaded several embroidery designs in "zipped" format. When I viewed them in the Get Info dialog, they were listed as Unix Executable Files. When I tried to open one, a dialog box came up saying that I needed to choose a file to open them with. What program or helper app do I choose?
    Respectfully,
    Patricia

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

  • Converting Unix Executable Files for use in DVD Studio Pro

    I have several projects that were created in iDVD 2 back in 2002. In Finder, the file kind is listed as Unix Executable Files. If I add the extension .dvdproj using Get Info and try to open them in DVD Studio Pro, I get the error Wrong File Format and it will not open the project.
    The machine I am currently using does not have iDVD on it.
    Does anyone have a recommendation on a way to make these files usable for DVD Studio Pro? I understand if it is not possible.

    You can import iDVD project into DVD Studio Pro, however I think it won't work with projects from iDVD 5. I'm not sure about iDVD 2. Also these files have no extension and are listed as Unix Executable Files.

Maybe you are looking for