Serious Unarchive and Applescript Errors

I have run into a little problem.
After cleaning up some of my applications, something went weird and I can not unarchive a file using the OS BOMarchivehelper and several applications give me applescript errors.
When I try to unzip a file, I get this error:
Unable to unarchive: "CoreDuoTemp.zip" into "Downloads". (Error 32 - Broken Pipe.)
When I use another app to unzip the coreduo app, and attempt to run the app I get this error:
AppleScript Error
sh: line 1: top: command not found
sh: line 1: grep: command not found
sh: line 1: cut: command not found(127)
another app brings up:
sh: line 1: defaults: command not found(127)
I have googled these errors and nothing useful has come up. If anyone has any ideas as to how get these two portions of the OS to function properly (without reinstalling), I would greatly appreciate it.

There are at least 3 possibilities here as all those commands are in the /usr/bin/ folder with Mac OS X 10.5.1
1. You've deleted the /usr/bin folder or maybe just reset it's permissions.
2. You've deleted or munged the setup file (probably bash.rc or profile.rc) for the shell you're using so that it isn't setting the "path" variable correctly. Execute "echo $PATH" in terminal to show it. It should contain several colon separated posix paths and appear something like this -
/bin:/opt/local/bin:/opt/local/sbin:/sw/bin:/sw/sbin:/bin:/sbin:/usr/bin:/usr/sb in
3. If you are in single user mode, you haven't typed in the full path to the commands i.e. "/usr/bin/defaults"
Try "/usr/bin/whereis top" in your shell to see if it exists. If it doesn't return a path to the command or otherwise errors, you might want to re-install the Mac's OS as you may have a lot of stuff missing. If it does return a path then it's either item 2 or 3.
Note: As "whereis" is also located in /usr/bin it will not work if the folder is gone or damaged.

Similar Messages

  • Internal error 10014, 7686536,7686826, 10069773. FrameMaker has detected a serious problem and must

    Hi,
    I am getting the below error whenever I try to run the extend script. Please let me know how to solve the issue.
    "Internal error 10014, 7686536,7686826, 10069773. FrameMaker has detected a serious problem and must quit.
    A file named "C:\Documents and Settings\valee\Application Data\Adobe\FrameMaker\10\FrameLog_11.07.28_15.41.01.txt" has been generated which contains information that may help Frame development improve the product for future releases."
    Review the file content here:
    === Header Begin ===
    Internal Error: 10014, 7686536, 7686826, 10069773
    FrameMaker 10.0.1 for Intel
    Build: 10.0.1.402
    Window System: MSWindows
    Operating System: Windows NT 5.1 (major.minor.build: 5.1.2600 Service Pack 3)
    Generated on: Thursday, July 28, 2011 3:41:01 PM
    To file: C:\Documents and Settings\valee\Application Data\Adobe\FrameMaker\10\FrameLog_11.07.28_15.41.01.txt
    === Header End ===
    === Stack Trace Begin ===
    $754988
    $754aaa
    $99a70d
    === Stack Trace End ===
    === Open Window List Begin ===
    # not implemented
    === Open Window List End ===
    === Recent Commands Begin ===
    === Recent Commands End ===
    === Recent API Calls Begin ===
    # not implemented
    === Recent API Calls End ===
    === Windows Relocation Information Begin ===
    Application: 00400000
    FrameMaker.exe: 00400000 0092f000
    ntdll.dll: 7c900000 000b2000
    kernel32.dll: 7c800000 000f6000
    FMRuntime.dll: 10000000 00042000
    USER32.dll: 7e410000 00091000
    GDI32.dll: 77f10000 00049000
    tbb.dll: 00350000 00020000
    MSVCP90.dll: 78480000 0008e000
    MSVCR90.dll: 78520000 000a3000
    FMGridCtrl.dll: 00370000 0002c000
    mfc90u.dll: 789e0000 003a1000
    SHLWAPI.dll: 77f60000 00076000
    ADVAPI32.dll: 77dd0000 0009b000
    RPCRT4.dll: 77e70000 00093000
    Secur32.dll: 77fe0000 00011000
    msvcrt.dll: 77c10000 00058000
    COMCTL32.dll: 773d0000 00103000
    MSIMG32.dll: 76380000 00005000
    OLEAUT32.dll: 77120000 0008b000
    ole32.dll: 774e0000 0013e000
    Asn.er.dll: 003b0000 0003c000
    OLECLI32.dll: 71e10000 00015000
    MPR.dll: 71b20000 00012000
    AdobePSL.dll: 00d30000 00d0d000
    FMBMP2Tiff.dll: 01a40000 00006000
    libtiff.dll: 01a50000 00085000
    zlib1.dll: 01ae0000 00013000
    MSVCP60.dll: 76080000 00065000
    FMTiff2PS.dll: 01b00000 0000b000
    COMDLG32.dll: 763b0000 00049000
    SHELL32.dll: 7c9c0000 00817000
    gdiplus.dll: 4ec50000 001ab000
    USP10.dll: 74d90000 0006b000
    FMDBMS32.dll: 01b10000 0000e000
    oledlg.dll: 7df70000 00022000
    VERSION.dll: 77c00000 00008000
    WININET.dll: 3d930000 000d1000
    Normaliz.dll: 01b20000 00009000
    iertutil.dll: 3dfd0000 00045000
    WINSPOOL.DRV: 73000000 00026000
    amtlib.dll: 01b30000 000ee000
    AIDE.dll: 01c30000 00064000
    MSVCR80.dll: 78130000 0009b000
    MSVCP80.dll: 7c420000 00087000
    BIB.dll: 01cb0000 00049000
    CoolType.dll: 01d10000 002fb000
    SVGRE.dll: 6f130000 00332000
    icuuc32.dll: 4a800000 00095000
    icudt32.dll: 4ad00000 0095a000
    MSVCR71.dll: 7c340000 00056000
    icuin32.dll: 4a900000 000aa000
    NetLib.dll: 02030000 0001e000
    CoreTypes.dll: 30100000 00026000
    NetIO.dll: 30900000 00018000
    LIBCURL.dll: 30000000 00023000
    WS2_32.dll: 71ab0000 00017000
    WS2HELP.dll: 71aa0000 00008000
    WINMM.dll: 76b40000 0002d000
    SSLEAY32.dll: 02090000 00027000
    LIBEAY32.dll: 020c0000 000d1000
    WSOCK32.dll: 71ad0000 00009000
    icuio32.dll: 4ab00000 0000b000
    MSVCP71.dll: 7c3a0000 0007b000
    AdobePDFL.dll: 021a0000 0067b000
    AdobeXMP.dll: 02830000 0004c000
    JP2KLib.dll: 02890000 000aa000
    BIBUtils.dll: 02950000 00040000
    AGM.dll: 029a0000 0059d000
    AXE8SharedExpat.dll: 02f50000 0002e000
    XAPToolkitRelease.dll: 02f90000 0008b000
    AdobeXMPFiles.dll: 03030000 0006c000
    AdobeLinguistic.dll: 030b0000 001af000
    PSAPI.DLL: 76bf0000 0000b000
    AdobeOwl.dll: 03270000 00156000
    AdobeOwlCanvas.dll: 033e0000 00048000
    LogSession.dll: 03440000 00056000
    SETUPAPI.dll: 77920000 000f3000
    adbeape.dll: 034b0000 00009000
    ahclient.dll: 034d0000 00021000
    IMM32.DLL: 76390000 0001d000
    LPK.DLL: 629c0000 00009000
    tbbmalloc.dll: 03a30000 0000a000
    UxTheme.dll: 5ad70000 00038000
    MFC90ENU.DLL: 5d360000 0000d000
    rdpsnd.dll: 5dac0000 00008000
    WINSTA.dll: 76360000 00010000
    NETAPI32.dll: 5b860000 00055000
    MSCTF.dll: 74720000 0004c000
    fmres.dll: 0ad90000 0025e000
    fmdlg.dll: 04c40000 00064000
    fmcustom.dll: 04cb0000 0005d000
    msctfime.ime: 755c0000 0002e000
    amtservices.dll: 0b0f0000 00112000
    IPHLPAPI.DLL: 76d60000 00019000
    WINHTTP.dll: 4d4f0000 00059000
    adobe_caps.dll: 0b460000 0006a000
    NTMARTA.DLL: 77690000 00021000
    SAMLIB.dll: 71bf0000 00013000
    WLDAP32.dll: 76f60000 0002c000
    asneu.dll: 0b5f0000 00028000
    xpsp2res.dll: 0b840000 002c5000
    CLBCATQ.DLL: 76fd0000 0007f000
    COMRes.dll: 77050000 000c5000
    wbemprox.dll: 74ef0000 00008000
    wbemcomn.dll: 75290000 00037000
    wbemsvc.dll: 74ed0000 0000e000
    fastprox.dll: 75690000 00076000
    NTDSAPI.dll: 767a0000 00013000
    DNSAPI.dll: 76f20000 00027000
    updaternotifications.dll: 0be20000 00092000
    mstask.dll: 75830000 00045000
    USERENV.dll: 769c0000 000b4000
    owlres.dll: 0b640000 000ae000
    NetIODav.dll: 30a00000 0002c000
    xerces-c_2_7.dll: 12000000 0019e000
    rsaenh.dll: 68000000 00036000
    unidrvui.dll: 7e5a0000 000ba000
    mxdwdrv.dll: 3f500000 000c0000
    FontSub.dll: 69310000 00017000
    ATMLIB.dll: 73c20000 0000b000
    adbeapecore.dll: 0c810000 0001b000
    ACE.dll: 0c940000 000fe000
    dvaadameve.dll: 0d580000 00354000
    boost_threads.dll: 0d8f0000 0000e000
    dvacore.dll: 0d910000 0018c000
    dvaui.dll: 0dab0000 00381000
    OPENGL32.dll: 5ed00000 000cc000
    GLU32.dll: 68b20000 00020000
    DDRAW.dll: 73760000 0004b000
    DCIMAN32.dll: 73bc0000 00006000
    WTSAPI32.dll: 76f50000 00008000
    clickprt.dll: 0bff0000 0002f000
    fmmediaannot.dll: 0c020000 0004a000
    frame2pdf.dll: 0e470000 00044000
    mailer.dll: 0c070000 00039000
    MAPI32.DLL: 61e00000 0001f000
    bookerrlog.dll: 0e4c0000 0003a000
    ditamaperrlog.dll: 0e500000 0003a000
    pdfsize.dll: 0e540000 0003d000
    fmpdfreflow.dll: 0e580000 00041000
    ecm.dll: 0e5d0000 000c3000
    sgen.dll: 0e6a0000 000a8000
    dispatch.dll: 0e760000 000cf000
    trnslate.dll: 0e850000 0022b000
    Xalan-C_1_10.dll: 0eb10000 001f8000
    XalanMessages_1_10.DLL: 0ea90000 00007000
    GoMarkup.dll: 0ed10000 0013b000
    GoCore.dll: 0ee50000 00081000
    SCL.dll: 0eaa0000 00044000
    xmlcss.dll: 0f040000 001f8000
    docbook.dll: 0f250000 001f3000
    xhtml.dll: 0f460000 001f2000
    qstart.dll: 0f670000 0002f000
    cnvschma.dll: 0f6a0000 00093000
    u3dfilter.dll: 0f750000 00038000
    rt3d.dll: 0f790000 00327000
    ditafm.dll: 0fad0000 00281000
    ditafm_app.dll: 0fd70000 00210000
    find_references.dll: 10050000 000a2000
    PDFCommentsImport.dll: 10100000 00078000
    InitCharMap.dll: 0ffa0000 00031000
    PreserveEntity.dll: 10180000 001ed000
    FrameMakerScriptingSupport.dll: 10370000 0025b000
    ExtendScript.dll: 105d0000 000a6000
    ScCore.dll: 10690000 00091000
    RoboHelpPublish.dll: 10840000 00042000
    AdobeCaptivatePlugin.dll: 10890000 0004a000
    AdobeIllustratorPlugin.dll: 108e0000 00030000
    mapper.dll: 10910000 00057000
    masterpages.dll: 10970000 00036000
    PhotoshopPlugin.dll: 109b0000 00031000
    RHFrameMakerServer10.dll: 109f0000 00032000
    RoboScreenCapturePlugin.dll: 10a50000 00031000
    tablesort.dll: 10a90000 00037000
    TextEditorPlugin.dll: 10ad0000 00031000
    WebWorks.FrameMaker9.Client.dll: 10b10000 0003b000
    AdobeSWFL.dll: 10b60000 00843000
    OLEACC.dll: 74c80000 0002c000
    CRYPT32.dll: 77a80000 00095000
    MSASN1.dll: 77b20000 00012000
    urlmon.dll: 113c0000 00128000
    mscms.dll: 73b30000 00015000
    DSOUND.dll: 73f10000 0005c000
    dbghelp.dll: 59a60000 000a1000
    mlang.dll: 75cf0000 00091000
    icm32.dll: 66e90000 00041000
    WINTRUST.dll: 76c30000 0002e000
    IMAGEHLP.dll: 76c90000 00028000
    wdmaud.drv: 72d20000 00009000
    msacm32.drv: 72d10000 00008000
    MSACM32.dll: 77be0000 00015000
    midimap.dll: 77bd0000 00007000
    schannel.dll: 767f0000 00028000
    RASAPI32.dll: 76ee0000 0003c000
    rasman.dll: 76e90000 00012000
    TAPI32.dll: 76eb0000 0002f000
    rtutils.dll: 76e80000 0000e000
    msv1_0.dll: 77c70000 00025000
    cryptdll.dll: 76790000 0000c000
    sensapi.dll: 722b0000 00005000
    mswsock.dll: 71a50000 0003f000
    rasadhlp.dll: 76fc0000 00006000
    hnetcfg.dll: 662b0000 00058000
    wshtcpip.dll: 71a90000 00008000
    appHelp.dll: 77b40000 00022000
    cscui.dll: 77a20000 00054000
    CSCDLL.dll: 76600000 0001d000
    browseui.dll: 75f80000 000fd000
    ntshrui.dll: 76990000 00025000
    ATL.DLL: 76b20000 00011000
    shdocvw.dll: 7e290000 00173000
    CRYPTUI.dll: 754d0000 00080000
    === Windows Relocation Information End ===
    === Windows Exception Information Begin ===
    [Exception Record]
    0012be90: c0000005 00000000 00000000 103c150c
    0012bea0: 00000002 00000000 00000000 0001003f
    0012beb0: 00000000 00000000 00000000 00000000
    0012bec0: 00000000 00000000 ffff027f ffff0100
    0012bed0: ffffffff 106c2676 05d8001b 00000000
    [Exception Context]
    0012beac: 0001003f 00000000 00000000 00000000
    0012bebc: 00000000 00000000 00000000 ffff027f
    0012becc: ffff0100 ffffffff 106c2676 05d8001b
    0012bedc: 00000000 ffff0023 00000000 00000000
    0012beec: 00800000 00800080 ffff0080 00000000
    0012befc: 80000000 0000c003 00000000 4004e000
    0012bf0c: 00000000 e8000000 00004004 00000000
    0012bf1c: 4004c000 00000000 e8000000 00004004
    0012bf2c: 00000000 7fffc000 00000000 00000000
    0012bf3c: 0000003b 00000023 00000023 00000000
    0012bf4c: 1ff10000 00000000 1ff10000 0012c264
    0012bf5c: 00000000 0d433820 103c150c 0000001b
    0012bf6c: 00250212 0012c178 00000023 0100027f
    0012bf7c: 05d80000 106c2676 0000001b 00000000
    0012bf8c: 00000023 00001fa1 0000ffff 00000000
    0012bf9c: 00000000 00000000 00000000 00800080
    0012bfac: 00800080 0000ffff 00000000 00000000
    0012bfbc: 80000000 0000c003 00000000 00000000
    0012bfcc: e0000000 00004004 00000000 00000000
    0012bfdc: e8000000 00004004 00000000 00000000
    0012bfec: c0000000 00004004 00000000 00000000
    0012bffc: e8000000 00004004 00000000 00000000
    0012c00c: c0000000 00007fff 00000000 0000002b
    0012c01c: 00000000 00000433 00000000 00000000
    0012c02c: 40240000 00000000 00000000 00000000
    0012c03c: 8a45f1c8 00000001 00000001 00000000
    0012c04c: 8054c127 00000000 34306847 00000000
    0012c05c: a201c954 bf802b2f 00000000 00000000
    0012c06c: 408fe000 00000000 00000000 ba338540
    0012c07c: 00000000 806e7410 8968bb20 a201ca74
    0012c08c: 00000000 806e7427 00000008 0377de70
    0012c09c: 0377df0a 0377de70 77f6797d 0377e0c4
    0012c0ac: 00000000 7c9c6ec8 0377e0c4 77f64de0
    0012c0bc: 00000000 0377e0a0 77f67abb 0377e0c4
    0012c0cc: 0377de94 7c9c63f0 7cbcfef4 77f67ad4
    0012c0dc: 77f64de0 0377e0c4 006f0053 00740066
    0012c0ec: 00610077 00650072 004d005c 00630069
    0012c0fc: 006f0072 006f0073 00740066 0057005c
    0012c10c: 006e0069 006f0064 00730077 0043005c
    0012c11c: 00720075 00650072 0074006e 00650056
    0012c12c: 00730072 7c90cffa 77dd6c03 00000b2c
    0012c13c: 00000002 0377e030 77f643e0 0000ffff
    0012c14c: 0377e07c 00000004 00000002 0377eb70
    0012c15c: 7c9c94f8 77f643ed 7c9c94f8 00000004
    0012c16c: 00000000 0377e07c 00000b2c
    === Windows Exception Information End ===
    === Windows Stack Traceback Begin ===
    === Windows Stack Traceback End ===
    Regards,
    Valee

    Thanks for your swift response. Here is my small script.
    var doc = app.ActiveDoc();
    var tbl = doc.FirstTblInDoc;
    while (tbl.ObjectValid()){
        $.writeln ("Loop through doc tables: " + tbl.ObjectValid());
        tbl.NextTblInDoc
    My another small script is:
    alert("Hi Valee");
    I am trying to run it from my FrameMaker 10 (Version: 10.0.1.402). Also I have updated the latest patch versions.
    Regards,
    Valee

  • I am trying to load a calpatch to a program called Caldera, but i keep getting the following "AppleScript Error – Terminal got an error:apple event timed out ( -1712)" my IOS is Yosemite, and i am running the latest version of the caldera program

    I am trying to load a calpatch to a program called Caldera, but i keep getting the following “AppleScript Error – Terminal got an error:apple event timed out ( -1712)” my IOS is Yosemite, and i am running the latest version of the caldera program

    Hi Linc, thanks for this ... it is weird, we tried this previously, but we only did a restart.
    This morning our Mac was 'off' even though we hadn't turned it off, (maybe a power outage) I restarted and ran the calpatch immediately, and it worked !!
    it is embarrassing, because as a service engineer, I am always telling customers to restart and even power down completely before trying again.
    Thanks.
    Snakeydee

  • Internal error "Framemaker has dectected a serious problem and must quit"

    I keep getting an Internal error "Framemaker has dectected a serious problem and must quit." Can someone tell me what I need to do to correct this?

    I get error messages about font not being available and about links failing to update but I don't think either of these should cause the "serious problem" Framemaker is detecting. We just subscribed to Framemaker less than one month ago. I wouldn't think I'd be behind on updates but when I tried to update I encountered another problem with Adobe Application Manager. I'm going to have an IT person at our company look into this. Hopefully, he'll have better luck than I'm having. If you have any helpful information to pass along, I'd still like to hear it. I will pass it along to our IT person. If not, thank you for your help. I appreciate it!

  • So I downloaded the wrong Airplane Mode program for my operating system and I now have AppleScript Error message.  It will not allow me to quit the program.  Also, once that happens how do I remove the program from the computer?

    So I downloaded the wrong Airplane Mode program for my operating system and I now have AppleScript Error message.  It will not allow me to quit the program.  Also, once that happens how do I remove the program from the computer?

    What Airplane Mode program? To stop a running program launch Activity Monitor (in utilities folder) and quit the program from there. To remove the program drag it to the trash or better use the uninstaller that should have come with it.

  • Trying to batch print to postscript and getting AppleScript Error!

    Here is the script as copied from Script Editor:
    -- make a variable for the print settings to use:
    set thPrintSettings to "Publishers PDF standard"
    global thPrintSettings
    -- initially, we'll allow for picking destinations at script start
    set targetFolder to choose folder with prompt "Location for PDF files..."
    global targetFolder
    set varBasename to "CTB"
    tell application "Adobe InDesign CS3"
    -- Environment test: We want 1 book, no documents open:
    try
    get document 1
    display dialog "Please run this script without any documents open (except one Book)" buttons "OK" default button 1
    return
    on error
    -- we must be good to go, no documents open
    end try
    try
    set thBook to book 1
    on error
    display dialog "Please open an InDesign Book to use this script" buttons "OK" default button 1
    end try
    if modified of thBook then
    display dialog "This Book has been modified. Do you want to continue running the script?" buttons {"Cancel", "Yes"} default button 1
    end if
    tell thBook
    set countOfThBook to (count of book contents)
    set thContentsList to (full name of book contents) as list
    end tell
    -- return {countOfThBook, thContentsList}
    set user interaction level of script preferences to never interact -- avoid any dialogs (for printing or saving)
    set n to 0
    repeat with j from 1 to countOfThBook -- loop through book's documents
    set thDoc to item j of thContentsList
    open thDoc
    tell active document
    repeat with c from 1 to (count of every ink)
    tell ink c
    set convert to process to true
    end tell
    end repeat
    set myName to varBasename
    repeat with i from 1 to count of pages -- loop through book's pages
    set y to name of page i
    set n to n + 1
    tell print preferences
    set page range to y --page range sets which page(s) to print
    set active printer preset to thPrintSettings
    set print file to alias ("" & targetFolder & myName & "_" & n & ".ps")
    end tell
    print --without print dialog
    end repeat
    close saving no
    end tell
    end repeat
    end tell
    Every time I try to run it I get the following error:
    AppleScript Error
    Adobe InDesign CS3 got an error: Invalid parameter.
    Help!!!

    On 2/12/08 1:52 AM, "Jaime C. Starkey" <[email protected]> wrote:<br /><br />> I replaced the "set active printer preset" line to "set thPrintSettings to<br />> printer preset "CTB"<br /><br />No -- you should leave the "set active printer preset to thPrintSettings"<br />line as it was. The line you need to change is "set thPrintSettings to<br />"Publishers PDF standard"" -- that's where you need to insert "printer<br />preset".<br /><br />-- <br />Shane Stanley <[email protected]><br />AppleScript Pro Florida, April 2009 <a href=http://scriptingmatters.com/aspro>

  • Applescript error 600

    I keep getting an Applescript error -600.........application isn't running.  When I click on "ok" Cocktail opens and runs pilot.  The script is then gone but eventually comes back.  Is there any way to stop this error from appearing?
    Thanks for helping.
    Ron

    That error was reported as a Cocktail error in pre- 6.3 versions. (See: fixed problems with a -600 error)
    Try uninstalling Cocktail to see if Cocktail is causing the error.

  • AppleScript error -609 in Automator workflow

    I created an AppleScript on one computer and incorporated it in an Automator workflow. The script works perfectly well stand-alone or as part of the workflow.
    Then I copied both files to a headless computer via VNC. I adjusted the workflow to look at the new location of the script, and the script itself to look at the new location of the file it's processing. Now, on that second computer, the script works perfectly well by itself, but I get AppleScript error -609 Connection Is Invalid if it's run from the workflow.
    For testing purposes I reduced the script to its simplest expression:
    tell application "Finder"
    end tell
    and it's still generating the error.
    Strangely, from the workflow the full script does what's it's supposed to, but the workflow stops because of the error. The error appears even if this script is alone in the workflow. Does anybody know what it means?

    That error means that the script wasn't able to communicate with the targeted application properly, which can happen if the application crashes while the script is running. If that error doesn't cause any problems, it's appearance can be suppressed:
    try
    (your code)
    on error number -609
    end try
    This construct will not execute any code on or after the line which produces the error.
    (32099)

  • Connecting with Bluetooth--AppleScript Error

    My current internet connection is through my mobile company here in Italy while studying abroad using the bluetooth of my phone. There's a program that I have to run from the company to connect, and the first few days after installing Leopard I was able to still connect, but with several glitches (i.e. locking up, my menu bar freezing in the connection, time, and power area showing the pinwheel when I hovered over it) and this caused me to have to force my laptop to shut down by holding the power button on several occasions.
    Now when I open the program, as it is loading the phone information and taking control of the network settings, I am greeted by a message saying, "The application FMM3MYIC quit unexpectedly." offering me to ignore, report, or relaunch. Both ignoring and relaunching lead to a second message saying (translated from Italian) "AppleScript Error: The localconnectionstatus variable is not defined. (-2753)" Ultimately this leads me without a connection.
    Any hints as to why it was running fine before and not now? I've recently installed the two latest updates thinking that might help and deleted the files as well as re-installed the program.
    I know nothing really about scripts, but would it be possible to edit the script for the program. Any help would be great--I went to a local Mac store (not an official one--just a support and sales place) here in Milan and they were really of no help. His suggestion was to run DiskUtility, which did me no good. Anyway thanks in advance.

    Could you verify a couple of things please?
    Are the 64-bit desktop and 32-bit laptop both paired to the same Nokia 5800, and are they used in such a way that both computers could be connected via Bluetooth to the 5800 at the same time? You should verify that the previous Bluetooth connection is turned off before using another. This can be done for example by disabling the bluetooth dongle from the other computer. It could be said that Ovi Suite doesn't support connecting to a mobile phone from multiple computers.
    Are you able to pair your Nokia 5800 with the Toshiba laptop at all? Or did I understand the problem correctly, that after restarting the Mobile device, it can be connected to the laptop? If it is a pairing problem, you could try pairing the device outside Ovi Suite by using the Microsoft Bluetooth stack directly.
    If the problem is not one of the above mentioned, and it persists, it could help if you post the following information to your reply (from Ovi Suite):
    Help->About->System Information->Copy text to clipboard

  • Two days ago, I loaded Light Room 6. Today I went back to Light Room 5. LR 6 corrupted an entire folder of images, and caused errors on my Raid 5 causing win 7 to run "Chk Dsk" and fix the errors to the operating system. LR 5 has not shut down for the las

    Two days ago, I loaded Light Room 6. Today I went back to Light Room 5. LR 6 corrupted an entire folder of images, and caused errors on my Raid 5 causing win 7 to run "Chk Dsk" and fix the errors to the operating system. LR 5 has not shut down for the last 5 hours. LR 6 has a serious bug. Anyone else experiencing this problem. Yesterday I was on tech support, waiting for 3 hours, finally they picked up and informed me there department was closing and someone else would call me on Monday. So, I'm working today and all day Sunday to make up for the down time using LR 6.
    I don't know if the bug exists in the program or the "Creative Cloud.
    Question: Does anyone know why if I bought Light Room 6 [NOT Light Room CC with the monthly rental], I have to enter my serial number if I want to use it?

    Entering the serial number is probably part of the registration process.
    Just out of curiosity, what were you doing on LR6 when the folder of images became corrupted?

  • AppleScript Error when use with VisualHub

    Hi all,
    When i try to convert any movie with audio on VisualHub, then will show up these:
    sh: -c: line 1: unexpected EOF while looking for matching
    sh: -c: line 2: syntax error: unexpected end of file (2)
    Pls help or how can i fix it?
    Many Many Thanks
    morningpanda

    And your AppleScript code looks like ? ...
    **The Applescript error**
    **sh: -c: line 1: unexpected EOF while looking for matching**
    **sh: -c: line 2: syntax error: unexpected end of file (2)**
    And the format of the movie file (to be converted) is ? ...
    *quicktime to mp4*

  • Automator/Applescript error for Library selection - workarounds ?

    I am creating some Automator actions to simplfy my workflow, but do it in a way that suits me. eg.
    Step 1. Copy CF images to Time Capsule (easy)
    Step 2. Import CF images into Aperture doing the following:
    a. Import with option to create a new project (non-refd)
    b. Set ratings to 1.
    c. Set some IPTC data.
    d. Select some basic keywording
    Bang ! - import it all
    Seems and is reasonably easy, however two observations in the import to Aperture execution:
    - It runs very slowly (i might be able to live with this)
    - I often get an Applescript error and it seems linked to this old Apple doc asking me to add a 'Set Aperture Library" step in the Applescript ?! Huh ?
    http://docs.info.apple.com/article.html?artnum=307040
    Currently triggering both actions as Applications, but hope to sequentiall link them if i can get the solve for the error.
    Q1. Can i 'fix' this error within Automator actions ?
    Q2. Is it normal for the set rating and IPTC tagging to be glacial slow ?
    Getting more impressed with Automator power, but it sometimes seems to be a little flakey (perhaps or its me!)
    Appreciate any pointers...

    Scripts currently run v. slowly if you have a large library... submit a bug using the feedback form!

  • Learning Unix and AppleScript on Lion

    Hi everyone,
    I want to learn Unix on OS X Lion and AppleScripts very well. I've been a Mac user since Tiger OS X, but now I've decided to be serious about Unix and AppleScript. Can anybody recommend good books for this purpose. I would like to have books which start from basics but later go on to great details to fully explore these two things. I really need expert opinion here, plz.
    Best,
    Naveen

    If you already know something about unix commands, there is a scripting tutorial at http://www.tldp.org/LDP/abs/html/index.html
    If you need a tutorial on unix commands, http://osxfaq.com/Tutorials/LearningCenter/UnixTutorials/LoseTheMouse/index.ws had a pretty good tutorial, although at the moment, that link isn't loading for me now so I don't know if it is still up online or not.
    for creating logout hooks, http://www.bombich.com/mactips/loginhooks.html might help.
    Also, in Terminal, type man launchd.plist if you can think of a scenario where you could implement a "cron-like" solution. Then refer to Apple's own periodic daily/weekly/monthly launchd plists (com.apple.periodic-*ly.plist) at/System/Library/LaunchDaemons/. There are more triggers available than just day/date/time, such as "watchPaths" and "RunAtLoad." Home grown launchd plists ones should go in /Library/LaunchDaemons/ or Library/LaunchAgents, not /System/Library/LaunchDaemons/. Also man launchd (no ".plist").

  • No sound -- AppleScript error

    I don't have sound on my iMac G5 running OS 10.5.8
    This problem just developed recently, but I think it relates to a little program I installed a long time ago called psst! (it's supposed to make the startup chime quieter) I also recently installed a newer version of Finale (Finale 2011) that I was using to play midi sounds through my internal speaker.
    When I shut the computer down I see a error message with an icon from psst. The error reads:
    AppleScript Error
    Can't make missing value into type integer. (-1700)
    I tried turning off psst!, but I can't because the same error message comes up. I tried removing Psst! to the trash, but that didn't help. I installed a new version of Psst! and that didn't fix the problem either.

    Turns out that I found the answer to this question in an iMac G5 discussion. It appears that I was correct in assuming a program messed up my sound settings. When that happens, the easiest and quickest way to return them to normal is to open up and use Garage Band and have it make some sound. At least, that just worked for me! I guess Garage Band takes charge and puts things in their proper places.

  • Applescript errors in 10.5.1

    I have 2 x iMacs, one a mid2007 and one a late 2006. Both have varying degrees of applescript errors. The mid 2007 reports an applescript error when using alarm clock pro and/or Superduper. The late 2006 has applescript errors all over the place especially when using maintainence (3rd party) utilities.It is also very prone to spinning beach ball. I've tried creating a new user but thats the same - also safeboot mode (still applescript errors) This particular machine works fine when logged in as root. I suspect the other will too although I haven't checked it yet as root user. All the applications that have applescript errors on these machines, work well on my Mac Pro. All my machines are bang up to date with all the latest software updates. I've done a pretty intensive google search but haven't found a fix from it. Please E-Mail [email protected] if you could assist me please. If possible, I want to avoid an archive & Install.PS - Have cleared out caches, and deleted swap files etc.

    It sounds like a permission issue. Particularly if everything runs ok as root.
    You'll have to check all the permissions against the working mac.

Maybe you are looking for