Update NetRestore Images (New Hardware)
Good Afternoon,
I've just taken over Mac Imaging from a colleague who's moved in to another department, we have 2 Mavericks images now, 1 for schools and 1 for corporate. They are easy to create (we build the users and software then capture the image with NetRestore on Mavericks Server) but everytime we get a new MacBook with updated hardware the image fails to go on the new machine (it is backward compatible with no issues).
I come from a Windows backgroud where we use SysPrep to make sure all images are hardware independent - there doesn't seem to be a tool which will do this for Mac, not easily anyway.
My colleague used to create 2 new images completely from scratch every time hardware changed, this to me seems like a waste of time, I would if possible like to see if we could just update the images (via a combo update or something?), run software updates and then recapture it, saving literally a days work every time a new piece of hardware comes out.
Has anyone done this effectively? I know their are 3rd party tools availible that may be able to help but if possible I would like to do it whilst still using NetRestore (our deployment team are familiar with this method).
Kind Regards,
Jon Roberts
We have had some success building images entirely from media. We have an SIU worflow that makes an image directly from the latest OSX installer as downloaded from the App store. Plus a long list of application packages like Office and Adobe CS. So when we get a new version of OSX and/or an application package we just rerun the workflow. We do not install all this stuff over and over again on a "golden" machine du jour.
The (non-tirvial) cost of this approach is that we have to re-package all our apps for non-interactive installation. Most commercial applications are distributed in a manner assuming interactive installation on one Mac at a time. The benefit is that we get clean installs, reproducible results and fewer surprises. We have found the Composer tool from JAMF to be invaluable for creating these application packages.
Also, you can speed up SIU builds dramatically using solid state disk.
Similar Messages
-
HT4178 Updating NetRestore Images for New Hardware?
Good Afternoon,
I've just taken over Mac Imaging from a colleague who's moved in to another department, we have 2 Mavericks images now, 1 for schools and 1 for corporate. They are easy to create (we build the users and software then capture the image with NetRestore on Mavericks Server) but everytime we get a new MacBook with updated hardware the image fails to go on the new machine (it is backward compatible with no issues).
I come from a Windows backgroud where we use SysPrep to make sure all images are hardware independent - there doesn't seem to be a tool which will do this for Mac, not easily anyway.
My colleague used to create 2 new images completely from scratch every time hardware changed, this to me seems like a waste of time, I would if possible like to see if we could just update the images (via a combo update or something?), run software updates and then recapture it, saving literally a days work every time a new piece of hardware comes out.
Has anyone done this effectively? I know their are 3rd party tools availible that may be able to help but if possible I would like to do it whilst still using NetRestore (our deployment team are familiar with this method).
Kind Regards,
Jon RobertsYes, your process as described seems appropriate. Have you tried this on an example? Have you run into any issues?
Regards,
Brandon V.
Applications Engineer
National Instruments -
Do Combo Updates include new hardware drivers / info?
So I'm having a debate with fellow OS X techies and we're split and would like to know a more definitive answer.
Do OS X Combo Updates actually take into account new hardware released after the .0 release of an OS? So for instance, 10.6 was released. Since then several Mac models have been introduced. Can I use the 10.6 retail DVD on the newer Mac models if I cannot locate those discs, and then run Combo Update to 10.6.4 on say a recent MBP? Or must I use the 10.6.3 MBP discs and move to 10.6.4 for true compatibility?
When 10.6.5 is released to the public, can that be used for the new Mac Minis that have a special build of 10.6.4?Here is one case right now the Mid-2010 Mac Pro all run OS X builds that are later than 10.6.4 (and there are likely changes even here every two weeks as they ship). Drivers needed for new graphic cards (ATI 5870 and 5770) are newer than ATI drivers for say iMac 2010 that has an ATI graphics unit.
And changes to support new processors, memory configurations, native booting into 64-bit kernel mode, to name a few changes.
Eventually all of those changes should make their way into general available standalone updates (delta and combo) at some point.
As for your need to build images, I'll leave that to others to sift through. My gut feeling, that OS X Server is the only time/place that would fit in. Windows Home Server NAS products like HP Smart MediaServer NAS support TimeMachine, SuperDuper, and ability to manage a mix of Macs and PCs. Something an Xserve in a client-server environment, with even more tools to deploy and handle remove images and push updates (and store updates locally rather than each seat have to redownload all over again).
Nehalem family of processors shipped in early 2009, before that was Penryn and found in say Mid-2008 iMac, Early Mac Pro 2008 (I'm sure you know or can find that on Apple or even Wikipedia on Macs and Intel processors). -
i just upgraded my iphone 3gs to ios 6 not sure if it updated but now when i turn on my phone it says automatically that i need to connect it to itunes using the USB port but when i connect it it comes up as new hardware and cannot find a program/software for my device even though i have the latest itunes on my computer. i have tried reinstalling itunes but it still cannot find my phone and now i cannot use my phone as it is stuck on the sync to itunes screen
Have you downloaded and installed the latest version of iTunes from here:
http://www.apple.com/itunes/download/ -
Hi, I have been trying to update many things on my 2009 white macbook. Everytime I do it tells me I need a different version. I don't know what versions I need or even where to begin or if I need to purchase new hardware? It says my version is 10.5.8. I have tried downloading 10.6 but not sure what to do. Everyone else seems to be updating there's and mine is way behind however it still tells me I have no software updates...Any suggestions?
You have to understand the difference between an Update and an Upgrade.
An Update is a free change to add to the base code or as a bug fix within an existing Operating System. Such as the .8 added to 10.5.
An Upgrade is a complete new Operating System that must be purchased. Such as 10.5 Leopard to 10.6 Snow Leopard.
10.5 Leopard was based on Power PC code and was written to be able to run on both Power PC and Intel processors.
10.6 Snow Leopard has completely rewritten code and only runs on Intel Macs.
10.7 Lion used some 32 bit which allows it to run on Late 2006 through Early 2008 MacBooks and a lot of 64 bit code.
10.8 Mountain Lion is pure 64 bit, which excludes more systems than Lion did. It's not something you can add memory to, for example, as it involves the base architecture. -
Does the 7th generation nano consist of new hardware or is it the 6th generation with new software?
It is a 6th gen that currently comes with 1.1 that you update to 1.2. Also sells for a lower cost and doesn't require you to pay more for the nike+ kit.
https://discussions.apple.com/message/16297530#16297530 -
My Ipod is stuck at restore mode, when I downloaded fixrecovery and zlib1, they gave me a file which I can't open iBSS.n72ap. Fixrecovery wanted me to put it in DFU mode and I did but a window from my computer pops up telling me that it found new hardware and wants a CDrom to install. The ipod did not come with a CDrom software. It wont go back, and iTunes does not recongnize it. What should I do?
Try here.
iOS: Device not recognized in iTunes for Windows
I would first try removing and reinstalling all the Apple software using:
Removing and reinstalling iTunes, QuickTime, and other software components for Windows Vista or Windows 7
or
Removing and Reinstalling iTunes, QuickTime, and other software components for Windows XP -
Snow Leopard client for NetRestore image not being recognized in Mountain Lion Server
I target firewired a MacBook Pro running Snow Leopard and ran System Imaging Utility and the machine does not show up as an option. Does Mountain Lion Server support Snow Leopard NetRestore images or am I doing something wrong?
I'm actually trying to figure that out as well. We have 10.5, 10.6, 10.7, and 10.8 Images we wanted to put together for our netrestore images on our server, but can only do 10.8 images currently.
We also have the AppleCare Helpdesk diagnostic kit which includes hardware tests, we were only able to get the newer mid-2012 and late-2012 Diagnostic utilities to netboot but none of the older ones.
So do we need a server running the older OS to get these or is there a better alternative? i mean really shouldnt be a problem considering theyre running inside of an image and dont rely heavily on the server resources other than to say "Yep, goto this file/directory".
I'd like to know more as well.... -
When deploying a single server on new hardware, do you virtualize it or not?
There are a few questions that I've found on ServerFault that hint around this topic, and while it may be somewhat opinion-based, I think it can fall into that "good subjective" category based on the below:
Constructive subjective questions:
* tend to have long, not short, answers
* have a constructive, fair, and impartial tone
* invite sharing experiences over opinions
* insist that opinion be backed up with facts and references
* are more than just mindless social fun
So that out of the way.
I'm helping out a fellow sysadmin that is replacing an older physical server running Windows 2003 and he's looking to not only replace the hardware but "upgrade" to 2012 R2 in the process.
In our discussions about his replacement hardware, we discussed the possibility of him installing ESXi and then making the 2012 "server" a VM and migrating the old apps/files/roles from the 2003 server to the VM instead of to a non-VM
install on the new hardware.
He doesn't perceive any time in the next few years the need to move anything else to a VM or create additional VMs, so in the end this will either be new hardware running a normal install or new hardware running a single VM on ESXi.
My own experience would lean towards a VM still, there isn't a truly compelling reason to do so other than possibilities that may arise to create additional VMs. But there is the additional overhead and management aspect of the hypervisor now, albeit
I have experienced better management capabilities and reporting capabilities with a VM.
So with the premise of hoping this can stay in the "good subjective" category to help others in the future,what
experiences/facts/references/constructive answers do you have to help support either outcome (virtualizing or not a single "server")?In the general case, the advantage of putting a standalone server on a hypervisor is future-proofing. It makes future expansion or upgrades much easier, much faster, and as a result, cheaper. The primary drawback is additional complexity and cost (not necessarily
financially, but from a man-hours and time perspective).
So, to come to a decision, I ask myself three questions (and usually prefer to put the server on a hypervisor, for what it's worth).
How big is the added cost of the hypervisor?
Financially, it's usually minimal or non-existent.
Both VMware and Microsoft have licensing options that allow you to run a host and a single guest for free, and this is sufficient for most standalone servers, exceptions generally being servers that are especially resource-intensive.
From a management and resource standpoint, determining cost can be a bit trickier.
You basically double the cost of maintaining the system, because now you have two systems to monitor, manage and keep up-to-date with patches and updates (the guest OS and the host OS).
For most uses, this is not a big deal, as it's not terribly taxing to maintain one server, though for some especially small or especially technically challenged organizations, this can be a real concern.
You also add to the technical skills required. Now, instead of just needing someone who can download updates from Windows Update, you need someone who knows enough to manage and maintain the virtualization environment.
Again, not usually a problem, but sometimes, it's more than an organization can handle.
How big is the benefit from ease-of upgrade or expansion?
This boils down to how likely future expansion is, because obviously, if they don't expand or upgrade their server assets, this benefit is zero.
If this is the type of organization that's just going to stuff the server in a corner and forget about it for 10 years until it needs to be replaced anyway, there's no point.
If they're likely to grow organizationally, or even just technically (by say adding new servers with different roles, instead of just having an all-in-one server), then this provides a fairly substantial benefit.
What's the benefit now?
Virtualization bring benefits beyond future-proofing, and in some use-cases, they can be substantial.
The most obvious one is the ability to create snapshots and trivial-to-restore backups before doing something on the system, so if it goes bad, you can revert in one click.
The ability to experiment with other VMs (and play the "what if" game) is another one I've seen management get excited about. For my money, though, the biggest benefit is the added portability you get from running a production server on a hypervisor. If something
goes really wrong and you get yourself into a disaster-recovery or restore-from-backups situation, it is almost infinitely easier to restore a disk image to a machine running the same hypervisor than trying to do a bare-metal restore. -
Hello all,
We are attempting to create a NetRestore image of a Macbook Pro running Yosemite (10.10) from a Mavericks (10.9) Mac Mini running OS X Server. Previously we connected a Macbook Pro in target mode to our Mac Mini (both running Mavericks) using System Image Utility to create a NetRestore SP0 from which we could deploy to all of the computers in our lab running Mavericks. We did this as a method to update the applications on each iMac locally from the hosted NetRestore image we created. We are now receiving several new iMacs and Mac Pros running Yosemite (10.10) native and we wish to use the same process to update these machines from our Mac Mini (Mavericks) running OS X Server.
We are now trying create a NetRestore image from a native Yosemite Macbook Pro using System Image Utility on our Mac Mini (running Mavericks) however when the Yosemite Macbook Pro is connected in target mode, System Image Utility does not recognize the volume although it is recognized by our Mac mini (e.g., the yellow-orange image icon is displayed on the Mac Mini's desktop). Some of our lab computers are still running Mavericks, and my understanding is that Mavericks NetRestore Images cannot be created from a Mac Mini with OS X Server running Yosemite.
Must we upgrade our Mac mini from Mavericks to Yosemite for System Image Utility to recognize our Yosemite Macbook Pro (connected in target mode) in order to create a Yosemite NetRestore Image?
Note: We know there are better alternatives (e.g., Munki) to deploy updates to our machines via server and are working to establish a more convenient process, but this is the method we have been comfortable using before running into the above issue.
Thanks all!You could use DeployStudio to 'serve' both Yosemite and Mavericks images from your Mac mini which can still run Mavericks. You would also use DeployStudio to make an image of the MacBook once it has been loaded and then this image can be restored to multiple machines.
See http://www.deploystudio.com -
Code doesn't update when uploading new files to website.
code doesn't update when uploading new files to website. I was using an old DW version for a long time then forced to upgrade when I bought my MacBook Pro. Now when I make changes to my pages and link to new files etc on my harddrive, when i upload the pages it won't image because the code still points to harddrive (this did not used to be a problem)... I manually changed the code on the web host site to point to the site and it loaded fine. But now my files on my harddrive also point to the web host files and now don't image on my computer. I never had to worry about this so far and wonder if the new version has a setting I'm supposed to be aware of so that I can design on my hardrive and upload and it knows that the files are being uploaded with it? Ugh hpe this makes sense - I'm NOT a webs designer and the new DW is way more than I use in it's technology.
Hi
This sounds like you have not defined your site in the site definition.
Follow the steps in these 2 tutorials to set-up your site locally and for the remote server -
http://www.adobe.com/devnet/dreamweaver/articles/first_website_pt1.html
http://www.adobe.com/devnet/dreamweaver/articles/first_website_pt6.html
PZ -
To my non-arrival notification oo update.
Updated with the new version downloaded from Appstore.
The previous version worked fine.
I have not time to open the library - the program closes. For 1-2 seconds I see the old look of your library.
Process: Aperture [831]
Path: /Applications/Aperture.app/Contents/MacOS/Aperture
Identifier: com.apple.Aperture
Version: 3.4.4 (3.4.4)
Build Info: Aperture-320085000000000~4
App Item ID: 408981426
App External ID: 14995585
Code Type: X86-64 (Native)
Parent Process: launchd [134]
User ID: 501
Date/Time: 2013-05-13 08:39:42.877 +0400
OS Version: Mac OS X 10.8.3 (12D78)
Report Version: 10
Interval Since Last Report: 25451 sec
Crashes Since Last Report: 15
Per-App Interval Since Last Report: 275 sec
Per-App Crashes Since Last Report: 15
Anonymous UUID: 0480FD60-05CB-BDA2-9EC7-9186A9908C06
Crashed Thread: 12
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Application Specific Information:
*** Terminating app due to uncaught exception 'NSRangeException', reason: '*** -[__NSCFString substringToIndex:]: Range or index out of bounds'
terminate called throwing an exception
abort() called
Application Specific Backtrace 1:
0 CoreFoundation 0x00007fff9566cb06 __exceptionPreprocess + 198
1 libobjc.A.dylib 0x00007fff8b2b93f0 objc_exception_throw + 43
2 CoreFoundation 0x00007fff9566c8dc +[NSException raise:format:] + 204
3 Foundation 0x00007fff935b8ee9 -[NSString substringToIndex:] + 97
4 RedRock 0x000000010b7aa994 +[RKFileNamingPolicy fileSafeName:] + 221
5 RedRock 0x000000010b955958 -[RKVersion(Imaging) proxyWritePath:] + 141
6 RedRock 0x000000010b955edf -[RKVersion(Imaging) absoluteProxyWritePath:] + 28
7 RedRock 0x000000010b949b97 -[JPEGFileCacheStore filePathForVersion:key:withWrite:] + 51
8 RedRock 0x000000010ba1dd64 -[IPMiniJPEGFileCacheStore newCachePageLookupForRequest:] + 428
9 ProXTCore 0x000000010cf9114e -[XTCachePersistentPolicy newCachePageOnLookupForRequest:] + 136
10 ProXTCore 0x000000010cf884e1 -[XTCacheEvictionPolicy newCachePageLookupForRequest:] + 23
11 ProXTCore 0x000000010cf8e32a -[XTCacheStore newObjectLookupInEvictionPolicyForRequest:] + 44
12 ProXTCore 0x000000010cf8e524 -[XTCacheStore newObjectLookupRequest:rootStore:] + 39
13 ProXTCore 0x000000010cf8f28e -[XTCacheStore newObjectForRequest:] + 65
14 Geode 0x000000010cd2cfc0 -[DGTier2Factory readRequest:intoPageRef:] + 482
15 Geode 0x000000010cd2d604 -[DGTier2Factory cache:cacheStore:onFulfillRequest:intoPageRef:] + 589
16 ProXTCore 0x000000010cf88f47 -[XTCacheFactory backgroundFulfillment:] + 532
17 ProXTCore 0x000000010cf69736 -[XTDistributor distributeMessage:] + 444
18 ProXTCore 0x000000010cf690fa -[XTThread handleMessage:] + 342
19 ProXTCore 0x000000010cf67eb3 -[XTThread run:] + 345
20 Foundation 0x00007fff935eecd2 __NSThread__main__ + 1345
21 libsystem_c.dylib 0x00007fff8c7a97a2 _pthread_start + 327
22 libsystem_c.dylib 0x00007fff8c7961e1 thread_start + 13
Thread 0:: Dispatch queue: com.apple.main-thread
0 libFontParser.dylib 0x00007fff8f00ff4e TTrueTypeFontHandler::TGlyphHeaderData::GetHead() const + 26
1 libFontParser.dylib 0x00007fff8f011aa3 TTrueTypeFontHandler::GetBounds(unsigned short, double&, double&, double&, double&, bool) const + 107
2 libFontParser.dylib 0x00007fff8f012408 FPFontGetGlyphIdealBounds + 203
3 libCGXType.A.dylib 0x00007fff91f2b4ed xt_font_get_glyph_bboxes + 448
4 libCGXType.A.dylib 0x00007fff91f2b32b get_glyph_bboxes + 9
5 com.apple.CoreGraphics 0x00007fff90cf40d5 CGFontGetGlyphBBoxes + 140
6 com.apple.CoreGraphics 0x00007fff90cf8364 get_char_top + 45
7 com.apple.CoreGraphics 0x00007fff90cf7fe0 CGFontAutohintTransformCreate + 380
8 com.apple.CoreGraphics 0x00007fff90d2f6a7 CGFontCreateGlyphBitmap32 + 339
9 com.apple.CoreGraphics 0x00007fff90cf76f3 CGGlyphLockLockGlyphBitmaps + 1172
10 libRIP.A.dylib 0x00007fff90589173 ripc_DrawGlyphs + 1865
11 com.apple.CoreGraphics 0x00007fff90cb6e48 draw_glyphs + 699
12 com.apple.CoreGraphics 0x00007fff90cf5a63 CGContextShowGlyphsWithAdvances + 489
13 com.apple.CoreText 0x00007fff91e6f3ab CTFontDrawGlyphsWithAdvances + 105
14 com.apple.AppKit 0x00007fff8fa1cbc4 -[NSLineFragmentRenderingContext drawAtPoint:inContext:] + 6402
15 com.apple.AppKit 0x00007fff8fa0d1eb _NSStringDrawingCore + 3052
16 com.apple.AppKit 0x00007fff8fa000e7 _NSDrawTextCell + 6244
17 com.apple.AppKit 0x00007fff8fc60075 _NXDrawTextCell + 56
18 com.apple.prokit 0x000000010c2d45ea -[NSProTextFieldCell drawInteriorWithFrame:inView:] + 1092
19 com.apple.prokit 0x000000010c2d4e5b -[NSProTextFieldCell drawWithFrame:inView:] + 371
20 com.apple.prokit 0x000000010c2cc264 -[NSProPopUpButtonCell drawTitleWithFrame:inView:] + 708
21 com.apple.AppKit 0x00007fff8fac6216 -[NSMenuItemCell drawInteriorWithFrame:inView:] + 510
22 com.apple.AppKit 0x00007fff8fa01806 -[NSControl drawRect:] + 400
23 com.apple.AppKit 0x00007fff8f9f5094 -[NSView _drawRect:clip:] + 4217
24 com.apple.AppKit 0x00007fff8f9f36f1 -[NSView _recursiveDisplayAllDirtyWithLockFocus:visRect:] + 1656
25 com.apple.AppKit 0x00007fff8f9f3b09 -[NSView _recursiveDisplayAllDirtyWithLockFocus:visRect:] + 2704
26 com.apple.AppKit 0x00007fff8f9f3b09 -[NSView _recursiveDisplayAllDirtyWithLockFocus:visRect:] + 2704
27 com.apple.AppKit 0x00007fff8f9f3b09 -[NSView _recursiveDisplayAllDirtyWithLockFocus:visRect:] + 2704
28 com.apple.AppKit 0x00007fff8f9f3b09 -[NSView _recursiveDisplayAllDirtyWithLockFocus:visRect:] + 2704
29 com.apple.AppKit 0x00007fff8f9f3b09 -[NSView _recursiveDisplayAllDirtyWithLockFocus:visRect:] + 2704
30 com.apple.AppKit 0x00007fff8f9f1722 -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectFor View:topView:] + 817
31 com.apple.AppKit 0x00007fff8fb40fdb -[NSNextStepFrame _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectFor View:topView:] + 286
32 com.apple.AppKit 0x00007fff8f9ecd9d -[NSView _displayRectIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:] + 4675
33 com.apple.AppKit 0x00007fff8f9b6cc3 -[NSView displayIfNeeded] + 1830
34 com.apple.AppKit 0x00007fff8fb40e94 -[NSNextStepFrame displayIfNeeded] + 84
35 com.apple.AppKit 0x00007fff8f9b61fc _handleWindowNeedsDisplayOrLayoutOrUpdateConstraints + 738
36 com.apple.AppKit 0x00007fff8ff818f1 __83-[NSWindow _postWindowNeedsDisplayOrLayoutOrUpdateConstraintsUnlessPostingDisabled]_block_ invoke_01208 + 46
37 com.apple.CoreFoundation 0x00007fff95633417 __CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION__ + 23
38 com.apple.CoreFoundation 0x00007fff95633381 __CFRunLoopDoObservers + 369
39 com.apple.CoreFoundation 0x00007fff9560e7b8 __CFRunLoopRun + 728
40 com.apple.CoreFoundation 0x00007fff9560e0e2 CFRunLoopRunSpecific + 290
41 com.apple.HIToolbox 0x00007fff91795eb4 RunCurrentEventLoopInMode + 209
42 com.apple.HIToolbox 0x00007fff91795b94 ReceiveNextEventCommon + 166
43 com.apple.HIToolbox 0x00007fff91795ae3 BlockUntilNextEventMatchingListInMode + 62
44 com.apple.AppKit 0x00007fff8f9b3563 _DPSNextEvent + 685
45 com.apple.AppKit 0x00007fff8f9b2e22 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 128
46 com.apple.Aperture 0x000000010b1572f9 0x10acdf000 + 4686585
47 com.apple.AppKit 0x00007fff8f9aa1d3 -[NSApplication run] + 517
48 com.apple.prokit 0x000000010c27f6c5 NSProApplicationMain + 378
49 com.apple.Aperture 0x000000010acef52e 0x10acdf000 + 66862
50 com.apple.Aperture 0x000000010aceee54 0x10acdf000 + 65108
Thread 1:: Dispatch queue: com.apple.libdispatch-manager
0 libsystem_kernel.dylib 0x00007fff98026d16 kevent + 10
1 libdispatch.dylib 0x00007fff923e9dea _dispatch_mgr_invoke + 883
2 libdispatch.dylib 0x00007fff923e99ee _dispatch_mgr_thread + 54
Thread 2:: Dispatch queue: RKPublishedServiceManager AlbumDelete
0 libsystem_kernel.dylib 0x00007fff980246c2 semaphore_wait_trap + 10
1 libdispatch.dylib 0x00007fff923ebc32 _dispatch_thread_semaphore_wait + 16
2 libdispatch.dylib 0x00007fff923eba92 _dispatch_barrier_sync_f_slow + 188
3 com.apple.iLifeSQLAccess 0x000000010d0bb325 -[HgEntity _dispatch_sync_if_needed_suspend:withBlock:] + 255
4 com.apple.iLifeSQLAccess 0x000000010d0c3b45 -[HgEntity insertIntoRidList:idsForColumn:fromQuery:] + 431
5 com.apple.iLifeSQLAccess 0x000000010d0bfda5 -[HgEntity selectDistinctList:fromQuery:] + 242
6 com.apple.iLifeSQLAccess 0x000000010d0bfee9 -[HgEntity selectDistinctList:where:] + 195
7 com.apple.RedRock 0x000000010ba636db +[RKVersionGroup groupsContainingVersion:] + 37
8 com.apple.RedRock 0x000000010ba6390c +[RKVersionGroup removeVersionFromAllGroups:] + 74
9 com.apple.RedRock 0x000000010b846631 -[RKVersion willBeDeleted] + 35
10 com.apple.iLifeSQLAccess 0x000000010d0cffc0 -[HgModel deleteModel] + 49
11 com.apple.RedRock 0x000000010b846373 +[RKVersion deleteVersions:deleteMode:] + 1743
12 com.apple.RedRock 0x000000010b831e2f +[RKMaster deleteMasters:deleteReferencedFiles:deleteImmediately:skip:progressBlock:] + 1882
13 com.apple.RedRock 0x000000010b832227 +[RKMaster deleteMasters:deleteReferencedFiles:progressBlock:] + 268
14 com.apple.RedRock 0x000000010b83233b +[RKMaster async_deleteMasters:deleteReferencedFiles:] + 192
15 com.apple.Aperture 0x000000010afa6523 0x10acdf000 + 2913571
16 libdispatch.dylib 0x00007fff923eaf01 _dispatch_call_block_and_release + 15
17 libdispatch.dylib 0x00007fff923e70b6 _dispatch_client_callout + 8
18 libdispatch.dylib 0x00007fff923e847f _dispatch_queue_drain + 235
19 libdispatch.dylib 0x00007fff923e82f1 _dispatch_queue_invoke + 52
20 libdispatch.dylib 0x00007fff923e81c3 _dispatch_worker_thread2 + 249
21 libsystem_c.dylib 0x00007fff8c7abd0b _pthread_wqthread + 404
22 libsystem_c.dylib 0x00007fff8c7961d1 start_wqthread + 13
Thread 3:: Dispatch queue: com.apple.Mercury.KDatabaseMgr
0 libsystem_kernel.dylib 0x00007fff98026faa pread + 10
1 com.apple.iLifeSQLAccess 0x000000010d052ced seekAndRead + 86
2 com.apple.iLifeSQLAccess 0x000000010d052c59 unixRead + 31
3 com.apple.iLifeSQLAccess 0x000000010d06d46b readDbPage + 447
4 com.apple.iLifeSQLAccess 0x000000010d06cb6f sqlite3PagerAcquire + 342
5 com.apple.iLifeSQLAccess 0x000000010d06c9db btreeGetPage + 30
6 com.apple.iLifeSQLAccess 0x000000010d07a3c1 getAndInitPage + 66
7 com.apple.iLifeSQLAccess 0x000000010d07a7d3 moveToChild + 68
8 com.apple.iLifeSQLAccess 0x000000010d0895ea sqlite3BtreeMovetoUnpacked + 698
9 com.apple.iLifeSQLAccess 0x000000010d06758a sqlite3VdbeExec + 26166
10 com.apple.iLifeSQLAccess 0x000000010d060c5a sqlite3_step + 2420
11 com.apple.iLifeSQLAccess 0x000000010d080df9 -[HgKPreparedSql updateWithArgs:] + 230
12 com.apple.iLifeSQLAccess 0x000000010d0b9dc0 __35-[HgEntity executeUpdate:withArgs:]_block_invoke_0 + 36
13 libdispatch.dylib 0x00007fff923eaf01 _dispatch_call_block_and_release + 15
14 libdispatch.dylib 0x00007fff923e70b6 _dispatch_client_callout + 8
15 libdispatch.dylib 0x00007fff923e847f _dispatch_queue_drain + 235
16 libdispatch.dylib 0x00007fff923e82f1 _dispatch_queue_invoke + 52
17 libdispatch.dylib 0x00007fff923e8448 _dispatch_queue_drain + 180
18 libdispatch.dylib 0x00007fff923e82f1 _dispatch_queue_invoke + 52
19 libdispatch.dylib 0x00007fff923e81c3 _dispatch_worker_thread2 + 249
20 libsystem_c.dylib 0x00007fff8c7abd0b _pthread_wqthread + 404
21 libsystem_c.dylib 0x00007fff8c7961d1 start_wqthread + 13
Thread 4:: Dispatch queue: com.apple.root.default-priority
0 libsystem_kernel.dylib 0x00007fff98026faa pread + 10
1 com.apple.proxtcore 0x000000010cfae368 -[XTSegmentFile readData:forIndexEntry:] + 453
2 com.apple.proxtcore 0x000000010cfaf135 -[XTSegmentFile loadData:length:forIdentifier:] + 136
3 com.apple.RedRock 0x000000010b9015bd __block_global_0 + 306
4 libdispatch.dylib 0x00007fff923eaf01 _dispatch_call_block_and_release + 15
5 libdispatch.dylib 0x00007fff923e70b6 _dispatch_client_callout + 8
6 libdispatch.dylib 0x00007fff923e81fa _dispatch_worker_thread2 + 304
7 libsystem_c.dylib 0x00007fff8c7abd0b _pthread_wqthread + 404
8 libsystem_c.dylib 0x00007fff8c7961d1 start_wqthread + 13
Thread 5:
0 libsystem_kernel.dylib 0x00007fff980266d6 __workq_kernreturn + 10
1 libsystem_c.dylib 0x00007fff8c7abf4c _pthread_workq_return + 25
2 libsystem_c.dylib 0x00007fff8c7abd13 _pthread_wqthread + 412
3 libsystem_c.dylib 0x00007fff8c7961d1 start_wqthread + 13
Thread 6:: Dispatch queue: com.apple.Mercury.KDatabaseMgr
0 libsystem_kernel.dylib 0x00007fff98026faa pread + 10
1 com.apple.iLifeSQLAccess 0x000000010d052ced seekAndRead + 86
2 com.apple.iLifeSQLAccess 0x000000010d052c59 unixRead + 31
3 com.apple.iLifeSQLAccess 0x000000010d06d46b readDbPage + 447
4 com.apple.iLifeSQLAccess 0x000000010d06cb6f sqlite3PagerAcquire + 342
5 com.apple.iLifeSQLAccess 0x000000010d06c9db btreeGetPage + 30
6 com.apple.iLifeSQLAccess 0x000000010d07a3c1 getAndInitPage + 66
7 com.apple.iLifeSQLAccess 0x000000010d07a7d3 moveToChild + 68
8 com.apple.iLifeSQLAccess 0x000000010d0895ea sqlite3BtreeMovetoUnpacked + 698
9 com.apple.iLifeSQLAccess 0x000000010d061621 sqlite3VdbeExec + 1741
10 com.apple.iLifeSQLAccess 0x000000010d060c5a sqlite3_step + 2420
11 com.apple.iLifeSQLAccess 0x000000010d080df9 -[HgKPreparedSql updateWithArgs:] + 230
12 com.apple.iLifeSQLAccess 0x000000010d0b9dc0 __35-[HgEntity executeUpdate:withArgs:]_block_invoke_0 + 36
13 libdispatch.dylib 0x00007fff923eaf01 _dispatch_call_block_and_release + 15
14 libdispatch.dylib 0x00007fff923e70b6 _dispatch_client_callout + 8
15 libdispatch.dylib 0x00007fff923e847f _dispatch_queue_drain + 235
16 libdispatch.dylib 0x00007fff923e82f1 _dispatch_queue_invoke + 52
17 libdispatch.dylib 0x00007fff923e8448 _dispatch_queue_drain + 180
18 libdispatch.dylib 0x00007fff923e82f1 _dispatch_queue_invoke + 52
19 libdispatch.dylib 0x00007fff923e81c3 _dispatch_worker_thread2 + 249
20 libsystem_c.dylib 0x00007fff8c7abd0b _pthread_wqthread + 404
21 libsystem_c.dylib 0x00007fff8c7961d1 start_wqthread + 13
Thread 7:: Dispatch queue: com.apple.Mercury.KDatabaseMgr
0 libsystem_kernel.dylib 0x00007fff98026faa pread + 10
1 com.apple.iLifeSQLAccess 0x000000010d052ced seekAndRead + 86
2 com.apple.iLifeSQLAccess 0x000000010d052c59 unixRead + 31
3 com.apple.iLifeSQLAccess 0x000000010d06d46b readDbPage + 447
4 com.apple.iLifeSQLAccess 0x000000010d06cb6f sqlite3PagerAcquire + 342
5 com.apple.iLifeSQLAccess 0x000000010d06c9db btreeGetPage + 30
6 com.apple.iLifeSQLAccess 0x000000010d07a3c1 getAndInitPage + 66
7 com.apple.iLifeSQLAccess 0x000000010d07a7d3 moveToChild + 68
8 com.apple.iLifeSQLAccess 0x000000010d0895ea sqlite3BtreeMovetoUnpacked + 698
9 com.apple.iLifeSQLAccess 0x000000010d06758a sqlite3VdbeExec + 26166
10 com.apple.iLifeSQLAccess 0x000000010d060c5a sqlite3_step + 2420
11 com.apple.iLifeSQLAccess 0x000000010d080df9 -[HgKPreparedSql updateWithArgs:] + 230
12 com.apple.iLifeSQLAccess 0x000000010d0b9dc0 __35-[HgEntity executeUpdate:withArgs:]_block_invoke_0 + 36
13 libdispatch.dylib 0x00007fff923eaf01 _dispatch_call_block_and_release + 15
14 libdispatch.dylib 0x00007fff923e70b6 _dispatch_client_callout + 8
15 libdispatch.dylib 0x00007fff923e847f _dispatch_queue_drain + 235
16 libdispatch.dylib 0x00007fff923e82f1 _dispatch_queue_invoke + 52
17 libdispatch.dylib 0x00007fff923e8448 _dispatch_queue_drain + 180
18 libdispatch.dylib 0x00007fff923e82f1 _dispatch_queue_invoke + 52
19 libdispatch.dylib 0x00007fff923e81c3 _dispatch_worker_thread2 + 249
20 libsystem_c.dylib 0x00007fff8c7abd0b _pthread_wqthread + 404
21 libsystem_c.dylib 0x00007fff8c7961d1 start_wqthread + 13
Thread 8:
0 libsystem_kernel.dylib 0x00007fff980260fa __psynch_cvwait + 10
1 libsystem_c.dylib 0x00007fff8c7ae023 _pthread_cond_wait + 927
2 com.apple.Foundation 0x00007fff93619fe3 -[NSCondition waitUntilDate:] + 357
3 com.apple.Foundation 0x00007fff93619e39 -[NSConditionLock lockWhenCondition:beforeDate:] + 235
4 com.apple.proxtcore 0x000000010cf68c5a -[XTMsgQueue waitForMessage] + 47
5 com.apple.proxtcore 0x000000010cf67ea3 -[XTThread run:] + 329
6 com.apple.Foundation 0x00007fff935eecd2 __NSThread__main__ + 1345
7 libsystem_c.dylib 0x00007fff8c7a97a2 _pthread_start + 327
8 libsystem_c.dylib 0x00007fff8c7961e1 thread_start + 13
Thread 9:
0 libsystem_kernel.dylib 0x00007fff980260fa __psynch_cvwait + 10
1 libsystem_c.dylib 0x00007fff8c7ae023 _pthread_cond_wait + 927
2 com.apple.Foundation 0x00007fff93619fe3 -[NSCondition waitUntilDate:] + 357
3 com.apple.Foundation 0x00007fff93619e39 -[NSConditionLock lockWhenCondition:beforeDate:] + 235
4 com.apple.proxtcore 0x000000010cf68c5a -[XTMsgQueue waitForMessage] + 47
5 com.apple.proxtcore 0x000000010cf67ea3 -[XTThread run:] + 329
6 com.apple.Foundation 0x00007fff935eecd2 __NSThread__main__ + 1345
7 libsystem_c.dylib 0x00007fff8c7a97a2 _pthread_start + 327
8 libsystem_c.dylib 0x00007fff8c7961e1 thread_start + 13
Thread 10:
0 libsystem_kernel.dylib 0x00007fff980260fa __psynch_cvwait + 10
1 libsystem_c.dylib 0x00007fff8c7ae023 _pthread_cond_wait + 927
2 com.apple.Foundation 0x00007fff93619fe3 -[NSCondition waitUntilDate:] + 357
3 com.apple.Foundation 0x00007fff93619e39 -[NSConditionLock lockWhenCondition:beforeDate:] + 235
4 com.apple.proxtcore 0x000000010cf68c5a -[XTMsgQueue waitForMessage] + 47
5 com.apple.proxtcore 0x000000010cf67ea3 -[XTThread run:] + 329
6 com.apple.Foundation 0x00007fff935eecd2 __NSThread__main__ + 1345
7 libsystem_c.dylib 0x00007fff8c7a97a2 _pthread_start + 327
8 libsystem_c.dylib 0x00007fff8c7961e1 thread_start + 13
Thread 11:
0 libsystem_kernel.dylib 0x00007fff980260fa __psynch_cvwait + 10
1 libsystem_c.dylib 0x00007fff8c7ae023 _pthread_cond_wait + 927
2 com.apple.Foundation 0x00007fff93619fe3 -[NSCondition waitUntilDate:] + 357
3 com.apple.Foundation 0x00007fff93619e39 -[NSConditionLock lockWhenCondition:beforeDate:] + 235
4 com.apple.proxtcore 0x000000010cf68c5a -[XTMsgQueue waitForMessage] + 47
5 com.apple.proxtcore 0x000000010cf67ea3 -[XTThread run:] + 329
6 com.apple.Foundation 0x00007fff935eecd2 __NSThread__main__ + 1345
7 libsystem_c.dylib 0x00007fff8c7a97a2 _pthread_start + 327
8 libsystem_c.dylib 0x00007fff8c7961e1 thread_start + 13
Thread 12 Crashed:
0 libsystem_kernel.dylib 0x00007fff98026212 __pthread_kill + 10
1 libsystem_c.dylib 0x00007fff8c7aab54 pthread_kill + 90
2 libsystem_c.dylib 0x00007fff8c7eedce abort + 143
3 libc++abi.dylib 0x00007fff907849eb abort_message + 257
4 libc++abi.dylib 0x00007fff9078239a default_terminate() + 28
5 libobjc.A.dylib 0x00007fff8b2b9873 _objc_terminate() + 91
6 libc++abi.dylib 0x00007fff907823c9 safe_handler_caller(void (*)()) + 8
7 libc++abi.dylib 0x00007fff90782424 std::terminate() + 16
8 libc++abi.dylib 0x00007fff9078358b __cxa_throw + 111
9 libobjc.A.dylib 0x00007fff8b2b950c objc_exception_throw + 327
10 com.apple.CoreFoundation 0x00007fff95700f49 -[NSException raise] + 9
11 com.apple.proxtcore 0x000000010cf693b3 -[XTThread handleMessage:] + 1039
12 com.apple.proxtcore 0x000000010cf67eb3 -[XTThread run:] + 345
13 com.apple.Foundation 0x00007fff935eecd2 __NSThread__main__ + 1345
14 libsystem_c.dylib 0x00007fff8c7a97a2 _pthread_start + 327
15 libsystem_c.dylib 0x00007fff8c7961e1 thread_start + 13
Thread 13:
0 libsystem_kernel.dylib 0x00007fff980260fa __psynch_cvwait + 10
1 libsystem_c.dylib 0x00007fff8c7ae023 _pthread_cond_wait + 927
2 com.apple.Foundation 0x00007fff93619fe3 -[NSCondition waitUntilDate:] + 357
3 com.apple.Foundation 0x00007fff93619e39 -[NSConditionLock lockWhenCondition:beforeDate:] + 235
4 com.apple.proxtcore 0x000000010cf68c5a -[XTMsgQueue waitForMessage] + 47
5 com.apple.proxtcore 0x000000010cf67ea3 -[XTThread run:] + 329
6 com.apple.Foundation 0x00007fff935eecd2 __NSThread__main__ + 1345
7 libsystem_c.dylib 0x00007fff8c7a97a2 _pthread_start + 327
8 libsystem_c.dylib 0x00007fff8c7961e1 thread_start + 13
Thread 14:: Dispatch queue: com.apple.Mercury.KDatabaseMgr
0 com.apple.iLifeSQLAccess 0x000000010d06cf90 pcache1Fetch + 22
1 com.apple.iLifeSQLAccess 0x000000010d06cc7d sqlite3PcacheFetch + 193
2 com.apple.iLifeSQLAccess 0x000000010d06ca88 sqlite3PagerAcquire + 111
3 com.apple.iLifeSQLAccess 0x000000010d06c9db btreeGetPage + 30
4 com.apple.iLifeSQLAccess 0x000000010d07a3c1 getAndInitPage + 66
5 com.apple.iLifeSQLAccess 0x000000010d07a7d3 moveToChild + 68
6 com.apple.iLifeSQLAccess 0x000000010d0895ea sqlite3BtreeMovetoUnpacked + 698
7 com.apple.iLifeSQLAccess 0x000000010d07a875 sqlite3VdbeCursorMoveto + 43
8 com.apple.iLifeSQLAccess 0x000000010d0694b5 sqlite3VdbeExec + 34145
9 com.apple.iLifeSQLAccess 0x000000010d060c5a sqlite3_step + 2420
10 com.apple.iLifeSQLAccess 0x000000010d088edb -[HgKResultSet next] + 262
11 com.apple.iLifeSQLAccess 0x000000010d0be43c __36-[HgEntity countOfModelsWhere:args:]_block_invoke_0 + 62
12 libdispatch.dylib 0x00007fff923e70b6 _dispatch_client_callout + 8
13 libdispatch.dylib 0x00007fff923ed4e3 _dispatch_function_recurse_invoke + 40
14 libdispatch.dylib 0x00007fff923e70b6 _dispatch_client_callout + 8
15 libdispatch.dylib 0x00007fff923e8723 _dispatch_barrier_sync_f_invoke + 39
16 libdispatch.dylib 0x00007fff923ebad2 _dispatch_barrier_sync_f_slow + 252
17 com.apple.iLifeSQLAccess 0x000000010d0bb325 -[HgEntity _dispatch_sync_if_needed_suspend:withBlock:] + 255
18 com.apple.iLifeSQLAccess 0x000000010d0b1246 -[HgEntity countOfModelsWhere:args:] + 416
19 com.apple.iLifeSQLAccess 0x000000010d0b0ff6 +[HgModel countOfModelsFromDatabase:where:] + 195
20 com.apple.RedRock 0x000000010b76d1b9 -[RKFolder updateVersionCount] + 256
21 com.apple.RedRock 0x000000010b846543 +[RKVersion deleteVersions:deleteMode:] + 2207
22 com.apple.RedRock 0x000000010b831e2f +[RKMaster deleteMasters:deleteReferencedFiles:deleteImmediately:skip:progressBlock:] + 1882
23 com.apple.RedRock 0x000000010b832227 +[RKMaster deleteMasters:deleteReferencedFiles:progressBlock:] + 268
24 com.apple.iLifeSQLAccess 0x000000010d115d46 __28-[HgDispatchQueue addBlock:]_block_invoke_0 + 19
25 libdispatch.dylib 0x00007fff923eaf01 _dispatch_call_block_and_release + 15
26 libdispatch.dylib 0x00007fff923e70b6 _dispatch_client_callout + 8
27 libdispatch.dylib 0x00007fff923e847f _dispatch_queue_drain + 235
28 libdispatch.dylib 0x00007fff923e82f1 _dispatch_queue_invoke + 52
29 libdispatch.dylib 0x00007fff923e81c3 _dispatch_worker_thread2 + 249
30 libsystem_c.dylib 0x00007fff8c7abd0b _pthread_wqthread + 404
31 libsystem_c.dylib 0x00007fff8c7961d1 start_wqthread + 13
Thread 15:
0 libsystem_kernel.dylib 0x00007fff980260fa __psynch_cvwait + 10
1 libsystem_c.dylib 0x00007fff8c7ae023 _pthread_cond_wait + 927
2 com.apple.Foundation 0x00007fff93619fe3 -[NSCondition waitUntilDate:] + 357
3 com.apple.Foundation 0x00007fff93619e39 -[NSConditionLock lockWhenCondition:beforeDate:] + 235
4 com.apple.proxtcore 0x000000010cf68c5a -[XTMsgQueue waitForMessage] + 47
5 com.apple.proxtcore 0x000000010cf67ea3 -[XTThread run:] + 329
6 com.apple.Foundation 0x00007fff935eecd2 __NSThread__main__ + 1345
7 libsystem_c.dylib 0x00007fff8c7a97a2 _pthread_start + 327
8 libsystem_c.dylib 0x00007fff8c7961e1 thread_start + 13
Thread 16:
0 libsystem_kernel.dylib 0x00007fff980266d6 __workq_kernreturn + 10
1 libsystem_c.dylib 0x00007fff8c7abf4c _pthread_workq_return + 25
2 libsystem_c.dylib 0x00007fff8c7abd13 _pthread_wqthread + 412
3 libsystem_c.dylib 0x00007fff8c7961d1 start_wqthread + 13
Thread 17:
0 libsystem_kernel.dylib 0x00007fff980266d6 __workq_kernreturn + 10
1 libsystem_c.dylib 0x00007fff8c7abf4c _pthread_workq_return + 25
2 libsystem_c.dylib 0x00007fff8c7abd13 _pthread_wqthread + 412
3 libsystem_c.dylib 0x00007fff8c7961d1 start_wqthread + 13
Thread 18:
0 libsystem_kernel.dylib 0x00007fff980266d6 __workq_kernreturn + 10
1 libsystem_c.dylib 0x00007fff8c7abf4c _pthread_workq_return + 25
2 libsystem_c.dylib 0x00007fff8c7abd13 _pthread_wqthread + 412
3 libsystem_c.dylib 0x00007fff8c7961d1 start_wqthread + 13
Thread 19:
0 libsystem_kernel.dylib 0x00007fff980266d6 __workq_kernreturn + 10
1 libsystem_c.dylib 0x00007fff8c7abf4c _pthread_workq_return + 25
2 libsystem_c.dylib 0x00007fff8c7abd13 _pthread_wqthread + 412
3 libsystem_c.dylib 0x00007fff8c7961d1 start_wqthread + 13
Thread 20:
0 libsystem_kernel.dylib 0x00007fff980266d6 __workq_kernreturn + 10
1 libsystem_c.dylib 0x00007fff8c7abf4c _pthread_workq_return + 25
2 libsystem_c.dylib 0x00007fff8c7abd13 _pthread_wqthread + 412
3 libsystem_c.dylib 0x00007fff8c7961d1 start_wqthread + 13
Thread 12 crashed with X86 Thread State (64-bit):
rax: 0x0000000000000000 rbx: 0x0000000000000006 rcx: 0x0000000118f12a68 rdx: 0x0000000000000000
rdi: 0x0000000000009903 rsi: 0x0000000000000006 rbp: 0x0000000118f12a90 rsp: 0x0000000118f12a68
r8: 0x00007fff7b40f278 r9: 0x000000000000000a r10: 0x0000000020000000 r11: 0x0000000000000206
r12: 0x0000000118f12bf0 r13: 0x000000010d000610 r14: 0x0000000118f14000 r15: 0x0000000118f12ad0
rip: 0x00007fff98026212 rfl: 0x0000000000000206 cr2: 0x00007fff7b408ff0
Logical CPU: 0
Binary Images:
0x10acdf000 - 0x10b43cff7 com.apple.Aperture (3.4.4 - 3.4.4) <7C43FF75-DA6F-3613-AF60-ACAFBB73D673> /Applications/Aperture.app/Contents/MacOS/Aperture
0x10b661000 - 0x10b661fff libgenkit.dylib (1) <4D2704B4-9F86-2EBA-D1A7-3A990FEF9854> /usr/lib/libgenkit.dylib
0x10b668000 - 0x10b671ff7 com.apple.PhotoFoundation (1.0 - 20.12) <9E3EA726-0AE7-3A40-AF03-EA7BDF21C099> /Applications/Aperture.app/Contents/Frameworks/PhotoFoundation.framework/Versio ns/A/PhotoFoundation
0x10b6e7000 - 0x10b6e8ff7 libCyrillicConverter.dylib (61) <D06971D7-9F16-3FE6-81E8-33E0FE4D6586> /System/Library/CoreServices/Encodings/libCyrillicConverter.dylib
0x10b6ed000 - 0x10bc4bfff com.apple.RedRock (1.9.4 - 321.1) <EAD3BDC5-3A3E-3246-B69F-DB2E39695403> /Applications/Aperture.app/Contents/Frameworks/RedRock.framework/Versions/A/Red Rock
0x10bf82000 - 0x10c005ff7 com.apple.iLifePageLayoutCore (1.0 - 210.38) <BC05B804-298B-38CD-9647-1CDAD4F714E8> /Applications/Aperture.app/Contents/Frameworks/iLifePageLayoutCore.framework/Ve rsions/A/iLifePageLayoutCore
0x10c067000 - 0x10c06cff7 com.apple.iLifePhotoStreamConfiguration (3.4 - 2.5) <9D62897F-2817-3C68-8EDF-A52539B11EE7> /Applications/Aperture.app/Contents/Frameworks/iLifePhotoStreamConfiguration.fr amework/Versions/A/iLifePhotoStreamConfiguration
0x10c075000 - 0x10c0a6fff com.apple.iLifeAssetManagement (2.7 - 45.19) <EBF43BAB-B1EF-3A26-8C17-F5A8AD4F1923> /Applications/Aperture.app/Contents/Frameworks/iLifeAssetManagement.framework/V ersions/A/iLifeAssetManagement
0x10c0d7000 - 0x10c0e4fff com.apple.iphoto.AccountConfigurationPlugin (1.2 - 1.2) <EA624F78-C441-3514-9A77-362F96B84A94> /Applications/Aperture.app/Contents/Frameworks/AccountConfigurationPlugin.frame work/Versions/A/AccountConfigurationPlugin
0x10c0f6000 - 0x10c199ff7 com.apple.MobileMe (13 - 1.0.4) <78787555-A65F-3F23-8473-E9CEBCD14BF3> /Applications/Aperture.app/Contents/Frameworks/MobileMe.framework/Versions/A/Mo bileMe
0x10c215000 - 0x10c222ff7 com.apple.PluginManager (1.7.6 - 55) <9C4EFFC0-1CDC-360B-9294-57E710B2912A> /Library/Frameworks/PluginManager.framework/Versions/B/PluginManager
0x10c236000 - 0x10c247fff com.apple.AERegistration (1.2 - 401) <17EFD8F0-87B5-3189-9FDA-4510279D5B35> /Applications/Aperture.app/Contents/Frameworks/AERegistration.framework/Version s/A/AERegistration
0x10c261000 - 0x10c4d7ff7 com.apple.prokit (7.3.2 - 1944.10) <41FA1781-64AA-37C2-8CBF-9D72CFD705C0> /System/Library/PrivateFrameworks/ProKit.framework/Versions/A/ProKit
0x10c673000 - 0x10ca17fff com.apple.iLifeSlideshow (3.1 - 1151.4) <6AE8C8C0-9B04-3AA6-9600-F536F8104B64> /Applications/Aperture.app/Contents/Frameworks/iLifeSlideshow.framework/Version s/A/iLifeSlideshow
0x10cb9e000 - 0x10cbb5ff7 com.apple.iLifeFaceRecognition (1.0 - 30.11) <097EDA03-9287-358F-9962-B8009A676610> /Applications/Aperture.app/Contents/Frameworks/iLifeFaceRecognition.framework/V ersions/A/iLifeFaceRecognition
0x10cbc8000 - 0x10cc01fff com.apple.fayray.PrintServices (920121212 - 11.7) <DC591C90-2028-3CC9-8B99-0E631160D751> /Applications/Aperture.app/Contents/Frameworks/PrintServices.framework/Versions /A/PrintServices
0x10cc3c000 - 0x10cc70ff7 com.apple.ProUtils (1.1 - 220.17) <8768EBB7-58BE-3F75-914E-DA488BEAA828> /Applications/Aperture.app/Contents/Frameworks/ProUtils.framework/Versions/A/Pr oUtils
0x10cc95000 - 0x10ce8eff7 com.apple.geode (1.5.3 - 280.22) <6C000034-D863-3022-A36D-3754EDE789F5> /Applications/Aperture.app/Contents/Frameworks/Geode.framework/Versions/A/Geode
0x10cf64000 - 0x10cfdffff com.apple.proxtcore (1.4.1 - 270.13) <A2D53FDF-C510-3A57-9C21-20AE9B631AFD> /Applications/Aperture.app/Contents/Frameworks/ProXTCore.framework/Versions/A/P roXTCore
0x10d04b000 - 0x10d166fff com.apple.iLifeSQLAccess (1.7.1 - 70.30) <7D154ED6-7BD3-345C-9BC1-614017DAB6C6> /Applications/Aperture.app/Contents/Frameworks/iLifeSQLAccess.framework/Version s/A/iLifeSQLAccess
0x10d1d4000 - 0x10d1d6fff com.apple.ExceptionHandling (1.5 - 10) <47FF83ED-0C07-308C-A375-2A2189DB1056> /System/Library/Frameworks/ExceptionHandling.framework/Versions/A/ExceptionHand ling
0x10d1df000 - 0x10d207fff com.apple.iPhoto.Tellus (1.3 - 90.10) <E124C420-0AE4-36BB-98E0-A38D2B280F11> /Applications/Aperture.app/Contents/Frameworks/Tellus.framework/Versions/A/Tell us
0x10d22f000 - 0x10d258fff com.apple.iPhoto.Tessera (1.1 - 90.10) <6252DE02-ED5D-364B-8DAD-E67917478A86> /Applications/Aperture.app/Contents/Frameworks/Tessera.framework/Versions/A/Tes sera
0x10d276000 - 0x10d27eff7 com.apple.AEProfiling (1.2 - 23) <AF1D815F-B5F7-316B-91C1-9C4FCAF13BBF> /Applications/Aperture.app/Contents/Frameworks/AEProfiling.framework/Versions/A /AEProfiling
0x10d28f000 - 0x10d292fff com.apple.LibraryRepair (1.0 - 1) <14701E47-E2B2-309F-A04E-96D260E83B54> /System/Library/PrivateFrameworks/LibraryRepair.framework/Versions/A/LibraryRep air
0x10d298000 - 0x10d29afff +eOkaoCom.dylib (1) <393F340C-3AD1-C89B-6C37-9D8ABF4BFFD9> /Applications/Aperture.app/Contents/Frameworks/iLifeFaceRecognition.framework/V ersions/A/Resources/eOkaoCom.dylib
0x10d2a5000 - 0x10d2ccff2 +eOkaoPt.dylib (1) <E6500FB8-157F-57B5-FE25-2A3A1CB3574C> /Applications/Aperture.app/Contents/Frameworks/iLifeFaceRecognition.framework/V ersions/A/Resources/eOkaoPt.dylib
0x10d2d3000 - 0x10d308fe7 +eOkaoDt.dylib (1) <7A74253D-8930-6FF1-B513-0929C4E111A2> /Applications/Aperture.app/Contents/Frameworks/iLifeFaceRecognition.framework/V ersions/A/Resources/eOkaoDt.dylib
0x10d310000 - 0x10d478fef +eOkaoFr.dylib (1) <510E837E-135A-92C8-9AC0-465691EA43D2> /Applications/Aperture.app/Contents/Frameworks/iLifeFaceRecognition.framework/V ersions/A/Resources/eOkaoFr.dylib
0x10d47c000 - 0x10d4d7fff com.apple.NyxAudioAnalysis (12.4 - 12.4) <7E92057A-2C05-31D1-A7AC-8323606AF300> /Library/Frameworks/NyxAudioAnalysis.framework/Versions/A/NyxAudioAnalysis
0x114be6000 - 0x114c0fff7 com.apple.prokit.LionPanels (7.3.2 - 1944.10) <0203CE91-E926-32CC-80A3-94D8C1C558A1> /System/Library/PrivateFrameworks/ProKit.framework/Versions/A/Resources/LionPan els.bundle/Contents/MacOS/LionPanels
0x114c61000 - 0x114e1ffff GLEngine (8.7.25) <8398B57C-EE2D-3006-940C-CECE8E719D3B> /System/Library/Frameworks/OpenGL.framework/Resources/GLEngine.bundle/GLEngine
0x114e56000 - 0x114fc6fff libGLProgrammability.dylib (8.7.25) <EE2DD8AF-C6C3-303D-976E-87B4AABF8371> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLProgramma bility.dylib
0x114ffe000 - 0x1152b6fff com.apple.ATIRadeonX2000GLDriver (8.10.44 - 8.1.0) <7D70DE9A-6C60-36EE-BDB1-712331A1756C> /System/Library/Extensions/ATIRadeonX2000GLDriver.bundle/Contents/MacOS/ATIRade onX2000GLDriver
0x115313000 - 0x115320fff libGPUSupport.dylib (8.7.25) <F884DCD6-8234-3D23-BEC6-4EC4CE5101EF> /System/Library/PrivateFrameworks/GPUSupport.framework/Versions/A/Libraries/lib GPUSupport.dylib
0x115327000 - 0x115352fff GLRendererFloat (8.7.25) <BB54593F-07F0-392A-8993-CA844F4A20E8> /System/Library/Frameworks/OpenGL.framework/Resources/GLRendererFloat.bundle/GL RendererFloat
0x11535b000 - 0x115364fe7 libcldcpuengine.dylib (2.2.16) <DB9678F6-7D50-384A-A961-6109B61D1607> /System/Library/Frameworks/OpenCL.framework/Versions/A/Libraries/libcldcpuengin e.dylib
0x11571e000 - 0x115726fff com.apple.Aperture.TaskView (1.1 - 1.0) <86BD1732-359D-3A6F-B3A6-D3049B8F5DBD> /Applications/Aperture.app/Contents/PlugIns/TaskView.bundle/Contents/MacOS/Task View
0x118fe2000 - 0x11909bff7 ColorSyncDeprecated.dylib (400) <7CE58F6E-D2C8-39FB-8EE0-28CC6EC6D04F> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ColorSync.framework/Versions/A/Resources/ColorSyncDeprecated.dylib
0x1190ff000 - 0x119107fff com.apple.proapps.mrcheckpro (1.4 - 397) <DEB9E6D4-E4A9-3F32-8477-C9AD48C37A69> /Applications/Aperture.app/Contents/Resources/MRCheckPro.bundle/Contents/MacOS/ MRCheckPro
0x119ca7000 - 0x119cacff7 libFontRegistryUI.dylib (100) <9F172961-DB6F-3A82-9F90-28F9A233F755> /System/Library/Frameworks/ApplicationServices.framework/Frameworks/ATS.framewo rk/Resources/libFontRegistryUI.dylib
0x119d1e000 - 0x119d46fff com.apple.iPhoto.FacebookPublisher (1.2 - 1.2) <91BFD72D-C43A-38F3-8038-7D845A679E79> /Applications/Aperture.app/Contents/PlugIns/FacebookPublisher.publisher/Content s/MacOS/FacebookPublisher
0x119d66000 - 0x119d86ff7 com.apple.iPhoto.FlickrPublisher (1.2 - 1.2) <7B77737F-75F5-371C-AA23-B855A4D0935E> /Applications/Aperture.app/Contents/PlugIns/FlickrPublisher.publisher/Contents/ MacOS/FlickrPublisher
0x119da0000 - 0x119dd5ff7 com.apple.iPhoto.MobileMePublisher (1.2 - 1.2) <E74B9FD4-6162-352D-9010-0C4E5575AC37> /Applications/Aperture.app/Contents/PlugIns/MobileMePublisher.publisher/Content s/MacOS/MobileMePublisher
0x119dfb000 - 0x119e11fff com.apple.iPhoto.SharedPhotoStreamPublisher (1.0 - 1.0) <5AECD4B4-26E6-3C43-A17A-913A5D2C7A8C> /Applications/Aperture.app/Contents/PlugIns/SharedPhotoStreamPublisher.publishe r/Contents/MacOS/SharedPhotoStreamPublisher
0x119e2a000 - 0x119e2fff7 com.apple.iphoto.accountconfig.Facebook (1.2 - 1.2) <051DB4A3-7D17-3289-9328-77D5B5512EC2> /Applications/Aperture.app/Contents/PlugIns/Facebook.accountconfigplugin/Conten ts/MacOS/Facebook
0x119e37000 - 0x119e3bfff com.apple.iphoto.accountconfig.Flickr (1.1 - 1) <556E3A54-B1CA-3CD0-A439-AB46B45A4BE0> /Applications/Aperture.app/Contents/PlugIns/Flickr.accountconfigplugin/Contents /MacOS/Flickr
0x119e42000 - 0x119e48ff7 com.apple.iphoto.accountconfig.MobileMe (1.1 - 1) <FDCA4A8F-C649-365F-8FE5-22418FB03EE2> /Applications/Aperture.app/Contents/PlugIns/MobileMe.accountconfigplugin/Conten ts/MacOS/MobileMe
0x11a889000 - 0x11a88affb +cl_kernels (???) <FFCFA284-2B52-4BFD-A0D2-314D2875021C> cl_kernels
0x11a897000 - 0x11a897ff9 +cl_kernels (???) <C0631488-C5E3-4CBC-A723-E27C3B71BDB3> cl_kernels
0x11a899000 - 0x11a933ff7 unorm8_bgra.dylib (2.2.16) <5D62BED8-DF5D-3C51-94B4-57368FF10DDB> /System/Library/Frameworks/OpenCL.framework/Versions/A/Libraries/ImageFormats/u norm8_bgra.dylib
0x7fff6a8df000 - 0x7fff6a91393f dyld (210.2.3) <A40597AA-5529-3337-8C09-D8A014EB1578> /usr/lib/dyld
0x7fff8b0f9000 - 0x7fff8b0fbff7 com.apple.print.framework.Print (8.0 - 258) <34666CC2-B86D-3313-B3B6-A9977AD593DA> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Print.framewo rk/Versions/A/Print
0x7fff8b0fc000 - 0x7fff8b158ff7 com.apple.Symbolication (1.3 - 93) <F2C7E0B6-B241-3020-B30A-0636D0FA3378> /System/Library/PrivateFrameworks/Symbolication.framework/Versions/A/Symbolicat ion
0x7fff8b159000 - 0x7fff8b1a4fff com.apple.CoreMedia (1.0 - 926.87) <F51205F8-A102-359C-A9A3-22A48524C081> /System/Library/Frameworks/CoreMedia.framework/Versions/A/CoreMedia
0x7fff8b1a5000 - 0x7fff8b2a7fff libcrypto.0.9.8.dylib (47) <74F165AD-4572-3B26-B0E2-A97477FE59D0> /usr/lib/libcrypto.0.9.8.dylib
0x7fff8b2a8000 - 0x7fff8b3c092f libobjc.A.dylib (532.2) <90D31928-F48D-3E37-874F-220A51FD9E37> /usr/lib/libobjc.A.dylib
0x7fff8b490000 - 0x7fff8b49eff7 libkxld.dylib (2050.22.13) <4AAF0573-8632-3D06-BE32-C5675F77638D> /usr/lib/system/libkxld.dylib
0x7fff8b49f000 - 0x7fff8b4c1ff7 libxpc.dylib (140.42) <BBE558BD-5E55-35E4-89ED-1AA6B056D05A> /usr/lib/system/libxpc.dylib
0x7fff8b562000 - 0x7fff8b5cfff7 com.apple.datadetectorscore (4.1 - 269.2) <4FD4A7CE-BB00-3AAB-B7AA-AE395D5400EC> /System/Library/PrivateFrameworks/DataDetectorsCore.framework/Versions/A/DataDe tectorsCore
0x7fff8b95c000 - 0x7fff8b992fff libsystem_info.dylib (406.17) <4FFCA242-7F04-365F-87A6-D4EFB89503C1> /usr/lib/system/libsystem_info.dylib
0x7fff8b993000 - 0x7fff8b996fff libutil.dylib (30) <EF3340B2-9A53-3D5E-B9B4-BDB5EEECC178> /usr/lib/libutil.dylib
0x7fff8b997000 - 0x7fff8b9adfff com.apple.MultitouchSupport.framework (235.29 - 235.29) <617EC8F1-BCE7-3553-86DD-F857866E1257> /System/Library/PrivateFrameworks/MultitouchSupport.framework/Versions/A/Multit ouchSupport
0x7fff8b9ae000 - 0x7fff8b9dcff7 libsystem_m.dylib (3022.6) <B434BE5C-25AB-3EBD-BAA7-5304B34E3441> /usr/lib/system/libsystem_m.dylib
0x7fff8b9dd000 - 0x7fff8bb36ff7 com.apple.syncservices (7.1 - 713.1) <1B20AF09-C1E5-3B70-A57F-177A4D92E403> /System/Library/Frameworks/SyncServices.framework/Versions/A/SyncServices
0x7fff8bb39000 - 0x7fff8bc0cff7 com.apple.DiscRecording (7.0 - 7000.2.4) <49FD2D2F-4F2C-39B6-877B-6E3172577D18> /System/Library/Frameworks/DiscRecording.framework/Versions/A/DiscRecording
0x7fff8bc0d000 - 0x7fff8bc0dfff com.apple.AOSMigrate (1.0 - 1) <585B1483-490E-32DD-97DC-B9279E9D3490> /System/Library/PrivateFrameworks/AOSMigrate.framework/Versions/A/AOSMigrate
0x7fff8bc0e000 - 0x7fff8bc30fff com.apple.AOSAccounts (1.1.2 - 1.1.95) <9A1A8780-1F48-3CCA-96EB-D3137F93B676> /System/Library/PrivateFrameworks/AOSAccounts.framework/Versions/A/AOSAccounts
0x7fff8bc31000 - 0x7fff8bc46fff com.apple.ImageCapture (8.0 - 8.0) <17A45CE6-7DA3-36A5-B7EF-72BC136981AE> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/ImageCapture. framework/Versions/A/ImageCapture
0x7fff8bc52000 - 0x7fff8bc69fff com.apple.CFOpenDirectory (10.8 - 151.10) <FFBBA538-00B5-334E-BA5B-C8AD6CDCDA14> /System/Library/Frameworks/OpenDirectory.framework/Versions/A/Frameworks/CFOpen Directory.framework/Versions/A/CFOpenDirectory
0x7fff8bc92000 - 0x7fff8bcecff7 com.apple.opencl (2.2.18 - 2.2.18) <4A78E53C-17B0-3B2D-A9EA-EF8720FE4134> /System/Library/Frameworks/OpenCL.framework/Versions/A/OpenCL
0x7fff8bcf7000 - 0x7fff8bd31fff com.apple.framework.internetaccounts (2.1 - 210) <546769AA-C561-3C17-8E8E-4E65A700E2F1> /System/Library/PrivateFrameworks/InternetAccounts.framework/Versions/A/Interne tAccounts
0x7fff8bd32000 - 0x7fff8bd32fff libkeymgr.dylib (25) <CC9E3394-BE16-397F-926B-E579B60EE429> /usr/lib/system/libkeymgr.dylib
0x7fff8bd33000 - 0x7fff8bd90fff com.apple.ExchangeWebServices (3.0 - 157) <58BFD72E-27F3-3F22-A421-B883FACA0E19> /System/Library/PrivateFrameworks/ExchangeWebServices.framework/Versions/A/Exch angeWebServices
0x7fff8bd91000 - 0x7fff8bdaeff7 com.apple.openscripting (1.3.6 - 148.3) <C008F56A-1E01-3D4C-A9AF-97799D0FAE69> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/OpenScripting .framework/Versions/A/OpenScripting
0x7fff8bdaf000 - 0x7fff8bdb7ff7 libsystem_dnssd.dylib (379.37) <616FC901-151E-38BF-B2C4-24A351C5FAAD> /usr/lib/system/libsystem_dnssd.dylib
0x7fff8bdb8000 - 0x7fff8bdb8fff 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
0x7fff8bdb9000 - 0x7fff8be5fff7 com.apple.CoreServices.OSServices (557.6 - 557.6) <1BDB5456-0CE9-301C-99C1-8EFD0D2BFCCD> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/OSServi ces.framework/Versions/A/OSServices
0x7fff8be60000 - 0x7fff8be6dfff com.apple.AppleFSCompression (49 - 1.0) <5508344A-2A7E-3122-9562-6F363910A80E> /System/Library/PrivateFrameworks/AppleFSCompression.framework/Versions/A/Apple FSCompression
0x7fff8be71000 - 0x7fff8bf02fff com.apple.CorePDF (2.0 - 2) <EB5660B1-0D79-34F3-B242-B559AE0A5B4A> /System/Library/PrivateFrameworks/CorePDF.framework/Versions/A/CorePDF
0x7fff8bf03000 - 0x7fff8bf35fff com.apple.framework.Admin (12.0 - 12.0) <21E02DE3-B255-3A55-8F55-7FC9EE864C06> /System/Library/PrivateFrameworks/Admin.framework/Versions/A/Admin
0x7fff8bf36000 - 0x7fff8bfd1fff com.apple.CoreSymbolication (3.0 - 117) <C304FDB8-2FF7-34BC-858A-2B96C2B039D5> /System/Library/PrivateFrameworks/CoreSymbolication.framework/Versions/A/CoreSy mbolication
0x7fff8bfe1000 - 0x7fff8c06eff7 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
0x7fff8c06f000 - 0x7fff8c07cff7 com.apple.NetAuth (4.0 - 4.0) <F5BC7D7D-AF28-3C83-A674-DADA48FF7810> /System/Library/PrivateFrameworks/NetAuth.framework/Versions/A/NetAuth
0x7fff8c07d000 - 0x7fff8c07dfff libOpenScriptingUtil.dylib (148.3) <F8681222-0969-3B10-8BCE-C55A4B9C520C> /usr/lib/libOpenScriptingUtil.dylib
0x7fff8c07e000 - 0x7fff8c180fff libJP2.dylib (849) <4EEA33EB-AF9F-365D-A572-F7D11AD1C76F> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libJP2.dylib
0x7fff8c181000 - 0x7fff8c1acfff libxslt.1.dylib (11.3) <441776B8-9130-3893-956F-39C85FFA644F> /usr/lib/libxslt.1.dylib
0x7fff8c1ad000 - 0x7fff8c1c7fff com.apple.CoreMediaAuthoring (2.1 - 914) <CFA664F9-D5A7-3281-A12F-3ED8A98FD8C1> /System/Library/PrivateFrameworks/CoreMediaAuthoring.framework/Versions/A/CoreM ediaAuthoring
0x7fff8c1c8000 - 0x7fff8c1d3fff libsystem_notify.dylib (98.5) <C49275CC-835A-3207-AFBA-8C01374927B6> /usr/lib/system/libsystem_notify.dylib
0x7fff8c1d4000 - 0x7fff8c1d6fff libquarantine.dylib (52) <4BE2E642-A14F-340A-B482-5BD2AEFD9C24> /usr/lib/system/libquarantine.dylib
0x7fff8c1d7000 - 0x7fff8c1d9ff7 libunc.dylib (25) <92805328-CD36-34FF-9436-571AB0485072> /usr/lib/system/libunc.dylib
0x7fff8c21d000 - 0x7fff8c4c1ff7 com.apple.CoreImage (8.2.4 - 1.0.1) <4A6B017F-B9F7-36DA-943D-A95611F147EA> /System/Library/Frameworks/QuartzCore.framework/Versions/A/Frameworks/CoreImage .framework/Versions/A/CoreImage
0x7fff8c51d000 - 0x7fff8c560ff7 com.apple.bom (12.0 - 192) <0BF1F2D2-3648-36B7-BE4B-551A0173209B> /System/Library/PrivateFrameworks/Bom.framework/Versions/A/Bom
0x7fff8c561000 - 0x7fff8c56cff7 com.apple.bsd.ServiceManagement (2.0 - 2.0) <C12962D5-85FB-349E-AA56-64F4F487F219> /System/Library/Frameworks/ServiceManagement.framework/Versions/A/ServiceManage ment
0x7fff8c56d000 - 0x7fff8c570fff libRadiance.dylib (849) <F7D9A0FD-1195-34CB-BFE5-79DAF3F40AC3> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libRadiance.d ylib
0x7fff8c571000 - 0x7fff8c585fff 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
0x7fff8c586000 - 0x7fff8c6fbfff com.apple.CFNetwork (596.3.3 - 596.3.3) <3739DC8D-8610-3740-80EC-43E130779CB8> /System/Library/Frameworks/CFNetwork.framework/Versions/A/CFNetwork
0x7fff8c714000 - 0x7fff8c794ff7 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
0x7fff8c795000 - 0x7fff8c861ff7 libsystem_c.dylib (825.26) <4C9EB006-FE1F-3F8F-8074-DFD94CF2CE7B> /usr/lib/system/libsystem_c.dylib
0x7fff8c862000 - 0x7fff8c862fff com.apple.Carbon (154 - 155) <372716D2-6FA1-3611-8501-3DD1D4A6E8C8> /System/Library/Frameworks/Carbon.framework/Versions/A/Carbon
0x7fff8c863000 - 0x7fff8cae3ff7 com.apple.AOSKit (1.05 - 152.2) <43361229-45F3-3946-A11A-CC0FF2129F06> /System/Library/PrivateFrameworks/AOSKit.framework/Versions/A/AOSKit
0x7fff8cae4000 - 0x7fff8cba1ff7 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
0x7fff8cba2000 - 0x7fff8cbacfff libcsfde.dylib (296.16) <DE03E28D-7979-3C31-9F46-2A7337CE0DBA> /usr/lib/libcsfde.dylib
0x7fff8cbad000 - 0x7fff8cbfeff7 com.apple.SystemConfiguration (1.12.2 - 1.12.2) <A4341BBD-A330-3A57-8891-E9C1A286A72D> /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfi guration
0x7fff8cc07000 - 0x7fff8cc96fff libCoreStorage.dylib (296.16) <E5BF76A1-2B3E-3FD8-ABF4-F8D18829BF0A> /usr/lib/libCoreStorage.dylib
0x7fff8ccc1000 - 0x7fff8d0defff FaceCoreLight (2.4.1) <A34C9575-C4C1-31B1-809B-7751070B4E8B> /System/Library/PrivateFrameworks/FaceCoreLight.framework/Versions/A/FaceCoreLi ght
0x7fff8d0df000 - 0x7fff8d0e0ff7 libdnsinfo.dylib (453.19) <14202FFB-C3CA-3FCC-94B0-14611BF8692D> /usr/lib/system/libdnsinfo.dylib
0x7fff8d0e1000 - 0x7fff8d26cff7 com.apple.WebKit (8536 - 8536.28.10) <792FA1F3-68F2-36F8-A070-898B3682F5DE> /System/Library/Frameworks/WebKit.framework/Versions/A/WebKit
0x7fff8d288000 - 0x7fff8d2a9ff7 libCRFSuite.dylib (33) <736ABE58-8DED-3289-A042-C25AF7AE5B23> /usr/lib/libCRFSuite.dylib
0x7fff8d32d000 - 0x7fff8d35bfff com.apple.CoreServicesInternal (154.2 - 154.2) <3E6196E6-F3B4-316F-9E1F-13B6B9694C7E> /System/Library/PrivateFrameworks/CoreServicesInternal.framework/Versions/A/Cor eServicesInternal
0x7fff8d544000 - 0x7fff8d544fff com.apple.Cocoa (6.7 - 19) <1F77945C-F37A-3171-B22E-F7AB0FCBB4D4> /System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa
0x7fff8d571000 - 0x7fff8d5b5fff libcups.2.dylib (327.3) <71E771A1-0489-3417-8A4A-56A2C930F80C> /usr/libTry this: http://support.apple.com/kb/TS4412
-
Best Practice to migrate existing Message/Central Instance to new hardware?
I've done some searching for this, but it all seems to be fairly old (I found one decent thread from 2008, but it just seemed outdated). I would like to get some updated info & suggestions on a process to follow for this task.
Here is some info about the current config:
I have an existing SAP ERP 6.0 EHP5 system. SID "XYZ"
Everything is currently running on Windows x64.
ABAP only config.
It is currently setup as a distributed system.
DB server is SQL, which is running on its own hardware as a dedicated DB server. I don't need to touch this.
Uses logon groups to distribute the load between 3 App servers.
One of the App Servers is setup as the Message/CI server. This is what I am wanting to move to VM hardware.
The other two App Servers are setup just as Dialog Instances. VM already. I don't need to touch these.
What I am wanting to do:
I am wanting to migrate the existing Message/CI server to VM hardware to get the current Message/CI system off of very old hardware.
I need to keep the system with the same name & IP.
I do not need/want to mess with the DB server at all.
Need to minimize downtime as much as possible.
I do NOT want to go to an HA environment. That is a different project for the future.
Suggestions? I would like to hear what some of you have done.
Minimize downtime? I have a short maintenance window of a few hours coming up in the next few months, and would like to do this changeover during that downtime.
How do I handle setting this up on the new hardware using the same name & IP, especially with the existing system still running.
What I think I need to do: (Some of these may be out of order, which is why I'm asking for suggestions)
Setup new Windows VM server, named differently than current Message/CI server (Done already).
Run SAPINST to run Global Host Preparation on the new Windows VM server.
Run SAPINST to setup ASCS Instance on the new Windows VM server.
Skip the Database Instance installation, since I already have one running.
Run SAPINST to setup Central Instance on the new Windows VM server.
Copy all of the appropriate profile parameters that were on the old server.
Start SAP and make sure everything is running and working correctly.
Copy all job, spool files, etc. from the old server.
What needs to be done in between those steps for the server rename & IP changes?
Which of these steps can I do in advance of my maintenance downtime window, without it affecting the currently running system?
I have a test environment that I am going to test this with. I'm just trying to get a jump start on my instructions, so that I can hopefully do this quickly and easily. I'm very comfortable doing the installs. Just needing some guidance on how to handle this case.
I'm open to suggestions, and any links you can send my way that show some more recent success at doing this. Everything I keep finding talks about doing the migration for the DB. I am not migrating my DB. It is staying where it is. I'm just wanting to migrate my Message/Central Instance to a VM, without affecting the users, and hopefully them never noticing the changes.
Thanks!If you're using VMWare, there is a tool provided to virtualize existing systems. Basically it makes a copy of the old system (while it is down) and recreates it as a VM with the same name, IP, etc. I haven't double-checked to see if this process is 'officially' supported by SAP, and I don't know the technical details about how it's done or how long it will take (VMWare is managed by the Network Operations group in my team, so as the SAP sysadmin I'm basically a customer of theirs). However, we have virtualized a few smaller systems that needed to get off failing hardware in a hurry and it worked very well, so I would expect it would for an SAP dialog instance as well. As you're not copying a database, just the app server, it probably would fit within your maintenance window.
If this route works for you, then there is no need to actually install the SAP system on the VM instance... you just copy the old server as-is, then make any adjustments required due to no longer needing old drivers, etc, plus potentially having different memory parameters. -
The wife tried to do an update on her new IPhone 5c now it is frozen at an ITunes screen, the screen has a pic of a cable and phone connector pointing to an ITunes symbol with the word ITunes under it. when it tries to do a restore the computer comes up with an error 21.
What has she done.Check for hardware issues
Related errors: 1, 3, 10-47, 1002, 1011, 1012, 1014, 1000-1020, 1669.
Try to restore your iOS device two more times while connected with a cable, computer, and network you know are good. Also, confirm your security software and settings are allowing communication between your device and update servers. If you still see the error message when you update or restore, contact Apple support.
Error 1015 might happen after making unauthorized modifications to iOS, also called "jailbreaking." -
SOLVED: 1030NR - SD Card Reader launches Found New Hardware Wizard when media is inserted
I purchased the HP Mini 1000 1030NR a few days ago and have been very happy with it so far. Last night I attempted to use the integrated SD card reader to view some photos from my digital cameras SD card. When I inserted the card into the drive, Windows did its normal hardware initializations. It should have detected and installed the SD Card Reader automatically, but instead I was presented with the "Found New Hardware" wizard. Every attempt to install the driver automatically via the Wizard failed. Every SD card I tried in the reader produced the same results.
After spending 2 and a half hours online with HP support, their eventual resolution was to do a full System Restore. As owners of the HP Mini 1000 will know, this process is made difficult due to the units lack of a DVD-ROM drive. Furthermore, the problem here is clearly a missing driver. Doing a System Restore as suggested would be like swatting at a fly with a cinderblock. It may resolve the problem, but there is a much more straightforward way.
The problem is that due to the nature of the XP installation on the 1030NR,(scaled down for performance/size reasons), the linkage between recognized hardware and the internal Windows driver respository has been broken, at least as far as USB devices are concerned. I found this out after the same HP support technician suggested I uninstall all of my USB Root Hubs from Device Manager and reboot. Those never came back either. Fortunately I had created an XP restore point beforehand and quickly got my USB ports back. Of course, my SD card reader still didn't work.
The solution is to restore that linkage between recognized hardware and the internal Windows driver repository so that the operating system can "find" the USB drivers and in turn, install the necessary software components for the SD card reader. Instructions for doing this are as follows:
1. Insert an SD card into the SD card reader. The "Found New Hardware" Wizard will appear.
2. Check the radio button to not allow Windows Update to search for software. Click Next.
3. Check the radio button to "Install from a list or specific Location (Advanced). Click Next.
4. Check the radio button to "Search For the Best Driver In These Locations. Then click the checkbox "Include this location in the search."
5. Click the Browse button and navigate to "C:\Windows\inf" If you cannot navigate to this folder you may type it in the box manually. Click Next.
6. Follow the remaining on-screen prompts to complete the software driver installation. You may receive an error code at the end indicating that the device could not start. Disregard this for now. Once driver installation has been completed, reboot the computer.
7. Once the system is back up, the "Found New Hardware" wizard will probably reappear. If it doesn't, make sure the SD Card Reader has a card inserted in it. Cancel the Found New Hardware wizard and click Start - Control Panel - System - Hardware tab - Device Manager and look for entries with either an exclamation point or a question mark. You'll probably see the SD Card Reader with an exclamation point and an "Unknown Device" with a question mark.
8. For the SD card reader, right click on it and select "Update Driver..." from the list of options. Follow steps 2 through 6 above to complete installation. At the end, the card reader should be functional (you can see it in Windows Explorer, etc.) but you'll still have an "Unknown Device" in Device Manager.
9. To resolve the "Unknown Device", once again go to Device Manager, right click on the Unknown Device entry, click Update Driver and follow steps 2 through 6 above.
10. One final reboot and the SD card reader should be functional and no ? or ! warnings/errors should be present in Device Manager.
The reason for this issue in the first place is most certainly due to the way Windows XP is configured on the HP Mini 1000. Although this solution works for the 1030NR, it should also work for models in the same family that contain the 2-in-1 SD card reader. HP really needs to provide an official fix for this issue, preferably a "patch" that re-establishes the linkage between recognized hardware devices and the internal Windows XP driver repository. Their official support suggestion of doing a complete System Restore to solve the problem is impractical, heavy handed, and may in fact not solve the issue.
It took me nearly 5 hours total to resolve this problem. I hope this post saves somebody both time and trouble.C:\Windows is the default folder for the Windows XP installation on the 1030nr. Unless changed during installation, all PC's (not just mini's) that have XP installed will have this folder present. As for the inf folder specifically, this is hidden from view in Windows Explorer unless you tick the option to "Show Hidden Files and Folders" from Tools - Folder Options - View tab.
Still, you shouldn't need to "see" this folder for the above instructions to work. When running the "Found New Hardware" wizard, you can just type the path in manually at the appropriate spot. If you truly do not have a C:\Windows\inf folder, then it sounds like something is wrong with your Windows installation and a full System Recovery may be the best option. It might be a good idea to contact HP support first before donig that though.
Does your Mini run Windows? If not, unfortunately the instructions I laid out above will not help you. I believe the "other" Mini's run some HP customized version of Ubuntu Linux. For that OS, you'll need to obtain a driver specifically for it to get the card reader working. Try the HP site for a download for the SD card reader or contact support.
Message Edited by neildittmar on 05-11-2009 03:42 AM
Maybe you are looking for
-
IPod Shuffle will not sync music - "files not available"
I originally thought at first I had a defective Shuffle. I returned the Shuffle and exchanged it for a new one and I am having the same problem. I also have already done a restore and software update to the new Shuffle and it did not solve the proble
-
Exporting to PDF in Grayscale - Black and White
We have recently been told that even though some of our reports have been created in black and white, they are not printing in grayscale. Since there is quite a difference in the price, we are trying to explore how we can export in grayscale. We ar
-
Is my Stor.E alu2 USB HDD covered by warranty?
Good morning all, I was wondering whether somebody can confirm whether my StorE Alu2 external USB Hard Drive has a warranty period? I have had it for just over a month and it has stopped working. It was dropped once, not heavily though, and has a tin
-
Only balances in local crcy (no efect)
Hi, I have a problem with an account that didn't have the ''Only balances in local crcy'' checkmark on in FS00. After I activated this checkmark, I am still able to see balances in other currencies and this is not normal. Do I have to make something
-
Anyone notice new choice of "iPhone" in Contacts?
I was cleaning up my contacts today on my iPhone and I noticed that there is a new choice in the phone number section: iPhone. Does anyone know if this does anything other than display "iPhone" under someone's name when they call you? Lisa