Eliminate metadata?

Originally posted this in Bridge General, was suggested that I repost here...
Trying to eliminate the shooting data from image files using Bridge (including shutter speed, f-stop).
I see options to affect virtually everything except for those two things it seems.
Does Bridge have a way to remove this information or simply "blank out" all metadata from image files?
...further detail...
I need to save the original full-resolution images w/o the metadata.
Exporting in virtually any form will eliminate the metadata as a new file is being created. I have 1000's of original images that I simply want to strip the metadata from and have as little (or no) generation loss as possible.

Found a HUGE amount of documentation on the ExifTool commands, but can't get the program to do a single thing. There is apparently some missing syntax that isn't allowing the program to function.
http://www.sno.phy.queensu.ca/~phil/exiftool/exiftool_pod.html#reading_examples
No matter what combination I try to get the program to react somehow, the only response is either "Pattern not found" or "File not found".
If you know of a single example of a complete command line - any command line at all - in the Mac OS terminal window using ExifTool, that's all I'd need.

Similar Messages

  • Adobe Bridge - White balance metadata

    When I browse raw files from my Canon EOS Rebel XT/350D in Adobe Bridge I always look at the Metadata tab to check for the f-stop value, speed, white balance settings, etc. of the currently-selected raw image file.
    I noticed that the pictures shot in Automatic White Balance appear on the upper-left portion of the Metadata tab as an icon indicating AWB. However, whenever I take pictures with manually-set white balances, such as shade, day light, tungsten, etc., the metadata tab no longer indicates the white balance I chose, instead, it either shows an icon of a camera or two dashes, as in --.
    Is there any way I can set Adobe Bridge to show the appropriate White Balance icon for pictures I take with manually-set white balances?

    Hi Curt,
    Thanks for your reply. Yes, White Balance is checked in preferences/metadata. All of the Exposure metadata entries are also checked.
    I forgot to mention that my version of Camera Raw is 4.5 (the latest).
    You know, although White Balance is checked, I cannot find a White Balance text entry on any of the metadata lists (File properties, IPTC core, Camera Data (EXIF), etc.). The only place where I can see the White Balance setting in on the upper left corner of the Metadata tab, under the f-stop value.
    Here is a personal question for you: When you browse your pictures in Adobe Bridge and you select one that was taken with a specific White Balance (not Auto), does your Adobe Bridge display an icon for that particular White Balance setting? I just want to eliminate the possibility that this happening only in my computer.
    Thanks a lot for your time and attention.

  • Removing EXIF and other Metadata from iPhoto 5 Library

    This post is intended for users who have upgraded to iPhoto5 and have suffered extensive slowdowns because of metadata that has accumulated in their iPhoto library, specifically in the Library.iPhoto file.
    This occurs if certain Pentax, Canon, and other digital cameras are used for pictures. Search this forum for "metadata" or "EXIF" or "makernote" (no quotes) for additional information about this issue.
    If you are affected by this issue and want to rid your iPhoto 5 library of this extra garbage, follow the steps below.
    1. Make two copies of your complete iPhoto Library folder and put them someplace else other than in the normal location. If something goes wrong, you'll have the backups. In any event, understand that if you follow these instructions, you are responsible for any problems, errors, or loss of photos. If you aren't prepared to take that responsibility, then do not read any further.
    2. Go to http://www.versiontracker.com and search for and download the free SmallImage application. Install it in your Applications folder.
    3. In your original iPhoto library, trash the Library.iPhoto file.
    4. Launch SmallImage by dragging your entire (ORIGINAL) iPhoto Library folder on top of SmallImage.
    5. There are 5 categories (checkboxes) of metadata (called profiles) that you can eliminate. I selected them all. Uncheck the "Recompress at quality:" checkbox. You don't want your photos altered. Uncheck the "Add Suffix" checkbox so that SmallImage will overwrite your photos with ones without the metadata. Select whether you want keep any custom file icons or not. Then, hold your breath and push the "Process Files" button in the SmallImage toolbar. If you have thousands of photos and/or a slow computer, it might take many hours.
    6. When SmallImage is finished, lauch iPhoto5, holding down the command/apple, option and shift keys. Before iPhoto fully loads, you'll be presented with the library rebuilding dialog box. Check ALL 4 options (especially the last one) and then allow iPhoto to rebuild the library. This also can take a very long time, depending on computer speed and the number of photos you have. When iPhoto is finished rebuilding the libary and reloading your photos, you'll have an iPhoto library without any the metadata that seems to be slowing it down. If you hold down the wrong keys and don't get the library rebuilding dialog box, don't panic. Quit iPhoto, and try it again. Your photos are still there.
    7. If you stay with your current camera (that is generating the metadata), manually transfer your picture files to your computer (but not directly into iPhoto) and use SmallImage to remove the metadata BEFORE you manually import them into iPhoto5.
    Hopefully, future versions of iPhoto5 will include an import option to strip metadata from photo files. If SmallImage can do it, why can't our favorite fruit company?
    Best of luck.
    12 inch 1.5Ghz Powerbook Mac OS X (10.4.3)
    12 1.5Ghz Powerbook   Mac OS X (10.3.9)  

    Link the two Macs together and use iPhoto Library Manager
    Regards
    TD

  • Unable to access Planning 9.3.1 from Workspace & Metadata load question

    Hi:
    I created a planning application through Classic View and was able to successfully register the app. I even updated the dimensions. I did all this using the Admin ID provided by a thrid party installation firm. They updated my security to match the Admin and when I re-log in to Workspace and click on the Planning app I just created there is an error message:
    Unable to connect to Essbase server. Check log for detail.
    I try using the Admin ID again but the same error message appear. IS anyone out there can give me some advice on what might went wrong and what should I ask them to check? They claim that all servers are up and running. I have tried to see if I can re-create another app but there is no data source available (is this because the Essbase connection problem or becuase one data source can only have one app associated with it?) Any suggestions/help will be greatly appreciated!
    Also, they did not install BPMA. I have not done 9.3.1 before but I heard I can no longer use HAL to load metadata. So without BPMA, is my other options DIM and ODI? Has anyone use any of these and which is the best tool to load metadata? Is BPMA a better option compares to the DIM/ODI?
    Thanks so much!
    Mike

    Hi,
    First I would check in shared services whether the correct access has been provisioned.
    Next try and log in directly to planning and not through workspace to eliminate any issues there. http://<planning server:8300/HyperionPlanning/
    Unable to connect to Essbase server sounds like either permissions are not correct or server details are incorrect, check the datasource details in the config utility and try and connect directly to essbase with them.
    There will not be extra datasources available if they have not been set up, you will need to create these through the config utility on the server.
    My experience of BPMA is that it is not up to being qualified as a fully stable product yet, all depends on the size of the implementation on how to you use it to whether BPMA will be useful, that leaves DIM and ODI, DIM is a third party product and is not cheap and I am not sure how much of a shelf life it will have, Oracle are pushing ODI which they now own, it is a much more stable product and has a many more rich features than BPMA though it does have a steeper learning curve and is more aimed at a technical audience.
    Hope this helps
    John
    John

  • What happens when there is a conflict between develop settings stored in file metadata, and the catalog?

    Hello,
    Wondering if someone could quickly help me with understanding how develop settings are read back into lightroom... (I'm using lightroom 3.6) as I've just had a bit of a panic that my mis-understanding of the system might have screwed things up a bit!
    As I do all my image tinkering on a laptop with a small disk, I am often archiving directories of images to an old server we have, and then just bringing them back onto my laptop whenever I need them again. I have a single lightroom catalog on my laptop, and I thought (I now think wrongly!) that all my develop settings updates were stored solely in the lightroom catalog on my laptop, and as long as I kept a copy of the original jpeg images knocking around somewhere so that I could restore them to my laptop when needed, that I could always get back to the most recently edited version of my images. Often I copied a directory of images from the server to the laptop, edited them with lightroom, then deleted the jpg files from the laptop thinking the originals left on the server would be sufficient to restore my work later.
    However recently just before deleting a batch of jpgs from the laptop, I did a quick compare with the server and was horrified to realise that the files where different, and that changes *are* written to the jpeg files! Looking in lightroom I have the 'Include Develop settings in metadata inside JPEG [etc] files' turned on.
    My questions would be:
    1 - Have I lost work by effectively deleting the metadata from the jpeg files or is it also preserved in the catalog?
    2 - What would happen if some develop settings for an image were stored in the catalog, and a completely different set of develop settings were stored in the file - which would take priority?
    3 - Have I screwed up and if so is there anything I can do to minimise the damage? : {
    Many thanks for any advice!!
    Nicola

    My questions would be:
    1 - Have I lost work by effectively deleting the metadata from the jpeg files or is it also preserved in the catalog?
    2 - What would happen if some develop settings for an image were stored in the catalog, and a completely different set of develop settings were stored in the file - which would take priority?
    3 - Have I screwed up and if so is there anything I can do to minimise the damage? : {
    1. Lightroom ALWAYS stores the edits in its catalog file.
    2. Lightroom ALWAYS uses the edits in its catalog file. The information stored in the JPG is NEVER used to display the image in Lightroom.
    3. As long as you don't eliminate the photo from the catalog, you are fine, your edits are present in the catalog file and Lightroom will use those to display the image.
    As I do all my image tinkering on a laptop with a small disk, I am often archiving directories of images to an old server we have, and then just bringing them back onto my laptop whenever I need them again.
    If you have moved the photos to the server, using Lightroom (or using Adobe Lightroom - Find moved or missing files and folders), there's no need to bring them back to your laptop. You can leave the photos on the server, and access them on the server, and everything works properly

  • Adobe Bridge Canon .mov Metadata Importing

    I am using Adobe Bridge CS4 on Windows XP SP3 32bit.
    I have recently seen the light and am now going through my years of photos and videos and adding metadata tags and key words. I realise that my image files which consist mostly of Canon RAW files largely look after them self in that all the meta data recorded by the camera is easily read. Things like aperture, lens type etc are easily seen and seen to be accurately captured.
    With my video files however (at the moment I'm concentrating on 5D Mark II video files) I have come to realise that there is no metadata like there is in photos embedded within the file. Bridge just picks up the basic file info which is relatively inaccurate when it comes to creation date etc. After becoming disillusioned with the lack of metadata on my videos I then realised that when I use Zoom Browser (Canon image and video browsing software) that it has a stack of information that Bridge doesn't see. After some investigating I opened some .thm files with note pad and found the metadata stored in those.
    From what I understand these are known as side car files. However as I want one program to rule them all, I want Bridge to have all the metadata. I had planned on manually entering all the data that I could read from Zoom Browser into Bridge but even this won't work because things like Aperture and Creation Date aren't editable fields in Bridge.
    Is there a way I can get Bridge to extract the data from these .thm files?
    Thanks in advance for your help.

    Hi Curt,
    Thanks for your reply. Yes, White Balance is checked in preferences/metadata. All of the Exposure metadata entries are also checked.
    I forgot to mention that my version of Camera Raw is 4.5 (the latest).
    You know, although White Balance is checked, I cannot find a White Balance text entry on any of the metadata lists (File properties, IPTC core, Camera Data (EXIF), etc.). The only place where I can see the White Balance setting in on the upper left corner of the Metadata tab, under the f-stop value.
    Here is a personal question for you: When you browse your pictures in Adobe Bridge and you select one that was taken with a specific White Balance (not Auto), does your Adobe Bridge display an icon for that particular White Balance setting? I just want to eliminate the possibility that this happening only in my computer.
    Thanks a lot for your time and attention.

  • How do I import Bridge keywords and metadata to CS6 from CS4 so that I don't lose them if CS4 is not

    I have hundreds of keywords and metadata including Ratings and Labels using CS4 and Bridge CS4.
    It is time to replace my PPC Mac with a new Intel Mac.
    I am going to install CS6 on the new Intel Mac without installing CS4.
    By default.... this eliminates ALL keywords and ratings and labels from my Bridge browser. The keywords will still be present on the files but Not present in Bridge keywords list and all ratings and labels will be lost.
    Making a copy of Bridge CS4 metadata to another computer is quite simple.
    Simply copy All of the Bridge CS4 application support folder to the other computer.
    The question then becomes.... can I aslo do this with CS6 without introducing an incompatibility?
    1. incompatible due to CS6 application support.
    2. incompatible due to transfer from a PPC (APM) to Intel (GUID).
    This concern results from an Bridge CS4 export problem I experienced.
    Bridge CS4 will export all of your keywords and you can import them from a text file but it has some odd troubles. (try it and you will see)
    This does Not mean that CS6 has the same troubles.
    What do I require to preserve existing metedata and keywords that exist on a PPC using CS4 and import them into CS6 using Intel?
    Sound simple?
    I doubt it.
    The points are.
    1. CS4 not installed.
    2. CS4 source is PPC not Intel.
    3. Ratings and Labels are metadata that Are Not part of the file metadata and unique to Bridge only.
    4. Keyword Search and keyword Use requires that Bridge have keyword list, otherwise Finder is the far more useful browser and the new version of Bridge will require hours of keyword listing.
    I don't want to spends hours retyping keywords lists in Bridge.

    Ratings are NOT placed into the file under CS4 Bridge and neither are
    Labels.
    That depends on your file type and settings voor Camera Raw.
    Like Curt stated usually metadata is written in to the file itself. Only Raw files can't be written to and by default they create a XMP file, also called Sidecar XMP files (and do have the same filename, only a different extension called .xmp). These files are also by default hidden in Bridge but If you use Bridge to move files they travel along with the original.
    If you move or copy them using finder you have to be sure these XMP files are also copied with the originals to the new location.
    Using the menu View / show hidden files should reveal the XMP files.
    An other option for the Camera Raw prefs is to set metadata to the Camera Raw database instead of written to sidecar XMP files ( to my knowledge using sidecar files has been the default since about CS3).
    Now here it becomes a bit tricky and I only can tell you my findings, not to be confused with true facts. (and mind you, it is at least 5 years ago I was on a PPC and not even remember which OSX 10 was able to work on it, I just present the acting of CS6 on an intel Mac Pro with OSX 10.7, but I don't believe the difference in location is that much)
    Having written the Metadata to the Camera Raw Database your image settings get written to a file in the user library preferences folder called logically "Adobe Camera Raw Database". But also some info gets added to the Camera Raw Cache folder (User library / Caches/ Adobe Camera Raw) in a file called index.dat.
    Also not having set metadata to xmp sidecars stores the ACR settings in a new .dat file with a unique number (not to be traced as a corresponding filename. And also the default maximum is set to 1 GB of space and when full the oldest files are overwritten with the new ones.
    Personally I use converted DNG files that are capable of writing metadata to so all info and settings are in the file itself and I don't need to bother about central storage that can get lost. The downside is that changes to a DNG need to save the whole file instead of a small xmp file and probably reading cache takes more time then getting info from central storage but I like to be on the safe side and speed is not really needed to be nailed down to split seconds in my workflow.
    Keywords are stored as a file in the Bridge preferences but Like Curt already stated exporting the old list first and then via the same route import again to CS6 should solve your problem and they will be back as persistent, otherwise the files in the content window show as italic and sadly enough have to be made persistent one by one with right click mouse menu, so that is not really an option for you.
    Exporting the list does create a text file that can also be altered manually with a simple text app and as said, again be imported in newer versions as Curt described earlier.
    Making a copy of Bridge CS4 metadata to another computer is quite simple.
    Simply copy All of the Bridge CS4 application support folder to the other computer.
    Well, in fact it is true to call copying this folders a simple task but replacing the existing new CS6 would not be my method. The biggest change for Bridge CS6 was the transition to 64 bit and I lack the knowledge for this but also cache format for thumbs and previews has been different for every version.
    But if you have located the CS4 folder for Bridge in your PPC user library / application support / Adobe / Bridge CS4 you should find a file called 'Adobe Bridge Keywords.xml' and it is fairly safe to replace this CS4 version with the new CS6 version.
    Also custom settings for the output module can be copied (however to my memory the option for custom settings in Output where introduced in CS5) and collections can be copied.
    So for your keywords the copy option might work, rating and labeling for Raw files they will be read in CS6 if they are stored as XMP. ACR settings idem but CS6 ACR has a new (2012) conversion mode that has different settings that do not work with previous settings (unless you first choose to use the 2010 conversion as default Raw setting.
    If it is in the Central Data Base I would start trying to replace the CS4 with the CS6 edition (after back up of existing CS6 version) and see what happens. If it works your out of trouble.
    You can also open the Camera raw Database as a text file but there is a lot of data in. Maybe scripting would be able to reveal those data and transfer to XMP but you have to visit the dedicated Scripting forum for this.
    And while you state to have not installed CS4 anymore it might be wise to reinstall it (but first make a proper back up of the previous mentioned folders and files to be on the save side.
    This gives you the opportunity to export keywords properly and if needed you can use Show Items from subfolders option with filter and set preferences to XMP sidecar to refresh the rating and labels to those XMP files. Just an escape route that might not be as painstakingly as it looks at first sight, just use the options for Bridge to filter.

  • Lightroom Metadata editing and workflow is tedious nightmare!

    I'm new to Lightroom in just the past month, but have used it enough to see that a serious interface problem makes Lightroom version 1x virtually unusable in a deadline-oriented publishing workflow. Lightroom's Metadata editing and workflow is just a terrible nightmare, and far too tedious and slow. It appears to be an afterthought implemented by good-hearted souls who've never had to edit this sort of information under serious deadline pressures. I know Lightroom is marketed as an image database and not a file browser, but we're all looking to simplify our workflow here and with just a few subtle enhancements, Lightroom could be an excellent file browser and file import manager too.
    As it is now, the Lightroom v1x handling of File Naming and Renaming, Metadata Editing and Keyword Editing is poorly implemented and in need of an immediate overhaul to help professional photographers expedite this crucial and time-consuming first step in the archiving workflow. While Lightroom is very good at many other tasks, I give it a big fat "F" of a failing grade for these tasks.
    First, the Lightroom Library Module needs an even more simple, linear interface that steps users through a precise procedures (and helps them remember them). Arguably, to accomplish this, the Import function may need to become a separate Module that can be selected and used separately before entering the Library. As File Naming and Renaming, Metadata Editing and Keyword Editing currently are implemented, I, for one, am always forgetting to fill out one of these critical sections and can't even seem to remember that some may need to be done before importing while others appear to be conceived to be done after importing. My point is, all these related steps really need to be done together, but the Interface spreads out the functions too much, and it is nearly impossible to build a logical and linear Import workflow, especially when you are first learning Lightroom.
    I'd like to see a workflow that walks me through applying and editing (in order), File Naming, Basic and IPTC Metadata, Captioning and Keywords, so that I don't always forget some obscure step in the process (which I keep doing). Here are some specific suggestions, some of which may prove to be valid, some of which may be problems due to my lack of experience with thye software.
    1. As currently implemented, Metadata editing requires too much thought, and does not have enough intelligent automation. Eliminate as much typing as possible (See Photo Mechanic!)
    2. Lightroom needs better Metadata Presets. A "Quick Edit" view to simplify interface for editing minimal metadata info (File Name, Basic Info, Keywords, Headline, Limited Copyright Info).
    3. Separating Keyword Tags, Metadata Browser, Keywording Presets and Metadata Presets confuses the workflow. They should all appear together under one selectable module that organizes a suggested, linear workflowfor these tasks, but allows it to be customized. This is the sort of tasks that need to be learned by rote memory, and having all these panes floating around on both sides of the photo make it impossible to quickly step through these tasks.
    - Name (or Rename) files, Edit/Apply Basic and IPTC Metadata, Edit/Apply Keywords, Import or...
    - Import, Name (or Rename) files, Edit/Apply Basic and IPTC Metadata, Edit/Apply Keywords, Import
    4. Rename should offer the option of renaming the master file names on the disk, not just file names in the database (which I think is what Lightroom does, but again, this is very confusing for new users)! So, it is my belief that this feature needs a checkbox option to rename one, the other or both. But you need to be able to quickly find this dialog box every time you do an import, and it should not be hidden away out of view under the Library menu. Ideally and logically (for workflow), File Renaming should be handled when starting the Import into Lightroom.
    This is critically important because many user

    Lightroom metadata editing Part 2 (see Part 1 at top of thread)...
    ...This is critically important because many users just do not want to trust their images solely to any database and we want the ability to go look for master files with identical names should something go wrong with the software or we decide to edit the file in Photoshop outside of Lightroom or even switch to another library software program.
    My own habit is to rename every file with the date followed by a unique, three-digit file number, as in 20070717_001, 20070717_002...up to 999 etc. (I have never shot more than 999 files in a single day, but this could be a four-digit number). To file these on disk, a folder with a similar naming scheme is created for each day's shoot, although a keyword slug is added to the end instead of file numbers.
    5. Metadata Presets (Basic Info, IPTC metadata, EXIF metadata), Keywords need to be able to toggled on or off (promote/demote-expand/contract). Turning Off/On one section at a time via the Metadata Presets popup menu is too tedious...and you can't display IPTC and Large Caption together or leave Large Caption turned on. It also is difficult to remember where the Large Caption default (Preferences) setting is...
    6. Please get the EXIF data out of the way entirely when editing captions and visa-versa...And the EXIF data should not separate Basic Info and IPTC Info fields. Please relocate the EXIF to the bottom of the Metadata pane...
    7. IPTC Content, IPTC Copyright, IPTC Creator, IPTC Image expand/collapse sections need more automation:
    - The Presets fields need Preset lists of entry choices for cities, states, countries, etc.!
    - ISO Country Code automatically should be filled in when a country is entered.
    - Date created automatically should be filled in from camera EXIF data
    - Metadata Presets "Save As" should fill in old name, and allow you to rename it; (When it appears, the new name field should not be empty. This would aid in consistent, alphabetical naming
    - Metadata Presets naming should support job names, with actual Presets saved under each job name...
    8. IPTC Status EXIF, Contact, etc.
    - Caption field MUST display more than one line...(6-8 lines)!
    - Caption field MUST support Shift/Return!
    - Headline (IPTC Content) should be displayed with (and above) caption. Please present information logically!
    - Yellow popups should describe what each field name is for...some are real brain teasers...

  • I'm trying to clean up extra iPhoto positions. What other folders and files can I eliminate?

    I have too much redundancy. iPhoto Libraries have been started over the last couple of years without much thought to structure.  If I identify and remove the picture files in "Originals" and "Modifieds" (identified by using "Show Package Contents") and move them to secure locations (designated folders on another drive) what other files can I eliminate? Inside of "Show Package Contents" I see folders for Data.noindex, Library.iphoto, Contents, and Metadata Backup? Other files show as well.  Can these be eliminated or do they contain critical picture files?  I'm working with iPhoto Manager to identify and manage libararies.

    Whoa!
    Don't change anything in the iPhoto Library Folder via the Finder or any other application. iPhoto depends on the structure as well as the contents of this folder. Moving things, renaming things,, deleting them or otherwise making changes will prevent iPhoto from working and could even cause you to damage or lose your photos.
    I don't know anyway to make things clearer.
    What are you trying to do?

  • Updating Content Type from other metadata field

    Hi.
    In the process of creation of metadata fields a customer use a custom metadata field called 'class' to define what type the content are. The field Content Type was leave untouchble. Now they have tons of content in the same folder inside vault cause content server uses the metadata content type to create vault subfolders. What is the best way to eliminate the field class, transporting the metadata to the correct field content type and mantain the correlation of the links to the native files and weblayout files of the content? If I just update the column content type with the data in column class I believe that willl be a mess of broken links. Can anyone suggest anything?
    Thank you!

    Hi there,
    Thought i could not comprehend all that you want, I could get that you have problem with a meta data filed.
    Instead of using "Content Type" earlier contributors used "class" and now you want to chagne the "class" field with appropriate value of "Content Type".
    This can be done provided the original "class" type was used intellegently by using following steps
    1) depending on various values of class(e.g. all document for which class=A) created exports using archiver, also deleted them same time.
    2) Import the archiver created in step one and prove an input map for the "class" field to appropriate value as "Content Type"(content type =B)
    In this way all content items with class=A would be converted into content type=B.
    Hope that helps you.
    regards,
    sapan

  • Request: Ability to update metadata via spreadsheet view or csv file upload

    A fairly simple change to make Muse more efficient and user-friendly.
    I'm in the process of building out a medium size site for a client (90+ pages) - my first experience using Muse - and editing metadata is a pain. I've planned the site: page titles, descriptions, page names, etc, but updating metadata isn't the first step in my creation process and now I'm going back through updating information. My have a 2013 Mac Pro and 2013 Macbook Pro and both systems take time to update this information with so much data buffering and being updated.
    My request:
    The ability to update metadata across a site without the changes being executed until we applied the changes. For example, changing site view to a spreadsheet view with each pages information. Then, I could update a bunch of pages and hit enter, and walk away while it takes 5 minutes to update. This would also eliminate the hassle of requesting page properties from each page separately.
    Thanks in advance.

    Is your DTP full or delta.
    Here is some interesting discussion.
    /thread/348238 [original link is broken]

  • Bridge won't write metadata; Photoshop will

    I have some TIFFs created from scans. Here's the problem I'm seeing.
    When opening the image in PS CS5 I often get a message saying This file contains file info data which cannot be read and which has been ignored.
    First, I try to change some metadata in Bridge and save the image. Sometimes this solves the problem. Often, though, I get a message saying There was an error writing metadata to "filename".
    Next, I open the image in PS simply clicking OK on the error message above. I open File Info, change some metadata and save the image. So far this has always solved the problem thus far.
    The source of hte problem will likely not be easy to discover since the error message provides no useful information and since it is happening frequently, but not universally. At first I thought it was related to specific fields, but further testing seems to indicate it is not. Then I thought since another running application gave me a low storage message, it might be related to that. That does not seem to be the case either.
    However, even if I don't find the root cause, it would be helpful if Bridge would simply rewrite the metadata to fix the problem rather than having to go into PS.
    Any thoughts?
    Dale

    From
    what you are saying the TIFF's are corrupt somehow.  Open them in PS
    and then save with another name and see it you can then write metadata.
    For whatever reason Bridge may be more sensitive to the error than PS. 
    Can you change the scan to another format to eliminate the problem?
    Granted the metadata is somehow corrupt. However opening them in PS and then saving them with the same name solves the problem, so it must rebuild the corrupt metadata fields.
    I've scanned several hundred TIFFs and only had the problems on a few files. The only archival formats Nikon Scan 4 gives me are TIFF and nef and if I used nef ACR won't recognize the colorspace.
    Dale

  • Slow finder: "com.apple.metadata.mdserver"

    When I click on a file in the finder, I now get a beach ball that spins for several minutes until the preview shows up.
    When I launch the Activity Monitor, I get a process called "mds" at the root level that is taking up 60+% of my CPU power.
    I launched the console and looked in the console log, I get a repeating message of "Can't checkin with server named com.apple.metadata.mdserver, error 0x10000004" among several other messages.
    I have been saving several JPGs and have put many fairly long descriptions in the Spotlight information. Is this what is slowing me down? I don't want to lose those comments by deleting the .DS_store files.

    Hi Charles,
    3 things...
    Spotless should fix the Spotlight problem, might have to get everything wiped and start Spotlight again when it can have the computer for a weekend.
    occasionally causes Kernel panics when you quit the applications that use it.
    Repair the HDDs after every crash/KP.
    Onyx. And while it's not "supposed" to help,
    Many love Onyx, but a few have had AJ cure/clear what Onyx didn't.
    I think you should get Applejack...
    http://www.versiontracker.com/dyn/moreinfo/macosx/19596
    After installing, reboot holding down CMD+s, (+s), then when the DOS like prompt shows, type in...
    applejack AUTO
    Then let it do all 5 of it's things.
    At least it'll eliminate some questions if it doesn't fix it.
    The 5 things it does are...
    Correct any Disk problems.
    Repair Permissions.
    Clear out Cache Files.
    Repair/check several plist files.
    Dump the VM files for a fresh start.
    First reboot will be slower, sometimes 2 or 3 restarts will be required for full benefit... my guess is files relying upon other files relying upon other files!
    Disconnect the USB cable from any UPS so the system doesn't shut down in the middle of the process.

  • How can I eliminate delays in one NIC when there is traffic on second NIC

    Using LabVIEW TCP/IP VIs, my LV application is  accessing a database though a LAN, and  through a second NIC, it is controlling an instrument.  The instrument is connected directly to the computer NIC with a cross-over cable.  I have made a permanent route for the IP address of the instrument in the IP route table.  The LAN and the instrument have different subnet numbers.  Using a packet sniffer, I don't see any traffic meant for the LAN going to the NIC connected to the instrument.  The OS of the computer is Windows XP and the NICs are PCI cards.
    The message traffic to the instrument suffers from intermittent delays when there is traffic going to the LAN. 
    How can I eliminate the delays?  What could be the cause of the delays?  Thanks in advance for your recommendations and suggestions.

    Hi LabBard,
    Could you tell us a little more about the device that you are connected to? What you could try is to have a VI accessing the LAN, and a separate VI communicating with the instrument, and see how things play out.
    Let us know how it goes!
    Rasheel

  • I've tried to eliminate system errors by performing a clean install of ML. What's the best way to set up my iMac for a singlet user?

    One of my main goals is to be able to run a Windows application on my iMac, purchased in July, 2012, with the Intel 2.5Ghz i5, 4GB RAM, 500GB hard drive. At first I installed Boot Camp and then Win 7, then the application I need to run, and I don't recall having problems. But I tired of the required reboot each time and got greedy and needy - so I installed VMWare Fusion, only to be told that the W7 software I use won't work with Fusion, but it will with Parallels! So, I was able to get Parallels at a discount (because I had Fusion), and decided I would import Boot Camp into Parallels.
    Then the problems began. I suspect I did something I shouldn't have during this process, but to shorten the story I did a clean install of ML, set up iCloud, and monitored Console for problems. And problems there were - lots of them, and they all seemed to reference iCloud in some way. Since I have the ML installer on a thumb drive I thought I'd see what happened if I did another clean install, but this time I'd ignore iCould altogether (yes, I have everything backed up to mypcback.com) and proceeded. As before, the errors streamed down Console's face as if it were my own. I've run OnyX, which seemed to help, but many of the issues persist. I'm at a loss as how to proceed other than invoke Apple Support, which, BTW, is not covered under Warranty.
    I need to have a stable ML platform before I start using W7 and refuse to believe that the OSX is "just buggy." Can someone help. I have no other iDevices that need to be synced, and really don't see the need to set up iCloud. Noone else than I use the iMac. It should be pretty simple to create a stable OSX so I can go where I need to go. I realize 4GB is not a lot of memory and will look into that. For the moment, I can stip down Win 7, and OSX for that matter, to free up memory. I didn't want to included a bunch of log files, but I will if someone thinks that it would be helpful.
    The follow are the latest entries into my system log file, after I lost connection to the internet, and then regained connection after rebooting my cable modem:
    Dec 18 16:03:37 173-22-144-11.client.mchsi.com com.apple.SecurityServer[15]: Succeeded authorizing right 'system.volume.removable.unmount' by client '/usr/sbin/diskarbitrationd' [18] for authorization created by '/System/Library/CoreServices/Finder.app' [142] (100002,0)
    Dec 18 16:04:49 173-22-144-11 kernel[0]: Ethernet [AppleBCM5701Ethernet]: Link down on en0
    Dec 18 16:04:50 Marks-iMac.local configd[17]: setting hostname to "Marks-iMac.local"
    Dec 18 16:04:50 Marks-iMac.local configd[17]: network changed: v4(en0-:173.22.144.11) DNS- Proxy- SMB
    Dec 18 16:04:55 Marks-iMac.local digest-service[2296]: label: default
    Dec 18 16:04:55 Marks-iMac.local digest-service[2296]:           dbname: od:/Local/Default
    Dec 18 16:04:55 Marks-iMac.local digest-service[2296]:           mkey_file: /var/db/krb5kdc/m-key
    Dec 18 16:04:55 Marks-iMac.local digest-service[2296]:           acl_file: /var/db/krb5kdc/kadmind.acl
    Dec 18 16:04:55 Marks-iMac.local digest-service[2296]: digest-request: uid=0
    Dec 18 16:04:55 Marks-iMac.local rpcsvchost[2297]: sandbox_init: com.apple.msrpc.netlogon.sb succeeded
    Dec 18 16:04:55 Marks-iMac.local digest-service[2296]: digest-request: init request
    Dec 18 16:04:55 Marks-iMac.local digest-service[2296]: digest-request: init return domain: 173-22-144-11 server: MARKS-IMAC
    Dec 18 16:08:21 Marks-iMac com.apple.launchd.peruser.89[1579] (com.apple.cfprefsd.xpc.agent[1584]): Exited: Killed: 9
    Dec 18 16:08:21 Marks-iMac kernel[0]: memorystatus_thread: idle exiting pid 1584 [cfprefsd]
    Dec 18 16:08:21 Marks-iMac com.apple.launchd.peruser.89[1579] (com.apple.distnoted.xpc.agent[1582]): Exited: Killed: 9
    Dec 18 16:08:21 Marks-iMac kernel[0]: memorystatus_thread: idle exiting pid 1582 [distnoted]
    Dec 18 16:08:25 Marks-iMac kernel[0]: (default pager): [KERNEL]: ps_select_segment - send HI_WAT_ALERT
    Dec 18 16:08:25 Marks-iMac kernel[0]: macx_swapon SUCCESS
    Dec 18 16:08:26 Marks-iMac.local distnoted[2307]: # distnote server agent  absolute time: 25574.335618917   civil time: Tue Dec 18 16:08:26 2012   pid: 2307 uid: 89  root: no
    Dec 18 16:08:42 Marks-iMac com.apple.launchd.peruser.89[1579] (com.apple.cfprefsd.xpc.agent[2308]): Exited: Killed: 9
    Dec 18 16:08:42 Marks-iMac kernel[0]: memorystatus_thread: idle exiting pid 2308 [cfprefsd]
    Dec 18 16:09:56 Marks-iMac com.apple.launchd.peruser.89[1579] (com.apple.distnoted.xpc.agent[2307]): Exited: Killed: 9
    Dec 18 16:09:56 Marks-iMac kernel[0]: memorystatus_thread: idle exiting pid 2307 [distnoted]
    Dec 18 16:09:58 Marks-iMac com.apple.launchd.peruser.501[127] (com.apple.pbs[194]): Exited: Killed: 9
    Dec 18 16:09:58 Marks-iMac kernel[0]: memorystatus_thread: idle exiting pid 194 [pbs]
    Dec 18 16:10:52 Marks-iMac.local HelpViewer[2304]: : event.layerX and event.layerY are broken and deprecated in WebKit. They will be removed from the engine in the near future. (line: 0)
    Dec 18 16:11:18 --- last message repeated 9 times ---
    Dec 18 16:11:18 Marks-iMac com.apple.launchd.peruser.501[127] (com.apple.NetworkDiagnostics): The following job tried to hijack the service "com.apple.NetworkDiagnostic.agent" from this job: [0x0-0x12b12b].com.apple.NetworkDiagnostics
    Dec 18 16:11:20 Marks-iMac.local distnoted[2315]: # distnote server agent  absolute time: 25748.275081657   civil time: Tue Dec 18 16:11:20 2012   pid: 2315 uid: 89  root: no
    Dec 18 16:13:08 Marks-iMac kernel[0]: CODE SIGNING: cs_invalid_page(0x1000): p=2318[GoogleSoftwareUp] clearing CS_VALID
    Dec 18 16:15:30 Marks-iMac kernel[0]: Ethernet [AppleBCM5701Ethernet]: Link up on en0, 100-Megabit, Full-duplex, No flow-control, Debug [796d,0301,0de1,0300,41e1,0000]
    Dec 18 16:15:34 Marks-iMac.local configd[17]: network changed: v4(en0+:192.168.100.2) DNS* Proxy+ SMB
    Dec 18 16:16:31 Marks-iMac.local WindowServer[72]: CoreAnimation: context hosting changed while locked!
    Dec 18 16:16:43 Marks-iMac.local configd[17]: network changed: v4(en0-:192.168.100.2) DNS* Proxy- SMB
    Dec 18 16:16:48 Marks-iMac.local configd[17]: network changed: v4(en0+:173.22.144.11) DNS+ Proxy+ SMB
    Dec 18 16:16:48 173-22-144-11.client.mchsi.com configd[17]: setting hostname to "173-22-144-11.client.mchsi.com"
    Dec 18 16:16:53 173-22-144-11.client.mchsi.com digest-service[2346]: label: default
    Dec 18 16:16:53 173-22-144-11.client.mchsi.com digest-service[2346]:           dbname: od:/Local/Default
    Dec 18 16:16:53 173-22-144-11.client.mchsi.com digest-service[2346]:           mkey_file: /var/db/krb5kdc/m-key
    Dec 18 16:16:53 173-22-144-11.client.mchsi.com digest-service[2346]:           acl_file: /var/db/krb5kdc/kadmind.acl
    Dec 18 16:16:53 173-22-144-11.client.mchsi.com digest-service[2346]: digest-request: uid=0
    Dec 18 16:16:53 173-22-144-11.client.mchsi.com digest-service[2346]: digest-request: init request
    Dec 18 16:16:53 173-22-144-11.client.mchsi.com digest-service[2346]: digest-request: init return domain: MARKS-IMAC server: 173-22-144-11
    Dec 18 16:20:31 173-22-144-11.client.mchsi.com mdwrite[2355]: [ERROR] [0.000s] com.apple. UBItemStatusNotification.c:805 _do_UBItemStatusNotificationRegisterURLs() can't find realpath for "/Users/mine/Library/Mobile Documents/com~apple~system~spotlight/mdlabels", was blocked at "/Users/morkgallagher/Library/Mobile Documents": 2 (No such file or directory)
    Dec 18 16:20:31 173-22-144-11.client.mchsi.com mdwrite[2355]: [ERROR] [0.001s] com.apple. UBItemStatusNotification.c:805 _do_UBItemStatusNotificationRegisterURLs() can't find realpath for "/Users/mine/Library/Mobile Documents/com~apple~system~spotlight/mdlabels", was blocked at "/Users/morkgallagher/Library/Mobile Documents": 2 (No such file or directory)
    Dec 18 16:44:38 173-22-144-11.client.mchsi.com Locum[2366]: Connection with distnoted server was invalidated
    Dec 18 17:02:34 173-22-144-11.client.mchsi.com mtmd[49]: Set snapshot time: 2012-12-18 17:02:36 -0600 (current time: 2012-12-18 17:02:34 -0600)
    Dec 18 17:02:34 173-22-144-11 kernel[0]: nspace-handler-set-snapshot-time: 1355871756
    This DNS change is only the lastest manifestation of what seems like an endless list. Can anybody give me some direction before I have to pay Apple to fix what I think they broke themselvesa?!?  BTW, I am not a tech. Thanking everyone who read this and especially to anyone who can help.

    Linc, thanks for the tips. I knew you'd have a good method. I asked for it because I have learned of some of the myths about OSX and it's need (or lack thereof) to be scrubbed, rinsed, and blown dry; suckering folks into buying all manner of utilities to keep your Mac spiffy at all times, when in fact it rarely needs any intervention at all because of its Unix background. In fact, I rarely shut mine down and I've learned that the system is actually designed to be left running under most circumstances.
    To keep your data secure the three most important things to know is backup, backup, backup. I use a third-party, cloud-based back-up system. It can automatically make backups every hour if that's what I want and I can supplement that anytime by simply dropping a file into the application's desktop interface.
    Since I last posted my Mac has been running smoothly and I've been able to install Parallels and Windows 7, as well as the VantagePoint software I mentioned. Though it crashed once this morning and I submit one line from the log file:
    12/20/12 10:31:00.639 AM appleeventsd[54]: BUG in libdispatch: 12C60 - 1510 - 0x4
    After a reboot, log entries spewed all manner of troubling messages, from those that are osascript-related to broken forks, etc. but as far as I know there were no actual crash logs generated until this afternoon, one being just a few minutes ago. Linc, would you be so kind to take a look and tell me if there's something I need to do?
    Process:    
    mds [434]
    Path:       
    /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Metadata .framework/Versions/A/Support/mds
    Identifier: 
    mds
    Version:    
    707.3
    Code Type:  
    X86-64 (Native)
    Parent Process:  launchd [1]
    User ID:    
    0
    Date/Time:  
    2012-12-20 16:01:07.242 -0600
    OS Version: 
    Mac OS X 10.8.2 (12C60)
    Report Version:  10
    Crashed Thread:  4  Dispatch queue: com.apple.metadata.spotlightindex
    Exception Type:  EXC_BAD_ACCESS (SIGSEGV)
    Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000bad
    VM Regions Near 0xbad:
    -->
    __TEXT            
    0000000109f9e000-000000010a0be000 [ 1152K] r-x/rwx SM=COW  /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Metadat a.framework/Versions/A/Support/mds
    Application Specific Information:
    [0x112562000]/SourceCache/Spotlight_frameworks/Spotlight-707.3/index/ContentInde x/FlatStore.c:169: failed assertion 'pageSize >= pageEnd && pageSize && (__builtin_popcount(pageSize+int_sizeof(*page)) == 1)' /.Spotlight-V100/Store-V2/FA53EC3A-E90C-4259-B76B-4B236308D7CD/live.0.indexArra ys (hfs, t: 0x11, st: 0x1, f: 0x480d000) ps:56, pe:18624, pk:0, po:aac0, ss:20000 se:146c0
    [0x112669000]/SourceCache/Spotlight_frameworks/Spotlight-707.3/index/ContentInde x/PayloadIterator.c:681: failed assertion '!nxtLink |
    Thread 0:: Dispatch queue: com.apple.main-thread
    0   libsystem_kernel.dylib   
    0x000000010bb7b686 mach_msg_trap + 10
    1   libsystem_kernel.dylib   
    0x000000010bb7ac42 mach_msg + 70
    2   com.apple.CoreFoundation 
    0x000000010b1e2803 __CFRunLoopServiceMachPort + 195
    3   com.apple.CoreFoundation 
    0x000000010b1e7ee6 __CFRunLoopRun + 1078
    4   com.apple.CoreFoundation 
    0x000000010b1e76b2 CFRunLoopRunSpecific + 290
    5   mds                      
    0x0000000109faca54 0x109f9e000 + 59988
    6   libdyld.dylib            
    0x000000010b9a87e1 start + 1
    Thread 1:: Dispatch queue: com.apple.libdispatch-manager
    0   libsystem_kernel.dylib   
    0x000000010bb7dd16 kevent + 10
    1   libdispatch.dylib        
    0x000000010b973dea _dispatch_mgr_invoke + 883
    2   libdispatch.dylib        
    0x000000010b9739ee _dispatch_mgr_thread + 54
    Thread 2:
    0   libsystem_kernel.dylib   
    0x000000010bb7dffa read + 10
    1   mds                      
    0x0000000109fa7ced 0x109f9e000 + 40173
    2   libsystem_c.dylib        
    0x000000010ba0c742 _pthread_start + 327
    3   libsystem_c.dylib        
    0x000000010b9f9181 thread_start + 13
    Thread 3:
    0   libsystem_kernel.dylib   
    0x000000010bb7d6d6 __workq_kernreturn + 10
    1   libsystem_c.dylib        
    0x000000010ba0eeec _pthread_workq_return + 25
    2   libsystem_c.dylib        
    0x000000010ba0ecb3 _pthread_wqthread + 412
    3   libsystem_c.dylib        
    0x000000010b9f9171 start_wqthread + 13
    Thread 4 Crashed:: Dispatch queue: com.apple.metadata.spotlightindex
    0   com.apple.spotlight.index
    0x000000010a2262b1 mergeEntryFlat + 465
    1   com.apple.spotlight.index
    0x000000010a21cad2 mergeEntryFat + 642
    2   com.apple.spotlight.index
    0x000000010a212410 bt_mergeEntry + 208
    3   com.apple.spotlight.index
    0x000000010a2122d9 bt_mergeCallback + 345
    4   com.apple.spotlight.index
    0x000000010a2131e2 bt_mergeSet + 3346
    5   com.apple.spotlight.index
    0x000000010a22aa80 index_FlushCache + 1088
    6   com.apple.spotlight.index
    0x000000010a232e8c indexPrepareForSync + 220
    7   com.apple.spotlight.index
    0x000000010a220823 indexPrepareForSyncBulk + 493
    8   com.apple.spotlight.index
    0x000000010a22037d _CISyncContextSync + 149
    9   com.apple.spotlight.index
    0x000000010a21fc0c _ContentIndexSyncIndexBulk + 86
    10  com.apple.spotlight.index
    0x000000010a1e18fa syncIndex + 1364
    11  com.apple.spotlight.index
    0x000000010a1e1063 runLoop + 51
    12  com.apple.spotlight.index
    0x000000010a209691 work_fun + 662
    13  libdispatch.dylib        
    0x000000010b9710b6 _dispatch_client_callout + 8
    14  libdispatch.dylib        
    0x000000010b97247f _dispatch_queue_drain + 235
    15  libdispatch.dylib        
    0x000000010b9722f1 _dispatch_queue_invoke + 52
    16  libdispatch.dylib        
    0x000000010b972448 _dispatch_queue_drain + 180
    17  libdispatch.dylib        
    0x000000010b9722f1 _dispatch_queue_invoke + 52
    18  libdispatch.dylib        
    0x000000010b972448 _dispatch_queue_drain + 180
    19  libdispatch.dylib        
    0x000000010b9722f1 _dispatch_queue_invoke + 52
    20  libdispatch.dylib        
    0x000000010b9721c3 _dispatch_worker_thread2 + 249
    21  libsystem_c.dylib        
    0x000000010ba0ecab _pthread_wqthread + 404
    22  libsystem_c.dylib        
    0x000000010b9f9171 start_wqthread + 13
    Thread 5:
    0   libsystem_kernel.dylib   
    0x000000010bb7d6d6 __workq_kernreturn + 10
    1   libsystem_c.dylib        
    0x000000010ba0eeec _pthread_workq_return + 25
    2   libsystem_c.dylib        
    0x000000010ba0ecb3 _pthread_wqthread + 412
    3   libsystem_c.dylib        
    0x000000010b9f9171 start_wqthread + 13
    Thread 6:
    0   libsystem_kernel.dylib   
    0x000000010bb7d6d6 __workq_kernreturn + 10
    1   libsystem_c.dylib        
    0x000000010ba0eeec _pthread_workq_return + 25
    2   libsystem_c.dylib        
    0x000000010ba0ecb3 _pthread_wqthread + 412
    3   libsystem_c.dylib        
    0x000000010b9f9171 start_wqthread + 13
    Thread 4 crashed with X86 Thread State (64-bit):
      rax: 0xd62a2de7cde283a2  rbx: 0x000000000000aac0  rcx: 0x00000000002f4180  rdx: 0x00000000001430d0
      rdi: 0x0000000112258800  rsi: 0x0000000000000003  rbp: 0x00000001125605a0  rsp: 0x000000011255f450
       r8: 0x0000000000000007   r9: 0x00000000ccd96941  r10: 0x00007f92fb4219d0  r11: 0x00000000381b522a
      r12: 0x000000000000aac0  r13: 0x00007f92f9096650  r14: 0x0000000112560898  r15: 0x0000000000000000
      rip: 0x000000010a2262b1  rfl: 0x0000000000010206  cr2: 0x0000000000000bad
    Logical CPU: 3
    Binary Images:
    0x109f9e000 -   
    0x10a0bdff7  mds (707.3) <1448C11E-D2EC-305E-88C9-C6DAF1FEB535> /System/Library/Frameworks/CoreServices.framework/Frameworks/Metadata.framework /Support/mds
    0x10a110000 -   
    0x10a114ff7  com.apple.TCC (1.0 - 1) <F2F3B753-FC73-3543-8BBE-859FDBB4D6A6> /System/Library/PrivateFrameworks/TCC.framework/Versions/A/TCC
    0x10a120000 -   
    0x10a121fff  libDiagnosticMessagesClient.dylib (8) <8548E0DC-0D2F-30B6-B045-FE8A038E76D8> /usr/lib/libDiagnosticMessagesClient.dylib
    0x10a12a000 -   
    0x10a197ff7  com.apple.framework.IOKit (2.0 - 755.18.10) <142E19DD-1C8D-3D61-ABC8-83994A73279F> /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit
    0x10a1c9000 -   
    0x10a398fff  com.apple.spotlight.index (10.7.0 - 707.3) <DB706194-BC57-3853-9993-95DC58D3A07C> /System/Library/PrivateFrameworks/SpotlightIndex.framework/Versions/A/Spotlight Index
    0x10a3fb000 -   
    0x10a3fbfff  com.apple.CoreServices (57 - 57) <9DD44CB0-C644-35C3-8F57-0B41B3EC147D> /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices
    0x10a406000 -   
    0x10a40cfff  com.apple.DiskArbitration (2.5.1 - 2.5.1) <F7DAF7CC-5893-3F06-9168-3B0192B66D15> /System/Library/Frameworks/DiskArbitration.framework/Versions/A/DiskArbitration
    0x10a419000 -   
    0x10a775fff  com.apple.Foundation (6.8 - 945.11) <A5D41956-A354-3ACC-9355-BE200072223B> /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation
    0x10a99d000 -   
    0x10a9b0ff7  libbsm.0.dylib (32) <F497D3CE-40D9-3551-84B4-3D5E39600737> /usr/lib/libbsm.0.dylib
    0x10a9ba000 -   
    0x10a9ccff7  libz.1.dylib (43) <2A1551E8-A272-3DE5-B692-955974FE1416> /usr/lib/libz.1.dylib
    0x10a9d4000 -   
    0x10a9daff7  com.apple.MDSChannel (1.2 - 1.2) <05A6F55A-8197-316A-A127-DE6528F9B291> /System/Library/PrivateFrameworks/MDSChannel.framework/Versions/A/MDSChannel
    0x10a9e7000 -   
    0x10aa2aff7  com.apple.bom (12.0 - 192) <0BF1F2D2-3648-36B7-BE4B-551A0173209B> /System/Library/PrivateFrameworks/Bom.framework/Versions/A/Bom
    0x10aa42000 -   
    0x10aa47fff  com.apple.OpenDirectory (10.8 - 151.10) <CF44120B-9B01-32DD-852E-C9C0E1243FC0> /System/Library/Frameworks/OpenDirectory.framework/Versions/A/OpenDirectory
    0x10aa55000 -   
    0x10ab75fff  com.apple.desktopservices (1.7.2 - 1.7.2) <CDE8C2C2-C505-31B0-8C61-E40E4EA364A5> /System/Library/PrivateFrameworks/DesktopServicesPriv.framework/Versions/A/Desk topServicesPriv
    0x10abeb000 -   
    0x10abeeff7  com.apple.ServerInformation (1.1 - 1) <0F1E39E4-5195-39ED-B91C-CA72BAD74820> /System/Library/PrivateFrameworks/ServerInformation.framework/Versions/A/Server Information
    0x10abfb000 -   
    0x10abfefff  com.apple.AppleSystemInfo (2.0 - 2) <BC221376-361F-3F85-B284-DC251D3BB442> /System/Library/PrivateFrameworks/AppleSystemInfo.framework/Versions/A/AppleSys temInfo
    0x10ac0a000 -   
    0x10aedafff  com.apple.security (7.0 - 55179.1) <639641EF-8156-3190-890C-1053658E044A> /System/Library/Frameworks/Security.framework/Versions/A/Security
    0x10b012000 -   
    0x10b020fff  com.apple.Librarian (1.1 - 1) <1635162F-239A-341E-83C7-710C55E254AF> /System/Library/PrivateFrameworks/Librarian.framework/Versions/A/Librarian
    0x10b02f000 -   
    0x10b050fff  com.apple.Ubiquity (1.2 - 243.10) <F97D3A33-2C8B-3CFF-AF75-A74866D42853> /System/Library/PrivateFrameworks/Ubiquity.framework/Versions/A/Ubiquity
    0x10b067000 -   
    0x10b068ff7  libSystem.B.dylib (169.3) <9089D72D-E714-31E1-80C8-698A8E8B05AD> /usr/lib/libSystem.B.dylib
    0x10b075000 -   
    0x10b18d92f  libobjc.A.dylib (532.2) <90D31928-F48D-3E37-874F-220A51FD9E37> /usr/lib/libobjc.A.dylib
    0x10b1b3000 -   
    0x10b39cfff  com.apple.CoreFoundation (6.8 - 744.12) <EF002794-DAEF-31C6-866C-E3E3AC387A9F> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
    0x10b4fb000 -   
    0x10b547ff7  libauto.dylib (185.1) <73CDC482-16E3-3FC7-9BB4-FBA2DA44DBC2> /usr/lib/libauto.dylib
    0x10b55e000 -   
    0x10b75efff  libicucore.A.dylib (491.11.1) <CC318A27-878A-38CE-9292-1B98353FA9C7> /usr/lib/libicucore.A.dylib
    0x10b800000 -   
    0x10b868ff7  libc++.1.dylib (65.1) <20E31B90-19B9-3C2A-A9EB-474E08F9FE05> /usr/lib/libc++.1.dylib
    0x10b8c6000 -   
    0x10b8ebff7  libc++abi.dylib (24.4) <E7BD9363-1D25-3551-A68A-2E2FF6ABECD7> /usr/lib/libc++abi.dylib
    0x10b920000 -   
    0x10b925fff  libcache.dylib (57) <65187C6E-3FBF-3EB8-A1AA-389445E2984D> /usr/lib/system/libcache.dylib
    0x10b92d000 -   
    0x10b93bfff  libcommonCrypto.dylib (60026) <2D6537F5-1B5E-305C-A1CF-D1FA80CA3939> /usr/lib/system/libcommonCrypto.dylib
    0x10b94a000 -   
    0x10b94ffff  libcompiler_rt.dylib (30) <08F8731D-5961-39F1-AD00-4590321D24A9> /usr/lib/system/libcompiler_rt.dylib
    0x10b95b000 -   
    0x10b962fff  libcopyfile.dylib (89) <876573D0-E907-3566-A108-577EAD1B6182> /usr/lib/system/libcopyfile.dylib
    0x10b96f000 -   
    0x10b984ff7  libdispatch.dylib (228.23) <D26996BF-FC57-39EB-8829-F63585561E09> /usr/lib/system/libdispatch.dylib
    0x10b9a0000 -   
    0x10b9a1ff7  libdnsinfo.dylib (453.18) <E7595861-ECF9-336E-9901-BED2620FAA80> /usr/lib/system/libdnsinfo.dylib
    0x10b9a6000 -   
    0x10b9a9ff7  libdyld.dylib (210.2.3) <F59367C9-C110-382B-A695-9035A6DD387E> /usr/lib/system/libdyld.dylib
    0x10b9b1000 -   
    0x10b9b1fff  libkeymgr.dylib (25) <CC9E3394-BE16-397F-926B-E579B60EE429> /usr/lib/system/libkeymgr.dylib
    0x10b9b7000 -   
    0x10b9bffff  liblaunch.dylib (442.26.2) <2F71CAF8-6524-329E-AC56-C506658B4C0C> /usr/lib/system/liblaunch.dylib
    0x10b9cc000 -   
    0x10b9d2fff  libmacho.dylib (829) <BF332AD9-E89F-387E-92A4-6E1AB74BD4D9> /usr/lib/system/libmacho.dylib
    0x10b9d9000 -   
    0x10b9dbfff  libquarantine.dylib (52) <4BE2E642-A14F-340A-B482-5BD2AEFD9C24> /usr/lib/system/libquarantine.dylib
    0x10b9e6000 -   
    0x10b9e7ff7  libremovefile.dylib (23.1) <DBBFAF35-AC78-3856-92F6-6E4FD9DF14A2> /usr/lib/system/libremovefile.dylib
    0x10b9f1000 -   
    0x10b9f2fff  libsystem_blocks.dylib (59) <D92DCBC3-541C-37BD-AADE-ACC75A0C59C8> /usr/lib/system/libsystem_blocks.dylib
    0x10b9f8000 -   
    0x10bac4fe7  libsystem_c.dylib (825.25) <8CBCF9B9-EBB7-365E-A3FF-2F3850763C6B> /usr/lib/system/libsystem_c.dylib
    0x10bb0d000 -   
    0x10bb15ff7  libsystem_dnssd.dylib (379.32.1) <62AA0B84-188A-348B-8F9E-3E2DB08DB93C> /usr/lib/system/libsystem_dnssd.dylib
    0x10bb1c000 -   
    0x10bb52fff  libsystem_info.dylib (406.17) <4FFCA242-7F04-365F-87A6-D4EFB89503C1> /usr/lib/system/libsystem_info.dylib
    0x10bb6b000 -   
    0x10bb86ff7  libsystem_kernel.dylib (2050.18.24) <C0535565-35D1-31A7-A744-63D9F10F12A4> /usr/lib/system/libsystem_kernel.dylib
    0x10bb9a000 -   
    0x10bbc8ff7  libsystem_m.dylib (3022.6) <B434BE5C-25AB-3EBD-BAA7-5304B34E3441> /usr/lib/system/libsystem_m.dylib
    0x10bbd3000 -   
    0x10bbe1ff7  libsystem_network.dylib (77.10) <0D99F24E-56FE-380F-B81B-4A4C630EE587> /usr/lib/system/libsystem_network.dylib
    0x10bbf0000 -   
    0x10bbfbfff  libsystem_notify.dylib (98.5) <C49275CC-835A-3207-AFBA-8C01374927B6> /usr/lib/system/libsystem_notify.dylib
    0x10bc0a000 -   
    0x10bc0bff7  libsystem_sandbox.dylib (220) <3C3B03CF-C525-3CB3-8557-62E91B93AC95> /usr/lib/system/libsystem_sandbox.dylib
    0x10bc11000 -   
    0x10bc13ff7  libunc.dylib (25) <92805328-CD36-34FF-9436-571AB0485072> /usr/lib/system/libunc.dylib
    0x10bc1b000 -   
    0x10bc21ff7  libunwind.dylib (35.1) <21703D36-2DAB-3D8B-8442-EAAB23C060D3> /usr/lib/system/libunwind.dylib
    0x10bc2a000 -   
    0x10bc4cff7  libxpc.dylib (140.41) <FAC04D8B-680E-325F-8F0C-DD69859D0E01> /usr/lib/system/libxpc.dylib
    0x10bc68000 -   
    0x10bcb7ff7  libcorecrypto.dylib (106.2) <CE0C29A3-C420-339B-ADAA-52F4683233CC> /usr/lib/system/libcorecrypto.dylib
    0x10bcc9000 -   
    0x10bd32fff  libstdc++.6.dylib (56) <EAA2B53E-EADE-39CF-A0EF-FB9D4940672A> /usr/lib/libstdc++.6.dylib
    0x10bd97000 -   
    0x10bda5ff7  libkxld.dylib (2050.18.24) <7027CE49-007D-3553-8FFA-3E3B428B2316> /usr/lib/system/libkxld.dylib
    0x10bdaa000 -   
    0x10bdb7fff  com.apple.AppleFSCompression (49 - 1.0) <5508344A-2A7E-3122-9562-6F363910A80E> /System/Library/PrivateFrameworks/AppleFSCompression.framework/Versions/A/Apple FSCompression
    0x10bdc5000 -   
    0x10bf39fff  com.apple.CFNetwork (596.2.3 - 596.2.3) <6A16C2BD-1035-30F9-AE96-D9E3BB54A976> /System/Library/Frameworks/CFNetwork.framework/Versions/A/CFNetwork
    0x10bffd000 -   
    0x10c314ff7  com.apple.CoreServices.CarbonCore (1037.3 - 1037.3) <DF7CABCA-F2CB-345B-8EFF-F0F4E937B7FF> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonC ore.framework/Versions/A/CarbonCore
    0x10c395000 -   
    0x10c416fff  com.apple.Metadata (10.7.0 - 707.3) <A45D75C1-B311-39F0-AF4A-63FCCC098C1D> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Metadat a.framework/Versions/A/Metadata
    0x10c472000 -   
    0x10c518ff7  com.apple.CoreServices.OSServices (557.4 - 557.4) <841878A8-6F3E-300D-8F01-444B3CC1F41D> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/OSServi ces.framework/Versions/A/OSServices
    0x10c57b000 -   
    0x10c608ff7  com.apple.SearchKit (1.4.0 - 1.4.0) <C7F43889-F8BF-3CB9-AD66-11AEFCBCEDE7> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SearchK it.framework/Versions/A/SearchKit
    0x10c651000 -   
    0x10c6aeff7  com.apple.AE (645.3 - 645.3) <FF867ACA-8628-3E5A-8FA0-AF429B42C5D7> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/AE.fram ework/Versions/A/AE
    0x10c6de000 -   
    0x10c78ffff  com.apple.LaunchServices (539.7 - 539.7) <DA7C602E-5E01-31B8-925D-B45360CA089F> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchS ervices.framework/Versions/A/LaunchServices
    0x10c7e6000 -   
    0x10c817ff7  com.apple.DictionaryServices (1.2 - 184.4) <054F2D6F-9CFF-3EF1-9778-25C551B616C1> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Diction aryServices.framework/Versions/A/DictionaryServices
    0x10c83c000 -   
    0x10c88dff7  com.apple.SystemConfiguration (1.12.2 - 1.12.2) <E095637C-457F-3D8F-AE32-A032F9D5A46C> /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfi guration
    0x10c8c1000 -   
    0x10c9befff  libsqlite3.dylib (138.1) <ADE9CB98-D77D-300C-A32A-556B7440769F> /usr/lib/libsqlite3.dylib
    0x10c9d7000 -   
    0x10cad4ff7  libxml2.2.dylib (22.3) <47B09CB2-C636-3024-8B55-6040F7829B4C> /usr/lib/libxml2.2.dylib
    0x10cb0a000 -   
    0x10cb19ff7  libxar.1.dylib (105) <370ED355-E516-311E-BAFD-D80633A84BE1> /usr/lib/libxar.1.dylib
    0x10cb28000 -   
    0x10cb2cfff  libpam.2.dylib (20) <C8F45864-5B58-3237-87E1-2C258A1D73B8> /usr/lib/libpam.2.dylib
    0x10cb37000 -   
    0x10cb37fff  libOpenScriptingUtil.dylib (148.2) <B8061D13-C1B2-38D5-A723-9A98D64E67AC> /usr/lib/libOpenScriptingUtil.dylib
    0x10cb41000 -   
    0x10cb4efff  libbz2.1.0.dylib (29) <CE9785E8-B535-3504-B392-82F0064D9AF2> /usr/lib/libbz2.1.0.dylib
    0x10cb55000 -   
    0x10cb5cfff  com.apple.NetFS (5.0 - 4.0) <82E24B9A-7742-3DA3-9E99-ED267D98C05E> /System/Library/Frameworks/NetFS.framework/Versions/A/NetFS
    0x10cb68000 -   
    0x10cb75ff7  com.apple.NetAuth (4.0 - 4.0) <F5BC7D7D-AF28-3C83-A674-DADA48FF7810> /System/Library/PrivateFrameworks/NetAuth.framework/Versions/A/NetAuth
    0x10cb82000 -   
    0x10cbeffff  com.apple.datadetectorscore (4.0 - 269.1) <B69645EB-C4BF-3D52-A49B-CB1A1A88512F> /System/Library/PrivateFrameworks/DataDetectorsCore.framework/Versions/A/DataDe tectorsCore
    0x10cc2c000 -   
    0x10cc2dfff  liblangid.dylib (116) <864C409D-D56B-383E-9B44-A435A47F2346> /usr/lib/liblangid.dylib
    0x10cc35000 -   
    0x10cc56ff7  libCRFSuite.dylib (33) <736ABE58-8DED-3289-A042-C25AF7AE5B23> /usr/lib/libCRFSuite.dylib
    0x10cc66000 -   
    0x10cc7dfff  com.apple.GenerationalStorage (1.1 - 132.2) <3F5C87BD-D866-3732-8CB9-D23ED9784D6E> /System/Library/PrivateFrameworks/GenerationalStorage.framework/Versions/A/Gene rationalStorage
    0x10cc87000 -   
    0x10cc9efff  com.apple.CFOpenDirectory (10.8 - 151.10) <10F41DA4-AD54-3F52-B898-588D9A117171> /System/Library/Frameworks/OpenDirectory.framework/Versions/A/Frameworks/CFOpen Directory.framework/Versions/A/CFOpenDirectory
    0x10ccb9000 -   
    0x10cce4fff  libxslt.1.dylib (11.3) <441776B8-9130-3893-956F-39C85FFA644F> /usr/lib/libxslt.1.dylib
    0x10ccf8000 -   
    0x10cd03ff7  com.apple.bsd.ServiceManagement (2.0 - 2.0) <C12962D5-85FB-349E-AA56-64F4F487F219> /System/Library/Frameworks/ServiceManagement.framework/Versions/A/ServiceManage ment
    0x10cd10000 -   
    0x10cd2fff7  com.apple.ChunkingLibrary (2.0 - 133.2) <D2A746DE-002A-3C6C-961E-BE94E71DB835> /System/Library/PrivateFrameworks/ChunkingLibrary.framework/Versions/A/Chunking Library
    0x10cd3d000 -   
    0x10cdb5fff  com.apple.DCERPC (1.5 - 53.1.1) <25F4A15A-5252-3C70-A1D0-8145357F78B8> /System/Library/PrivateFrameworks/DCERPC.framework/Versions/A/DCERPC
    0x10cde0000 -   
    0x10ce1afff  com.apple.GSS (3.0 - 2.0) <0BDF8090-5EF4-3759-94DE-8521D74188AA> /System/Library/Frameworks/GSS.framework/Versions/A/GSS
    0x10ce3f000 -   
    0x10ce58ff7  com.apple.SMBClient (1.8 - 1.8) <B30889AB-8E45-3E57-9DC8-1212E2B87A95> /System/Library/PrivateFrameworks/SMBClient.framework/Versions/A/SMBClient
    0x10ce6a000 -   
    0x10ceecfff  com.apple.Heimdal (3.0 - 2.0) <660A6C64-4912-32C8-A332-B64164032A2D> /System/Library/PrivateFrameworks/Heimdal.framework/Versions/A/Heimdal
    0x10cf1b000 -   
    0x10cf3aff7  libresolv.9.dylib (51) <0882DC2D-A892-31FF-AD8C-0BB518C48B23> /usr/lib/libresolv.9.dylib
    0x10cf45000 -   
    0x10cf50fff  com.apple.CommonAuth (3.0 - 2.0) <74A86DDD-57D0-3178-AB74-E1F31DBFFC39> /System/Library/PrivateFrameworks/CommonAuth.framework/Versions/A/CommonAuth
    0x10cf57000 -   
    0x10cf59fff  com.apple.TrustEvaluationAgent (2.0 - 23) <A97D348B-32BF-3E52-8DF2-59BFAD21E1A3> /System/Library/PrivateFrameworks/TrustEvaluationAgent.framework/Versions/A/Tru stEvaluationAgent
    0x10cf63000 -   
    0x10cf70fff  com.apple.KerberosHelper (4.0 - 1.0) <6815439D-1A03-3251-99FE-CC24CF4C93C5> /System/Library/PrivateFrameworks/KerberosHelper.framework/Versions/A/KerberosH elper
    0x10cf81000 -   
    0x10cf81fff  com.apple.ApplicationServices (45 - 45) <A3ABF20B-ED3A-32B5-830E-B37831A45A80> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Application Services
    0x10cf88000 -   
    0x10d05aff7  com.apple.CoreText (260.0 - 275.16) <5BFC1D67-6A6F-38BC-9D90-9C712684EDAC> /System/Library/Frameworks/CoreText.framework/Versions/A/CoreText
    0x10d0c1000 -   
    0x10d1daff7  com.apple.ImageIO.framework (3.2.0 - 845) <553B9828-A7D9-3AE4-A214-1C33417545FD> /System/Library/Frameworks/ImageIO.framework/Versions/A/ImageIO
    0x10d238000 -   
    0x10dbc8c67  com.apple.CoreGraphics (1.600.0 - 324.6) <DCC70C6E-AB6D-3457-A823-7569CB29B107> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ CoreGraphics.framework/Versions/A/CoreGraphics
    0x10dcd7000 -   
    0x10dd57ff7  com.apple.ApplicationServices.ATS (332 - 341.1) <BD83B039-AB25-3E3E-9975-A67DAE66988B> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ATS.framework/Versions/A/ATS
    0x10dd84000 -   
    0x10de41ff7  com.apple.ColorSync (4.8.0 - 4.8.0) <6CE333AE-EDDB-3768-9598-9DB38041DC55> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ColorSync.framework/Versions/A/ColorSync
    0x10de8a000 -   
    0x10dee0fff  com.apple.HIServices (1.20 - 417) <A1129272-FEC8-350B-BA26-5A97F23C413D> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ HIServices.framework/Versions/A/HIServices
    0x10df18000 -   
    0x10df2bff7  com.apple.LangAnalysis (1.7.0 - 1.7.0) <2F2694E9-A7BC-33C7-B4CF-8EC907DF0FEB> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ LangAnalysis.framework/Versions/A/LangAnalysis
    0x10df3d000 -   
    0x10df97fff  com.apple.print.framework.PrintCore (8.1 - 387.1) <1FA17B75-33E6-35BD-9198-35F92E37B248> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ PrintCore.framework/Versions/A/PrintCore
    0x10dfc7000 -   
    0x10e006ff7  com.apple.QD (3.42 - 285) <8DF36FCA-C06B-30F4-A631-7BE2FF7E56D1> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ QD.framework/Versions/A/QD
    0x10e026000 -   
    0x10e03afff  com.apple.speech.synthesis.framework (4.1.12 - 4.1.12) <94EDF2AB-809C-3D15-BED5-7AD45B2A7C16> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ SpeechSynthesis.framework/Versions/A/SpeechSynthesis
    0x10e053000 -   
    0x10e057fff  com.apple.IOSurface (86.0.3 - 86.0.3) <C121DE83-ED12-3DC1-BDB3-4FCB29AB0571> /System/Library/Frameworks/IOSurface.framework/Versions/A/IOSurface
    0x10e066000 -   
    0x10e066fff  com.apple.Accelerate (1.8 - Accelerate 1.8) <6AD48543-0864-3D40-80CE-01F184F24B45> /System/Library/Frameworks/Accelerate.framework/Versions/A/Accelerate
    0x10e06f000 -   
    0x10e17afff  libFontParser.dylib (84.5) <617A7D30-C7BC-39FC-A1FE-59367B4A5719> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ATS.framework/Versions/A/Resources/libFontParser.dylib
    0x10e1de000 -   
    0x10e22dff7  libFontRegistry.dylib (100) <2E03D7DA-9B8F-31BB-8FB5-3D3B6272127F> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ATS.framework/Versions/A/Resources/libFontRegistry.dylib
    0x10e256000 -   
    0x10e3f1fef  com.apple.vImage (6.0 - 6.0) <FAE13169-295A-33A5-8E6B-7C2CC1407FA7> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vImage.fr amework/Versions/A/vImage
    0x10e418000 -   
    0x10e418fff  com.apple.Accelerate.vecLib (3.8 - vecLib 3.8) <B5A18EE8-DF81-38DD-ACAF-7076B2A26225> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.fr amework/Versions/A/vecLib
    0x10e421000 -   
    0x10e489fff  libvDSP.dylib (380.6) <CD4C5EEB-9E63-30C4-8103-7A5EAEA0BE60> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.fr amework/Versions/A/libvDSP.dylib
    0x10e494000 -   
    0x10e52efff  libvMisc.dylib (380.6) <714336EA-1C0E-3735-B31C-19DFDAAF6221> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.fr amework/Versions/A/libvMisc.dylib
    0x10e53d000 -   
    0x10e934fff  libLAPACK.dylib (1073.4) <D632EC8B-2BA0-3853-800A-20DA00A1091C> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.fr amework/Versions/A/libLAPACK.dylib
    0x10e99c000 -   
    0x10eb22fff  libBLAS.dylib (1073.4) <C102C0F6-8CB6-3B49-BA6B-2EB61F0B2784> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.fr amework/Versions/A/libBLAS.dylib
    0x10eb50000 -   
    0x10eb78fff  libJPEG.dylib (845) <A32618D7-FB91-3EE2-A105-5407B2F3F8D8> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libJPEG.dylib
    0x10eb82000 -   
    0x10ebd7ff7  libTIFF.dylib (845) <ADCB4683-69EB-318B-8BE7-5FDF38BCADAF> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libTIFF.dylib
    0x10ebea000 -   
    0x10ec0afff  libPng.dylib (845) <C3CDD2B4-3CB0-3F6D-8411-DAAF267E952B> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libPng.dylib
    0x10ec1a000 -   
    0x10ec1efff  libGIF.dylib (845) <2690CE83-E934-3EF8-A30A-996EDADCE3E4> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libGIF.dylib
    0x10ec25000 -   
    0x10ed27fff  libJP2.dylib (845) <405CAF25-0AA5-3C6B-A4A6-94471A1EDD2F> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libJP2.dylib
    0x10ed52000 -   
    0x10ed55fff  libRadiance.dylib (845) <E8956A35-494E-3014-8B86-362D32576116> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libRadiance.d ylib
    0x10ed5a000 -   
    0x10ed9efff  libcups.2.dylib (327) <9B3F3321-D2BC-3195-BF20-4008FC52A390> /usr/lib/libcups.2.dylib
    0x10edb7000 -   
    0x10edd9ff7  com.apple.Kerberos (2.0 - 1) <C49B8820-34ED-39D7-A407-A3E854153556> /System/Library/Frameworks/Kerberos.framework/Versions/A/Kerberos
    0x10edf3000 -   
    0x10eee8fff  libiconv.2.dylib (34) <FEE8B996-EB44-37FA-B96E-D379664DEFE1> /usr/lib/libiconv.2.dylib
    0x10eefe000 -   
    0x10fb2bff7  com.apple.AppKit (6.8 - 1187.34) <1FF64844-EB62-3F96-AED7-6525B7CCEC23> /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit
    0x110227000 -   
    0x11026afff  com.apple.RemoteViewServices (2.0 - 80.5) <F3A897C9-A277-3B56-8FB3-2BC2C10C33BF> /System/Library/PrivateFrameworks/RemoteViewServices.framework/Versions/A/Remot eViewServices
    0x1102a4000 -   
    0x1103f5fff  com.apple.audio.toolbox.AudioToolbox (1.8 - 1.8) <833DA682-A3C1-39E7-AEC3-9EDC734DE2A9> /System/Library/Frameworks/AudioToolbox.framework/Versions/A/AudioToolbox
    0x11047f000 -   
    0x11047fffd  com.apple.audio.units.AudioUnit (1.8 - 1.8) <29E2C990-3617-3FA2-BDD7-DB7DF493E443> /System/Library/Frameworks/AudioUnit.framework/Versions/A/AudioUnit
    0x110486000 -   
    0x1106bbff7  com.apple.CoreData (106.1 - 407.7) <24E0A6B4-9ECA-3D12-B26A-72B9DCF09768> /System/Library/Frameworks/CoreData.framework/Versions/A/CoreData
    0x1107c3000 -   
    0x110af3ff7  com.apple.HIToolbox (2.0 - 625) <317F75F7-4B0F-35F5-89A7-F20BA60AC944> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.fra mework/Versions/A/HIToolbox
    0x110c4a000 -   
    0x110df8fff  com.apple.QuartzCore (1.8 - 304.0) <897FAA5D-FF13-33FE-878B-B164D684F019> /System/Library/Frameworks/QuartzCore.framework/Versions/A/QuartzCore
    0x110eb1000 -   
    0x110ebbfff  com.apple.speech.recognition.framework (4.1.5 - 4.1.5) <D803919C-3102-3515-A178-61E9C86C46A1> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SpeechRecogni tion.framework/Versions/A/SpeechRecognition
    0x110ec5000 -   
    0x110f8aff7  com.apple.coreui (2.0 - 181.1) <83D2C92D-6842-3C9D-9289-39D5B4554C3A> /System/Library/PrivateFrameworks/CoreUI.framework/Versions/A/CoreUI
    0x111002000 -   
    0x11105ffff  com.apple.audio.CoreAudio (4.1.0 - 4.1.0) <B3198BD6-EA1D-3E5E-ADD4-37D8E6B72678> /System/Library/Frameworks/CoreAudio.framework/Versions/A/CoreAudio
    0x111084000 -   
    0x11109afff  com.apple.MultitouchSupport.framework (235.28 - 235.28) <BD78B16E-9B5A-3E07-93B4-13AD1A538CAC> /System/Library/PrivateFrameworks/MultitouchSupport.framework/Versions/A/Multit ouchSupport
    0x1110b0000 -   
    0x1110d7ff7  com.apple.PerformanceAnalysis (1.16 - 16) <E4888388-F41B-313E-9CBB-5807D077BDA9> /System/Library/PrivateFrameworks/PerformanceAnalysis.framework/Versions/A/Perf ormanceAnalysis
    0x1110fd000 -   
    0x11110cff7  com.apple.opengl (1.8.6 - 1.8.6) <720CC06C-0D01-37AE-BB3D-D7F0242B262A> /System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL
    0x111118000 -   
    0x1111f2ff7  com.apple.backup.framework (1.4.1 - 1.4.1) <A3CFCA9E-717C-302D-821B-16FD35E6673F> /System/Library/PrivateFrameworks/Backup.framework/Versions/A/Backup
    0x111279000 -   
    0x1112a0fff  com.apple.framework.familycontrols (4.1 - 410) <AE49B2AB-7D2B-3D52-8E21-60EBEA1A38E6> /System/Library/PrivateFrameworks/FamilyControls.framework/Versions/A/FamilyCon trols
    0x1112c1000 -   
    0x11135fff7  com.apple.ink.framework (10.8.2 - 150) <84B9825C-3822-375F-BE58-A753444FBDE2> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Ink.framework /Versions/A/Ink
    0x111397000 -   
    0x1113c1ff7  com.apple.CoreVideo (1.8 - 99.3) <C424838A-889C-39E5-8108-FD05C93D26A0> /System/Library/Frameworks/CoreVideo.framework/Versions/A/CoreVideo
    0x1113dd000 -   
    0x111681fff  com.apple.CoreImage (8.2.2 - 1.0.1) <930B0B23-DD84-3B0C-B5A9-C09B7068A6F0> /System/Library/Frameworks/QuartzCore.framework/Versions/A/Frameworks/CoreImage .framework/Versions/A/CoreImage
    0x111767000 -   
    0x1117beff7  com.apple.ScalableUserInterface (1.0 - 1) <F1D43DFB-1796-361B-AD4B-39F1EED3BE19> /System/Library/Frameworks/QuartzCore.framework/Versions/A/Frameworks/ScalableU serInterface.framework/Versions/A/ScalableUserInterface
    0x1117ea000 -   
    0x111834ff7  libGLU.dylib (8.6.1) <DF45C1E3-3884-3991-B84F-F39B482E8BF8> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLU.dylib
    0x111844000 -   
    0x11184afff  libGFXShared.dylib (8.6.1) <CF55E720-1B9E-3E24-A1DA-7FA8B261CD8E> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGFXShared.d ylib
    0x111852000 -   
    0x111866fff  libGL.dylib (8.6.1) <2E00615F-97F5-34EB-BE07-75A24F3C18D7> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGL.dylib
    0x11187a000 -   
    0x1118b7fe7  libGLImage.dylib (8.6.1) <7F31DD61-3110-3541-A9BB-035CD1262E50> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLImage.dyl ib
    0x1118c3000 -   
    0x1118c5fff  libCVMSPluginSupport.dylib (8.6.1) <7EFDA31E-E463-3897-A8DC-7FD266EB713E> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCVMSPluginS upport.dylib
    0x1118ca000 -   
    0x1118cefff  libCoreVMClient.dylib (24.4) <55F71158-ADEE-3863-92E9-4772DCEA8E31> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCoreVMClien t.dylib
    0x1118d9000 -   
    0x1118e5fff  com.apple.CrashReporterSupport (10.8.2 - 415) <55783BF9-125E-3F9C-A412-6A095ECD9353> /System/Library/PrivateFrameworks/CrashReporterSupport.framework/Versions/A/Cra shReporterSupport
    0x1118fb000 -   
    0x111951ff7  com.apple.opencl (2.1.20 - 2.1.20) <AF142CA4-EA1D-31B0-A48F-AA2B75D4309E> /System/Library/Frameworks/OpenCL.framework/Versions/A/OpenCL
    0x111967000 -   
    0x111d84fff  FaceCoreLight (2.4.1) <A34C9575-C4C1-31B1-809B-7751070B4E8B> /System/Library/PrivateFrameworks/FaceCoreLight.framework/Versions/A/FaceCoreLi ght
    0x111f99000 -   
    0x111f99fff  com.apple.vecLib (3.8 - vecLib 3.8) <794317C7-4E38-338A-A874-5E18001C8503> /System/Library/Frameworks/vecLib.framework/Versions/A/vecLib
    0x111fa1000 -   
    0x112020ff7  com.apple.securityfoundation (6.0 - 55115.4) <8676E0DF-295F-3690-BDAA-6C9C1D210B88> /System/Library/Frameworks/SecurityFoundation.framework/Versions/A/SecurityFoun dation
    0x112066000 -   
    0x11206ffff  com.apple.CommerceCore (1.0 - 26) <997CD214-BC78-3C61-A1B8-813EA1CB9997> /System/Library/PrivateFrameworks/CommerceKit.framework/Versions/A/Frameworks/C ommerceCore.framework/Versions/A/CommerceCore
    0x11207c000 -   
    0x112116fff  com.apple.CoreSymbolication (3.0 - 87) <3D9CBE8D-F047-3DFA-B067-F9589E2AF8BA> /System/Library/PrivateFrameworks/CoreSymbolication.framework/Versions/A/CoreSy mbolication
    0x112162000 -   
    0x1121beff7  com.apple.Symbolication (1.3 - 93) <97F3B1D2-D81D-3F37-87B3-B9A686124CF5> /System/Library/PrivateFrameworks/Symbolication.framework/Versions/A/Symbolicat ion
    0x112201000 -   
    0x112237fff  com.apple.DebugSymbols (98 - 98) <14E788B1-4EB2-3FD7-934B-849534DFC198> /System/Library/PrivateFrameworks/DebugSymbols.framework/Versions/A/DebugSymbol s
    0x112698000 -   
    0x1126c6fff  com.apple.CoreServicesInternal (154.2 - 154.2) <3E6196E6-F3B4-316F-9E1F-13B6B9694C7E> /System/Library/PrivateFrameworks/CoreServicesInternal.framework/CoreServicesIn ternal
    0x119cd7000 -   
    0x119df0ff7  libmecab.1.0.0.dylib (359.50) <BDE1F58F-ED72-34BB-9027-2A7AA384F82E> /usr/lib/libmecab.1.0.0.dylib
    0x7fff69b9e000 -
    0x7fff69bd293f  dyld (210.2.3) <36CAA36E-72BC-3E48-96D9-B96A2DF77730> /usr/lib/dyld
    External Modification Summary:
      Calls made by other processes targeting this process:
    task_for_pid: 6
    thread_create: 0
    thread_set_state: 0
      Calls made by this process:
    task_for_pid: 0
    thread_create: 0
    thread_set_state: 0
      Calls made by all processes on this machine:
    task_for_pid: 2082
    thread_create: 0
    thread_set_state: 0
    VM Region Summary:
    ReadOnly portion of Libraries: Total=119.0M resident=105.4M(89%) swapped_out_or_unallocated=13.6M(11%)
    Writable regions: Total=200.0M written=37.3M(19%) resident=43.1M(22%) swapped_out=0K(0%) unallocated=156.9M(78%)
    REGION TYPE                 
    VIRTUAL
    ===========                 
    =======
    CoreServices                  
    2568K
    MALLOC                       
    136.6M
    MALLOC guard page               
    96K
    Memory tag=241                 
    392K
    Memory tag=243                
    24.0M
    Memory tag=243 (reserved)     
    6144K   
    reserved VM address space (unallocated)
    Memory tag=244                
    5440K
    Memory tag=246                
    4096K
    Memory tag=246 (reserved)     
    4096K   
    reserved VM address space (unallocated)
    Memory tag=247                
    3072K
    Memory tag=255                 
    288K
    STACK GUARD                   
    56.0M
    Stack                         
    11.0M
    VM_ALLOCATE                    
    424K
    __DATA                        
    10.5M
    __IMAGE                        
    528K
    __LINKEDIT                    
    24.5M
    __TEXT                        
    94.8M
    __UNICODE                      
    544K
    mapped file                  
    249.7M
    shared memory                 
    1136K
    ===========                 
    =======
    TOTAL                        
    635.2M
    TOTAL, minus reserved VM space
    625.2M
    Trust me when I tell you how much I appreciate your help.

Maybe you are looking for

  • I carry my macbook around all day long at school while it's asleep. Am I damaging it?

    I've had a pro for a little over a month now. For the past couple weeks it's been lagging during startup and general activity of different applications (even safari). I only use it for school and music, nothing too crazy. I'm wondering, could it be t

  • Wireless dhcp issue after upgrading WLC to 7.6.100

    Hi All, We have upgraded our controllers to version 7.6.100. After upgrading, the access points also upgraded their version to 15.2(4)JB3. But, the problem is that after this process the APs do not get IP. It stays on this state: *Sep 26 03:55:36.334

  • TABLE SIZE 및 INDEX SIZE(크기) 계산

    제품 : ORACLE SERVER 작성날짜 : 2002-10-15 TABLE SIZE 및 INDEX SIZE(크기) 계산 =================================== 1. TABLE SIZE 계산 공식(ORACLE BLOCK SIZE : 2K 로 가정) $ sqlplus scott/tiger SQL> SELECT GREATEST(4, ceil(ROW_COUNT / ((round(((1958 - (initrans * 23))

  • Why can i not play BBC player

    i have a new imac and cannot play i player probably a simple solution..can anyone help? thank you

  • How to see IMAP folders on BB Torch 8910?

    I've created folders for various clients in my email system but I can't figure out how to see them or set them up on my Torch. Any ideas?