Waiting for iLife '09 to arrive
Hi,
I'm still waiting on delivery of my iLife '09 software and questions keep popping into my head while I sit here waiting.
Is there an option after assigning a name in Faces to not have that particular person appear on the corkboard?
If you assign more than multiple names to a group photo, does Faces create duplicates or just use the one photo? (I asked this before but can't find the answer :P )
Is there an option after assigning a name in Faces to not have that particular person appear on the corkboard?
No.
If you assign more than multiple names to a group photo, does Faces create duplicates or just use the one photo? (I asked this before but can't find the answer :P
What are ”more that multiple names“?
No, iPhoto doesn't duplicate the file, it takes up no extra disk space.
Regards
TD
Similar Messages
-
I have bought an iphone 5 from cash converters. I'm waiting for a sim from my provider to arrive by post. I have left my phone on and twice it has turned its self off, is this right or is my phone seem faulty? I haven't been able to try the phone out yet as I didn't have a small SIM card. I'm worried as to why it would be turned off when I didn't turn it off.?.
If it turns off again take it back it,s not your problem ask for a refund or replacement
BSYDD Uk -
What will you be doing tomorrow instead of waiting for your phone to arrive?
What will the rest of the unlucky ones like me, be doing tomorrow instead of waiting like a kid at christmas for your new toy to arrive?
You really think any store will have one on Saturday ??? Good Luck, let us know how that works out.
-
I was originally getting the site through Google but had problems they told me to download Firefox which I did but still get no positive results. I am rather than old computer addict (88 yrs old) so I find it difficult to understand some computer technology,
First be sure login and password are OK. Sometimes the address starts wit "http://..." and sometime starts with "ftp://...". Try both normal FTP access and Scure FTP access (SFTP). At the end, contact the site's provider.
-
Emails arrive fast on my iPhone and my iPad but I have to wait for hours on my iMac ?
Why do new emails arrive fast on my iPhone and my iPad but I have to wait for hours on my iMac ?
They don't... and there are emails I only get on my iPhone 5, later on on my iPad and they don't arrive on my iMac... at all, NOT GOOD.
-
Please tell me, when will the ipad mini arrive in india, i'm eagerly waiting for that !
When Apple has a stock of refurbished iPads they will be sold.
There is no set time, date or quantity. -
I have just gone from PCM to MacBook Pro retina and would like to now go to imac. Is it worth waiting for retina on imac and when will it arrive
I'm not Klaus but can give an opinion on this part:
As a Mac man yourself do you think that the retina display is worth waiting for?
I'm 65, have used Macs since 1989, and struggle with displays, cataracts, and bifocals. What I've seen of the Retinas in stores is that text size gets sacrificed for image quality. There are quite a few complaints about Retina in the MacBook Pro forums about not being able to increase the size of menu text without it getting fuzzy.
My iMac 27-inch is about a year old and I can set the display res from its default of 2560x1440 to 1920x1080 and everything is sharp. I understand that handy trick will not work for either the older hi-res macbook pros or the Retinas, so I don't expect it for any other Macs.
Speculation on Apple policy and new product releases is actiually not allowed by the Terms of Use around here so I doubt you'll get an answer to the "when" part. Anyone who does answer "when" is either guessing it up or violating a non-disclosure agreement! Apple plays its cards close to its vest and we average users only know "when" when Apple posts the announcement. -
How can i verify my account to start using my iphone 5
Im waiting for an wmail but still... NO EMAILS
FEELING STRESSED AND DISSAPOINTED :-(Hi Kirby grace bete,
Thanks for visiting Apple Support Communities.
If you have not received the verification email for your Apple ID, I recommend visiting the My Apple ID page to make sure your email was entered correctly, and re-send the verification email.
You can also resend the email verification if the email address is not verified:
Sign in to My Apple ID to manage your account information.
Click Resend under Primary Email Address.
Verify your changes by following the link in the email you receive from Apple, then signing back in to your account.
From:
Apple ID: Associating and verifying email addresses with your Apple ID
http://support.apple.com/kb/he68
All the best,
Jeremy -
IPhone 4 stuck on upgrade "Waiting for iPhone..."
Hi,
i am trying to upgrade my iPhone 4, but it stuck on apple Logo with Progressbar, but no response from iPhone while iTunes show "Waiting for iPhone..." contineously.
guide me how i can fix the problem, i am using iPhone3_1_6.1.3_10B329_Restore.ipsw and my iTunes Version: 11.0.2.26.
complete updater log is given below:
2013-04-10 20:03:45.327 [5612:2c8]: restore library built Dec 21 2012 at 16:17:03
2013-04-10 20:03:45.327 [5612:2c8]: iTunes: iTunes 11.0.2.26
2013-04-10 20:03:45.328 [5612:2c8]: iTunes: Software payload version: 10B329 (option key)
2013-04-10 20:04:25.590 [5612:152c]: iTunes: Specifying UOI boot image
2013-04-10 20:04:25.604 [5612:152c]: device software does not support nonce generation
2013-04-10 20:04:25.614 [5612:152c]: requested restore behavior: Erase
2013-04-10 20:04:25.614 [5612:152c]: requested variant: Erase
2013-04-10 20:04:25.617 [5612:152c]: *** UUID 25C69700-C111-9C44-AFE2-793B8CA91FD8 ***
2013-04-10 20:04:25.640 [5612:152c]: amai: _AMAuthInstallBundleCreateServerRequestDictionary: withApTicket is False
2013-04-10 20:04:25.640 [5612:152c]: amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "RestoreLogo"
2013-04-10 20:04:25.640 [5612:152c]: amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "RestoreDeviceTree"
2013-04-10 20:04:25.640 [5612:152c]: amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "RestoreKernelCache" Digest = "<CFData 0641B718 [73B48078]>{length = 20, capacity = 20, bytes = 0xf9c7660c4c2994b9fd95cd826507cff3cb4f9105}"
2013-04-10 20:04:25.640 [5612:152c]: amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "RestoreRamDisk" Digest = "<CFData 0641B7B8 [73B48078]>{length = 20, capacity = 20, bytes = 0x9a46d40f4b54424c825f6c82670be22b86e03f0a}"
2013-04-10 20:04:25.640 [5612:152c]: amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "iBEC" Digest = "<CFData 0641B830 [73B48078]>{length = 20, capacity = 20, bytes = 0xdd4e78d11b416e9f81dc947a3e45125d726229de}"
2013-04-10 20:04:25.640 [5612:152c]: amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "iBSS" Digest = "<CFData 0641B880 [73B48078]>{length = 20, capacity = 20, bytes = 0x165d7df43bd289b3e13d48f5c1e8b21cf2a0335e}"
2013-04-10 20:04:25.641 [5612:152c]: amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "KernelCache" Digest = "<CFData 0641AFE8 [73B48078]>{length = 20, capacity = 20, bytes = 0xf9c7660c4c2994b9fd95cd826507cff3cb4f9105}"
2013-04-10 20:04:25.641 [5612:152c]: amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "BatteryLow1"
2013-04-10 20:04:25.641 [5612:152c]: amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "BatteryLow0"
2013-04-10 20:04:25.641 [5612:152c]: amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "LLB" Digest = "<CFData 0641B218 [73B48078]>{length = 20, capacity = 20, bytes = 0x023683df4637e071c5a733d59cebe67d2fc1bfea}"
2013-04-10 20:04:25.641 [5612:152c]: amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "iBoot"
2013-04-10 20:04:25.641 [5612:152c]: amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "DeviceTree"
2013-04-10 20:04:25.641 [5612:152c]: amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "BatteryCharging1"
2013-04-10 20:04:25.641 [5612:152c]: amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "BatteryCharging"
2013-04-10 20:04:25.641 [5612:152c]: amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "AppleLogo"
2013-04-10 20:04:25.641 [5612:152c]: amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "BatteryPlugin"
2013-04-10 20:04:25.641 [5612:152c]: amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "BatteryFull"
2013-04-10 20:04:25.641 [5612:152c]: amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "BatteryCharging0"
2013-04-10 20:04:25.641 [5612:152c]: amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "RecoveryMode"
2013-04-10 20:04:25.642 [5612:152c]: amai: _AMAuthInstallBundleCreateServerRequestDictionary: using UniqueBuildID <CFData 0641B920 [73B48078]>{length = 20, capacity = 20, bytes = 0x42cc389503004c4f8d52d0c4fb10bba845a9af0e}
2013-04-10 20:04:25.642 [5612:152c]: amai: AMAuthInstallRequestSendSync: SSO function returned NULL, SSO disabled.
2013-04-10 20:04:26.542 [5612:152c]: amai: tss_submit_job: HttpQueryInfo returned 200
2013-04-10 20:04:27.162 [5612:152c]: amai: AMAuthInstallRequestSendSync: received tss response (server version: 2.1.0)
2013-04-10 20:04:27.411 [5612:152c]: amai: _AMAuthInstallBundleInstallPersonalizedEntry: entry "KernelCache" has been previously personalized; skipping it
2013-04-10 20:04:27.838 [5612:12e4]: device software does not support nonce generation
2013-04-10 20:04:27.839 [5612:12e4]: <DFU Device 05B6B038>: production fused device
2013-04-10 20:04:27.839 [5612:12e4]: unable to open device_map.txt: No such file or directory
2013-04-10 20:04:27.840 [5612:12e4]: device software does not support nonce generation
2013-04-10 20:04:27.841 [5612:12e4]: WinDFU::OpenDFUDevice: path: \\?\USB#VID_05AC&PID_1227#{B8085869-FEB9-404B-8CB1-1E5C14FA8C54}\0000#85fc20a6
2013-04-10 20:04:27.841 [5612:12e4]: WinDFU::OpenDeviceByPath: \\?\USB#VID_05AC&PID_1227#{B8085869-FEB9-404B-8CB1-1E5C14FA8C54}\0000#85fc20a6
2013-04-10 20:04:27.868 [5612:12e4]: <DFU Device 05B6B038>: operation 0 progress 3
2013-04-10 20:04:27.908 [5612:12e4]: <DFU Device 05B6B038>: operation 0 progress 6
2013-04-10 20:04:27.950 [5612:12e4]: <DFU Device 05B6B038>: operation 0 progress 9
2013-04-10 20:04:27.977 [5612:12e4]: <DFU Device 05B6B038>: operation 0 progress 12
2013-04-10 20:04:27.995 [5612:12e4]: <DFU Device 05B6B038>: operation 0 progress 15
2013-04-10 20:04:28.015 [5612:12e4]: <DFU Device 05B6B038>: operation 0 progress 18
2013-04-10 20:04:28.043 [5612:12e4]: <DFU Device 05B6B038>: operation 0 progress 21
2013-04-10 20:04:28.060 [5612:12e4]: <DFU Device 05B6B038>: operation 0 progress 24
2013-04-10 20:04:28.078 [5612:12e4]: <DFU Device 05B6B038>: operation 0 progress 27
2013-04-10 20:04:28.095 [5612:12e4]: <DFU Device 05B6B038>: operation 0 progress 30
2013-04-10 20:04:28.111 [5612:12e4]: <DFU Device 05B6B038>: operation 0 progress 33
2013-04-10 20:04:28.129 [5612:12e4]: <DFU Device 05B6B038>: operation 0 progress 36
2013-04-10 20:04:28.146 [5612:12e4]: <DFU Device 05B6B038>: operation 0 progress 39
2013-04-10 20:04:28.164 [5612:12e4]: <DFU Device 05B6B038>: operation 0 progress 42
2013-04-10 20:04:28.225 [5612:12e4]: <DFU Device 05B6B038>: operation 0 progress 45
2013-04-10 20:04:28.254 [5612:12e4]: <DFU Device 05B6B038>: operation 0 progress 48
2013-04-10 20:04:28.270 [5612:12e4]: <DFU Device 05B6B038>: operation 0 progress 51
2013-04-10 20:04:28.286 [5612:12e4]: <DFU Device 05B6B038>: operation 0 progress 54
2013-04-10 20:04:28.302 [5612:12e4]: <DFU Device 05B6B038>: operation 0 progress 57
2013-04-10 20:04:28.318 [5612:12e4]: <DFU Device 05B6B038>: operation 0 progress 60
2013-04-10 20:04:28.334 [5612:12e4]: <DFU Device 05B6B038>: operation 0 progress 63
2013-04-10 20:04:28.350 [5612:12e4]: <DFU Device 05B6B038>: operation 0 progress 66
2013-04-10 20:04:28.366 [5612:12e4]: <DFU Device 05B6B038>: operation 0 progress 69
2013-04-10 20:04:28.382 [5612:12e4]: <DFU Device 05B6B038>: operation 0 progress 72
2013-04-10 20:04:28.398 [5612:12e4]: <DFU Device 05B6B038>: operation 0 progress 75
2013-04-10 20:04:28.414 [5612:12e4]: <DFU Device 05B6B038>: operation 0 progress 78
2013-04-10 20:04:28.430 [5612:12e4]: <DFU Device 05B6B038>: operation 0 progress 81
2013-04-10 20:04:28.446 [5612:12e4]: <DFU Device 05B6B038>: operation 0 progress 84
2013-04-10 20:04:28.462 [5612:12e4]: <DFU Device 05B6B038>: operation 0 progress 87
2013-04-10 20:04:28.478 [5612:12e4]: <DFU Device 05B6B038>: operation 0 progress 90
2013-04-10 20:04:28.495 [5612:12e4]: <DFU Device 05B6B038>: operation 0 progress 93
2013-04-10 20:04:28.513 [5612:12e4]: <DFU Device 05B6B038>: operation 0 progress 96
2013-04-10 20:04:28.529 [5612:12e4]: <DFU Device 05B6B038>: operation 0 progress 99
2013-04-10 20:04:28.530 [5612:12e4]: WinDFU::UploadData: EOF, cbRead: 489
2013-04-10 20:04:28.535 [5612:12e4]: <DFU Device 05B6B038>: operation 0 progress 100
2013-04-10 20:04:28.536 [5612:12e4]: WinDFU::UploadData: ZLP
2013-04-10 20:04:28.538 [5612:12e4]: WinDFU::FinalizeDfuUpdate: GetStatus: status: 0, state: 6
2013-04-10 20:04:28.539 [5612:12e4]: WinDFU::ProcessUpdateState: status.bState == DFU_STATE_MANIFEST_SYNC
2013-04-10 20:04:28.540 [5612:12e4]: WinDFU::FinalizeDfuUpdate: GetStatus: status: 0, state: 7
2013-04-10 20:04:28.540 [5612:12e4]: WinDFU::ProcessUpdateState: status.bState == DFU_STATE_MANIFEST, PollTimeout: 3000
2013-04-10 20:04:31.540 [5612:12e4]: WinDFU::FinalizeDfuUpdate: GetStatus: status: 0, state: 8
2013-04-10 20:04:31.541 [5612:12e4]: WinDFU::ProcessUpdateState: status.bState == DFU_STATE_MANIFEST_WAIT_RESET
2013-04-10 20:04:31.541 [5612:12e4]: WinDFU::ResetDevice: resetting...
2013-04-10 20:04:31.607 [5612:12e4]: WinDFU::FinalizeDfuUpdate: success
2013-04-10 20:04:31.607 [5612:12e4]: <DFU Device 05B6B038>: DFU succeeded
2013-04-10 20:04:31.920 [5612:c1c]: WinAMRestore::OnInterfaceRemoval: \\?\USB#VID_05AC&PID_1227#{B8085869-FEB9-404B-8CB1-1E5C14FA8C54}\0000#85fc20a6
2013-04-10 20:04:31.927 [5612:c1c]: WinAMRestore::ProcessDevNodesChanges: device: 0x05c069c0, notify: 2, connected: 1
2013-04-10 20:04:31.927 [5612:c1c]: AppleDevice::NotifyDisconnect: DFU \\?\USB#VID_05AC&PID_1227#{B8085869-FEB9-404B-8CB1-1E5C14FA8C54}\0000#85fc20a6, inst: 0x5c069c0
2013-04-10 20:04:31.929 [5612:c1c]: _AMDFUModeDeviceFinalize: 05B6B038
2013-04-10 20:04:32.692 [5612:c1c]: WinAMRestore::OnInterfaceArrival: \\?\USB#VID_05AC&PID_1227#{B8085869-FEB9-404B-8CB1-1E5C14FA8C54}\0000#b187d9bd
2013-04-10 20:04:32.692 [5612:c1c]: WinAMRestore::AddAppleDeviceToDeviceList: \\?\USB#VID_05AC&PID_1227#{B8085869-FEB9-404B-8CB1-1E5C14FA8C54}\0000#b187d9bd
2013-04-10 20:04:32.721 [5612:c1c]: AppleDevice::EnumerateHubPorts: DoesDriverNameMatchDeviceID failed
2013-04-10 20:04:32.744 [5612:c1c]: AppleDevice::EnumerateHubPorts: DoesDriverNameMatchDeviceID failed
2013-04-10 20:04:32.766 [5612:c1c]: AppleDevice::EnumerateHubPorts: DoesDriverNameMatchDeviceID failed
2013-04-10 20:04:32.775 [5612:c1c]: AppleDevice::SetNotification: CONNECT, interface type: 1, id: \\?\USB#VID_05AC&PID_1227#{B8085869-FEB9-404B-8CB1-1E5C14FA8C54}\0000#b187d9bd, inst: 0x5a4e728
2013-04-10 20:04:32.775 [5612:c1c]: WinAMRestore::AddAppleDeviceToDeviceList, new device
2013-04-10 20:04:32.775 [5612:c1c]: WinAMRestore::ProcessDevNodesChanges: device: 0x05c069c0, notify: 0, connected: 0
2013-04-10 20:04:32.775 [5612:c1c]: WinAMRestore::ProcessDevNodesChanges: device: 0x05a4e728, notify: 1, connected: 0
2013-04-10 20:04:32.775 [5612:c1c]: AppleDevice::NotifyConnect: Device type: 1, Interfaces total: 1, arrived: 1
2013-04-10 20:04:32.775 [5612:c1c]: AppleDevice::NotifyConnect: DFU \\?\USB#VID_05AC&PID_1227#{B8085869-FEB9-404B-8CB1-1E5C14FA8C54}\0000#b187d9bd, inst: 0x5a4e728
2013-04-10 20:04:32.795 [5612:2c8]: AppleDevice::GetDeviceID: failed for iBoot
2013-04-10 20:04:32.796 [5612:2c8]: AppleDevice::GetDeviceID: failed for iBoot
2013-04-10 20:04:32.797 [5612:2c8]: AppleDevice::GetDeviceID: failed for iBoot
2013-04-10 20:04:32.798 [5612:2c8]: iTunes: SCEP 2
2013-04-10 20:04:32.844 [5612:92c]: AppleDevice::GetDeviceID: failed for iBoot
2013-04-10 20:04:32.845 [5612:92c]: <DFU Device 05A507B0>: operation 44 progress -1
2013-04-10 20:04:32.846 [5612:92c]: requested restore behavior: Erase
2013-04-10 20:04:32.846 [5612:92c]: requested variant: Erase
2013-04-10 20:04:32.862 [5612:92c]: amai: _AMAuthInstallBundleCreateServerRequestDictionary: withApTicket is True
2013-04-10 20:04:32.862 [5612:92c]: amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "RestoreLogo" Digest = "<CFData 0641C118 [73B48078]>{length = 20, capacity = 20, bytes = 0x91024670dc5047de33036c446b5ef53cc22db756}"
2013-04-10 20:04:32.862 [5612:92c]: amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "RestoreDeviceTree" Digest = "<CFData 0641C078 [73B48078]>{length = 20, capacity = 20, bytes = 0xec0295f90e86975ec27258b69b4fdd995fa9b307}"
2013-04-10 20:04:32.862 [5612:92c]: amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "RestoreKernelCache" Digest = "<CFData 0641C0A0 [73B48078]>{length = 20, capacity = 20, bytes = 0xf9c7660c4c2994b9fd95cd826507cff3cb4f9105}"
2013-04-10 20:04:32.862 [5612:92c]: amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "RestoreRamDisk" Digest = "<CFData 0641C140 [73B48078]>{length = 20, capacity = 20, bytes = 0x9a46d40f4b54424c825f6c82670be22b86e03f0a}"
2013-04-10 20:04:32.862 [5612:92c]: amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "iBEC" Digest = "<CFData 0641C1B8 [73B48078]>{length = 20, capacity = 20, bytes = 0xdd4e78d11b416e9f81dc947a3e45125d726229de}"
2013-04-10 20:04:32.862 [5612:92c]: amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "iBSS" Digest = "<CFData 0641C208 [73B48078]>{length = 20, capacity = 20, bytes = 0x165d7df43bd289b3e13d48f5c1e8b21cf2a0335e}"
2013-04-10 20:04:32.862 [5612:92c]: amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "KernelCache" Digest = "<CFData 0641BF60 [73B48078]>{length = 20, capacity = 20, bytes = 0xf9c7660c4c2994b9fd95cd826507cff3cb4f9105}"
2013-04-10 20:04:32.862 [5612:92c]: amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "BatteryLow1" Digest = "<CFData 0641BBA0 [73B48078]>{length = 20, capacity = 20, bytes = 0x7c5b9e305d6713ca95a0bf52cfa9d74a76632165}"
2013-04-10 20:04:32.863 [5612:92c]: amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "BatteryLow0" Digest = "<CFData 0641BE48 [73B48078]>{length = 20, capacity = 20, bytes = 0x970dc6e48a164ce0c2fe50604fbc04ba00084b5b}"
2013-04-10 20:04:32.863 [5612:92c]: amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "LLB" Digest = "<CFData 0641BEE8 [73B48078]>{length = 20, capacity = 20, bytes = 0x023683df4637e071c5a733d59cebe67d2fc1bfea}"
2013-04-10 20:04:32.863 [5612:92c]: amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "iBoot" Digest = "<CFData 0641C258 [73B48078]>{length = 20, capacity = 20, bytes = 0x4de4c1c53f24322a593c4e0819486491ccad687d}"
2013-04-10 20:04:32.863 [5612:92c]: amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "DeviceTree" Digest = "<CFData 0641BCE0 [73B48078]>{length = 20, capacity = 20, bytes = 0xec0295f90e86975ec27258b69b4fdd995fa9b307}"
2013-04-10 20:04:32.863 [5612:92c]: amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "BatteryCharging1" Digest = "<CFData 0641BA60 [73B48078]>{length = 20, capacity = 20, bytes = 0xcc090e191df8c84c0190fc19d831b272ff8289a3}"
2013-04-10 20:04:32.863 [5612:92c]: amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "BatteryCharging" Digest = "<CFData 0641B9E8 [73B48078]>{length = 20, capacity = 20, bytes = 0x95bad50919c4e28a2cde4b0d62a4a4044e044e6e}"
2013-04-10 20:04:32.863 [5612:92c]: amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "AppleLogo" Digest = "<CFData 0641B538 [73B48078]>{length = 20, capacity = 20, bytes = 0x91024670dc5047de33036c446b5ef53cc22db756}"
2013-04-10 20:04:32.863 [5612:92c]: amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "BatteryPlugin" Digest = "<CFData 0641B998 [73B48078]>{length = 20, capacity = 20, bytes = 0x9af17593f66dc089400eeb384c7294baadad60b6}"
2013-04-10 20:04:32.863 [5612:92c]: amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "BatteryFull" Digest = "<CFData 0641BAB0 [73B48078]>{length = 20, capacity = 20, bytes = 0x70b6a985e9999f7ebba8fe057883e71e46a11827}"
2013-04-10 20:04:32.863 [5612:92c]: amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "BatteryCharging0" Digest = "<CFData 0641BA10 [73B48078]>{length = 20, capacity = 20, bytes = 0x0c65d77dce3418d0b9267136b8c9933bffda4cd7}"
2013-04-10 20:04:32.863 [5612:92c]: amai: _AMAuthInstallBundleCreateServerRequestDictionary: personalizing "RecoveryMode" Digest = "<CFData 0641C028 [73B48078]>{length = 20, capacity = 20, bytes = 0x9172551efd8c236e1f3c042aee9ddcd4716cdf4d}"
2013-04-10 20:04:32.863 [5612:92c]: amai: _AMAuthInstallBundleCreateServerRequestDictionary: using UniqueBuildID <CFData 0641C2A8 [73B48078]>{length = 20, capacity = 20, bytes = 0x42cc389503004c4f8d52d0c4fb10bba845a9af0e}
2013-04-10 20:04:32.864 [5612:92c]: amai: AMAuthInstallRequestSendSync: SSO function returned NULL, SSO disabled.
2013-04-10 20:04:33.536 [5612:92c]: amai: tss_submit_job: HttpQueryInfo returned 200
2013-04-10 20:04:34.057 [5612:92c]: amai: AMAuthInstallRequestSendSync: received tss response (server version: 2.1.0)
2013-04-10 20:04:34.065 [5612:92c]: amai: _AMAuthInstallBundleInstallPersonalizedEntry: entry "RestoreKernelCache" has been previously personalized; skipping it
2013-04-10 20:04:34.065 [5612:92c]: amai: _AMAuthInstallBundleInstallPersonalizedEntry: entry "RestoreRamDisk" has been previously personalized; skipping it
2013-04-10 20:04:34.065 [5612:92c]: amai: _AMAuthInstallBundleInstallPersonalizedEntry: entry "iBEC" has been previously personalized; skipping it
2013-04-10 20:04:34.065 [5612:92c]: amai: _AMAuthInstallBundleInstallPersonalizedEntry: entry "iBSS" has been previously personalized; skipping it
2013-04-10 20:04:34.065 [5612:92c]: amai: _AMAuthInstallBundleInstallPersonalizedEntry: entry "KernelCache" has been previously personalized; skipping it
2013-04-10 20:04:34.066 [5612:92c]: amai: _AMAuthInstallBundleInstallPersonalizedEntry: entry "LLB" has been previously personalized; skipping it
2013-04-10 20:04:34.074 [5612:92c]: AppleDevice::GetDeviceID: failed for iBoot
2013-04-10 20:04:34.075 [5612:92c]: <DFU Device 05A507B0>: production fused device
2013-04-10 20:04:34.076 [5612:92c]: unable to open device_map.txt: No such file or directory
2013-04-10 20:04:34.076 [5612:92c]: AppleDevice::GetDeviceID: failed for iBoot
2013-04-10 20:04:34.080 [5612:92c]: WinDFU::OpenDFUDevice: path: \\?\USB#VID_05AC&PID_1227#{B8085869-FEB9-404B-8CB1-1E5C14FA8C54}\0000#b187d9bd
2013-04-10 20:04:34.080 [5612:92c]: WinDFU::OpenDeviceByPath: \\?\USB#VID_05AC&PID_1227#{B8085869-FEB9-404B-8CB1-1E5C14FA8C54}\0000#b187d9bd
2013-04-10 20:04:34.091 [5612:92c]: <DFU Device 05A507B0>: operation 0 progress 0
2013-04-10 20:04:34.101 [5612:92c]: <DFU Device 05A507B0>: operation 0 progress 1
2013-04-10 20:04:34.111 [5612:92c]: <DFU Device 05A507B0>: operation 0 progress 2
2013-04-10 20:04:34.131 [5612:92c]: <DFU Device 05A507B0>: operation 0 progress 3
2013-04-10 20:04:34.141 [5612:92c]: <DFU Device 05A507B0>: operation 0 progress 4
2013-04-10 20:04:34.151 [5612:92c]: <DFU Device 05A507B0>: operation 0 progress 5
2013-04-10 20:04:34.171 [5612:92c]: <DFU Device 05A507B0>: operation 0 progress 6
2013-04-10 20:04:34.181 [5612:92c]: <DFU Device 05A507B0>: operation 0 progress 7
2013-04-10 20:04:34.201 [5612:92c]: <DFU Device 05A507B0>: operation 0 progress 8
2013-04-10 20:04:34.211 [5612:92c]: <DFU Device 05A507B0>: operation 0 progress 9
2013-04-10 20:04:34.221 [5612:92c]: <DFU Device 05A507B0>: operation 0 progress 10
2013-04-10 20:04:34.241 [5612:92c]: <DFU Device 05A507B0>: operation 0 progress 11
2013-04-10 20:04:34.251 [5612:92c]: <DFU Device 05A507B0>: operation 0 progress 12
2013-04-10 20:04:34.271 [5612:92c]: <DFU Device 05A507B0>: operation 0 progress 13
2013-04-10 20:04:34.281 [5612:92c]: <DFU Device 05A507B0>: operation 0 progress 14
2013-04-10 20:04:34.291 [5612:92c]: <DFU Device 05A507B0>: operation 0 progress 15
2013-04-10 20:04:34.311 [5612:92c]: <DFU Device 05A507B0>: operation 0 progress 16
2013-04-10 20:04:34.321 [5612:92c]: <DFU Device 05A507B0>: operation 0 progress 17
2013-04-10 20:04:34.331 [5612:92c]: <DFU Device 05A507B0>: operation 0 progress 18
2013-04-10 20:04:34.351 [5612:92c]: <DFU Device 05A507B0>: operation 0 progress 19
2013-04-10 20:04:34.361 [5612:92c]: <DFU Device 05A507B0>: operation 0 progress 20
2013-04-10 20:04:34.381 [5612:92c]: <DFU Device 05A507B0>: operation 0 progress 21
2013-04-10 20:04:34.391 [5612:92c]: <DFU Device 05A507B0>: operation 0 progress 22
2013-04-10 20:04:34.401 [5612:92c]: <DFU Device 05A507B0>: operation 0 progress 23
2013-04-10 20:04:34.421 [5612:92c]: <DFU Device 05A507B0>: operation 0 progress 24
2013-04-10 20:04:34.431 [5612:92c]: <DFU Device 05A507B0>: operation 0 progress 25
2013-04-10 20:04:34.451 [5612:92c]: <DFU Device 05A507B0>: operation 0 progress 26
2013-04-10 20:04:34.461 [5612:92c]: <DFU Device 05A507B0>: operation 0 progress 27
2013-04-10 20:04:34.471 [5612:92c]: <DFU Device 05A507B0>: operation 0 progress 28
2013-04-10 20:04:34.491 [5612:92c]: <DFU Device 05A507B0>: operation 0 progress 29
2013-04-10 20:04:34.501 [5612:92c]: <DFU Device 05A507B0>: operation 0 progress 30
2013-04-10 20:04:34.511 [5612:92c]: <DFU Device 05A507B0>: operation 0 progress 31
2013-04-10 20:04:34.531 [5612:92c]: <DFU Device 05A507B0>: operation 0 progress 32
2013-04-10 20:04:34.541 [5612:92c]: <DFU Device 05A507B0>: operation 0 progress 33
2013-04-10 20:04:34.561 [5612:92c]: <DFU Device 05A507B0>: operation 0 progress 34
2013-04-10 20:04:34.571 [5612:92c]: <DFU Device 05A507B0>: operation 0 progress 35
2013-04-10 20:04:34.581 [5612:92c]: <DFU Device 05A507B0>: operation 0 progress 36
2013-04-10 20:04:34.601 [5612:92c]: <DFU Device 05A507B0>: operation 0 progress 37
2013-04-10 20:04:34.611 [5612:92c]: <DFU Device 05A507B0>: operation 0 progress 38
2013-04-10 20:04:34.631 [5612:92c]: <DFU Device 05A507B0>: operation 0 progress 39
2013-04-10 20:04:34.641 [5612:92c]: <DFU Device 05A507B0>: operation 0 progress 40
2013-04-10 20:04:34.651 [5612:92c]: <DFU Device 05A507B0>: operation 0 progress 41
2013-04-10 20:04:34.671 [5612:92c]: <DFU Device 05A507B0>: operation 0 progress 42
2013-04-10 20:04:34.681 [5612:92c]: <DFU Device 05A507B0>: operation 0 progress 43
2013-04-10 20:04:34.691 [5612:92c]: <DFU Device 05A507B0>: operation 0 progress 44
2013-04-10 20:04:34.711 [5612:92c]: <DFU Device 05A507B0>: operation 0 progress 45
2013-04-10 20:04:34.721 [5612:92c]: <DFU Device 05A507B0>: operation 0 progress 46
2013-04-10 20:04:34.741 [5612:92c]: <DFU Device 05A507B0>: operation 0 progress 47
2013-04-10 20:04:34.751 [5612:92c]: <DFU Device 05A507B0>: operation 0 progress 48
2013-04-10 20:04:34.761 [5612:92c]: <DFU Device 05A507B0>: operation 0 progress 49
2013-04-10 20:04:34.781 [5612:92c]: <DFU Device 05A507B0>: operation 0 progress 50
2013-04-10 20:04:34.791 [5612:92c]: <DFU Device 05A507B0>: operation 0 progress 51
2013-04-10 20:04:34.811 [5612:92c]: <DFU Device 05A507B0>: operation 0 progress 52
2013-04-10 20:04:34.821 [5612:92c]: <DFU Device 05A507B0>: operation 0 progress 53
2013-04-10 20:04:34.831 [5612:92c]: <DFU Device 05A507B0>: operation 0 progress 54
2013-04-10 20:04:34.851 [5612:92c]: <DFU Device 05A507B0>: operation 0 progress 55
2013-04-10 20:04:34.861 [5612:92c]: <DFU Device 05A507B0>: operation 0 progress 56
2013-04-10 20:04:34.881 [5612:92c]: <DFU Device 05A507B0>: operation 0 progress 57
2013-04-10 20:04:34.891 [5612:92c]: <DFU Device 05A507B0>: operation 0 progress 58
2013-04-10 20:04:34.901 [5612:92c]: <DFU Device 05A507B0>: operation 0 progress 59
2013-04-10 20:04:34.921 [5612:92c]: <DFU Device 05A507B0>: operation 0 progress 60
2013-04-10 20:04:34.931 [5612:92c]: <DFU Device 05A507B0>: operation 0 progress 61
2013-04-10 20:04:34.941 [5612:92c]: <DFU Device 05A507B0>: operation 0 progress 62
2013-04-10 20:04:34.961 [5612:92c]: <DFU Device 05A507B0>: operation 0 progress 63
2013-04-10 20:04:34.971 [5612:92c]: <DFU Device 05A507B0>: operation 0 progress 64
2013-04-10 20:04:34.991 [5612:92c]: <DFU Device 05A507B0>: operation 0 progress 65
2013-04-10 20:04:35.001 [5612:92c]: <DFU Device 05A507B0>: operation 0 progress 66
2013-04-10 20:04:35.011 [5612:92c]: <DFU Device 05A507B0>: operation 0 progress 67
2013-04-10 20:04:35.031 [5612:92c]: <DFU Device 05A507B0>: operation 0 progress 68
2013-04-10 20:04:35.041 [5612:92c]: <DFU Device 05A507B0>: operation 0 progress 69
2013-04-10 20:04:35.061 [5612:92c]: <DFU Device 05A507B0>: operation 0 progress 70
2013-04-10 20:04:35.071 [5612:92c]: <DFU Device 05A507B0>: operation 0 progress 71
2013-04-10 20:04:35.081 [5612:92c]: <DFU Device 05A507B0>: operation 0 progress 72
2013-04-10 20:04:35.101 [5612:92c]: <DFU Device 05A507B0>: operation 0 progress 73
2013-04-10 20:04:35.111 [5612:92c]: <DFU Device 05A507B0>: operation 0 progress 74
2013-04-10 20:04:35.121 [5612:92c]: <DFU Device 05A507B0>: operation 0 progress 75
2013-04-10 20:04:35.141 [5612:92c]: <DFU Device 05A507B0>: operation 0 progress 76
2013-04-10 20:04:35.151 [5612:92c]: <DFU Device 05A507B0>: operation 0 progress 77
2013-04-10 20:04:35.171 [5612:92c]: <DFU Device 05A507B0>: operation 0 progress 78
2013-04-10 20:04:35.181 [5612:92c]: <DFU Device 05A507B0>: operation 0 progress 79
2013-04-10 20:04:35.191 [5612:92c]: <DFU Device 05A507B0>: operation 0 progress 80
2013-04-10 20:04:35.211 [5612:92c]: <DFU Device 05A507B0>: operation 0 progress 81
2013-04-10 20:04:35.221 [5612:92c]: <DFU Device 05A507B0>: operation 0 progress 82
2013-04-10 20:04:35.241 [5612:92c]: <DFU Device 05A507B0>: operation 0 progress 83
2013-04-10 20:04:35.251 [5612:92c]: <DFU Device 05A507B0>: operation 0 progress 84
2013-04-10 20:04:35.261 [5612:92c]: <DFU Device 05A507B0>: operation 0 progress 85
2013-04-10 20:04:35.281 [5612:92c]: <DFU Device 05A507B0>: operation 0 progress 86
2013-04-10 20:04:35.291 [5612:92c]: <DFU Device 05A507B0>: operation 0 progress 87
2013-04-10 20:04:35.301 [5612:92c]: <DFU Device 05A507B0>: operation 0 progress 88
2013-04-10 20:04:35.321 [5612:92c]: <DFU Device 05A507B0>: operation 0 progress 89
2013-04-10 20:04:35.331 [5612:92c]: <DFU Device 05A507B0>: operation 0 progress 90
2013-04-10 20:04:35.351 [5612:92c]: <DFU Device 05A507B0>: operation 0 progress 91
2013-04-10 20:04:35.361 [5612:92c]: <DFU Device 05A507B0>: operation 0 progress 92
2013-04-10 20:04:35.371 [5612:92c]: <DFU Device 05A507B0>: operation 0 progress 93
2013-04-10 20:04:35.391 [5612:92c]: <DFU Device 05A507B0>: operation 0 progress 94
2013-04-10 20:04:35.401 [5612:92c]: <DFU Device 05A507B0>: operation 0 progress 95
2013-04-10 20:04:35.421 [5612:92c]: <DFU Device 05A507B0>: operation 0 progress 96
2013-04-10 20:04:35.431 [5612:92c]: <DFU Device 05A507B0>: operation 0 progress 97
2013-04-10 20:04:35.441 [5612:92c]: <DFU Device 05A507B0>: operation 0 progress 98
2013-04-10 20:04:35.461 [5612:92c]: <DFU Device 05A507B0>: operation 0 progress 99
2013-04-10 20:04:35.461 [5612:92c]: WinDFU::UploadData: EOF, cbRead: 1257
2013-04-10 20:04:35.468 [5612:92c]: <DFU Device 05A507B0>: operation 0 progress 100
2013-04-10 20:04:35.468 [5612:92c]: WinDFU::UploadData: ZLP
2013-04-10 20:04:35.470 [5612:92c]: WinDFU::FinalizeDfuUpdate: GetStatus: status: 0, state: 6
2013-04-10 20:04:35.470 [5612:92c]: WinDFU::ProcessUpdateState: status.bState == DFU_STATE_MANIFEST_SYNC
2013-04-10 20:04:35.471 [5612:92c]: WinDFU::FinalizeDfuUpdate: GetStatus: status: 0, state: 7
2013-04-10 20:04:35.471 [5612:92c]: WinDFU::ProcessUpdateState: status.bState == DFU_STATE_MANIFEST, PollTimeout: 3000
2013-04-10 20:04:38.471 [5612:92c]: WinDFU::FinalizeDfuUpdate: GetStatus: status: 0, state: 8
2013-04-10 20:04:38.471 [5612:92c]: WinDFU::ProcessUpdateState: status.bState == DFU_STATE_MANIFEST_WAIT_RESET
2013-04-10 20:04:38.471 [5612:92c]: WinDFU::ResetDevice: resetting...
2013-04-10 20:04:38.537 [5612:92c]: WinDFU::FinalizeDfuUpdate: success
2013-04-10 20:04:38.537 [5612:92c]: <DFU Device 05A507B0>: DFU succeeded
2013-04-10 20:04:38.581 [5612:c1c]: WinAMRestore::OnInterfaceRemoval: \\?\USB#VID_05AC&PID_1227#{B8085869-FEB9-404B-8CB1-1E5C14FA8C54}\0000#b187d9bd
2013-04-10 20:04:38.582 [5612:c1c]: WinAMRestore::ProcessDevNodesChanges: device: 0x05c069c0, notify: 2, connected: 0
2013-04-10 20:04:38.582 [5612:c1c]: WinAMRestore::ProcessDevNodesChanges: device: 0x05a4e728, notify: 2, connected: 1
2013-04-10 20:04:38.582 [5612:c1c]: AppleDevice::NotifyDisconnect: DFU \\?\USB#VID_05AC&PID_1227#{B8085869-FEB9-404B-8CB1-1E5C14FA8C54}\0000#b187d9bd, inst: 0x5a4e728
2013-04-10 20:04:38.693 [5612:2c8]: _AMDFUModeDeviceFinalize: 05A507B0
2013-04-10 20:04:41.936 [5612:c1c]: WinAMRestore::OnInterfaceArrival: \\?\USB#VID_05AC&PID_1281#{ED82A167-D61A-4AF6-9AB6-11E52236C576}\IB0000#b187d9b d
2013-04-10 20:04:41.936 [5612:c1c]: WinAMRestore::AddAppleDeviceToDeviceList: \\?\USB#VID_05AC&PID_1281#{ED82A167-D61A-4AF6-9AB6-11E52236C576}\IB0000#b187d9b d
2013-04-10 20:04:41.961 [5612:c1c]: AppleDevice::EnumerateHubPorts: DoesDriverNameMatchDeviceID failed
2013-04-10 20:04:41.983 [5612:c1c]: AppleDevice::EnumerateHubPorts: DoesDriverNameMatchDeviceID failed
2013-04-10 20:04:42.005 [5612:c1c]: AppleDevice::EnumerateHubPorts: DoesDriverNameMatchDeviceID failed
2013-04-10 20:04:42.012 [5612:c1c]: AppleDevice::SetNotification: CONNECT, interface type: 1, id: \\?\USB#VID_05AC&PID_1281#{ED82A167-D61A-4AF6-9AB6-11E52236C576}\IB0000#b187d9b d, inst: 0x5a4ec28
2013-04-10 20:04:42.012 [5612:c1c]: WinAMRestore::AddAppleDeviceToDeviceList, new device
2013-04-10 20:04:42.012 [5612:c1c]: WinAMRestore::ProcessDevNodesChanges: device: 0x05c069c0, notify: 2, connected: 0
2013-04-10 20:04:42.012 [5612:c1c]: WinAMRestore::ProcessDevNodesChanges: device: 0x05a4e728, notify: 0, connected: 0
2013-04-10 20:04:42.012 [5612:c1c]: WinAMRestore::ProcessDevNodesChanges: device: 0x05a4ec28, notify: 1, connected: 0
2013-04-10 20:04:42.012 [5612:c1c]: AppleDevice::NotifyConnect: Device type: 2, Interfaces total: 2, arrived: 1
2013-04-10 20:04:42.012 [5612:c1c]: AppleDevice::NotifyConnect: Interfaces total != arrived, no notification
2013-04-10 20:04:42.114 [5612:c1c]: WinAMRestore::OnInterfaceArrival: \\?\USB#VID_05AC&PID_1281#{B8085869-FEB9-404B-8CB1-1E5C14FA8C54}\0000#b187d9bd
2013-04-10 20:04:42.115 [5612:c1c]: WinAMRestore::AddAppleDeviceToDeviceList: \\?\USB#VID_05AC&PID_1281#{B8085869-FEB9-404B-8CB1-1E5C14FA8C54}\0000#b187d9bd
2013-04-10 20:04:42.139 [5612:c1c]: AppleDevice::EnumerateHubPorts: DoesDriverNameMatchDeviceID failed
2013-04-10 20:04:42.161 [5612:c1c]: AppleDevice::EnumerateHubPorts: DoesDriverNameMatchDeviceID failed
2013-04-10 20:04:42.184 [5612:c1c]: AppleDevice::EnumerateHubPorts: DoesDriverNameMatchDeviceID failed
2013-04-10 20:04:42.191 [5612:c1c]: WinAMRestore::AddAppleDeviceToDeviceList, device already connected, new interface
2013-04-10 20:04:42.191 [5612:c1c]: AppleDevice::SetDeviceID: AMD_INTERFACE_DFU \\?\USB#VID_05AC&PID_1281#{B8085869-FEB9-404B-8CB1-1E5C14FA8C54}\0000#b187d9bd, inst: 0x5a4ec28
2013-04-10 20:04:42.191 [5612:c1c]: AppleDevice::SetNotification: CONNECT, interface type: 1, id: \\?\USB#VID_05AC&PID_1281#{B8085869-FEB9-404B-8CB1-1E5C14FA8C54}\0000#b187d9bd, inst: 0x5a4ec28
2013-04-10 20:04:42.191 [5612:c1c]: WinAMRestore::ProcessDevNodesChanges: device: 0x05c069c0, notify: 2, connected: 0
2013-04-10 20:04:42.191 [5612:c1c]: WinAMRestore::ProcessDevNodesChanges: device: 0x05a4e728, notify: 0, connected: 0
2013-04-10 20:04:42.191 [5612:c1c]: WinAMRestore::ProcessDevNodesChanges: device: 0x05a4ec28, notify: 1, connected: 1
2013-04-10 20:04:42.191 [5612:c1c]: AppleDevice::NotifyConnect: Device type: 2, Interfaces total: 2, arrived: 2
2013-04-10 20:04:42.191 [5612:c1c]: AppleDevice::NotifyConnect: IBOOT, IBOOT \\?\USB#VID_05AC&PID_1281#{ED82A167-D61A-4AF6-9AB6-11E52236C576}\IB0000#b187d9b d, inst: 0x5a4ec28
2013-04-10 20:04:42.191 [5612:c1c]: IBOOT, DFU \\?\USB#VID_05AC&PID_1281#{B8085869-FEB9-404B-8CB1-1E5C14FA8C54}\0000#b187d9bd, inst: 0x5a4ec28
2013-04-10 20:04:42.203 [5612:2c8]: iTunes: SCEP 2
2013-04-10 20:04:42.205 [5612:16f0]: iBoot build-version = iBoot-1537.9.55
2013-04-10 20:04:42.206 [5612:16f0]: iBoot build-style = RELEASE
2013-04-10 20:04:42.206 [5612:16f0]: <Recovery Mode Device 00946370>: operation 44 progress -1
2013-04-10 20:04:42.206 [5612:16f0]: requested restore behavior: Erase
2013-04-10 20:04:42.206 [5612:16f0]: requested variant: Erase
2013-04-10 20:04:42.210 [5612:16f0]: amai: _AMAuthInstallBundleCreateServerRequestDictionary: withApTicket is False
2013-04-10 20:04:42.210 [5612:16f0]: amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "RestoreLogo"
2013-04-10 20:04:42.210 [5612:16f0]: amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "RestoreDeviceTree"
2013-04-10 20:04:42.210 [5612:16f0]: amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry "RestoreKernelCache" has been previously personalized; skipping it
2013-04-10 20:04:42.211 [5612:16f0]: amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry "RestoreRamDisk" has been previously personalized; skipping it
2013-04-10 20:04:42.211 [5612:16f0]: amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry "iBEC" has been previously personalized; skipping it
2013-04-10 20:04:42.211 [5612:16f0]: amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry "iBSS" has been previously personalized; skipping it
2013-04-10 20:04:42.211 [5612:16f0]: amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry "KernelCache" has been previously personalized; skipping it
2013-04-10 20:04:42.211 [5612:16f0]: amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "BatteryLow1"
2013-04-10 20:04:42.211 [5612:16f0]: amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "BatteryLow0"
2013-04-10 20:04:42.211 [5612:16f0]: amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry "LLB" has been previously personalized; skipping it
2013-04-10 20:04:42.211 [5612:16f0]: amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "iBoot"
2013-04-10 20:04:42.211 [5612:16f0]: amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "DeviceTree"
2013-04-10 20:04:42.211 [5612:16f0]: amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "BatteryCharging1"
2013-04-10 20:04:42.211 [5612:16f0]: amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "BatteryCharging"
2013-04-10 20:04:42.211 [5612:16f0]: amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "AppleLogo"
2013-04-10 20:04:42.211 [5612:16f0]: amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "BatteryPlugin"
2013-04-10 20:04:42.211 [5612:16f0]: amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "BatteryFull"
2013-04-10 20:04:42.211 [5612:16f0]: amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "BatteryCharging0"
2013-04-10 20:04:42.211 [5612:16f0]: amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "RecoveryMode"
2013-04-10 20:04:42.211 [5612:16f0]: amai: _AMAuthInstallBundleCreateServerRequestDictionary: nothing to be done
2013-04-10 20:04:42.213 [5612:16f0]: unable to open device_map.txt: No such file or directory
2013-04-10 20:04:42.214 [5612:16f0]: found device map entry for 0x00008930 0x00000000. boardConfig=n90ap platform=s5l8930x
2013-04-10 20:04:42.215 [5612:16f0]: _AMRestoreCreateCFDataWithContentsOfFile: CreateFileA failed: 2
2013-04-10 20:04:42.215 [5612:16f0]: unable to create data from file: 17
2013-04-10 20:04:42.215 [5612:16f0]: device_map.plist file not found
2013-04-10 20:04:42.215 [5612:16f0]: AMDeviceIoControl: GetOverlappedResult failed
2013-04-10 20:04:42.215 [5612:16f0]: AMDeviceIoControl: pipe stall
2013-04-10 20:04:42.216 [5612:16f0]: USBControlTransfer: error 31, usbd status c0000004
2013-04-10 20:04:42.216 [5612:16f0]: command device request for 'getenv radio-error' failed: 2008
2013-04-10 20:04:42.216 [5612:16f0]: radio-error not set
2013-04-10 20:04:42.216 [5612:16f0]: unable to open device_map.txt: No such file or directory
2013-04-10 20:04:42.217 [5612:16f0]: <Recovery Mode Device 00946370>: production fused device
2013-04-10 20:04:42.218 [5612:16f0]: interface has 1 endpoints, file pipe = 1
2013-04-10 20:04:42.218 [5612:16f0]: <Recovery Mode Device 00946370>: operation 4 progress -1
2013-04-10 20:04:42.226 [5612:16f0]: <Recovery Mode Device 00946370>: operation 42 progress -1
2013-04-10 20:04:43.261 [5612:16f0]: <Recovery Mode Device 00946370>: operation 5 progress -1
2013-04-10 20:04:43.630 [5612:16f0]: unable to open device_map.txt: No such file or directory
2013-04-10 20:04:43.631 [5612:16f0]: found device map entry for 0x00008930 0x00000000. boardConfig=n90ap platform=s5l8930x
2013-04-10 20:04:43.631 [5612:16f0]: _AMRestoreCreateCFDataWithContentsOfFile: CreateFileA failed: 2
2013-04-10 20:04:43.632 [5612:16f0]: unable to create data from file: 17
2013-04-10 20:04:43.632 [5612:16f0]: device_map.plist file not found
2013-04-10 20:04:43.632 [5612:16f0]: AMDeviceIoControl: GetOverlappedResult failed
2013-04-10 20:04:43.632 [5612:16f0]: AMDeviceIoControl: pipe stall
2013-04-10 20:04:43.632 [5612:16f0]: USBControlTransfer: error 31, usbd status c0000004
2013-04-10 20:04:43.632 [5612:16f0]: command device request for 'getenv ramdisk-delay' failed: 2008
2013-04-10 20:04:45.668 [5612:16f0]: <Recovery Mode Device 00946370>: operation 6 progress -1
2013-04-10 20:04:46.679 [5612:16f0]: <Recovery Mode Device 00946370>: operation 7 progress -1
2013-04-10 20:04:46.955 [5612:16f0]: <Recovery Mode Device 00946370>: operation 8 progress -1
2013-04-10 20:04:46.956 [5612:16f0]: unable to open device_map.txt: No such file or directory
2013-04-10 20:04:46.957 [5612:16f0]: found device map entry for 0x00008930 0x00000000. boardConfig=n90ap platform=s5l8930x
2013-04-10 20:04:46.957 [5612:16f0]: _AMRestoreCreateCFDataWithContentsOfFile: CreateFileA failed: 2
2013-04-10 20:04:46.957 [5612:16f0]: unable to create data from file: 17
2013-04-10 20:04:46.957 [5612:16f0]: device_map.plist file not found
2013-04-10 20:04:46.958 [5612:16f0]: <Recovery Mode Device 00946370>: operation 9 progress -1
2013-04-10 20:04:46.958 [5612:16f0]: <Recovery Mode Device 00946370>: Recovery mode succeeded
2013-04-10 20:04:49.068 [5612:c1c]: WinAMRestore::OnInterfaceRemoval: \\?\USB#VID_05AC&PID_1281#{ED82A167-D61A-4AF6-9AB6-11E52236C576}\IB0000#b187d9b d
2013-04-10 20:04:49.070 [5612:c1c]: WinAMRestore::ProcessDevNodesChanges: device: 0x05c069c0, notify: 2, connected: 0
2013-04-10 20:04:49.070 [5612:c1c]: WinAMRestore::ProcessDevNodesChanges: device: 0x05a4e728, notify: 2, connected: 0
2013-04-10 20:04:49.070 [5612:c1c]: WinAMRestore::ProcessDevNodesChanges: device: 0x05a4ec28, notify: 2, connected: 1
2013-04-10 20:04:49.070 [5612:c1c]: AppleDevice::NotifyDisconnect: IBOOT, IBOOT \\?\USB#VID_05AC&PID_1281#{ED82A167-D61A-4AF6-9AB6-11E52236C576}\IB0000#b187d9b d, inst: 0x5a4ec28
2013-04-10 20:04:49.070 [5612:c1c]: IBOOT, DFU \\?\USB#VID_05AC&PID_1281#{B8085869-FEB9-404B-8CB1-1E5C14FA8C54}\0000#b187d9bd, inst: 0x5a4ec28
2013-04-10 20:04:49.071 [5612:c1c]: _AMRecoveryModeDeviceFinalize: 00946370
2013-04-10 20:04:49.113 [5612:c1c]: WinAMRestore::OnInterfaceRemoval: \\?\USB#VID_05AC&PID_1281#{B8085869-FEB9-404B-8CB1-1E5C14FA8C54}\0000#b187d9bd
2013-04-10 20:04:49.114 [5612:c1c]: WinAMRestore::ProcessDevNodesChanges: device: 0x05c069c0, notify: 2, connected: 0
2013-04-10 20:04:49.114 [5612:c1c]: WinAMRestore::ProcessDevNodesChanges: device: 0x05a4e728, notify: 2, connected: 0
2013-04-10 20:04:49.114 [5612:c1c]: WinAMRestore::ProcessDevNodesChanges: device: 0x05a4ec28, notify: 2, connected: 0
2013-04-10 20:04:53.659 [5612:3a4]: received kAMDeviceAttached action, device id CDF8C5CBA494A145 (05B0EB48), AFC error 0XE8000028
2013-04-10 20:04:53.659 [5612:3a4]: iTunes: Restore-mode device appeared, device 05B0EB48
2013-04-10 20:04:53.659 [5612:3a4]: iTunes: Creating restore mode device with usbMuxDeviceID 0X1
2013-04-10 20:04:53.659 [5612:3a4]: <Restore Device 05B0EBB0>: operation 3 progress -1
2013-04-10 20:04:53.663 [5612:3a4]: <Restore Device 05B0EBB0>: operation 4 progress -1
2013-04-10 20:04:53.666 [5612:3a4]: Supports value queries: 1
2013-04-10 20:04:53.749 [5612:16c0]: amai: AMAuthInstallBasebandPersonalizationRequired: failed to get fusing status
2013-04-10 20:04:53.749 [5612:16c0]: requested restore behavior: Erase
2013-04-10 20:04:53.769 [5612:16c0]: Getting baseband firmware from variant: Erase
2013-04-10 20:04:53.769 [5612:16c0]: _AMRestoreModeDeviceConfigureAuthInstall: setting customBbfwPath
2013-04-10 20:04:53.770 [5612:16c0]: <Restore Device 05B0EBB0>: operation 44 progress -1
2013-04-10 20:04:53.770 [5612:16c0]: requested restore behavior: Erase
2013-04-10 20:04:53.770 [5612:16c0]: requested variant: Erase
2013-04-10 20:04:53.770 [5612:16c0]: custom baseband firmware specified
2013-04-10 20:04:53.770 [5612:16c0]: amai: AMAuthInstallBundleOverrideEntry: overriding entry: BasebandFirmware
2013-04-10 20:04:53.772 [5612:16c0]: amai: _AMAuthInstallBundleCreateServerRequestDictionary: withApTicket is False
2013-04-10 20:04:53.772 [5612:16c0]: amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "RestoreLogo"
2013-04-10 20:04:53.772 [5612:16c0]: amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "RestoreDeviceTree"
2013-04-10 20:04:53.772 [5612:16c0]: amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry "RestoreKernelCache" has been previously personalized; skipping it
2013-04-10 20:04:53.772 [5612:16c0]: amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry "RestoreRamDisk" has been previously personalized; skipping it
2013-04-10 20:04:53.772 [5612:16c0]: amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry "iBEC" has been previously personalized; skipping it
2013-04-10 20:04:53.772 [5612:16c0]: amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry "iBSS" has been previously personalized; skipping it
2013-04-10 20:04:53.773 [5612:16c0]: amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry "KernelCache" has been previously personalized; skipping it
2013-04-10 20:04:53.773 [5612:16c0]: amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "BatteryLow1"
2013-04-10 20:04:53.773 [5612:16c0]: amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "BatteryLow0"
2013-04-10 20:04:53.773 [5612:16c0]: amai: _AMAuthInstallBundleCreateServerRequestDictionary: entry "LLB" has been previously personalized; skipping it
2013-04-10 20:04:53.773 [5612:16c0]: amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "iBoot"
2013-04-10 20:04:53.773 [5612:16c0]: amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "DeviceTree"
2013-04-10 20:04:53.773 [5612:16c0]: amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "BatteryCharging1"
2013-04-10 20:04:53.773 [5612:16c0]: amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "BatteryCharging"
2013-04-10 20:04:53.773 [5612:16c0]: amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "AppleLogo"
2013-04-10 20:04:53.773 [5612:16c0]: amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "BatteryPlugin"
2013-04-10 20:04:53.773 [5612:16c0]: amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "BatteryFull"
2013-04-10 20:04:53.773 [5612:16c0]: amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "BatteryCharging0"
2013-04-10 20:04:53.773 [5612:16c0]: amai: _AMAuthInstallBundleCreateServerRequestDictionary: not personalizing "RecoveryMode"
2013-04-10 20:04:53.773 [5612:16c0]: amai: _AMAuthInstallBundleCreateServerRequestDictionary: nothing to be done
2013-04-10 20:04:53.774 [5612:16c0]: fixed TcpWindowSize (64380) can cause restore failure if too large
2013-04-10 20:04:53.780 [5612:16c0]: device did not return saved USB log
2013-04-10 20:04:53.780 [5612:16c0]: device did not return saved panic log
2013-04-10 20:04:53.786 [5612:16c0]: connected to service com.apple.mobile.restored
2013-04-10 20:04:53.786 [5612:16c0]: using protocol version 12
2013-04-10 20:04:53.794 [5612:16c0]: unable to open device_map.txt: No such file or directory
2013-04-10 20:04:53.794 [5612:16c0]: board config = n90ap
2013-04-10 20:04:53.800 [5612:16c0]: no value returned for BootArgs
2013-04-10 20:04:53.800 [5612:16c0]: _copyDeviceProperty() failed for restore bootargs
2013-04-10 20:04:53.807 [5612:16c0]: no value returned for MarketingPartNumber
2013-04-10 20:04:53.807 [5612:16c0]: _copyDeviceProperty() failed for mpn
2013-04-10 20:04:53.813 [5612:16c0]: value query for 'HardwareModel' returned 'N90AP'
2013-04-10 20:04:53.828 [5612:16c0]: <Restore Device 05B0EBB0>: operation 28 progress -1See this:
iOS: Unable to update or restore
If the steps in the article don't help, this phone either has hardware damage or was previosly hacked/jailbroken and is DOA. -
IPhone4 Battery life: The report you all have been waiting for!!!
Hello fellow iPhoners,
I'm a proud owner of an iPhone4 who have been getting sporadic battery performance for a little while. One day I can get 5 to 6 hours of usage while another the phone can barely make it past 4 hours doing the same things.
Therefore, I decided to start my own observation and document my findings regarding why my iPhone 4 can give me good battery on some days and terrible in others.
Intro:
Now I'm sure all of you have read all the typical battery saving tips such as turn off fetch, dont game too much blah blah blah. Well, I wanted to know what is the real world impact do these things really do on battery and how much better is the battery life with them off.
The following are always ON for me: Wifi, notifications (no push or fetch), edge (I never use 3g - too slow anyway).
Screen brightness is set in the middle so IOS decides when to raise or lower it. Actually IOS seems to only be able to brighten the screen if you say, walk from a dark to well lit room. The reverse seems not possible. You must put your phone to sleep and wake it in order for the display to dims.
Keep in mind I typically get between 6 to 7 hours of medium usage. But I set out to find why do I get
less than 5 hours in some cases.
Observations:
1. After placing iphone in charge at night, went to sleep, woke up in morning to find that the iphone was at 65% and losing power while still PLUGGED IN. I had to unplug and replug.
2. Sometimes iphone will get real hot while I'm not using it. Even after a reboot, it would continue to remain hot and drains battery.
3. Observation 2 (above) has only happen 2 times unexpectedly.
Answers to Observations:
1. I no longer plug my iPhone on certain outlets to charge. I have come to realize that all outlets aren't equal and while some of them will charge up the iphone very fast, it tends to lose that power very fast also which would contribute to the days where I barely get 4 hours out of it. Thus I recommend plugging your phone into a wall outlet and not via an extended outlet. Also using USB to power it up via my PC doesn't provide the best battery life either.
2. When my iPhone4 gets hot on standby, I know the processor is still running(very fast) which to me means an app is still running even though IOS4 is SUPPOSED to only SUSPEND apps in the background. However, we dont know and assume apps that have not been updated to OS4 simply get closed when we press the home button. Well, I have never updated my AP Mobile app (because the latest update *****) and I feel like it may be one of the culprits that render my phone a hand warmer. However, I also feel like Call Of Duty: Zombies might be another culprit as I always have used one of these apps when the phone keeps getting hot.
Now of course I won't blame these apps solely as I also feel IOS4 itself IS buggy and may be the bigger culprit. Sometimes X'ing out everything in the background tray solved the hotness problem, sometimes it doesn't and the phone will keep on dropping in battery until it dies.
Now I always wondered how did apple arrive at their claim of "up to 14 hours talk time on 2g" and "up to 10 hours of internet use on wifi" when I can barely get within that vicinity. While I have been able to figure out how I potentially could get 14 hours of talk time on edge, I still can't see how 10 hours of internet is possible on wifi because... wait for it... WIFI as I have just discovered is one of the biggest slow battery drainers.
It's true. According to my observations, with Wifi TURNED OFF my iPhone will drop 1% of battery every 7 to 8 minutes of light usage such as reading a book via iBooks or reading jokes on iPhunny. If you do the math, 7.5 x 100 = 750 /60 = 12.5 hours of light usage. Remember this is with wifi off and on edge only.
Now with WIFI ON and about 2 notifications for apps, doing the same exact thing, I get between 4 to 5 minutes per 1% of battery. One may say, that's not a huge difference, but it is sizable when we do the math, 4.5 x 100 = 450 /60 = 7.5 hours of light usage. This falls in line with my usual 5 to 6 hours since I tend to play a lot of games as well, which required more battery usage than say just reading a book.
This also hold true for when the phone is on standby which drops 1% every 40 to 60 minutes with wifi OFF. With wifi ON, it was about half the time.
When I turned off notifications completely with wifi still ON, I failed to notice any significant improvements to battery life as a whole.
QUESTION:
Since I'm not an apple engineer, I was wondering if any body knows an answer to this: I'm aware that the iphone - when wifi is enabled- will keep on scanning all the time. However, I was under the impression that once it FINDS AND CONNECTS to a network, that it should STOP scanning. I mean, why should it keep on scanning if it's connected to a network already?
But, I feel like the reason why battery life is so different with wifi ON is because it keeps on scanning no matter what. So there's always this tiny process running all the time.
Conclusion:
Despite over blown antenna issues, iPhone4 is a great device with great battery life to boot. The question is whether you are fine with say 6 to 7 hours of usage? If you would like to get more, remember to use a good outlet, turn off 3g if you dont need the data speed since phone calls tend to drop less on edge anyway, and turn off wifi when you dont really need it. Those remedies can add at least 2 extra hours of usage for you.
DISCLAIMER: Please all the above is only my opinion based on my own observation of my own iPhone4. I'm no professional techie or engineer. So no flaming or raging.
Thanks!I couldn't do either here is why.
1. I have a back drop and the un-cropped image would look horrible and unprofessional
2. I have 400 kids and to crop and export each size differently would would be a confusing nightmare for everyone not to mention the time involved as I have pretty 8 difference sizes in each package.
It should be able to be done like life touch offers these kinds of packages all the time -
Waiting for Task Completion from multiple users
iam using Weblogic8.1 Integration BPM to design a worklist application. I need
to create a number of Tasks(number know only at runtime), assign to users and
wait for the completion of each of these task. I've tried using the Task Control
factory to accomplish this. But iam not able to hold the process instance execution
till each of these task is completed. The control gets released from the TaskControlFactory_onTaskCompleted
as soon as one of the above created task is completed.
Pls. let me know if there is a way to achieve this.
Regards
Raja V.Try to put the onTaskCompleted Control Receive in a loop which counts how
many of these
callbacks have already arrived, and the loop exit condition would be that
the count is equal
to the number of the created tasks.
Regards,
Robert Varga
"Raja V" <[email protected]> wrote in message
news:3f423f82$[email protected]..
>
iam using Weblogic8.1 Integration BPM to design a worklist application. Ineed
to create a number of Tasks(number know only at runtime), assign to usersand
wait for the completion of each of these task. I've tried using the TaskControl
factory to accomplish this. But iam not able to hold the process instanceexecution
till each of these task is completed. The control gets released from theTaskControlFactory_onTaskCompleted
as soon as one of the above created task is completed.
Pls. let me know if there is a way to achieve this.
Regards
Raja V. -
For how long do I have to wait for the delivery of my iPad mini 2?
I bought an Ipad mini 2 16Gb from the refurb 20minutes after it got available on the store, and I thought it would arrive pretty fast with the express delivery, It's been two weeks now and I am still waiting for my iPad, I bought it the 12th of november and that day I got an email that said that the delivery was expected for the 14th of november, the status of the order on apple website is still on "In stock, Ready for shipping" and it still says "delivery estimated for the 14th of november" I called apple and they said they don't know anything more than I do, on their screen they see the same thing as me (they are useless to make a long story short) I regularly buy from apple usually it takes 3 days maximum. What is going on? can I at least get an updated estimate of the delivery date?
It may take a few hours or get caught in a spam filter. The quickest way to make a purchase in this case is to create a new Apple ID, but neither iTunes Store credit nor previous purchases can be moved between them. In the case of applications, doing this may also complicate in-app purchases.
(97822) -
BPM Process Sleep / Wait for long duration - is it feasable in SAP PI?
Hi
We have a business requirement where based on a particular date in the future, we require a message we receive to "wait" until that date before it can bed processed (several weeks/months).
I understand that there is a "wait" step in CCBPM - has anybody had any experience with using this step for "long running processes".
When using this, is SAP PI intelligent enough to "sleep" and free resources for this process until the date arrives in the wait step?
What happens with other messages hitting the BPM and there is a process on a wait step? Can queing be setup that subsequent messages that are not on a wait step be processed ahead of the BPM sitting on a wait step?
Are there any other better solutions in SAP PI instead of using BPM wait for a long running transaction (several weeks)?
Thanks in advance.Hi,
AFAIK it's an anti pattern to run a process over such a long time.
Here it's said that at should not longer run than a few days:
http://help.sap.com/saphelp_nw04s/helpdata/en/43/d92e428819da2ce10000000a1550b0/frameset.htm
But even a day is quite a long time.
All informations of the process must get stored and it's very memory consuming specially if you expext a lot process instances.
It would try to avoid this situation.
Regards
Patrick -
Where do I get MPN for iLife that came with my computer?
I purchased a MacBook about a year ago. I just now have occasion to use iPhoto. I'd like to register it in case there are updates. When I attempt to do so I am asked for the "market product number" [MPN]. The methods explained for locating the MPN on Apple's website -- e.g., opening the Apple System Profiler -- do not work for me.
How can I locate the MPN? Alternatively, do I need to register my copy of iLife? It's iLife 08 and was purchased late December of 08.
Thanks,
Eric WeirEric:
iPhoto is only available with the iLife suite of iApps, not by itself. As for iLife 10 no one knows what the schedule is. In the past it had been released at the time of the MacWorld Expo. Since Apple is not participating in the Expo any more we don't know if there will be a scheduled release or not.
Since the Expo is only a few weeks away I would at least wait until it's over before ordering iLife 09 if you are interested in ordering 09. Otherwise, start using 08 and get familiar with it. Then compare the differences between 08 and 09 to see if it's worth it for you to upgrade.
TIP: For insurance against the iPhoto database corruption that many users have experienced I recommend making a backup copy of the Library6.iPhoto (iPhoto.Library for iPhoto 5 and earlier versions) database file and keep it current. If problems crop up where iPhoto suddenly can't see any photos or thinks there are no photos in the library, replacing the working Library6.iPhoto file with the backup will often get the library back. By keeping it current I mean backup after each import and/or any serious editing or work on books, slideshows, calendars, cards, etc. That insures that if a problem pops up and you do need to replace the database file, you'll retain all those efforts. It doesn't take long to make the backup and it's good insurance.
I've created an Automator workflow application (requires Tiger or later), iPhoto dB File Backup, that will copy the selected Library6.iPhoto file from your iPhoto Library folder to the Pictures folder, replacing any previous version of it. There are versions that are compatible with iPhoto 5, 6, 7 and 8 libraries and Tiger and Leopard. Just put the application in the Dock and click on it whenever you want to backup the dB file. iPhoto does not have to be closed to run the application, just idle. You can download it at Toad's Cellar. Be sure to read the Read Me pdf file.
NOTE: The new rebuild option in iPhoto 09 (v. 8.0.2), Rebuild the iPhoto Library Database from automatic backup" makes this tip obsolete. -
Hello,
1) I am working on DAQ and I need some help to take decision in best way. I am using JKI state machine, which having one case for DAQ and another cases for controlling the serial device. I need to swich the cases always until my Serial device fixed. I.e.. I need the Acquire the data may be 8 or 9 times for each serial device when the program is running. The cases in the state machine also defined in such manner for switching together. I am using USB 6008 and with rate of 5K and 500 samples to read and its a continuous acquisition.
2) Here comes problem, In DAQ case, I acquire the data and calculate the summation of arrived data. Here comes jitter and I need to be careful to remove this movement in the summation value. Of course, this jitter introduced because of my serial device. My plan is to make like this but so far I stop here with lots of confusion.
Especially in this case(DAQ case), I would like to wait for a second and I want to store the summation values occurred in this second into an array and after look for the maximum value occurred in that second. Well, in this period, DAQ should continue its Acquisition and should calculate the summation until it's get's the 5K samples in 1 Sec. After this I would probably continue my run to other cases.
I know that I have to attach my code here but it is big VI and you can find attachment of DAQ case.
I would appreciate someone's help here.
Attachments:
Array finding.vi 116 KBWelcome to Apple Discussions Marty
This is the most complained about bug in AppleWorks 6 - known as the "Recent Items bug." Take a look in the highlighted AppleWorks Frequently Asked Questions (FAQ) folder near the top of the entry of this forum for the User-Contributed Tips & Answers folder. In there are three articles dealing with Recent Items.
]Dale Gillard - AppleWorks slow? Spinning ball appears?
]Dale Gillard - Recent items not visible/updated
]Yvan Koenig - No more Recent Items
AppleWorks remembers every document ever opened. As this fills up, it slows down performance. This folder is located in HD/Users/username/Documents/AppleWorks User Data/Starting Points/Recent Items. Trash all of the aliases in this folder & restart AppleWorks. You should see an improvement.
Maybe you are looking for
-
I have a Send plan and also a Creative Cloud membership. It feels like paying twice for Adobe services, but maybe the CC-plan doesn't include Send?
-
Help needed: Download to excel without pop-up
Hi All, In a particular scenario, I require to trigger an action once a file have been successfully downloaded to EXCEL from Webdynpro UI. But in case of download functionilty, once the MS window pop-up for download comes up, the control is lost from
-
Calendar app crashes when going to march 2013
Does anyone else experience the same problem? I can recreate it on at least two iPads (the original iPad1 [iOS 5.1.1] and the latest Retina iPad [iOS 6.0.1]) While browsing the calendar in month view and going from febraury 2013 or april 2013 to marc
-
Macbook misses some key events for a few seconds
I have noticed that for last two months or so something strange happens to my Retina MBP. Once in a couple of days it stops responding to some key events. It is like it handles only one keypress out of 4-5. Nothing seems to be wrong with the keyboard
-
The number of leaf_blocks does not decrease after delete
hi All, this the example from Tom's book <<expert oracle database architecture>>, may anyone explain why the leaf_block oes not decrease to 523 after delete. db version is 10.2.0.3, SEGMENT SPACE MANAGEMENT MANUAL in the tablespace system sys@CS10G>