Problems of executive files after PC crash

My developing PC was crushed last week when LabView project was programming. The culprit is due to device driver conflict from both Keithley USB driver and NI 488.2 driver. After recovered the corrupted project, the executive files started showing errors like"LabVIEW:Memory is full"; "LabVIEW Load error code 33: Could not load front panel data logging...";"LabVIEW:End of file encountered" ; "LabVIEW load error code 12: Could not load connector type map" etc... when executive files were distributed to run-time PC.
I removed all LabView 8.0 developing suite and re-installed LabView 8.2. However, the problem was not resolved. The executive files are ruuning no problems on developing PC but failed on run-time PC.
I brought same source files to another developping PC and made executive files. They are also running fine on run-time PC. Really, I totally have no idea what's wrong with developping PC after crushed. How comes the installer and execution files start having problems even I re-installed LabVIEW? Thanks your kinding answer.

Some of those error codes have two possible causes. They are usually given as:
Possible reason(s):
LabVIEW: Some system capacity necessary for operation is not enabled.
=========================
NI-488: File system operation error.
Since you had problems with the NI-488 driver, my guess is that the possible reason is the second listed . Uninstalling and installing LabVIEW does not automatically uninstall and re-install the hardware drivers. Try doing a repair of NI-488 or completely uninstall that and re-install.

Similar Messages

Problems Recovering iPhoto files after a Crash

Hi All! I could really use assistance! I have an iMac running OS 10.6.8 with iPhoto '09 (v.8.1.2) The boot drive crashed and Genius Bar told me it was not recoverable and would need to be replaced. I couldn't even boot from install disk. I didn't belive them and took it home, tried booting from disc over and over until it finally worked. Repaired and reformatted with Disc Utility and restored from Time Machine. Things were a little funky, icons messed up etc. so I restored system sortware. Everything seems to be working well now EXCEPT for the last batch of photos I uploaded to iPhoto while the HD was in the process of dying.
Here's the wierd part, and the reason I am starting a new discussion. I haven't seen this particular problem on other threads. I can still see ALL photos (good and bad) as thumbnails, in both Events and Photos, I can create albums with the bad pix, but if I double click to see them full frame, or try to edit them I get the gray "!". I can't export the bad pix either. Even if I try exporting as current file type, I get the error message "Unasble to create..."
There is no logic I can figure out, why some are gone and some are working, all in the same set. Only thing I can think of is that the ones I modified in some way disappeared.
I searched for the file names of the missing photos, they are nowhere to be found. I opened the iPhoto Library, looked in both original and modified folders, and those pix are not in either, yet I can still see them in thumbnail versions. At this point I assume I have lost them for good, but I would love to at least save the thumbnail size versions and use them. BTW, the info on the bad photos still shows the name and file size corectly.
Any hints at all, how I can recover, or at least work with the thumbnails?
Thanks!
Escott

No, I never recoverd them. They are lost, other than the low rez thumbnails. Now when I donwload from my camera I leave them on the camera and only erase much later when I need the space. By that time Time Machine has backed them up.

Can't open file after Keynote crashed

I was working on a large Keynote file (about 130 Mb), when Keynote (4.0.1) quite unexpectedly. It happened a few times before, and I thought it was because of the instability of the new Leopard system. This time, however, I could not open the file after the crash. An error message was displayed: "Can't open file" followed by the path and the file name.
Does this happen to anyone else? Can anyone help? I hate to lose the work and go back to an early version.

Keynote and Leopard, especially in their newest iterations, are remarkably stable. That said, no file, program, or OS is totally immune from corruption. Whenever a program, or worse, your Mac, even starts to behave strangely, your first step ought to be to attend to it with a good fixit utility. Repairing permissions is usually fruitless, since it's highly unlikely there's a permissions problem. You already own *Disk Utility*, so you should try to repair the disk with that. Unfortunately, DU's disk repair is pretty wimpy, often unable to repair a problem, or erroneously reporting no problem when one obviously exists.
So, if you own a Mac, you owe it to yourself to buy at least one (but better, two) industrial-strength utility. There are really only three to choose from:
1. DiskWarrior is an absolute must. It's unbeatable in rebuilding the directory, and the directory is usually what's corrupted. It can now fix files, too, which is also helpful.
2. *TechTool Pro* is an excellent suite of fixits - directory, files, defrag, and some hardware tests. It also has a wonder feature, the eDrive. This is a small (10GB) bootable partition on your boot drive which has, among other things, TTP on it. If your main boot partition has a problem, you can boot from here and usually fix things. AFAIC, it's an absolute must on a laptop which you take on trips, far from your collection of fixit disks. You can also put DW on this partition, so you have everything you need right at your fingertips.
3. *Drive Genius* is a relative new-comer, also a good suite of fixits, and, I believe, does backups, too.
I have 1 and 2, and that has saved me from catastrophe more than once. 1 and 3 would probably be good, too. (You ought to have more than one of these serious apps because one can sometimes fix something another can't - different proprietary algorithms.)
One last thing: if you have anything on your computer it'd break your heart to lose (and who doesn't), remember +The First Rule of Computing+: There are two kinds of computer users: those who have already lost all their data at least once, and those who have not yet lost all their data at least once. So: *backup, backup, backup*. I vote for bootable clones, done often (at least daily if you work daily), TimeMachine is pretty good, and there are other options. Pick one, and do it religiously.

Problem store pdf file after downlod , message memery or store to little, the harddrive hav 1,3TB ;-

problem store pdf file after download from web. Message, store to littel from reader11. Where ist tht problem or the solution?
thanks

Dear Mr Willener
Thanks for the mail, that problem is soluted, press the botton, store as copy.I found it in secound read
A wish: In reader 9 is the solution better.
Regards from Ilmenau
L.Gleichmann
[signature and auto-quote removed by host]

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.

MISSING .indd file after Indesign crash

Using Indesign CC and Yosemite 10.10.2
I saved an .indd file to my hard drive successfully, tried to export as a PDF and it crashed.
And took the .indd file with it. It's not corrupted, it's simply GONE. And the PDF is a whopping 0k.
Indesign tried its best to recover after the crash, but needs the actual .indd file to do so, of course. First time Indesign CC crashed on me, actually.
I spotlight-searched my HD, trash, servers, everywhere. It's completely gone. or renamed? or hidden? I turned on hidden files via Terminal, not there. Restarted too.
Anybody had this happen?
Nope, I didn't have it backed up. Murphy's Law, the one time you put off backing up....

That's the gist of the first thread Bob suggested you see.
Removing programs tends to remove the file associations, too. You can either restore the association using Explorer, which will use the same icon for all version documents, or you can re-install which will restore the associations and enable the icon handler .dll to show you the correct icon for each version.
Not that it matters at this point, because the damage is done, but uninstalling older versions after installing new ones is generally poor practice and likely to remove something useful. If you are going to uninstall the old version, do it first. You can also create problems for yourself if you try to install an old version after the new one.
There's really not much reason to uninstall old versions of most Adobe products at all. The only one I know that won't co-exist nicely is Acrobat, and the installer will remove the old version for you these days. I still have ID installed going back to version 2, and you'd be surprised how often I want to open a legacy file in the original application.
Peter

Problem in Dimension File after securing Dimensions

Hi,
Why is there an error message "There is a problem in dimension file : ACCOUNT" in BPC for Excel if i do a "secure" and "R/W" on ACCOUNT dimension?
Actually this error message seems to happen to every dimension except for "Category" and "Entity", any idea why?
Cheers

Hi,
I do not believe that you can secure the Account dimensoin in BPC 5.1, you should however be able to secure all the other dimensions.
Can you please check if you have updated your Member Access Profiles after securing a new dimension. You need to add this new dimension to your Member Access Profile (for each applicaiton where the dimension is used), otherwise you will get error message in the Excel Front-End.
Regards,
Marcel

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.

Problems with Smart Album after Computer "crashed"

Hello
While working in Photoshop the cursor froze and nothing worked anymore so that I had to force the computer to shut down (while my aperture library was open). When I started the computer new. All the JPEG files that I created before were corrupt and the aperture library as well. I was working in a smart album and had about 1'000 pictures manually dragged together. When I started the library after the crash, the "custom-sort" was not functioning anymore. All pictures were sorted according to the image date. If I create a new smart album now, there is no more the possibility of "custom"-sort. Can someone please help me? Thank you very much in advance. Sarosa

I wrote some programs that will probably help:
This one removes the tracks that iTunes cannot find:
http://home.comcast.net/~teridon73/itunesscripts/itunesremovenotfound.zip
This one removes the duplicates (if they are exactly the same file, or one that is like "foofile.mp3", and "foofile 1.mp3")
http://home.comcast.net/~teridon73/itunesscripts/itunesremoveduplicates.zip

Problems publishing executable files

I am using Captivate 5 on PC and am having some trouble publishing executable files. We have a 3 slide (about 4 min) project with screen capture, audio and closed captioning. We need executables for both PC and MAC platforms. Her's my problem(s).
For PC (.exe) I'm getting a message that tells me the icon (.ico) file isn't right. What size should it be and should it be a single icon or a multi-res icon bundle?
For MAC (.app) First, I can't add an Icon. Anyone know why this option becomes "greyed out"?
And while the file seems to publish OK, when I try to run it on a MAC, it tells me the file is damaged. I can't begin to figure our why as it publishes the proper folder and (seemingly) all the right files and subfolders.
I've looked everywhere (but here (until now)) and I'm out of ideas.
Any help would be appreciated.
Coach Z

I've had Windows executable icon production problems in the past as well. This just appeared in the Cp5.5 help - and it worked for me (finally!):
Custom Icon
You can customize the icon that is displayed for the executable file. Click Browse (...) to add a custom icon for your file. Ensure that the icon file has a .ico extension (on Windows)/.icns (for Mac).(Applies only for Windows) You can create a custom icon file using any software meant for that purpose. Ensure that the file you create contains seven images of the following dimensions:
256x256 32-bit color image
48x48 32-bit color image
48x48 8-bit color image
32x32 32-bit color image
32x32 8-bit color image
16x16 32-bit color image
16x16 8-bit color image
Then I used this: http://icofx.ro/ - a really slick icon creater/packager. (.ico files can be a compilation of images)
Hope this helps others.

Problems "locating" referenced files after importing from iPhoto.

I recently began importing old iPhoto libraries to Aperture, mostly successfully, but have run into a couple problems locating referenced files. While the locate referenced files function worked for most of the photos, there are a handful of photos that, when I located the original file, the time stamp was different (by 2 hours in most cases) and it was about 15% smaller than the file Aperture was looking for. As a result, even though it was clear from the thumbnails that they were the same images, Aperture doesn't even give me the option to Reconnect them.
Aperture 3.4.5
OS X 10.7.5

. I use the Reconnect All button, but it only finds the one file, even when there are hundreds more in the same folder that are unlinked.
Reconnect all works best, if you select all files that need reconnecting at once, and then select the first file in the list to reconnect. If the other files are in the same folder and are correctly named and match, then "reconnect all" should do it. But if the filenames differ, you will have to do it one by one.
Also, the files are all still correctly linked in iPhoto, but every single link is broken once I import it to Aperture.
You are importing with "File > Import > Library", correct?
That is supposed to work. Have you tried to repair your iPhoto Library before importing to Aperture?
Use iPhotos First Aid Tools to repair:
Try to repair the permissions, followed by repairing the library.
To launch the First Aid Tools, hold down the Command and Option keys ⌥⌘ while double-clicking the iPhoto library or the iPhoto icon in the Dock.
The iPhoto Library First Aid dialog appears. Select the Repair option you want to use - first "permissions", then "database".
Léonie

Problem downloading JAR files after PIX 7.2(3) upgrade

Hello, I have upgraded a PIX 515 Firewall from Version 6.3(4) to
7.2(3) and am now experiencing problems downloading .jar files from
some web servers. I have tried disabling the "inspect http" option but
still not joy. I also tryied this:
http://www.cisco.com/warp/public/110/pix-asa-70-browse.pdf
But no luck.
Have anyone had similar problems.
Thanks in advance.

1. Turn router off for 30 seconds and on again
2. Settings>General>Reset>Reset Network Settings
3. Settings>General>Reset>Reset All Settings

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.

Problem with mp3 files after upgrading to iTunes 8.0

I have the following problem in iTunes after installing the 8.0 version:
I have noticed that certain (mp3 in this case) files do not play or download Album Cover from iTMS.
These files were in normal condition at least 1 day ago, before the update and I can still find them in my iPhone which has not been sync since the iTunes update.
Things I've done before posting:
1. Checked the files that they still exist in their original location as they are set in iTunes preferences.
2. Those files can be played either in Quick Time or in Finder Quick View (and Real Player and VLC).
3. I have restored the mp3 files from Time Machine but no solution found.
4. I have backed up and erased and created a new iTunes Library and tried to import them again on an empty library but nothing happened.
5. The files existed in iTunes (without Artwork which they did have previously) but I could not play them (double-click etc). Then I removed them, I cannot add them again (either by 'Add to Library' or by drag-drop)
6. Of course, I did a volume repair and permissions repair by booting from the OSX install DVD.
(edit) 7. I moved the files on my MacBook Pro and tried to add them in the iTunes there (completely empty and different library). This also had no result...
So after all these, the files are still not accepted in the iTunes but they still exist (and are playable) in my iPhone after yesterday's sync.
Any ideas? because i'm running short atm
Message was edited by: Periclesm

Had the same problem with the new update. I finally got back to my previous version by using system restore. After the restore I had to go to the "All Programs" list and click on Quicktime and iTunes individually to allow them to re-configure, then had to restart the computer again. After that all's well. My lbrary was intact.
I tried everything to get the newest version to work, including completely uninstalling my current versions of QT and iTunes, then downloading the latest directly from the Apple website, but, after 3 attempts, nothing worked. Guess I'll have to wait for the next update and try again.
By the way, your library is not actually stored in iTunes--it is stored in your Music folder, so you should not lose anything by uninstalling iTunes if you need to.

Unrepairable permission problems in some applications after hard crash.

Hi to all,
this is yet another topic for a problem I have concerning permissions repair on the root HDD. After a hard crash where Finder couldn't be relaunched, I was forced down to a hard reboot (Still looking for OS X reliability :-$).
Symptoms:
I clicked the "Repair permissions" button in Disk Utility, having selected "Macintosh HD" first.
I get this output, then "Repair complete":
Les autorisations sont différentes sur « System/Library/CoreServices/Front Row.app/Contents/CodeResources », elles devraient être -rw-r--r-- au lieu de lrw-r--r-- .
Les autorisations sont différentes sur « System/Library/CoreServices/Front Row.app/Contents/PlugIns/DVD.frappliance/Contents/CodeResources », elles devraient être -rw-r--r-- au lieu de lrw-r--r-- .
Les autorisations sont différentes sur « System/Library/CoreServices/Front Row.app/Contents/PlugIns/FRSettings.frappliance/Contents/CodeResources », elles devraient être -rw-r--r-- au lieu de lrw-r--r-- .
Les autorisations sont différentes sur « System/Library/CoreServices/Front Row.app/Contents/PlugIns/FRSources.frappliance/Contents/CodeResources », elles devraient être -rw-r--r-- au lieu de lrw-r--r-- .
Les autorisations sont différentes sur « System/Library/CoreServices/Front Row.app/Contents/PlugIns/Movies.frappliance/Contents/CodeResources », elles devraient être -rw-r--r-- au lieu de lrw-r--r-- .
Les autorisations sont différentes sur « System/Library/CoreServices/Front Row.app/Contents/PlugIns/Music.frappliance/Contents/CodeResources », elles devraient être -rw-r--r-- au lieu de lrw-r--r-- .
Les autorisations sont différentes sur « System/Library/CoreServices/Front Row.app/Contents/PlugIns/Photos.frappliance/Contents/CodeResources », elles devraient être -rw-r--r-- au lieu de lrw-r--r-- .
Les autorisations sont différentes sur « System/Library/CoreServices/Front Row.app/Contents/PlugIns/Podcasts.frappliance/Contents/CodeResources », elles devraient être -rw-r--r-- au lieu de lrw-r--r-- .
Les autorisations sont différentes sur « System/Library/CoreServices/Front Row.app/Contents/PlugIns/TV.frappliance/Contents/CodeResources », elles devraient être -rw-r--r-- au lieu de lrw-r--r-- .
Les autorisations sont différentes sur « System/Library/PrivateFrameworks/BackRow.framework/Versions/A/CodeResources » , elles devraient être -rw-r--r-- au lieu de lrw-r--r-- .
Les autorisations sont différentes sur « Users », elles devraient être drwxr-xr-x au lieu de lrwxr-xr-x .
Les autorisations sont différentes sur « Applications/iTunes.app/Contents/CodeResources », elles devraient être -rw-rw-r-- au lieu de lrw-rw-r-- .
Les autorisations sont différentes sur « Applications/iTunes.app/Contents/Frameworks/InternetUtilities.bundle/Contents /CodeResources », elles devraient être -rw-rw-r-- au lieu de lrw-rw-r-- .
Les autorisations sont différentes sur « Applications/iTunes.app/Contents/Resources/iTunesHelper.app/Contents/CodeReso urces », elles devraient être -rw-rw-r-- au lieu de lrw-rw-r-- .
Les autorisations sont différentes sur « System/Library/CoreServices/RawCamera.bundle/Contents/CodeResources », elles devraient être -rw-r--r-- au lieu de lrw-r--r-- .
Les autorisations sont différentes sur « System/Library/PrivateFrameworks/iLifeMediaBrowser.framework/Versions/A/CodeR esources », elles devraient être -rw-r--r-- au lieu de lrw-r--r-- .
Les autorisations sont différentes sur « System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/CodeResour ces », elles devraient être -rw-r--r-- au lieu de lrw-r--r-- .
Les autorisations sont différentes sur « System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/ Plugins/BlackAndWhiteEffect.IAPlugin/Contents/CodeResources », elles devraient être -rw-r--r-- au lieu de lrw-r--r-- .
Les autorisations sont différentes sur « System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/ Plugins/CubeTransition.IAPlugin/Contents/CodeResources », elles devraient être -rw-r--r-- au lieu de lrw-r--r-- .
Les autorisations sont différentes sur « System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/ Plugins/DissolveTransition.IAPlugin/Contents/CodeResources », elles devraient être -rw-r--r-- au lieu de lrw-r--r-- .
Les autorisations sont différentes sur « System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/ Plugins/DropletTransition.IAPlugin/Contents/CodeResources », elles devraient être -rw-r--r-- au lieu de lrw-r--r-- .
Les autorisations sont différentes sur « System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/ Plugins/FadeThroughBlackTransition.IAPlugin/Contents/CodeResources », elles devraient être -rw-r--r-- au lieu de lrw-r--r-- .
Les autorisations sont différentes sur « System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/ Plugins/FlipTransition.IAPlugin/Contents/CodeResources », elles devraient être -rw-r--r-- au lieu de lrw-r--r-- .
Les autorisations sont différentes sur « System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/ Plugins/MosaicFlipTransition.IAPlugin/Contents/CodeResources », elles devraient être -rw-r--r-- au lieu de lrw-r--r-- .
Les autorisations sont différentes sur « System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/ Plugins/MosaicFlipTransitionSmall.IAPlugin/Contents/CodeResources », elles devraient être -rw-r--r-- au lieu de lrw-r--r-- .
Les autorisations sont différentes sur « System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/ Plugins/PageFlipTransition.IAPlugin/Contents/CodeResources », elles devraient être -rw-r--r-- au lieu de lrw-r--r-- .
Les autorisations sont différentes sur « System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/ Plugins/PushTransition.IAPlugin/Contents/CodeResources », elles devraient être -rw-r--r-- au lieu de lrw-r--r-- .
Les autorisations sont différentes sur « System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/ Plugins/RevealTransition.IAPlugin/Contents/CodeResources », elles devraient être -rw-r--r-- au lieu de lrw-r--r-- .
Les autorisations sont différentes sur « System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/ Plugins/SepiaEffect.IAPlugin/Contents/CodeResources », elles devraient être -rw-r--r-- au lieu de lrw-r--r-- .
Les autorisations sont différentes sur « System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/ Plugins/TwirlTransition.IAPlugin/Contents/CodeResources », elles devraient être -rw-r--r-- au lieu de lrw-r--r-- .
Les autorisations sont différentes sur « System/Library/PrivateFrameworks/iPhotoAccess.framework/Versions/A/Resources/ Plugins/WipeTransition.IAPlugin/Contents/CodeResources », elles devraient être -rw-r--r-- au lieu de lrw-r--r-- .
(each line roughly translating as "Authorizations are different on xxx, they should be zzz instead of yyy)
Then it displays "Repair complete", not "Repair failed". Of course, when I run a "Check permissions" again, the exact same errors are still present.
Both my partitions are formatted as case-sensitive, journaled HFS+; is this setup prone to failure in case of crash? I was told by Epson Tech support, as side note, that this setup wasn't supported for their EPSON Scan 2.77A software.

Well, I never had these messages before, so I assume something changed, and my limited knowledge tells me it may have something to do with the crash.
I indeed tried to repair the disk in addition of the permissions, but Disk Utility told that disk doesn't need repair and is OK.
I'm not having persistent crashes in the sense that most of the time OS X is running smoothly, but whenever I try running it at a - subjective - full load, it starts to behave strangely, ultimately leading to unrecoverable crashes if I don't pay attention to close unneeded applications.
Of course, this is entirely subjective, and I don't have the exact words to describe what happens, let alone search for a possible solutions in the forums.

Problems of executive files after PC crash

Similar Messages

Maybe you are looking for