Application opens, file doesn't

Every time I double-click a JPG or other photoshop file in the finder (10.3.9) on a G5 the application PhotoShop CS opens, and that's all. The file that was double-clicked doesn't open. The only way I can open a file for PhotoShop is from within PhotoShop using File/Open or the File Browser. I have trashed known PhotoShop prefs and have fixed permissions. I also changed the default application away from PhotoshopCS to something else and changed it back again, no change... Any other ideas? It used to work..

Well Pat, I am basically lazy and when I started having that trouble---not all of them just a select few that PS decides not to open...I put PS in the doc then drag/drop the file to the icon and then it will open.
Now mind you for some reason there are still some files that even from within PS will nto open, maybe they had corrupted fonts embedded??? I do not know.
If all else fails you could try reinstalling PS

Similar Messages

  • Issues Running applications/opening files

           What has been suggested as a software issue has been present in my customers computer for months. 
       Heres whats happening...
    1. When a user attempts to open a program/application such as google chrome, documents library, itunes etc.... There is a prompt that appears on the screen showing a program reccomended to open the "file" the customer is trying to access.
        a. The program under the recommended section is called, Doxillion Document Converter by NCH Software
     2. Another interesting thing i noticed is that the majority of program icons on the desktop are not as they should be. They are instead replaced with an icon which is literally a blank page with a corner folded forward in the upper right hand corner.
     These things which im describing have basically made the computer disfonctional, and the suggested document converter is present to stop whatever function they may attempt to use the computer for.
    Lets work out a solution! 

    Hi, that sounds like associations etc have been hijacked by malware or other potentially unwanted programs (Doxillion).
    I would suggest, if you are not running windows 8 but are running on windows 7 or earlier, then head over to bleepingcomputer.com and download RKill, Combofix & AdwCleaner
    VERY IMPORTANT!!
    Any AntiVirus software must be disabled before running ComboFix.
    If you use AVG then you MUST uninstall it completely before running ComboFix.
    Failure to do this could cause Windows to fail on startup.
    ComboFix is a hardcore, aggressive virus removal tool & can remove any virus & repair damage done by most of them..
     1. Run RKill, this disables anything malicious that may be running in the background,
     2. Run Combofix, will take between 10-25 mins, once finished, wait for the computer to reboot. Problem should now be sorted.
    (3) Probably wont be necessary, but run AdwCleaner, just to quickly scan for a few more things, only takes 1 minute..
    After a restart, things should be back to normal.
    Another great virus removal tool is Malwarebytes Anti-Malware, the scan just takes a while, and i have recently come accross an infection that it could not remove.
    If you are on Windows 8 or 8.1, you CANT use Combofix, so instead do the following:
    1. RKill   ( running this will terminate any problematic malware etc that may be active. to be ran 1st to shutdown anything that may interfere with malware scanners )
    2. AdwCleaner ( a fast effective anti-Adware/anti-malware scanner )
    3. Junkware Removal Tool ( A different scanner to use after the above )
    4. TDSSKiller ( another quick scanning tool, just to be sure )
    5. Malwarebytes Anti Malware
    Hope this helps

  • Opening files doesn't work no matter how many times I press the button.

    Application Basics
    Name: Firefox
    Version: 31.0
    User Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:31.0) Gecko/20100101 Firefox/31.0
    Crash Reports for the Last 3 Days
    All Crash Reports
    Extensions
    Name: Adblock Plus
    Version: 2.6.4
    Enabled: true
    ID: {d10d0bf8-f5b5-c8b4-a8b2-2b9879e08c5d}
    Name: Battlefield Play4Free
    Version: 1.0.96.0
    Enabled: true
    ID: [email protected]
    Name: Bitdefender Wallet
    Version: 2.0
    Enabled: true
    ID: [email protected]
    Name: Copy As Plain Text
    Version: 1.0.9
    Enabled: true
    ID: {1a5dabbd-0e74-41da-b532-a364bb552cab}
    Name: DownThemAll!
    Version: 2.0.17
    Enabled: true
    ID: {DDC359D1-844A-42a7-9AA1-88A850A938A8}
    Name: Extended Statusbar
    Version: 1.5.10
    Enabled: true
    ID: {daf44bf7-a45e-4450-979c-91cf07434c3d}
    Name: FastestFox
    Version: 5.2.1
    Enabled: true
    ID: [email protected]
    Name: Freemake Video Downloader Plugin
    Version: 1.0.0
    Enabled: true
    ID: [email protected]
    Name: Freemake Youtube Download Button
    Version: 1.0.0
    Enabled: true
    ID: [email protected]
    Name: Greasemonkey
    Version: 2.1
    Enabled: true
    ID: {e4a8a97b-f2ed-450b-b12d-ee082ba24781}
    Name: InstantFox
    Version: 2.8.9
    Enabled: true
    ID: searchy@searchy
    Name: Multifox
    Version: 2.2.0
    Enabled: true
    ID: multifox@hultmann
    Name: Online Convert
    Version: 1.4
    Enabled: true
    ID: [email protected]
    Name: ProxMate - Proxy on steroids!
    Version: 2.3.3
    Enabled: true
    ID: jid1-QpHD8URtZWJC2A@jetpack
    Name: Show my Password
    Version: 2.0
    Enabled: true
    ID: {cd617372-6743-4ee4-bac4-fbf60f35719e}
    Name: Skype Click to Call
    Version: 7.3.16540.9015
    Enabled: true
    ID: {82AF8DCA-6DE9-405D-BD5E-43525BDAD38A}
    Name: Strict Pop-up Blocker
    Version: 0.2
    Enabled: true
    ID: jid1-P34HaABBBpOerQ@jetpack
    Name: Tab Badge
    Version: 1.15
    Enabled: true
    ID: [email protected]
    Name: Text to Voice
    Version: 1.10
    Enabled: true
    ID: [email protected]
    Name: Tile Tabs
    Version: 11.9
    Enabled: true
    ID: tiletabs@DW-dev
    Name: URL Fixer
    Version: 4.1
    Enabled: true
    ID: {0fa2149e-bb2c-4ac2-a8d3-479599819475}
    Name: Video Resumer
    Version: 1.1.3
    Enabled: true
    ID: videoresumer@jetpack
    Name: Yamli for Firefox
    Version: 1.1.0
    Enabled: true
    ID: [email protected]
    Name: Webexp Enhanced
    Version: 1.1
    Enabled: false
    ID: [email protected]
    Graphics
    Adapter Description: Intel(R) HD Graphics 4600
    Adapter Description (GPU #2): NVIDIA GeForce GTX 760M
    Adapter Drivers: igdumdim64 igd10iumd64 igd10iumd64 igdumdim32 igd10iumd32 igd10iumd32
    Adapter Drivers (GPU #2): nvd3dumx,nvwgf2umx,nvwgf2umx nvd3dum,nvwgf2um,nvwgf2um
    Adapter RAM: Unknown
    Adapter RAM (GPU #2): 2048
    Device ID: 0x0416
    Device ID (GPU #2): 0x11e3
    Direct2D Enabled: true
    DirectWrite Enabled: true (6.3.9600.17111)
    Driver Date: 1-22-2014
    Driver Date (GPU #2): 9-1-2013
    Driver Version: 10.18.10.3412
    Driver Version (GPU #2): 9.18.13.2702
    GPU #2 Active: false
    GPU Accelerated Windows: 1/1 Direct3D 10
    Vendor ID: 0x8086
    Vendor ID (GPU #2): 0x10de
    WebGL Renderer: Google Inc. -- ANGLE (Intel(R) HD Graphics 4600 Direct3D9Ex vs_3_0 ps_3_0)
    windowLayerManagerRemote: false
    AzureCanvasBackend: direct2d
    AzureContentBackend: direct2d
    AzureFallbackCanvasBackend: cairo
    AzureSkiaAccelerated: 0
    Important Modified Preferences
    accessibility.newtabplus.homepage: chrome://branding/locale/browserconfig.properties
    accessibility.newtabplus.page: 1
    accessibility.newtabplus.ver: 4.5.2
    accessibility.typeaheadfind.flashBar: 0
    browser.cache.disk.capacity: 358400
    browser.cache.disk.smart_size_cached_value: 358400
    browser.cache.disk.smart_size.first_run: false
    browser.cache.disk.smart_size.use_old_max: false
    browser.cache.frecency_experiment: 1
    browser.places.smartBookmarksVersion: 7
    browser.sessionstore.upgradeBackup.latestBuildID: 20140716183446
    browser.startup.homepage_override.buildID: 20140716183446
    browser.startup.homepage_override.mstone: 31.0
    browser.tabs.warnOnClose: false
    dom.mozApps.used: true
    dom.popup_allowed_events:
    extensions.lastAppVersion: 31.0
    font.internaluseonly.changed: true
    gfx.direct3d.last_used_feature_level_idx: 0
    network.cookie.prefsMigrated: true
    places.database.lastMaintenance: 1406922206
    places.history.expiration.transient_current_max_pages: 104858
    plugin.disable_full_page_plugin_for_types: application/pdf
    plugin.importedState: true
    plugin.state.npuplaypc: 0
    print.printer_Microsoft_XPS_Document_Writer.print_bgcolor: false
    print.printer_Microsoft_XPS_Document_Writer.print_bgimages: false
    print.printer_Microsoft_XPS_Document_Writer.print_colorspace:
    print.printer_Microsoft_XPS_Document_Writer.print_command:
    print.printer_Microsoft_XPS_Document_Writer.print_downloadfonts: false
    print.printer_Microsoft_XPS_Document_Writer.print_duplex: -854238192
    print.printer_Microsoft_XPS_Document_Writer.print_edge_bottom: 0
    print.printer_Microsoft_XPS_Document_Writer.print_edge_left: 0
    print.printer_Microsoft_XPS_Document_Writer.print_edge_right: 0
    print.printer_Microsoft_XPS_Document_Writer.print_edge_top: 0
    print.printer_Microsoft_XPS_Document_Writer.print_evenpages: true
    print.printer_Microsoft_XPS_Document_Writer.print_footercenter:
    print.printer_Microsoft_XPS_Document_Writer.print_footerleft: &PT
    print.printer_Microsoft_XPS_Document_Writer.print_footerright: &D
    print.printer_Microsoft_XPS_Document_Writer.print_headercenter:
    print.printer_Microsoft_XPS_Document_Writer.print_headerleft: &T
    print.printer_Microsoft_XPS_Document_Writer.print_headerright: &U
    print.printer_Microsoft_XPS_Document_Writer.print_in_color: true
    print.printer_Microsoft_XPS_Document_Writer.print_margin_bottom: 0.5
    print.printer_Microsoft_XPS_Document_Writer.print_margin_left: 0.5
    print.printer_Microsoft_XPS_Document_Writer.print_margin_right: 0.5
    print.printer_Microsoft_XPS_Document_Writer.print_margin_top: 0.5
    print.printer_Microsoft_XPS_Document_Writer.print_oddpages: true
    print.printer_Microsoft_XPS_Document_Writer.print_orientation: 0
    print.printer_Microsoft_XPS_Document_Writer.print_page_delay: 50
    print.printer_Microsoft_XPS_Document_Writer.print_paper_data: 1
    print.printer_Microsoft_XPS_Document_Writer.print_paper_height: 11.00
    print.printer_Microsoft_XPS_Document_Writer.print_paper_name:
    print.printer_Microsoft_XPS_Document_Writer.print_paper_size_type: 0
    print.printer_Microsoft_XPS_Document_Writer.print_paper_size_unit: 0
    print.printer_Microsoft_XPS_Document_Writer.print_paper_width: 8.50
    print.printer_Microsoft_XPS_Document_Writer.print_plex_name:
    print.printer_Microsoft_XPS_Document_Writer.print_resolution: 0
    print.printer_Microsoft_XPS_Document_Writer.print_resolution_name:
    print.printer_Microsoft_XPS_Document_Writer.print_reversed: false
    print.printer_Microsoft_XPS_Document_Writer.print_scaling: 1.00
    print.printer_Microsoft_XPS_Document_Writer.print_shrink_to_fit: true
    print.printer_Microsoft_XPS_Document_Writer.print_to_file: false
    print.printer_Microsoft_XPS_Document_Writer.print_unwriteable_margin_bottom: 0
    print.printer_Microsoft_XPS_Document_Writer.print_unwriteable_margin_left: 0
    print.printer_Microsoft_XPS_Document_Writer.print_unwriteable_margin_right: 0
    print.printer_Microsoft_XPS_Document_Writer.print_unwriteable_margin_top: 0
    privacy.sanitize.migrateFx3Prefs: true
    storage.vacuum.last.index: 1
    storage.vacuum.last.places.sqlite: 1406135669
    JavaScript
    Incremental GC: true
    Accessibility
    Activated: false
    Prevent Accessibility: 0
    Library Versions
    NSPR
    Expected minimum version: 4.10.6
    Version in use: 4.10.6
    NSS
    Expected minimum version: 3.16.2 Basic ECC
    Version in use: 3.16.2 Basic ECC
    NSSSMIME
    Expected minimum version: 3.16.2 Basic ECC
    Version in use: 3.16.2 Basic ECC
    NSSSSL
    Expected minimum version: 3.16.2 Basic ECC
    Version in use: 3.16.2 Basic ECC
    NSSUTIL
    Expected minimum version: 3.16.2
    Version in use: 3.16.2
    Experimental Features
    Hi. Whenever I want to upload a picture or a file, no matter how many times I press the "Upload" or "Browse" button, nothing happens. I can keep spam clicking on it and it wouldn't do anything. This is not specific to a site, but happens everywhere. Dragging and dropping files works on Facebook and Imgur, but not all websites support this. I'm using Firefox 31.0 on Windows 8.1. Yes, I have tried restarting Firefox and computer, this has been happening for a while now. Thanks.

    Boot the computer in Windows Safe Mode with network support (press F8 on the boot screen) as a test.
    *http://www.bleepingcomputer.com/tutorials/how-to-start-windows-in-safe-mode/
    This probably still applies to Windows 8:
    Try to delete the MRU (Most Recently Used) ComDlg32 registry keys with the registry editor (regedit.exe).
    Navigate to: HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\ComDlg32
    Delete the subkeys (LastVisitedPidlMRU and OpenSavePidlMRU)
    Be cautious with editing the registry as there is no Undo possible: all changes are applied immediately.
    You can export registry keys before making changes.
    * http://www.winhelponline.com/articles/195/1/How-to-clear-the-file-names-MRU-in-Common-Dialog-boxes-in-Windows-Vista.html

  • Open file doesn't work on Windows 7

    Hello ,
    I have this portion of code that should open a file and let windows decide what program to use for that :
    Code 1 : Runtime.getRuntime().exec("rundll32 url.dll,FileProtocolHandler "+"c:/x.xls");
    Code 2 : File f = new File("c:/x.xls");
    Desktop.getDesktop().open(f);
    None of this options opens the file , no error is caught , no nothing.
    The result of RUN si "Buid succesfull".
    Bouth CODE 1 and CODE 2 work on Windows Xp.
    Do you have any suggestions ?
    Thank you for your help !

    Works fine for me. The actual code lines I tested with:try {
      Desktop.getDesktop().open(new File("E:/drb/Docs/Personal/April2009.xls"));
    } catch (IOException ex) {
      ex.printStackTrace();
    Microsoft Windows [Version 6.1.7600]
    Copyright (c) 2009 Microsoft Corporation.  All rights reserved.
    C:\Users\Darryl>java -version
    java version "1.6.0_17"
    Java(TM) SE Runtime Environment (build 1.6.0_17-b04)
    Java HotSpot(TM) Client VM (build 14.3-b01, mixed mode, sharing)
    C:\Users\Darryl>db

  • Hi when i open my application folder, all the application is shown in trash folder. when i click the application it says this app is in trash first move it out. and when i try to open through finder go it says this file doesn't exist. can some1 plz help?

    hi when i open my application folder, all the application is shown in trash folder. when i click the application it says this app is in trash first move it out. and when i try to open through finder> go it says this file doesn't exist. can some1 plz help? how can i put all my application through application folder?

    Something really odd is going on. In your first screen shot, I noticed that the Applications folder does not have the proper icon displayed in the side bar. Also, in the title bar it lists it as Applications 08-59-29-909.
    Not sure where it's picking up that odd name, unless it's because it's still truly within the Trash folder.
    Try this. In the Finder > Preferences > General > turn on "Always open folders in a new window". (I have a feeling you have the default setting with this off).
    Now, in Finder > Go > move down and open the Applications Folder from there. Now open the folder where you see all your applications that you show in your screen shot, select all, and move them to this true appliactions folder.
    This is what you should properly seeing (but with different apps listed):
    See how the Applications folder has the icon of the letter A shaped with a pencil, ruler & pen.

  • Can't open file "~/Library/Application Support/iWeb/Domain.sites2."

    Hello,
    I have been using iWeb for over a year and I have a lot of my work on it. But for some reason, when I went to open iWeb, I get the error message:
    +Can’t open file “~/Library/Application Support/iWeb/Domain.sites2.”+
    Does anyone know how I can fix this and make sure my content doesn't get deleted?
    Thank You!

    Deleting the preference file does not affect the domain.sites2 file. If it's not in the default folder or has a name other than domain.sites2 then that's why iWeb couldn't find and open it. Find it and double-click on it to open it with iWeb 2. You do have a backup copy the domain file, right? If not download and use frequently the Automator application that Varkgirl created. You can get it at Varkgirl's iWeb Tips and Tricks site.

  • InDesign tries, but doesn't open files on server.

    When using a finder window to open CS3 and CS4 InDesign files from our server, I get the opening effect but not the open file.  I'm using Snow Leopard on a Mac. Double-clicking will not work, dragging the file into the application icon will not work, only the File > Open menu does the trick and opens the file. Note: double-clicking and dragging into the app icon does work for local files. Any fixes for the server file issue? Thanks!

    i have this problem too at random, i click on the indesign cs4 file in the snow leopard finder, indesign actually makes that temporary whatever it is in the finder but the layout pages don't open. my workaround is to quit indesign and start again and this usually works. but i am wondering if there is any other solution? when the file doesn't open it doesn't help to try to open it through the file menu. so i just quit and start again. (this may be a feature of indesign since sometimes at random the font sizing buttons don't work.)

  • Double-clicking on files doesn't open them

    Just started today:
    If I navigate to a file in the Finder and double-click on it, nothing happens. It doesn't open. If I open the application (e.g., MS Word) and go to the file menu and choose Open, navigate to the file, the file will open. But it happens in all applications, not just Word -- double-clicking on any file won't open the file in its parent application. It's like the link between files and apps has been lost.
    I restarted the Finder twice, restarted the whole computer twice, repaired Permissions with Disk Utility -- nothing has helped. Still can't open files by double-clicking on them.
    Am I missing something?
    Tx,
    WK

    Kappy,
    Followed these "Get Info" box instructions for two different files and their apps -- the correct apps were already listed as the Default, but I reselected them and "Changed All" again anyway. Still no change. Double-clicking on these docs in the Finder does not open files or the files creator Application. The only way I can still launch files and the proper App is through Control-click and "Open with" command.
    I even deleted the com.apple.finder.plist and restarted, thinking the Finder prefs file might be corrupt, but still no change, so took the original plist file out of the Trash and put it back in the Library>Preferences folder and restarted again. No change.
    THEN - a breakthrough. I checked the Keyboard/Mouse Prefs Pane and the double-click speed for the mouse was set completely to the right. I backed it off one "notch", went back to the Finder and double-clicked on a Word file and Voíla! -- the file and Word opened as it should.
    Went back to the Mouse Prefs Pane and moved the Double-CLick Speed indicator all the way to the right again ("Fast") and went back to Finder and focused on double-clicking files as fast as I could and they opened fine.
    SO -- I'm embarrassed to say that I just wasn't double-clicking fast enough. Not sure how the Speed indicator got moved so far to the right, but I have backed it off a notch to a normal double-click speed that I've used for years, and all seems to be working.
    Thanks again for all your help -- I learned some good things about how to connect files and apps which will no doubt come in handy in the future.
    Wk

  • "open file in Photoshop" doesn't work any more.

    When I right clicked a picture in Lr (most recent version) and selected "open file in Ps (CC 2014)" Photoshop launched, but the image didn't show up.
    I tried several times, with Ps closed or open, but to no avail. Opening the file as a "smart object in Ps" works, and also opening the file in a third party application (Perfect Effects 8) works fine. Just Ps CC 2014 doesn't load the image from Lr.
    Any hints?
    Mac OS X 10.9.4 and Adobe CC, all products at the most current level.

    See this article:
    Edit In doesn't work in Lightroom 5.5 from Photoshop CC 2014

  • Open File with Application in Automator - Bug???

    I have created a simple workflow to open a text file with TextEdit. It seems to work once, then subsequent times the workflow goes to the point that TextEdit opens but the file doesn't open along with it.
    I have encountered the same type of problem when trying to open other files with other applications - the applicaton opens but the file is not passed along with it.
    I am only using two actions:
    (1) Get Specified Finder Items
    (2) Open Finder Items
    I noticed there is another Finder action that doesn't seem to do anything called "Get Selected Finder Items"
    Am I doing something wrong?
    Help....

    I'm not sure about your main problem, but I can tell you about the "Get Selected Finder Items" action.
    That action refers to the items you have selected in the Finder. Selected items in the Finder are highlighted. So, if you haven't selected anything in the Finder yet, then the action will not have anything to give the workflow.
    In essence, this action allows you to specify an item (or items) each time you run a workflow merely by selecting an item in the Finder, instead of having to specify an item permanently in the workflow. That is, you don't have edit the workflow in order to use it for another item. So you don't need multiple copies of the workflow, each specifying a different file or set of files.
    Hope that clears up the mystery of that action.
    MacBook 2.0 GHz Intel Core Duo   Mac OS X (10.4.8)   512 MB RAM

  • Preview: double-click doesn't open files AFTER they have been modified

    Since a few weeks (maybe since I upgraded to OS 10.6.6 ?) Preview doesn't open files any more by double-clicking AFTER I have modified and saved them. They open when I drag them to the dock icon of Preview.
    For instance, photos downloaded from a camera open by double-clicking them. However, if I rotate or crop them and then save, Preview doesn't open them any more but shows two subsequent error messages: (1) "The application can't be found", (2) "The operation can't be completed. An unexpected error occurred (error code -43)".
    I found one workaround: when you close and reopen the folder in which these files are, they open again by double-clicking.
    Quicklook works fine.
    Looks like a bug in OS 10.6.6. Any other fixes?

    In the Finder, select one of the image files you want to open with Preview. Choose "Get Info" from the contextual menu or the File menu. In the "Open with" section, choose Preview from the pulldown menu if it's not already selected. If it is selected, choose another application (any other), then re-select Preview. Click the "Change All" button and close the dialog.

  • Open dataset doesn't lock the file at OS level

    Hi,
    I have a program, which tries to write a file on application server. Once the file is opened, and while program is writing to the file, if somebody goes at application server and deletes the file, I get a short dump, saying the file doesn't exist.
    Why doesn't SAP lock the file at OS level? Why is someone able to delete the file while SAP is processing it? What is to be done to check at OS level, to see if SAP is currently writing?
    Thanks,
    Juwin

    I tried what Kesav and Adrian told. I created 2 programs, 1st to create a file and 2nd to move the file.
    1st program: [url]http://www.mediafire.com/?gmrn1zyd0t0
    2nd program: [url]http://www.mediafire.com/?di2kzzzemkz
    Now, I executed the 1st program. While the 1st program is running, I executed the 2nd program. The Open dataset in the 2nd program always gave me sy-subrc as 0. So, I always got the message as ready to be moved. I tried executing the programs from different SAP user IDs as well. Got the same result. So, it seems, Open dataset, doesn't even lock the file at SAP level. I cannot use Open dataset for output in the second program, because that will erase the contents of the file.
    I cannot change the program, to execute a system command, because the file is created from a standard program, and we dont want to touch it.

  • Can't open file "/Applications/iWeb.app/Contents/Resources/Themes/Kids Pink.webtheme/pt.lproj/Welcome.webtemplate."

    Can’t open file “/Applications/iWeb.app/Contents/Resources/Themes/Kids Pink.webtheme/pt.lproj/Welcome.webtemplate.”
    What do i need to do to fix thisso I can use the program

    Try the troubleshooting steps under "Fix iWeb" here...
    http://www.iwebformusicians.com/iWeb/iWeb-Tips.html
    If that doesn't do it, try reinstalling the app as shown further down the page.

  • Getting error Can't open file "~/Library/Application Support/iWeb/Domain.sites2." when trying to open iWeb?

    I recently had to replace my harddrive a few months back and tried to open my iWeb to update my website.  When I click to open it, I get "Can’t open file “~/Library/Application Support/iWeb/Domain.sites2.”  I uploaded iLife again but that didn't seem to help.

    Did you confirm that you have a Domain.sites2 file in your Users/Home/Library/Application Support/iWeb folder?  If so double click on it to try to open with iWeb.  If that doesn't work try the following:
    delete the iWeb preference file, com.apple.iWeb.plist, that resides in your Home()/Library/Preferences folder.
    go to your Home()/Library/Caches/com.apple.iWeb folder and delete its contents.
    launch iWeb and try again.
    If that doesn't help continue with:
    move the domain file from your Home/Library/Application Support/iWeb folder to the Desktop.
    launch iWeb, create a new test site, save the new domain file and close iWeb.
    go to the your Home/Library/Application Support/iWeb folder and delete the new domain file.
    move your original domain file from the Desktop to the iWeb folder.
    launch iWeb and try again.
    OT

  • Opening files crashes Applications and closes Finder

    As I've been unofficial Apple "IT" for our graphics team in a biased world of PC and our IT haven't the knowhow or inclination to help I need REAL support!
    After the last security etc update my iTunes crashed every time I tried to open it (Dock or Folder).
    Re-installed from the Apple web download.
    It now works.
    Now when I open a job folder through Finder on the desktop then select the file to open Finder closes.
    When I have an application open - say Photoshop CS2 - and go > File > Open, once I select the file to open Photoshop "unexpectedly quits".
    This goes for ANY application!
    BUT...If I drag a file to the application on the dock all is well?
    If I want to place images /graphics etc from one application to whatever is open I now can't
    I hold hands high as not being the most in-depth technical Mac man but have a general feel for most niggles having grown with Classic onwards!
    This something new and hopefully someone can shine a light?

    You should do it from Disk Utility on your start-up disk.
    What are permissions?
    Every file and folder on a Mac OS X hard drive has a set of permissions—settings that determine which user(s) have access to each item, and exactly what that access is. For example, permissions dictate whether or not a particular user can open and edit a particular file. But permissions also determine which items the operating system—or specific parts of it—can access and modify, and which files are accessible by applications.
    What does repairing permissions do?
    The Repair Disk Permissions function—the process that actually performs the task of repairing permissions—examines certain files and folders on your Mac’s hard drive to see if their current permissions settings are what Mac OS X expects them to be; if discrepancies are found, the offending permissions are changed to match the expected settings.
    (In Mac OS X 10.3 and later, repairing permissions also performs one other, unrelated, task: If the invisible /tmp symbolic link—which is linked to the /private/tmp directory—is missing, the link will be recreated.)
    Why is it necessary to repair permissions?
    If permissions on particular files are “incorrect”—i.e., not what Mac OS X expects them to be or not what they need to be for your Mac’s normal operation—you can experience problems when the operating system tries to access or modify those files. For example, you may have trouble logging in to your account, printing, launching applications, or even starting up your Mac. Similarly, if an application—from Apple or a third-party developer—needs access to a particular file or folder to function, and the permissions on that item have changed in a way that prevents such access, the application may not function properly (or at all). The Repair Disk Permissions function can fix such problems by ensuring that certain files have the correct permissions.
    There’s also a security element here: Many system-level files have permissions set a particular way so that applications or users that shouldn’t be meddling with those files can’t. If the permissions on certain system-level files somehow get changed so that access to those files is no longer restricted, you’ve got the potential for a major security issue. Repairing permissions can resolve such issues by resetting permissions on those files to prevent unauthorized access.
    How do I repair permissions?
    The Repair Disk Permissions function is part of Apple’s Disk Utility (in /Applications/Utilities). After launching Disk Utility, select the desired disk—generally your startup disk—in the list to the left, then click the First Aid tab. At the bottom of the First Aid panel, click the Repair Disk Permissions button. (You could instead use the Verify Disk Permissions option to preview any potential repairs before performing them, but for most users there’s little benefit from this extra step.)
    Permissions can also be repaired via the shell (Terminal) by using the command sudo diskutil repairPermissions /. However, it’s unlikely that the typical user will ever need to perform the task in this manner. It’s useful if for some reason Disk Utility itself won’t launch, or for repairing permissions on a remote Mac when connected via Remote Login (SSH), but otherwise you’re just as well served using Disk Utility.
    How does the Repair Disk Permissions function know what the “correct” permissions are?
    When you use Apple’s Installer utility to install software (such as Mac OS X itself or an OS X update), the installation package (the .pkg file you double-click to begin installation, or that Software Update downloads in the background for an automatic installation) generally leaves behind a receipt—a smaller Mac OS X package that includes information about every file installed, including the permissions each file should have. This receipt is placed in /Library/Receipts. When you run the Repair Disk Permissions function, it examines the receipts in the /Library/Receipts directory of the disk being repaired—which means the feature works only on volumes with Mac OS X installed—and compares the information in the receipt with the actual files on your drive. If the Repair Disk Permissions function finds a file with permissions that differ from what a receipt claims they should be, that file’s permissions are reset to their receipt-specified values. (If you’re curious about the information contained in a receipt, the easiest way to view it is to use the utility Pacifist; simply drag and drop the appropriate receipt into the Pacifist window and you’ll be presented with a list of all files installed by the similarly-named installation package, along with each file’s original permissions.)
    It’s worth noting here that although the function is called “Repair Disk Permissions,” what is actually happening is that files’ permissions are being reset or restored to a particular state. It’s possible—though not common—for a particular file’s permissions to differ from what a receipt claims they should be without those permissions actually being “broken.”
    Are all files affected by Repair Disk Permissions?
    No. As you may have inferred from the above description, only those files installed using OS X’s Installer utility and whose installation packages leave behind a proper receipt in /Library/Receipts are affected by the Repair Disk Permissions function. This means that most of the files affected by the Repair Disk Permissions function are system-level files, application files, or system add-ons—not applications installed by drag-and-drop, and not your documents or other user-level files.
    If repairing permissions is useful in general, why doesn’t Apple recommend it as routine maintenance?
    Apple does, quite explicitly:
    It’s a good idea to repair disk permissions as a regular maintenance task after upgrading or installing new software.
    That’s taken from Mac Help—in both Panther and Tiger—right on your Mac. Similar statements can be found in other Support articles.
    (With thanks to another user who posted this here)

Maybe you are looking for