Corruption of the Location of Referenced Images

In other threads we have discussed problems with Aperture becoming confused about which referenced files it is supposed to connect with. Here is my analysis of one aspect of this problem.
When you have a group of referenced files, if you move some of them to another folder on the same volume or rename them Aperture attempts to find the moved file and change the reference to it. This might be what you want, or it might not, so Aperture ought to ask you whether to change the reference or not. But it does not.
If the volume on which you have your original files is not mounted, Aperture will mark the files as unavailable but will not change any links. This is clearly the behavior one would expect.
A problem occurs when your files are missing, but the volume they were on is mounted. This might happen if, for example, if one of your folders had been inadvertently deleted and needed to be reclaimed from a backup disk. In this situation Aperture "reconnects" the references in your Aperture library to what appears to be arbitrary files on the volume. The new references likely bear no relation to the files you really want. This is clearly not the behavior you would expect or want. When this happens it is usually impossible to use the "Manage Referenced Files" command to reconnect the files, because the correct files and the ones now referenced in the database aren't the same size and don't share the characteristics which permit the "Reconnect" button to be enabled when the reference and correct file are selected in the "Referenced File" dialog. Even the "option key" trick which sometimes allows the "Reconnect" button to be forcibly enabled will not work once this happens.
Obviously, this is a potentially catastrophic issue if a huge number of file references become corrupted in your library. The only way to fix things that I have found is to reimport all of the correct referenced image files, then lift and stamp metadata and image corrections from the corrupt reference entries in the library to the "new" referenced files. This is extraordinarily tedious if the number of files affected is large.
In any event, this is a serious bug and it should have been found long ago in Apple quality assurance testing and fixed. It ought also to be possible to just hand enter the correct reference to a referenced image in the library if nothing else works.

Possibly going to settings, general, international, region format, then select the country you are in.

Similar Messages

What is the point of referenced images

i'm starting to think either ap2.1 is a vastly inferior product to its predecessor, or there are just so many bugs and kinks that still have yet to be worked out and apple has given no indication when they will.
In addition to my still unresolved constant thumbnail regeneration issue when using referenced images from when ap2.0 launched, I am now experiencing problems when trying to edit referenced images using an external editor (in my case photoshop)
after exporting the image via aperture to photoshop for editing, making my edits, and then saving them in phothshop, the psd. file which is created in aperture is NOT acknowledging the edit...typically when working with a non-referenced image aperture will update the psd. file almost immediately with a new thumbnail image recognizing the change. in this case, not only is it not generating a new thumbnail, but when i click on generate thumbnail nothing happens. furthermore, upon closing and reopening aperture, the referenced psd. is missing, and the original referenced RAW image file is stacked with only itself (a small number 1 indicating a stack but only 1 image in the stack).
is there an aperture support number that I can call? I have been severely disappointed with the performance of this program.

To your post header, I think the point of referenced images is self evident. They allow you to store your images on external media, or to utilize your own folder structure for organization in the finder. Many people prefer this to having Aperture manage the images in one library. I use a combination of both methods.
That's the "point" of them. Now if you're having some issues using them, or it you're experiencing unusual behavior that's a different topic. I round trip to Photoshop (less and less with 2.1 and the new plug-ins) with my referenced images without the problems you describe. Once I've made my edits in Photoshop and save the image, when I return to Aperture the image appear next to the original, in a stack, displaying the edits I performed in Photoshop. Additionally the new image is stored in the same location as my referenced image.
Why you're not seeing this I'm not certain. There can't be a stack of one image. What can happen if you have a smart album for example, or the search field set to display only 5 star rated images, is that the photo from a stack that meets that criteria will show up in the browser. It will also show the stack number. However, if no other images in the stack meet the criteria of the search, they will not display even if you click on the stack. So it will seem like there is a stack of one image since you can display only that one image. This only happens if you've got a filter of some kind in effect.
I also don't have the problems with thumbnails you describe, and I use Aperture daily with thousands of images. I would suggest rebuilding your library as a first step (hold down the command-option key at launch).

Can I "redesignate" the location of my images in Lightroom?

Using LR over the years I have ended up with a rather clumsy storage scheme. I have been primarily storing my images on a NAS and importing them into LR as wanted (referencing them at their current location on the NAS). I now have many images imported into LR but still located on the NAS.
My NAS images are secondarily backed up to an external hard drive that connects via USB 3.0 to my desktop computer. It is an exact sync between the NAS and the USB drive, so at all times their content is identical.
It is now clear to me that I should be primarily storing on the USB drive and secondarily backing up to the NAS because accessing the USB drive through LR is much, much faster than accessing the NAS.
Because the file structures and content for image storage are identical on the USB drive and the NAS, can I somehow redirect LR to the USB drive as the primary location of my images without destroying all the links in my catalog file?
Thanks for your help.

Adobe Lightroom - Find moved or missing files and folders

Projects and Referenced Images

Hi - I have been using APerture 1.5.6 for a while but am suddenly confused and have several questions:
1)Most of my images are Referenced and exist on my hard drive in various folders with various titles. If I get rid of the Aperture Library, my referenced files will still be on my hard drive untouched including all the versions I have made - is this correct?
2) If I get rid of the Aperture library (delete it) all that will be lost is the names of my projects - is this correct?
3) Which brings to me to this question. The projects in Aperture do not match the names of my folders under Pictures on my hard drive. For example - on the hard drive I have a 2009 Folder and within this folder have Winter 2009, Fall 2009 and so on. In Aperture I have a 2009 Folder with many projects with names (like Sam's Birthday) which do not match the folders on my hard drive. Sam's Birthday project for example is in the 2009 Fall Folder. How do I reconcile this so all my projects are created as folders in the the right Parent folder in my hard drive. If I export the project is just duplicates the photos and I don't want this. Thanks so much

pavillion wrote:
1)Most of my images are Referenced and exist on my hard drive in various folders with various titles. If I get rid of the Aperture Library, my referenced files will still be on my hard drive untouched including all the versions I have made - is this correct? 2) If I get rid of the Aperture library (delete it) all that will be lost is the names of my projects - is this correct?
No. "Referenced" means the Masters images reside where you left them, not in the Aperture Library. But versions only live in the Library so deleting the Library would delete all edits and versions.
3) The projects in Aperture do not match the names of my folders under Pictures on my hard drive. For example - on the hard drive I have a 2009 Folder and within this folder have Winter 2009, Fall 2009 and so on. In Aperture I have a 2009 Folder with many projects with names (like Sam's Birthday) which do not match the folders on my hard drive. Sam's Birthday project for example is in the 2009 Fall Folder. How do I reconcile this so all my projects are created as folders in the the right Parent folder in my hard drive. If I export the project is just duplicates the photos and I don't want this. ...I don't want to ditch Aperture. I want my hard drive to reflect the same organization as the projects/catalogue in Aperture.
Personally I recommend trying to avoid what I call "folder-think," or thinking about digital image files the way we thought about film originals. Of course digitally we still have file folders, but any given folder is not necessarily relevant to the location of an image file (unlike with film, where only one folder has all the film in it). Dozens of folders in Aperture can all "point" to the same image version.
Apply keywords as needed in Aperture to allow you to easily correlate the image files that you renamed when you imported into Aperture with the folders outside of Aperture. In the future you may want to do what I do. After a shoot copy images from CF to a named folder on the hard drive like 20090314-SJoneswedmstr. Then when that folder is imported into Aperture name the Aperture folder 20090314-SJones_wed. Also include 20090314-SJones_wed as a batch keyword during import along with other important keywords like Jones, wed, etc.
2) So if I want to save the image modifications I have done on Aperture, I have to export the version of each modified image to my hard drive? ...I assume I need to do all this MANUALLY.
I don't really understand the question. The Aperture Referenced-Masters Library automatically saves all the edits/versions and links to Masters. Masters do need to be separately backed up from the Library, but that to me is natural anyway because IMO Masters should be fully redundantly on/off site backed up before ever importing into Aperture.
4) One more question. I am trying out photomechanic and what I really want to do is use Aperture in conjunction with Photomechanic as I am told Photomechanic is a better organizational tool.
I don't know who told you that but I disagree and unless you already have long experience with Photo Mechanic I would just stick to Aperture. One learning curve at a time is plenty!
HTH
-Allen Wicks

Managing backup systems for referenced image masters

The manual says:
+Aperture doesn’t back up the masters of referenced images located outside the Aperture library. *You must maintain your own backup system of referenced image masters.* Aperture does back up the versions, previews, and metadata information associated with referenced images, but not the masters themselves.+ (my bolding)
So, somehow, I ended up with some images (older, it seems) in the vault but other images (newer) as referenced. An incomplete back up to the vault. I understand how I can move those referenced to the Vault but:
1) is there a fast way to find and select all the referenced masters for this move? Like a menu item or a button in a dialog box that says "Find and move all referenced Masters to the vault"? Simple eh?
2) why does Apple not allow you to keep referenced Masters out of the vault but a copy of the Master backed up in it? When it goes to reinstall (hopefully never!), it can just reinstall the whole vault in Aperture - if need be. I could live with this especially if it makes backing up all my Masters easy and recovering all of them assured.
3) Since #2 is not possible for now - how do people back up referenced files and why do you do referenced over Vaulted or a combination of the two (which is what I have but, not knowing I was doing this)? I would like to be able to look at images on my MacBook Pro but really keep the bulk of the images and editing on a MacPro.
4) when I imported iPhoto to Aperture, did they all come in as vault Masters or referenced?

Joseph Coates wrote:
...when I imported iPhoto to Aperture, did they all come in as vault Masters or referenced?
Images are imported according to settings you select. Probably you initially imported using a Managed-Images Library. To import by Reference from within Aperture, import images from the hard drive folder into Aperture selecting "Store files in their current location."
...how do people back up referenced files
Using any normal data backup method. I like to simply manually Finder-copy to external hard drives.
and why do you do referenced over Vaulted or a combination of the two (which is what I have but, not knowing I was doing this)?
Actually the correct syntax is Referenced over Managed. Vault refers to one type of backup routine that does include Managed Masters.
The primary problem with using a Managed-Masters Library instead of a Referenced-Masters Library is that for almost all modern digital photogs using Aperture their quantity of image files will grow quickly, rapidly taking more and more space on a single internal hard drive if Managed-Masters keeps all image files on a single internal hard drive.
Hard drives slow as they fill, so unless a multi-drive SATA/eSATA array is used a Managed-Library drive will sooner or later lose performance. Use of Referenced-Masters allows the Library to forever stay small enough not to overfill a single drive.
Personally I consider separate backup of Masters outside Aperture's Vault protocol a benefit, not a negative.
Using a Managed-Masters Library works even for for laptop/iMac owners if completed Projects with Masters are constantly purged from Aperture but that is inappropriate workflow for most photogs, and the benefits of using a Managed-Masters workflow are minimal.
I would like to be able to look at images on my MacBook Pro but really keep the bulk of the images and editing on a MacPro.
Although various user workarounds exist, the issue of synching your laptop Library with your desktop Library has not (yet) been addressed by Apple. IMO Apple's failure (still) to address this key issue is a travesty; Apple's single-user Filemaker has had that capability since the 1980's.
I suggest going to "Provide Aperture Feedback" under the Aperture menu and requesting that Apple provide single-user synch capabilities for two Libraries (such as the laptop/desktop setups that you and I both have). Note that it is important to specify single-user, two-Libraries, because multi-user scenarios are entirely different solutions that - unlike single user solutions - are usually very complex and expensive.
-Allen Wicks

TestStand Location of Deployable Image

In TestStand, what is the difference between "Location of Deployable Image" on the System Source Tab, and "Default Installation Base & Sub Directory" on Installer Options.

Hello MrBean,
The "Location of Deployable Image" in "System Source" tab specifies the directory to which the deployment utility will copy an image of the system. This image can be copied over the network or put in an installer. So this is the copy of your installer on your computer that you can use to install the application on other computers,
The "Default Installation Base Directory" in "Installer Options" tab specifies the base directory used by the installer as the default installation location. So on your target computer it specifies the base directory of where the application will be installed. For example C:\Program Files\
The "Default Installation Subdirectory" in "Installer Options" tab specifies a subdirectory under the default installation base directory used by the installer as the default installation location. This is the sub directory inside your base directory for your application. For example C:\Program Files\My TestStand Application\
I hope this helps,
Rajiv Garg

Deleting Aperture Trash when 'The referenced image's master has not been found'

i'm in a bit of a stick- ive got 107 images in my aperture trash with the 'The referenced image’s master has not been found'
how do i delete these?
Thanks
Nish

If I have a referenced image which has a missing master file I can stil move the version to the trash and empty the trash and it is gone from Aperture.
The only time I get any warning is if I have the check box set to also move the move the referneced master to the trash. Of course in this case Aperture can't fine the master so it can't move it to the trash. But if I click continue on the warning box the version is still removed from the Aperture trash.
So is it the missing referenced masters that you are asking how to delete? If so locate them in the finder and delete them as you would any ordinary file.
If this isn't want you are trying to do you'll need to post back.
regards

I have about 10000 images of different persons with dimension of 640*480. I wan to crop face from these images to dimension of 200*280. The location of face varies in differnt pics. So, please let me know step by step how can I perform this using the Ligh

I have about 10000 images of different persons with dimension of 640*480. I wan to crop face from these images to dimension of 200*280. The location of face varies in differnt pics. So, please let me know step by step how can I perform this using the Lightroom software. Also I wan to know what should be the aspect ratio to do so.Thank you in advance

The aspect ratio should be set to 200x280, or equivalently 5x7.
I don't think it is possible to do the cropping automatically in Lightroom, you'd have to do this image by image to crop the faces correctly.

I was using photoshop CC as normal, when suddenly it started going haywire. It has corrupted all the one PSD files by distorting the images and colour. Does anyone know how to recover the original images?

I was using photoshop CC as normal, when suddenly it started going haywire. It has corrupted all the open PSD files by distorting the images and colour. They are now completely unrecognisable and unusable. Does anyone know how to recover the original images as I was saving them as I went along but the files are now corrupt?

What version of Photoshop are you running?
I've seen a couple of instances over the last week or two where Photoshop has added masks, strange colours and also merged content from two separate PSD files that were open at the same time.
This has occurred on two different iMacs, (both 10.10.x) running Photoshop CC 2014.2.2 (20141204.r.310 x64).
see image below for example:

I am using referenced images, saved on an external hard drive. It would be most helpful to transfer the new captions (version name) to the referenced images which still have the camera code on them. How can this be done? Thanks so much!

I am using referenced images, saved on an external hard drive. It would be most helpful to transfer the new captions (version name) to the referenced images which still have the camera code on them. How can this be done? Thanks so much!

You're question is hard to follow. Are you looking to rename your master files to the version name? Or are you looking to do something with IPTC caption field and the masters?

Aperture 2 Thinks Referenced Images are Offline with Network Home Directory

Aperture thinks my Home directory is offline, but it's not. My Home directory is on a Mac OS X Server on the LAN (i.e., not on the machine in front of me that I run Aperture 2 on). I'm able to import images from my Nikon D200 in RAW/NEF format using Aperture 2, and write them to my Network Home directory (again, on the Mac OS X Server across the LAN) with no problem. Images are added to Aperture Library as REFERENCED images. Actual image files and Aperture Library are within the Pictures folder in my Network Home directory (on the OS X Server across the LAN). Previews and images show up fine initially. However, after importing and quitting, the next launch of Aperture 2 shows those same imported/referenced images as being offline (i.e., alias badge with red strike-thru). No way to get Aperture 2 to recognize that these image files are really ONLINE, not off.
Tried to re-establish the link from Aperture to each image file using File->Manage Referenced Images..., but that corrupted something. Image becomes red slate with "Unsupported Image Format" message, and image preview goes blank/gray on next Aperture 2 launch.
Previous version of Aperture (v1.5.?) did not have this problem.

Thanks for the replies (in triplicate! from grommet). More information:
REFERENCED images that were imported earlier (using Aperture v1.5.x) show up ON-LINE in Aperture 2 (i.e., all is OK with the earlier images; referenced image badge has no red strike-thru).
The images that were imported more recently--all with Aperture 2--continue to show the referenced image badge with the red strike-thru, indicating Aperture thinks they're OFF-LINE (even though they're not). This makes it impossible to edit or use any of the more recent images that were imported with Aperture 2.
Here's the kicker: the more recent images imported with Aperture 2 and indicated as being OFF-LINE are stored in the SAME general file location as the earlier images that were imported with Aperture v1.5.x and are indicated as being ON-LINE!
My Home Directory is on a Mac OS X Server across the LAN.
Aperture Library is at: ~/Pictures/
Earlier images are at: ~/Pictures/Digital Photos/Roll-000001/1999-05-26-0001.NEF
Recent images are at: ~/Pictures/Digital Photos/Roll-000107/2008-04-17-0001.NEF
Clearly a bug with Aperture 2. I've filed feedback with Apple. Hope to heck this bug is not overlooked in next incremental release. I'm stuck/dead in the water without a fix.

Windows Deployment Service corrupts \systemroot\system32\config\software in images.

Hello,
Recently we have upgraded to Server 2012 R2 to handle our WDS services but some images are not deploying correctly.
When checking the event log on the machines that do not deploy correctly, the following error message is discovered: "\systemroot\system32\config\software was corrupted and it has been recovered'
We can restore the SOFTWARE registry backup from the regback folder and this corrects the problem, but this has to be done after the image is deployed and takes a lot of time.
The WIM files all deploy fine in all instances of deployment on Server 2008 R2, using DISM directly and ImageX.
For one image, this only occurs on certain machines. It has been tested on 3 Z200 with the same hardware setup and the error occurs on 2 consistently and does not occur on the 3rd.
On another one of the images, this error occurs every time it is deployed using Server 2012 R2 but never when deployed using WDS on Server 2008 R2, DISM or ImageX.
This occurs whether the deployment is set attended or unattended. The majority of deployments have been tested without using an unattended file to eleminate variables.
Does anyone have any suggestions? Any ideas would be appreciated.
Edit:
We have also exported the WIM file of the image that always "breaks" from WDS 2012 R2 and successfully deployed it every time using 2008R2 WDS DISM and ImageX.
We have created separate folders for these problem WIM files so that the RES file only contains the information from the specific WIM that is having problems; this does not fix the problem.
Edit 2:
There is an error in setupact.log but it onlys says that the mentioned registry setting is malformed or corrupt. I tried a web search on this and had results but the majority of the answers were related to errors sysprepping.
Starting WDS GUI
2014-02-12 16:47:07, Warning    [0x0a0180] UI     Failed to change the UI language to en-US.
2014-02-12 16:47:22, Error      [0x0a0052] UI     Failed to read image data from blackboard[gle=0x00000002]
2014-02-12 16:47:29, Warning    [0x07008d] DIAG   Win32_Processor : CoInitializeEx returned RPC_E_CHANGED_MODE. Continue. Error code = 0x80010106
2014-02-12 16:47:31, Warning    [0x070026] DIAG   Win32_Processor : Unable to retrieve Stepping, vtType = 8. Error code = 0x0
Setting up disk
2014-02-12 16:47:51, Warning    [0x0606cc] IBS    DeleteFileEx: Unable to clear out attributes on [D:\$WINDOWS.~BT\Sources\Rollback\bootsec.dat]; GLE = 0x2
2014-02-12 16:47:51, Warning               WDS    CallBack_WdsClient_MulticastCopyFiles: Error transferring files. Falling back to unicast. Error [0x80070002]
2014-02-12 16:47:51, Warning    [0x0b0095] WDS    CallBack_WdsClient_MulticastCopyFiles: Multicast transfer failed. Error code [0x80070002].
Active Dir Setup
2014-02-12 17:11:21, Info       [0x0b0083] WDS    MgLibpOpenLdapConnectionFromDN: DN=
2014-02-12 17:11:21, Error      [0x0b00c2] WDS    [
2014-02-12 17:11:21, Info       [0x0b00c2] WDS    <
2014-02-12 17:11:21, Error      [0x0b00c2] WDS    [
2014-02-12 17:11:21, Info       [0x0b00c2] WDS    <
2014-02-12 17:11:21, Error      [0x0b00c2] WDS    [
2014-02-12 17:11:21, Info       [0x0b007e] WDS    ProcessDomainJoinInformation: MachineName = [(null)], MachineDomain = [(null)]
2014-02-12 17:11:21, Warning    [0x0b0093] WDS    ProcessDomainJoinInformation: Error resetting machine account. Error [0x80070057].
2014-02-12 17:11:21, Error      [0x0b00c2] WDS    [
Set up IBSLIB
2014-02-12 17:12:39, Info                  IBSLIB Copying files from D:\Windows\Boot\PCAT\en-US to \\?\GLOBALROOT\Device\HarddiskVolume3\Boot\en-US...
2014-02-12 17:12:39, Info                  IBSLIB SetNamedSecurityInfo failed! Error code = 0x2
2014-02-12 17:12:39, Info                  IBSLIB Unable to open file \\?\GLOBALROOT\Device\HarddiskVolume3\Boot\en-US\bootmgr.exe.mui for read because the file or path does
not exist
2014-02-12 17:12:39, Info                  IBSLIB SetNamedSecurityInfo failed! Error code = 0x2
2014-02-12 17:12:39, Info                  IBSLIB Unable to open file \\?\GLOBALROOT\Device\HarddiskVolume3\Boot\en-US\memtest.exe.mui for read because the file or
2014-02-12 17:12:39, Warning               IBSLIB Resource files missing from D:\Windows\Boot\Resources. These files are required for some editions of Windows. If you are servicing older
versions of Windows, you can ignore this message.
Sysprep Plug N Play
2014-02-12 17:14:54, Info                  SYSPRP SPPNP: Removing the devices that are using service mpio ...
2014-02-12 17:14:54, Info                  SYSPRP SPPNP: The device Root\LEGACY_MPIO\0000 is using the service mpio.
2014-02-12 17:14:54, Warning               SYSPRP SPPNP: Error 0xE000020B occurred while adding device Root\LEGACY_MPIO\0000 to the device info set.
2014-02-12 17:14:54, Info                  SYSPRP SPPNP: Finished removing the devices that are using service mpio.
Sysprep specalize
2014-02-12 17:18:11, Info       [0x0f008a] SYSPRP RunRegistryDlls:Retrieved section name for this phase as Specialize
2014-02-12 17:18:11, Warning    [0x0f008f] SYSPRP RunRegistryDlls:Registry key is either empty or malformed: SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\SysPrepExternal\Specialize
2014-02-12 17:18:11, Info                  IBS    Callback_Specialize: External Providers Specialized Succeeded
Modify boot entries (Non UFI)
2014-02-12 17:18:15, Info       [0x0606cc] IBS    Flushing registry to disk...
2014-02-12 17:18:17, Info       [0x0606cc] IBS    Flush took 1201 ms.
2014-02-12 17:18:17, Info       [0x06036b] IBS    Callback_SystemRestore: Successfully set System Restore state.
2014-02-12 17:18:17, Info       [0x0606cc] IBS    GetSystemPartitionNTPath: Found system partition at [\Device\HarddiskVolume1].
2014-02-12 17:18:17, Warning    [0x0606cc] IBS    GetSystemPartitionPath: Unable to find DOS drive path for system partition [\Device\HarddiskVolume1].
2014-02-12 17:18:17, Info       [0x0606cc] IBS    GetSystemPartitionNTPath: Found system partition at [\Device\HarddiskVolume1].
2014-02-12 17:18:17, Warning    [0x0606cc] IBS    GetSystemPartitionPath: Unable to find DOS drive path for system partition [\Device\HarddiskVolume1].
2014-02-12 17:18:17, Warning               IBSLIB ModifyBootEntriesLegacy: There was an error getting the path to the boot.ini or ntldr. dwRetCode=[0x1F]
2014-02-12 17:18:17, Warning               IBSLIB ModifyBootEntriesLegacy: We did not successfully complete ModifyBootEntriesLegacy. This is non-fatal, continuing setup. dwRetCode[0x1F]
Error in system log:
Log Name:      System
Source:        Microsoft-Windows-Kernel-General
Date:          2/12/2014 5:14:28 PM
Event ID:      5
Task Category: None
Level:         Error
Keywords:
User:          SYSTEM
Computer:
Description:
{Registry Hive Recovered} Registry hive (file): '\SystemRoot\System32\Config\SOFTWARE' was corrupted and it has been recovered. Some data might have been lost.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="Microsoft-Windows-Kernel-General" Guid="{}" />
    <EventID>5</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8000000000000000</Keywords>
    <TimeCreated SystemTime="2014-02-13T01:14:28.620907400Z" />
    <EventRecordID>12326</EventRecordID>
    <Correlation />
    <Execution ProcessID="4" ThreadID="364" />
    <Channel>System</Channel>
    <Computer>COMPUTERNAME</Computer>
    <Security UserID="S-1-5-18" />
</System>
<EventData>
    <Data Name="FinalStatus">0x8000002a</Data>
    <Data Name="ExtraStringLength">36</Data>
    <Data Name="ExtraString">\SystemRoot\System32\Config\SOFTWARE</Data>
</EventData>
</Event>
Sysprep Panther Log:
2014-02-12 14:39:58, Warning    [0x0f008f] SYSPRP RunRegistryDlls:Registry key is either empty or malformed: SOFTWARE
\Microsoft\Windows\CurrentVersion\Setup\SysPrepExternal\Cleanup
2014-02-12 14:39:58, Warning    [0x0f008f] SYSPRP RunRegistryDlls:Registry key is either empty or malformed: SOFTWARE
\Microsoft\Windows\CurrentVersion\Setup\SysPrepExternal\Generalize
2014-02-12 14:40:10, Warning                      TapiSysPrep.dll:RetainTapiLocations:RegQueryValueEx() returned 2
2014-02-12 14:40:14, Warning               SYSPRP SPPNP: The original start type of service vhdmp was not found in its expected back-up location. Hence we will not be re-enabling this
service. This is not necessarily an error.
2014-02-12 14:40:14, Warning               SYSPRP SPPNP: The original start type of service VMBusHID was not found in its expected back-up location. Hence we will not be re-enabling this
service. This is not necessarily an error.
2014-02-12 14:40:14, Warning               SYSPRP SPPNP: The original start type of service Brserid was not found in its expected back-up location. Hence we will not be re-enabling this service.
This is not necessarily an error.
2014-02-12 14:40:14, Warning               SYSPRP SPPNP: The original start type of service usbcir was not found in its expected back-up location. Hence we will not be re-enabling this service.
This is not necessarily an error.
2014-02-12 14:40:14, Warning               SYSPRP SPPNP: The original start type of service usbccgp was not found in its expected back-up location. Hence we will not be re-enabling this service.
This is not necessarily an error.
2014-02-12 14:40:14, Warning               SYSPRP SPPNP: The original start type of service usbhub was not found in its expected back-up location. Hence we will not be re-enabling this service.
This is not necessarily an error.
2014-02-12 14:40:14, Warning               SYSPRP SPPNP: The original start type of service USBSTOR was not found in its expected back-up location. Hence we will not be re-enabling this service.
This is not necessarily an error.
2014-02-12 14:40:14, Warning               SYSPRP SPPNP: The original start type of service sffdisk was not found in its expected back-up location. Hence we will not be re-enabling this service.
This is not necessarily an error.
2014-02-12 14:40:14, Warning               SYSPRP SPPNP: The original start type of service vpcbus was not found in its expected back-up location. Hence we will not be re-enabling this service.
This is not necessarily an error.
2014-02-12 14:40:14, Warning               SYSPRP SPPNP: The original start type of service umbus was not found in its expected back-up location. Hence we will not be re-enabling this service.
This is not necessarily an error.
2014-02-12 14:40:14, Warning               SYSPRP SPPNP: The original start type of service swenum was not found in its expected back-up location. Hence we will not be re-enabling this service.
This is not necessarily an error.
2014-02-12 14:40:14, Warning               SYSPRP SPPNP: The original start type of service rdpbus was not found in its expected back-up location. Hence we will not be re-enabling this service.
This is not necessarily an error.
2014-02-12 14:40:15, Warning               SYSPRP SPPNP: The original start type of service iScsiPrt was not found in its expected back-up location. Hence we will not be re-enabling this
service. This is not necessarily an error.
2014-02-12 14:40:15, Warning               SYSPRP SPPNP: The original start type of service CompositeBus was not found in its expected back-up location. Hence we will not be re-enabling this
service. This is not necessarily an error.
2014-02-12 14:40:15, Warning               SYSPRP SPPNP: The original start type of service circlass was not found in its expected back-up location. Hence we will not be re-enabling this
service. This is not necessarily an error.
2014-02-12 14:40:15, Warning               SYSPRP SPPNP: The original start type of service ebdrv was not found in its expected back-up location. Hence we will not be re-enabling this service.
This is not necessarily an error.
2014-02-12 14:40:15, Warning               SYSPRP SPPNP: The original start type of service b06bdrv was not found in its expected back-up location. Hence we will not be re-enabling this service.
This is not necessarily an error.
2014-02-12 14:40:15, Warning               SYSPRP SPPNP: The original start type of service s3cap was not found in its expected back-up location. Hence we will not be re-enabling this service.
This is not necessarily an error.
2014-02-12 14:40:15, Warning               SYSPRP SPPNP: The original start type of service 1394ohci was not found in its expected back-up location. Hence we will not be re-enabling this
service. This is not necessarily an error.
2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service usbehci was not found in its expected back-up location. Hence we will not be re-enabling this service.
This is not necessarily an error.
2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service usbohci was not found in its expected back-up location. Hence we will not be re-enabling this service.
This is not necessarily an error.
2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service usbuhci was not found in its expected back-up location. Hence we will not be re-enabling this service.
This is not necessarily an error.
2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service ohci1394 was not found in its expected back-up location. Hence we will not be re-enabling this
service. This is not necessarily an error.
2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service HDAudBus was not found in its expected back-up location. Hence we will not be re-enabling this
service. This is not necessarily an error.
2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service BrUsbMdm was not found in its expected back-up location. Hence we will not be re-enabling this
service. This is not necessarily an error.
2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service BrSerWdm was not found in its expected back-up location. Hence we will not be re-enabling this
service. This is not necessarily an error.
2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service HidBatt was not found in its expected back-up location. Hence we will not be re-enabling this service.
This is not necessarily an error.
2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service MTConfig was not found in its expected back-up location. Hence we will not be re-enabling this
service. This is not necessarily an error.
2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service mouhid was not found in its expected back-up location. Hence we will not be re-enabling this service.
This is not necessarily an error.
2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service kbdhid was not found in its expected back-up location. Hence we will not be re-enabling this service.
This is not necessarily an error.
2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service sfloppy was not found in its expected back-up location. Hence we will not be re-enabling this service.
This is not necessarily an error.
2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service usbprint was not found in its expected back-up location. Hence we will not be re-enabling this
service. This is not necessarily an error.
2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service HidUsb was not found in its expected back-up location. Hence we will not be re-enabling this service.
This is not necessarily an error.
2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service UmPass was not found in its expected back-up location. Hence we will not be re-enabling this service.
This is not necessarily an error.
2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service HidIr was not found in its expected back-up location. Hence we will not be re-enabling this service.
This is not necessarily an error.
2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service HidBth was not found in its expected back-up location. Hence we will not be re-enabling this service.
This is not necessarily an error.
2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service BTHMODEM was not found in its expected back-up location. Hence we will not be re-enabling this
service. This is not necessarily an error.
2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service hcw85cir was not found in its expected back-up location. Hence we will not be re-enabling this
service. This is not necessarily an error.
2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service WacomPen was not found in its expected back-up location. Hence we will not be re-enabling this
service. This is not necessarily an error.
2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service Processor was not found in its expected back-up location. Hence we will not be re-enabling this
service. This is not necessarily an error.
2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service IPMIDRV was not found in its expected back-up location. Hence we will not be re-enabling this service.
This is not necessarily an error.
2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service intelppm was not found in its expected back-up location. Hence we will not be re-enabling this
service. This is not necessarily an error.
2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service AmdK8 was not found in its expected back-up location. Hence we will not be re-enabling this service.
This is not necessarily an error.
2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service AmdPPM was not found in its expected back-up location. Hence we will not be re-enabling this service.
This is not necessarily an error.
2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service AcpiPmi was not found in its expected back-up location. Hence we will not be re-enabling this service.
This is not necessarily an error.
2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service CmBatt was not found in its expected back-up location. Hence we will not be re-enabling this service.
This is not necessarily an error.
2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service sermouse was not found in its expected back-up location. Hence we will not be re-enabling this
service. This is not necessarily an error.
2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service ErrDev was not found in its expected back-up location. Hence we will not be re-enabling this service.
This is not necessarily an error.
2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service WmiAcpi was not found in its expected back-up location. Hence we will not be re-enabling this service.
This is not necessarily an error.
2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service flpydisk was not found in its expected back-up location. Hence we will not be re-enabling this
service. This is not necessarily an error.
2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service fdc was not found in its expected back-up location. Hence we will not be re-enabling this service.
This is not necessarily an error.
2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service Parport was not found in its expected back-up location. Hence we will not be re-enabling this service.
This is not necessarily an error.
2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service pcmcia was not found in its expected back-up location. Hence we will not be re-enabling this service.
This is not necessarily an error.
2014-02-12 14:40:16, Warning               SYSPRP SPPNP: The original start type of service i8042prt was not found in its expected back-up location. Hence we will not be re-enabling this
service. This is not necessarily an error.

We have discovered that this is only happening to target computers with installed
RAM greater than 4gb. If the machine has greater than 4gb of RAM, the mentioned corruption occurs. If the machine has
4gb or less, the corruption does not occur. We still have not found a fix for this, (besides removing the excess RAM during imaging and reinstalling after.) Any ideas/thoughts would be helpful! Thank you in advance.

Referencing images in off-line approjects - possible?

I like to keep my Aperture library as slim and "clean" as possible. I only keep essential shoots and images in the library at any one time. Before the 1.5 update, I was exporting images in the form of approjects in order to keep all versions and image adjustments intact. I could reimport them if I needed to access any images.
Now that 1.5 is out with referencing possibilities, I was hoping to be able to reference the images in my exported approjects. I haven't been able to find a way to do this. Has anyone else?
Anther question on the same topic. Now that Aperture allows the export of xmp files with mastes and versions, is this a better solution than exporting approject? or would it be better to export the approject and be able to reference it?
Any thoughts?
Jeff

If you were always exporting projects before, a better way to go now might be to relocate the masters for a project in a simialrily named directory and locate it wherever you put approjects before... that way you keep the project in your library for reference, but also get to keep the larger master images offline.
I would make sure you had exactly the settings you want for previews if you are going to do this as they too can be kind of large unless you keep the size down a bit. Just make sure you have previews at a quality level and size you wil be comfortable storing for a lot of images.
I am also exploring an approach where I relocate all lower rated masters out of the library and put them offline, while leaving the very highest rated image masters in place for quick access. That might be a good stratey to keep you from dipping into the offline bucket too much.

Upgrading from Aperture 2-3. What happens to referenced images?

I'm upgrading from Aperture 2 to 3. I have referenced images on some external hard drives. Will my referenced images be okay and still read correctly from my HD if I upgrade?

Hi
I had no problems it retained the Referenced File location info you will have to ensure the externals connected.
If they are not linked as indicated by a red line through the referenced file icon bottom RH corner
Select the images that need reconnecting and then go to File / Locate Referenced Files
You will get a dialogue box which enables you to find the Referenced File/s then click Reconnect or Reconnect All
I just had to do it because I renamed an external drive
Hope this helps

How to change to working with referenced images but keep library on laptop

Hi,
So, my iPhoto library is getting too big - I'd like to be able to have the images stored on an external drive and refer to them from within iPhoto, whilst keeping the iPhoto Library itself on the laptop. I know exactly how to do this from scratch, by unchecking 'copy items to my iPhoto library' in advanced preferences, but I'm trying to figure out how to convert my existing library, which has all the photos stored within it, to one where all the original files are on an external drive and are referenced by iPhoto. This way, I can see the previews when I'm away without the external drive attached.
Thanks!

There is no easy way to do it and I would strongly urge you to reconisder.
In a Referenced Library, iPhoto creates aliases to the location of the actual file. While there is at least one app that will help you replace those aliases with the actual files (convert a Referenced to Managed library) there is no app that will convert those files to aliases that point to the new location of the files. You will need to do each file manually.
More importantly, iPhoto has no tools to manage Referenced files. While on the same volume, aliases will track moved files. However this is not the case where the files are on different volumes. The upshot of this is that should the link to the files be broken then you could find yourself reconnecting each and every alias in your Library, one by one.
Also, I'm not sure about 09 but earlier versions of iPhoto would not open if there were movie files in the Library that were not available at time of launch.
You can move an entire Library to an external disk. There are firewire and usb disks now no bigger than a pack of playing cards and will run from the laptop's power supply.
Regards
TD

Corruption of the Location of Referenced Images

Similar Messages

Maybe you are looking for