IMovie - Console message: Error writing to disk!   App indicates nothing..

My daughter spent hours working in iMovie v7.1.4, building a project. The system choked, in the end we went through a reboot and tried to reopen the project file. It indicated a 0s duration, with no pictures, music, etc...
Upon research, I notice that in the console messages, there are about 100+ messages in the following format. The application never once indicated there was an issue.
iMovie [[<PID>]] Project '/Users/<user>/Movies/iMovie Projects.localized/My First Project.rcproject' - save: Error writing to disk!
She was working in a user account that has parental restrictions. Not sure if this has any bearing...
Has anyone else ever had an issue like this? Where console indicates write errors, yet the application does not.

I would run Disk Utility and repair permissions. If that does not fix it, check to make sure that she has write access to the drive.

Similar Messages

  • Why is Premiere 6 giving a "Error writing file (disk full?)" message?

    Hello helpful experts,
    I'm using Premiere 6 on a Windows 7 machine.
    I have a file imported in to the timeline and it is set to play in reverse via the speed setting being set to -100 and it plays back in the preview window correctly, in reverse, when I click the play button.
    But when I do a  "File>Export Timeline>Movie" command I get an error message saying "An error occurred while making the movie. Error writing file (disk full?)"... but my hard drive is not nearly full, with over 30 gigs left open on it... and my RAM usage gadget shows over half of my RAM capacity is unused.
    Now previously, weeks ago on a different project, I was getting this same error message for a while when I would hit enter to preview my movie on the timeline (but that worked itself out somehow and eventually stopped giving me that error message).  But when I went to save and export, then I would not get the error message... now, it is just the opposite... I'm now getting the error message when trying to do an export and save the movie.
    And also now when I hit enter to preview, as opposed to just clicking the play button on the preview window, Premiere is going through the process of saving the movie since it is saving a temporary preview file... hopefully, since I'm getting this error message, I can find the temporary preview file and save it as my exported AVI file.
    But I still shouldn't be getting this error message when trying to save, or when trying to preview, as I did for a while a couple of weeks ago.
    Does anyone know about the erroneous error message that says, "An error occurred while making the movie. Error writing file (disk full?)"
    Thanks,
    numetro

    Depending on your hard drive size, P6 may be confused... since drives were not as large when it was written
    For Win7 64bit Pro or Ultimate (or Enterprise?) this is ONE example of using Virtual XP http://forums.adobe.com/thread/702693?tstart=0
    This is saved from an OLD message that may help
    File size limits by disk format type
    Fat = 2 Gig maximum file size
    Fat32 = 4 Gig
    NTFS = ?Terrabytes?
    Message saved from Premiere forum
    John Acocks - 07:52am Apr 17, 2003 Pacific
    I am unable to complete captures because I get a message
    that says "capture stopped because disk was full." What
    does this mean?
    Daniel Conklin - 08:02am Apr 17, 2003 Pacific (#1 of 2)   
    If you are using a Pinnacle card, a possible solution to
    this is to right click on the recycle bin, and set the
    percentage on your media drive to less than 2%.
    There a several other possible causes as well, but you
    need to supply some info about your system. How are you
    capturing and what format is your video? How big is
    your hard drive?
    Jeff Schell - 09:57am Apr 17, 2003 Pacific (#2 of 2)   
    this is one of my favorite error messages. Basically,
    you've chosen an incorrect setting in your DV settings.
    (Odds are you have DV settings). If so, read on:
    1. The DV format is very rigid. Meaning that if you
       make changes to the format, it cannot export as
       requested, because your movie file must match every
       single spec exactly.
    2. When Premiere goes to export a project, the DV codec
       says "Whoa. I can't do anything, because the settings
       don't match."
    3. Then Premiere comes back to you and has to report an
       error. (Don't shoot the messenger). Unfortunately,
       Premiere doesn't know why it wasn't able to export a
       movie. So it says to you, "Um... I can't make the movie.
       Um... maybe your hard drives are full?"
    It's a complete guess. And has nothing to do with your harddrives.
    Check your project settings and/or your export settings. Make
    sure you have chosen one of the "presets" that will specify
    every correct setting for you. Make sure it is one of the DV
    presets, if you are using DV video, or make sure it is one of
    the presets supplied by your capture card manufacturer (in this
    case I'm going to guess Pinnacle or Matrox.)
    To choose a preset, go to Project > Settings Viewer, and then
    click on the project settings column, and then click 'load' to
    load a correct preset. Do the same with export settings.

  • Itunes will not install. I get the error message "Error writing to file: C:\Program Files\Common Files\Apple\Mobile Device Support\com.apple.IE.client_main.dll     Verify that you have access to that directory."

    Itunes will not install. I get the error message "Error writing to file: C:\Program Files\Common Files\Apple\Mobile Device Support\com.apple.IE.client_main.dll     Verify that you have access to that directory."

    That one's consistent with disk/file damage. The first thing I'd try with that is running a disk check (chkdsk) over your C drive.
    XP instructions in the following document: How to perform disk error checking in Windows XP
    Vista instructions in the following document: Check your hard disk for errors
    Windows 7 instructions in the following document: How to use CHKDSK (Check Disk)
    Select both Automatically fix file system errors and Scan for and attempt recovery of bad sectors, or use chkdsk /r (depending on which way you decide to go about doing this). You'll almost certainly have to schedule the chkdsk to run on startup. The scan should take quite a while ... if it quits after a few minutes or seconds, something's interfering with the scan.
    Does the chkdsk find/repair any damage? If so, can you get an install to go through properly afterwards?

  • I cannot complete an installation of ITunes.  During the install, I receive the following error message:   Error writing to file: C:\Program Files\Bonjour\dns_sd.jar.

    I cannot complete an installation of ITunes.  During the install, I receive the following error message:
    Error writing to file: C:\Program Files\Bonjour\dns_sd.jar.

    That one's consistent with disk/file damage. The first thing I'd try with that is running a disk check (chkdsk) over your C drive.
    XP instructions in the following document: How to perform disk error checking in Windows XP
    Vista instructions in the following document: Check your hard disk for errors
    Windows 7 instructions in the following document: How to use CHKDSK (Check Disk)
    Select both Automatically fix file system errors and Scan for and attempt recovery of bad sectors, or use chkdsk /r (depending on which way you decide to go about doing this). You'll almost certainly have to schedule the chkdsk to run on startup. The scan should take quite a while ... if it quits after a few minutes or seconds, something's interfering with the scan.
    Does the chkdsk find/repair any damage? If so, can you get an install to go through properly afterwards?

  • Lost all photos on my iPhoto and get the ERROR WRITING TO DISK when trying to reload from Time Machine. iPhoto cannot import your photos because there was a problem writing to the volume containing your iPHOTO LIBRARY  . Looking for solution.

    Lost all photos on my iPhoto and get the ERROR WRITING TO DISK when trying to reload from Time Machine. iPhoto cannot import your photos because there was a problem writing to the volume containing your iPHOTO LIBRARY  . Looking for solution.

    Problems such as yours are sometimes caused by files that should belong to you but are locked or have wrong permissions. This procedure will check for such files. It makes no changes and therefore will not, in itself, solve your problem.
    First, empty the Trash, if possible.
    Triple-click anywhere in the line below on this page to select it, then copy the selected text to the Clipboard by pressing the key combination command-C:
    find ~ $TMPDIR.. \( -flags +sappnd,schg,uappnd,uchg -o ! -user $UID -o ! -perm -600 \) 2>&- | wc -l | pbcopy
    Launch the built-in Terminal application in any of the following ways:
    ☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
    ☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
    ☞ Open LaunchPad. Click Utilities, then Terminal in the icon grid.
    Paste into the Terminal window (command-V). The command may take a noticeable amount of time to run. Wait for a new line ending in a dollar sign ($) to appear.
    The output of the command will be a number. It's automatically copied to the Clipboard. Please paste it into a reply.
    The Terminal window doesn't show the output. Please don't copy anything from there.

  • Why does iPhoto say "Error writing to disk"?

    When I go on iPhoto I click on the "import all" button and try imorting my pictures from my iPhone to my mac and after a while of importing it completely stops and a window pops out saying "Error writing to disk" and I really don't know what to do to this solution.

    Hello JJ,
    Could be many things, we should start with this...
    "Try Disk Utility
    1. Insert the Mac OS X Install disc, then restart the computer while holding the C key.
    2. When your computer finishes starting up from the disc, choose Disk Utility from the Installer menu at the top of the screen. (In Mac OS X 10.4 or later, you must select your language first.)
    Important: Do not click Continue in the first screen of the Installer. If you do, you must restart from the disc again to access Disk Utility.
    3. Click the First Aid tab.
    4. Select your Mac OS X volume.
    5. Click Repair. Disk Utility checks and repairs the disk."
    http://docs.info.apple.com/article.html?artnum=106214
    Then try a Safe Boot, (holding Shift key down at bootup), run Disk Utility in Applications>Utilities, then highlight your drive, click on Repair Permissions, reboot when it completes.
    (Safe boot may stay on the gray radian for a long time, let it go, it's trying to repair the Hard Drive.)

  • I am trying to upgrade to itunes 10.7 using windows and keep getting the following error message: "Error writing to file: C:\Config.Msi\364460.rbf   Verify access to this dierctory". Help!

    I am trying to upgrade to itunes 10.7 using windows and keep getting the following error message: "Error writing to file: C:\Config.Msi\364460.rbf   Verify access to this dierctory". Help!

    Fixed! (win7 64 bit)! Just stop your antivirus during the upgrade/installation (I've got Kaspersky).
    Good luck!

  • Insufficient disk space / Error writing to Disk: when using photo library manager

    First I couldn't open my iphoto library (again!) so I am rebuilding my library (again- 4th time). NOW I'm told I donot  have sufficient disk space to import photos.
    Using OSX 10-9-5  Memory 4GB
    And just as I'm writing this I get Error Writing to disk memo
    iPhoto cannot import your photos because there was a problem writing to the volume containing your iPhoto library.

    Freeing Up Space on The Hard Drive
      1. See Lion/Mountain Lion/Mavericks' Storage Display.
      2. You can remove data from your Home folder except for the /Home/Library/ folder.
      3. Visit The XLab FAQs and read the FAQ on freeing up space on your hard drive.
      4. Also see Freeing space on your Mac OS X startup disk.
      5. See Where did my Disk Space go?.
      6. See The Storage Display.
    You must Empty the Trash in order to recover the space they occupied on the hard drive.
    You should consider replacing the drive with a larger one. Check out OWC for drives, tutorials, and toolkits.
    Try using OmniDiskSweeper 1.8 or GrandPerspective to search your drive for large files and where they are located.
    If you select the disk icon for your hard drive on the Desktop, then Press COMMAND-I to open the Get Info window. In the upper panel it will show your drive's space statistics - Capacity, Used, and Available. It is the latter you are interested in to see how much space is left on the drive. If you have less than 1 GB or so, then you must stop trying to write to the drive or you may corrupt it completely.

  • Premiere 6 error writing file - disk full?

    have premiere installed on new windows 7 pc. plenty of space. edited short (minute) video. went to render and get this error message saying error occurred while making the movie, eoor writing file...disk full?  saw forums on settings...am clueless as to where i went wrong? i uploaded via windows movie maker as avi? so discouraged. could anyone give me a clue as to whether i can do this??? and how??? thanks for any ideas.

    I don't have the particular notes file where I am (and it's so old I may not even have it at home) but for P6 that "disk full" message may mean the disk is full... and it may be a complete GUESS since "something happened" that P6 can't handle, so it throws up a message just to let you know that something went wrong
    I do know from past experience that P6 does NOT like AVI type 1, so you might check around to find a converter to convert your Type 1 file to an AVI Type 2 file with 16bit 48khz sound
    >uploaded via windows movie maker as avi
    What does that mean?
    Do you mean you have a tape based DV camcorder, and you are transferring files to your computer via Firewire?
    This is aimed at Premiere Pro, but may help
    Work through all of the steps (ideas) listed at http://ppro.wikia.com/wiki/Troubleshooting
    If your problem isn't fixed after you follow all of the steps, report back with ALL OF THE DETAILS asked for in the FINALLY section, the questions at the end of the troubleshooting link... most especially the codec used... see Question 1

  • Creative Cloud App Panel - Console message error

    i am running the new cc app manager
    On mac Pro OS X 10.7.5
    com.adobe.AdobeCreativeCloud: objc[296]: Class HTTPHeader is implemented in both /Applications/Utilities/Adobe Creative Cloud/AppsPanel/AppsPanelIL.dylib and /Applications/Utilities/Adobe Application Manager/UWA/UpdaterCore.framework/UpdaterCore. One of the two will be used. Which one is undefined.

    Aeleen_frisch then please contact our support team.  For the best assistance, I recommend our chat support at http://adobe.ly/yxj0t6.  Our chat representatives can provide a personalized experience to resolve the issue you have described.

  • Trying to update itunes for ipod touch.  Error message: error writing to file c:\Program /files (x86)\ itunes\itunes.resources\cs.lproj\djintro\objects.xib

    After 4 hours I am getting ready to throw my Acer out the window.  I have tried everything I can possible think of.  Initially couldn't sync ,y ipod but after following advice managed this.  Removed all itunes components on system but the above message continues to pop up on installling.  Any advice would be very much appreciated. 
    TIA

    That one's consistent with disk/file damage. The first thing I'd try with that is running a disk check (chkdsk) over your C drive.
    XP instructions in the following document: How to perform disk error checking in Windows XP
    Vista instructions in the following document: Check your hard disk for errors
    Windows 7 instructions in the following document: How to use CHKDSK (Check Disk)
    Select both Automatically fix file system errors and Scan for and attempt recovery of bad sectors, or use chkdsk /r (depending on which way you decide to go about doing this). You'll almost certainly have to schedule the chkdsk to run on startup. The scan should take quite a while ... if it quits after a few minutes or seconds, something's interfering with the scan.
    Does the chkdsk find/repair any damage? If so, can you get an install to go through properly afterwards?

  • IPhoto error writing to disk

    I'm trying to import photos into iPhoto and I get this :  iPhoto cannot import your photos because there was a problem writing to the volume containing your iPhoto library.  
    I've also gotten a message when trying to import from my iPhone4 that the photos are unregonizable or wrong format.

    Sounds like some kind of corruption on your disk - maybe repair permissions (a wild guess)? If no one answers soon, there is a separate iPhoto Forum that might be of help:
    https://discussions.apple.com/community/ilife/iphoto

  • HT1926 trying to download itunes 10.7 I get message; error writing to file: c:/program files/common fies/apple/apple application support/pluxil.exe verify that you have access to that directory.

    How can I get access to this application and install itunes 10.7?
    many thanks

    That one's consistent with disk/file damage. The first thing I'd try with that is running a disk check (chkdsk) over your C drive.
    XP instructions in the following document: How to perform disk error checking in Windows XP
    Vista instructions in the following document: Check your hard disk for errors
    Windows 7 instructions in the following document: How to use CHKDSK (Check Disk)
    Select both Automatically fix file system errors and Scan for and attempt recovery of bad sectors, or use chkdsk /r (depending on which way you decide to go about doing this). You'll almost certainly have to schedule the chkdsk to run on startup. The scan should take quite a while ... if it quits after a few minutes or seconds, something's interfering with the scan.
    Does the chkdsk find/repair any damage? If so, can you get an install to go through properly afterwards?

  • Console message errors

    mac pro 3.1 osx 10.8.5
    I get these errors in my console
    what do i have to do with NSImage warning and what with SMC error ???
    18/10/14 3:25:19.633 PM DashboardClient[410]: *** WARNING: -[NSImage compositeToPoint:operation:] is deprecated in MacOSX 10.8 and later. Please use -[NSImage drawAtPoint:fromRect:operation:fraction:] instead.
    18/10/14 3:25:19.633 PM DashboardClient[410]: *** WARNING: -[NSImage compositeToPoint:fromRect:operation:] is deprecated in MacOSX 10.8 and later. Please use -[NSImage drawAtPoint:fromRect:operation:fraction:] instead.
    18/10/14 3:25:19.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TC0H kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff801665c000
    18/10/14 3:25:19.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TG0P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff801665c000
    18/10/14 3:25:19.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TO0P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff801665c000
    18/10/14 3:25:19.000 PM kernel[0]: SMC::smcReadKeyAction ERROR Th0H kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff801665c000
    18/10/14 3:25:19.000 PM kernel[0]: SMC::smcReadKeyAction ERROR Th1H kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff801665c000
    18/10/14 3:25:19.000 PM kernel[0]: SMC::smcReadKeyAction ERROR Th2H kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff801665c000
    18/10/14 3:25:19.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TG0H kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff801665c000
    18/10/14 3:25:19.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TG1H kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff801665c000
    18/10/14 3:25:19.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TG0D kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff801665c000
    18/10/14 3:25:19.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TB0T kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff801665c000
    18/10/14 3:25:19.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TB1T kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff801665c000
    18/10/14 3:25:19.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TB2T kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff801665c000
    18/10/14 3:25:19.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TB3T kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff801665c000
    18/10/14 3:25:19.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TN0P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff801665c000
    18/10/14 3:25:19.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TN1P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff801665c000
    18/10/14 3:25:19.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TM4S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff801665c000
    18/10/14 3:25:19.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TM5S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff801665c000
    18/10/14 3:25:19.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TM6S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff801665c000
    18/10/14 3:25:19.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TM7S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff801665c000
    18/10/14 3:25:19.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TMCS kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff801665c000
    18/10/14 3:25:19.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TMDS kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff801665c000
    18/10/14 3:25:19.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TMES kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff801665c000
    18/10/14 3:25:19.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TMFS kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff801665c000
    18/10/14 3:25:19.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TM3P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff801665c000
    18/10/14 3:25:19.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TM4P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff801665c000
    18/10/14 3:25:19.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TM5P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff801665c000
    18/10/14 3:25:19.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TM6P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff801665c000
    18/10/14 3:25:19.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TM7P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff801665c000
    18/10/14 3:25:19.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TMBP kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff801665c000
    18/10/14 3:25:19.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TMCP kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff801665c000
    18/10/14 3:25:19.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TMDP kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff801665c000
    18/10/14 3:25:19.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TMEP kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff801665c000
    18/10/14 3:25:19.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TMFP kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff801665c000
    18/10/14 3:25:19.000 PM kernel[0]: SMC::smcReadKeyAction ERROR Tm0P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff801665c000
    18/10/14 3:25:19.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TW0P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff801665c000
    18/10/14 3:25:19.000 PM kernel[0]: SMC::smcReadKeyAction ERROR Tp0P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff801665c000
    18/10/14 3:25:19.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TA0S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff801665c000
    18/10/14 3:25:19.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TA1S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff801665c000
    18/10/14 3:25:19.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TA2S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff801665c000
    18/10/14 3:25:19.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TA3S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff801665c000
    18/10/14 3:25:19.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TA1P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff801665c000
    18/10/14 3:25:19.000 PM kernel[0]: SMC::smcReadKeyAction ERROR Tp1P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff801665c000
    18/10/14 3:25:19.000 PM kernel[0]: SMC::smcReadKeyAction ERROR Tp2P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff801665c000
    18/10/14 3:25:19.000 PM kernel[0]: SMC::smcReadKeyAction ERROR Tp3P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff801665c000
    18/10/14 3:25:19.000 PM kernel[0]: SMC::smcReadKeyAction ERROR Tp4P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff801665c000
    18/10/14 3:25:19.000 PM kernel[0]: SMC::smcReadKeyAction ERROR Tp5P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff801665c000
    18/10/14 3:25:19.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TC0H kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff801665c000
    18/10/14 3:25:19.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TG0P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff801665c000
    18/10/14 3:25:19.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TO0P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff801665c000
    18/10/14 3:25:19.000 PM kernel[0]: SMC::smcReadKeyAction ERROR Th0H kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff801665c000
    18/10/14 3:25:19.000 PM kernel[0]: SMC::smcReadKeyAction ERROR Th1H kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff801665c000
    18/10/14 3:25:19.000 PM kernel[0]: SMC::smcReadKeyAction ERROR Th2H kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff801665c000
    18/10/14 3:25:19.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TG0H kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff801665c000
    18/10/14 3:25:19.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TG1H kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff801665c000
    18/10/14 3:25:19.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TG0D kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff801665c000
    18/10/14 3:25:19.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TB0T kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff801665c000
    18/10/14 3:25:19.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TB1T kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff801665c000
    18/10/14 3:25:19.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TB2T kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff801665c000
    18/10/14 3:25:19.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TB3T kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff801665c000
    18/10/14 3:25:19.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TN0P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff801665c000
    18/10/14 3:25:19.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TN1P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff801665c000
    18/10/14 3:25:19.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TM4S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff801665c000
    18/10/14 3:25:19.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TM5S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff801665c000
    18/10/14 3:25:19.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TM6S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff801665c000
    18/10/14 3:25:19.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TM7S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff801665c000
    18/10/14 3:25:19.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TMCS kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff801665c000
    18/10/14 3:25:19.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TMDS kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff801665c000
    18/10/14 3:25:19.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TMES kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff801665c000
    18/10/14 3:25:19.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TMFS kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff801665c000
    18/10/14 3:25:19.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TM3P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff801665c000
    18/10/14 3:25:19.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TM4P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff801665c000
    18/10/14 3:25:19.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TM5P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff801665c000
    18/10/14 3:25:19.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TM6P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff801665c000
    18/10/14 3:25:19.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TM7P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff801665c000
    18/10/14 3:25:19.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TMBP kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff801665c000
    18/10/14 3:25:19.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TMCP kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff801665c000
    18/10/14 3:25:19.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TMDP kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff801665c000
    18/10/14 3:25:19.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TMEP kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff801665c000
    18/10/14 3:25:19.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TMFP kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff801665c000
    18/10/14 3:25:19.000 PM kernel[0]: SMC::smcReadKeyAction ERROR Tm0P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff801665c000
    18/10/14 3:25:19.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TW0P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff801665c000
    18/10/14 3:25:19.000 PM kernel[0]: SMC::smcReadKeyAction ERROR Tp0P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff801665c000
    18/10/14 3:25:19.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TA0S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff801665c000
    18/10/14 3:25:19.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TA1S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff801665c000
    18/10/14 3:25:19.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TA2S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff801665c000
    18/10/14 3:25:19.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TA3S kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff801665c000
    18/10/14 3:25:19.000 PM kernel[0]: SMC::smcReadKeyAction ERROR TA1P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff801665c000
    18/10/14 3:25:19.000 PM kernel[0]: SMC::smcReadKeyAction ERROR Tp1P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff801665c000
    18/10/14 3:25:19.000 PM kernel[0]: SMC::smcReadKeyAction ERROR Tp2P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff801665c000
    18/10/14 3:25:19.000 PM kernel[0]: SMC::smcReadKeyAction ERROR Tp3P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff801665c000
    18/10/14 3:25:19.000 PM kernel[0]: SMC::smcReadKeyAction ERROR Tp4P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff801665c000
    18/10/14 3:25:19.000 PM kernel[0]: SMC::smcReadKeyAction ERROR Tp5P kSMCBadArgumentError(0x89) fKeyHashTable=0x0xffffff801665c000

    If everything is working properly, ignore them.

  • Error writing to disk

    I use iPhoto 09 a Olympus E-520
    up till today uploading was simple and worked like a charm, and I'm not even sure if this is the right place to put my question.
    I just came back from a event and used up all my camera card's memory, and trying to upload, it uploads what seems like normal, until half way through or so, and it gives me this error message
    http://images.plurk.com/1426340_fab5e5ffc34f60259f3906cfc9986f05.jpg
    and I tried unplugging and plugging in a different usb port (just to see if that wouldn't fix it) and the same thing happened.
    So question: What's going on? How can I fix it/get things back to normal?

    Hi All,
    I had a similar problem after upgrading to iPhoto 09. I use a Canon Powershot SD750 and have CHDK software installed on the memory stick. I have several .crw and other program files for the CHDK software on the memory stick. I solved the problem by selecting the jpg versions of the photos I wanted to import rather than just selecting "import all". This worked for me, and hope it does for you too.
    Cheers,
    Dustin

Maybe you are looking for