Pram and Main Battery relationship
AS a result of the self igniting battery problem I removed the main battery from my 15 month old Powerbook while waiting for the replacement battery to arrive.
After a few days the Powerbook would no longer have the time and date settings when initially powered up.
A check of the forums indicated a Pram battery failure, so I called Apple Care described the problem, explaining that the main battery had been removed to avoid any insurance liability re self ignition. The Applecare agent said - the Pram battery needed replacing, take it to a local Apple dealer/specialist and they would be able to replace it while I wait. I rang two repair shops and was told it would take about 10 days to fix as they did not have any PRAM bateries in stock.
Took the Powerbook in to the repair shop on Tuesday, I was telephoned to day, with the news that there was nothing wrong with the machine and that the Pram had discharged because of the removal of the main battery.
My questions are :
If the diagnosis is correct why did the Applecare agent tell me to get a new PRAM battery fitted?
Why did he tell me that it was a while you wait job when it appears that the PRAM battery is not kept in stock.
Oh and incidently on my IBM Thinkpad the Bios battery lasted for nearly 6 years with often the main battery removed to reduce the number of power cylcles of the battery before I had to easily replace it.
G4 Powerbook 15 inch Mac OS X (10.4.7)
More information
I collected my Powerbook from the service agent today.
I expected that Apple would re-imburse the repair shop for the time that they had spent checking out the computer, however Apple only pay for labour when parts are ordered.
So to net out
The repair shop spent time checking the machine at their expense
I spent time on the phone to Apple care, spent time backing up the hard disk and removing sensitive data, and driving 70 miles.
I hope that the qusetionaire I filled in in response to the Apple Care call will be carefully considered by Apple.
Similar Messages
-
180c PRAM Battery vs. Main Battery Workarounds??
Hello,
I'm trying to determine if there is ANY definitive information out there for a work-a-round for PRAM Battery failure, either on some emergency resuccitation (sp) or other power usage?
Approaching the question another way. IF, for example, one had a good fully charged Main Battery, is there NO internal software switching via the power manager circuits where that necessary portion of the machine can be "fed" the 3.0 volts.
On an emergency revival for data retrieval, I recently read in the duo world which is similiar (but 6.0 v feed) that they WOULD eventually come up. But one might have to KEEP doing the 45 sec to 1 minute power switch hold down time after time to "shock" it out of sleep? Implying to me the possibility of that method charging up a capacitor somewhere which would charge up enough to carry the moment? Is that 100% valid? Or would that be only a high probability if the machine has a PRAM battery which has degenerated to JUST AT the threshold of its PROM? circuitry?
My objective is for data retrieval from long term stored units at the moment, vs hard drive removal and transfer to something else. Thanks
LowellDenis,
Thank you for the detailed response. There were many helpful items in your reply. We DID miraculously bring back the one 180c that was data Critical over and retrieve valuable data that had been "lost" for a year.
I have worked with these 180c's for 8-10 years now, and in this particular arena of have never been able to quantatively define functions and methods. Even this critical Data retrieval was inconclusive. Hence if you'd read thru this and make any comments I'd appreciate it. I've also listed a few more technical questions, numbered, if you have time to respond. Additionally I've written my experience detailed for others.
First, your input on full "terminal voltage" was very helpful and new input for me. Second, I never knew or thought about the "backup" battery being designed for the temporary coverage you mentioned. (I'd mentally thought "clock" and critical RAM only)
QUESTION 1
IF a backup battery is weak to the point where it will not HOLD the clock time, can these units "draw" from the main battery in storage? Also, if one has a main battery of unknown condition, is it better to store the PB without the main battery? Further, along those lines, if convenient to do so, would it be best to store with main battery (weak one) OUT, but STILL with AC power to the unit? Or, Per your comment about terminal voltage, do I assume in that (no main battery) configuration, the backup battery wouldn't be maintained anyway?
Back to the one you helped me with. That 180c had slowly failed during daily usage a year ago at at critical time where I couldn't do much. It had a "fair" main battery. It's primary symptom was that if I had a lock-up and had to turn it off, it absolutely would not come back up unless I went thru one or more of the Power Manager Reset procedures. Under a tight schedule I had to use it that way for almost a month, leaving it asleep overnight but always on AC power.
Finally, it reached the point where NOTHING would revive it. I tried probably 25-50 different tries and several Power Manager ways over several days, always leaving it on AC power in between (except for the Power Manager reset procedures). Nothing.
Then, with your note on terminal voltage, (after the unit had been setting for a year, dead, with a main battery in it, but unplugged from AC, I did the following:
1. Plugged to AC for 24 hours.
2. Read your note, and Switched to a battery that had been in another 180c that had been stored for the same length of time, but had faithfully come up.
3. Left THAT battery in it on AC for 12 hours or more.
4. First try - Held back Power ON button DOWN for a full 120 seconds. Also held Shift down. Let up on Power button first, (nothing). Then let up on Shift key. Got light on the screen, and then the bad chimes. (4 up, 4 down).
5. Unplugged from AC to move from storage to table. Plugged back to AC in less than a minute. Held Power ON button DOWN for 60 seconds as well as Shift KEY. Let up on Power button first, then Shift, and Unbelieveably, got a smiley face. That stayed for maybe 5-10 seconds, then there was a screen blip and the smiley face came right back, AND the extensions began loading. (It was JUST as tho I'd hit the PULL DOWN - RESET. Also, of course, I HAD expected it to start with Extensions OFF, tho it never gave me that prompt option)
At this point, the machine was completely alive. We worked on it slowly for 3 days, using floppys, then finally file sharing to transfer everything except the few items that would not copy from "being in use"
We gained enough confidence in it to put it to sleep several times. It always woke up fine, and we kept working till done.
6. After 3 days, and data retrieved, we shut it down. WE tried it normally after about 3 minutes. It came right back up. Then we shut it down for 2 hours. It would NOT come up, and has been DEAD ever since. I've tried EXACTLY the same procedures as I did when it "AWAKENED" for 3 days after a year. but I absolutely cannot get it back. I do have a PRAM battery on order, but I CAN'T believe the WAKE-UP can't be repeated. And I certainly can't believe it's any type of hardware failure?
Question 2
Per your "terminal voltage" for the main battery? Are you saying a maximum voltage that THAT battery can achieve after hours of charging, or is your terminal voltage term the same as my "Threshold Voltage"? IF so, are you saying that for a back-up battery to begin charging, a main battery must reach, say 5 volts, out of 7.5? And if that battery is old and would only reach 3 volts, then the PRAM battery can't charge up enough to help bring up the machine?
Question 3 (final one)
Per question 2 above, if one has "iffy" main batteries in a stored unit, is it better to plug the unit up for days with the main battery OUT when trying to revive a stored unit?
In closing, this is not just a hobby posting, I use, plan to use, and need to use THESE machines for my work (A lot of Claris CAD drawings) for which I've never been able to do nearly as well with trackpad vs the track ball (carpal tunnel also). So any REPEATABLE procedure in this arena would help until I can get my several units re-furbished with NEW PRAM batteries. And certainly having a technical background, I'd really like to KNOW quantatively how those circuits work enough to deal with them.
Thank you all.
Lowell
------Denis - your posting below --------
Lowell
The backup battery of portables is rechargeable, as
opposed to the chuckability of desktop/tower
machines, because its designed function is not solely
to maintain PRAM settings.
If portables are off the mains supply, their backup
batteries are intended to have power enough, as the
main batteries approach a critical level of
exhaustion, to allow you to 1) swap in a charged main
battery, or 2) reattach a powered AC adapter, and to
maintain the contents of RAM the while. If neither
1) nor 2) is possible, they should also be able to
maintain the contents of RAM for up to 24 hours as
you licketty-split across the continent to a
sufficient source of main power. Augmented backups
of 50mAh capacity were available (instead of the
standard 30mAh). The significance of those figures
is apparent if you compare it with the new capacity
of 1730mAh in a PB500 main battery.
The backups were also rugged. I recently revived one
in a PB160 that had, by best available estimate, not
been in service for 13 years. It was also
characteristic of them that they did not recharge
before the main battery reached full terminal
voltage. (Note: not 'full capacity'.) A main
battery can approach full terminal voltage without
having much capacity to store charge, as most owners
of older PBs know to their sorrow. So the backups
are most easily restored by leaving the powered AC
adapter permanently attached to the PB, at least for
several days.
Apple IIe; 68K: 11DT +
4PB; PPC: 5DT + 3PB; G3: 6DT System
6.0.8 to OS 10.4.x -
Ultrabay battery won't switch to main battery and results in sudden shutdown.
Hi,
I just changed my windows 7 32 bit to 64 but version. The power manager version is 3.66 and driver version 1.64, bios version is LENOVO 7UET93WW (3.23 , 12/15/2011). The ultrabay battery drains to zero and won't switch to main battery, which leads to a sudden shutdown without any warning. In windows 7 32 bit version, I don't have such problem. It's annoying. My computer is T400 7147 CTO.
Thanks!
chicagot400Hi I have the exact same problem. I have a T400 2764 CTO. Changes I have recently made (past 2 weeks): I upgraded to Windows 7 64, added a PC Card media reader, added an express card USB 3.0, a Samsung 256 GB SSD and the Ultra Bay Battery. Everything was working great... both batteries recognized, ran Lenovo Update... Have everything...
Well the battery meter recognizes both batteries (a 4-cell and a 3-cell), combines their life, but it drains the 3-cell first to ZERO... and isn't bright enough to figure out how to switch before abruptly dropping power to the system.
Hopefully like the ATI switchable graphics that had bugs for ages this battery issue eventually gets fixed. Let me know if you figure out any solution. AND LENOVO, if you are reading, try and set it up so that the 2 battery usage maximizes the life of both batteries with whatever controller you put together.
Thanks.
- Tom -
X1 (1286) main battery good condition at 1% and not charging
Hello,
I recently noticed that the main battery is no longer charging. It is now at 1% and not charging when AC plugged in (screenshots of powermanager attached). Power Mgr says it is in good condition. Since I usually have the slice battery attached on the road or AC plugged in at home, it has always been in Optmize for Health mode.
The battery gauge reset procedure was performed and hasn't helped.
I've run the battery firmware update utility and it has stated that battery firmware is up to date.
And as always the case, 1yr warranty expired 3weeks ago
I'll try updating BIOS (1.66) to latest, which I believe is 1.69, and post back if any success.
Any clues please? Thanking you in advance.
Link to image 1
Link to image 2
Details from msinfo32:
OS Name Microsoft Windows 7 Professional N
Version 6.1.7601 Service Pack 1 Build 7601
OS Manufacturer Microsoft Corporation
System Name THINKX1
System Manufacturer LENOVO
System Model 1286CTO
System Type x64-based PC
Processor Intel(R) Core(TM) i7-2640M CPU @ 2.80GHz, 2801 Mhz, 2 Core(s), 4 Logical Processor(s)
BIOS Version/Date LENOVO 8MET66WW (1.66 ), 26/06/2012
SMBIOS Version 2.6
Windows Directory C:\Windows
System Directory C:\Windows\system32
Boot Device \Device\HarddiskVolume1
Locale Australia
Hardware Abstraction Layer Version = "6.1.7601.17514"
Time Zone AUS Eastern Standard Time
Installed Physical Memory (RAM) 8.00 GB
Total Physical Memory 7.89 GB
Available Physical Memory 5.07 GB
Total Virtual Memory 15.8 GB
Available Virtual Memory 12.8 GB
Page File Space 7.89 GB
Page File C:\pagefile.sys
Moderator note: images totalling more than 50k converted to links per forum rules: Lenovo Community Participation RulesThanks for responding Jin and helping out.
Unfortunately updating bios and power manager hasn't resolved this. The new version of power manager 6.54 dispays same battery details.
Furthermore, i am now noticing that the slice battery charges to only 80% despite setting charge mode to fully charge. Could be experiencing this problem (x1 slice battery won't pass 80% unless internal battery is 100%) too, unfortunately no answers to that post.
In the process to updating drivers via LSC but not holding my breath -
Without main battery, CMOS checksum invalid.Doesn't keep time and BIOS settings. Backup batt is OK.
Good morning all,some months ago my dv6-6159sl laptop started to have this problem: WITHOUT MAIN BATTERY (using as desktop replacement with AC adapter only, unplugging from wall outlet when I don't use it) immediatly after power on button pressed, I get black screen error" CMOS Checksum is invalid . CMOS reset (502) . " and it restarts with all BIOS settings reset and time reset at 00:00:00 year 2010... The problem appears randomly: for days I don't get it, then I get it once, twice...then everything OK for one, two, many days...and again shows up...and so on... NOTE THAT BACKUP BATTERY CR2032 HAS BEEN REPLACED TWICE (for being sure) AND IS BRAND NEW, AND IS OK: A VOLTMETER SAYS 3,03 V . Tried to update BIOS to last F1.B , tried to revert back to F1.A and previous version (that is: I tried every single available BIOS on support page...)... No luck...Tried to recover BIOS with this procedure: http://support.hp.com/us-en/document/c04126730 ... nothing changed...Tried to recover whole system...Nothing fixed... Notes: hardware hasn't changed , HDD and RAM are OK (tests done). What to do now? Call for repair? Thanks.
Hello , Welcome to the HP Support Forums! It is a great place to find the help you need, both from other users, HP experts and other support personnel. I read your post about the BIOS, and wanted to assist you! Here are a few things you can try. Start with a Hard Reset. Then try using the HP Support Assistant to install any necessary drivers. Check the Windows Update as well. If you are having trouble finding or installing updates, then you can use this site to help: Open the Windows Update troubleshooter
You can always perform a System Recovery to put the notebook back to its factory settings. Also, please review the following document, as it may help to resolve the issue for you: HP PCs - HP BIOS Application Selected Is Corrupt or Missing If you are still having trouble, or would like to contact HP Phone Support, you can do so with the following link: http://www.hp.com/contacthp If you live outside the US/Canada, please click the link below to get the contact information for your region.
http://www8.hp.com/us/en/contact-hp/ww-phone-assist.html Please let me know if this information was helpful by clicking the thumbs up below.
Have a great day! -
Equium L10: Issue with main battery and RTC battery
Hi
I have the Toshiba Equium L10 and it is around 14 months old and I am having problems with the battery pack and how long it lasts after a full charge. I am also having problems with the RTC battery and an ERROR 0271: Check date and time settings message when I turn on the notebook.
With regard to the battery pack, I can fully charge it up in around 3 hours but when I start to use it, it only seems to last around one and a half hours or so and it then needs to be charged again. I may have it on for around 40 minutes or so and then turn it off and come back to it later or in a day(s) or so. How long should I expect from a fully charged battery?
Regarding the RTC batttery, this is really becoming a pain and I have only started getting the ERROR 0271 message at boot time, over the last few weeks or so. I can fully charge the battery pack up and then leave it for a couple of days, but when I turn it on, I get the ERROR 0271 message about the date and time settings being incorrect. Surely after a full charge, the RTC battery should last longer than a couple of days?
The user manual states that if the RTC battery is exhausted or getting low, you should charge the RTC battery for 24 hours, but in another part of the manual it states between 24 and 48 hours, but how can you charge it for that long when the sections regarding the charging of the battery pack state that after charging the battery pack you should disconnect the AC adaptor because leaving it connected will shorten the life of the battery pack. So how can we charge the RTC battery for 24 to 48 hours if we are not supposed to leave the AC adaptor connected after the battery pack is charged - which is around three hours. Any suggestions regarding these problems, would be appreciated.
By the way we all know it's easy to change the RTC/CMOS battery in your desktop base unit, but how easy is it to change it in a Toshiba L10 Equium?
Regards
Brave0Hi Brave0,
The normal recommendation for the CMOS (RTC) battery is to leave the notebook connected to the AC adapter for at leat 12 hours once the main battery is fully charged. The charging circuitry will divert the charge current to the RTC battery automatically and no current will be passed to your main battery.
The recommendation for not leaving the AC adapter plugged in when the main battery is fully charged is really only applicable to older notebooks which did not use Li-Ion batteries and consequently they had to be fully discharged before recharging so as to avoid any 'memory' effects in the battery.
With modern Li-Ion batteries it is quite safe to leave the battery in place when fully charged and still power the notebook from the AC adapter. The charging circuitry will not pass any charge to the battery if it is fully charged.
regards, -
Do Intel Macs have a PRAM? I need some kind off prof like an Apple doc. There seams to be a lot of people still using optioncommandR-P to fix issues but it doesn't seem to be actually reseting PRAM. Can some one tell me the difference between PRAM and NVRAM?
There are very few instances where resetting PRAM would be used for troubleshooting OS X. Note the reference in that article to another article about what OS X stores in PRAM. Most users posting on these forums about problems they have may try troubleshooting methods that are not relevant to their problem hence their conclusion that they don't work. Furthermore, just because resetting the PRAM doesn't solve a problem doesn't mean it doesn't work, but that the problem is more serious.
PRAM can on rare occasion become corrupted as a result of a radical system crash or runaway software problem. The main effects may be loss of information on the boot volume (only truly relevant in a multi-drive system,) video settings, and date and time. More important is whether the battery that maintains the PRAM is dead or dying which can cause the loss of PRAM information. In this case resetting the PRAM will only fix the problem until the computer is shut down after which the PRAM data will again be lost. Replace that battery within 3-5 years if your machine uses one. Some laptops have separate PRAM batteries while others rely exclusively on the main battery - hence the need to keep the main battery properly charged.
Resetting PRAM and repairing permissions are probably the 'best known' things to do if you have a problem. However, neither solves very many problems and rarely solve the kind of problems users frequently post. -
My Macbook Pro 2012 is painfully slow and the battery dies out really fast
I don't do a lot of downloading or installing on my computer, I basically just use it to browse the internet or use microsoft office. I haven't used much memory and all the specs on my computer seem fine. I recently went to the genius bar at an apple store and they ran a bunch of diagnostic tests but everything seemed to come up normal. I've backed up all my data and even restored my computer to factory settings. However, my computer still has the same problem. I was told I didn't have any viruses or malware/adware problems and the only reasonable solution the genius bar representative told me that it was tiem to upgrade. However, since these laptops cost over $1,500 new I don't think that's a reasonable solution for me. So if anyone could shine a light on what is possibly happening that would be awesome!
Thank you!Pre-Mavericks
Open Activity Monitor in the Utilities folder. Select All Processes from the Processes dropdown menu. Click twice on the CPU% column header to display in descending order. If you find a process using a large amount of CPU time (>=70,) then select the process and click on the Quit icon in the toolbar. Click on the Force Quit button to kill the process. See if that helps. Be sure to note the name of the runaway process so you can track down the cause of the problem.
Mavericks and later
Open Activity Monitor in the Utilities folder. Select All Processes from the View menu. Click on the CPU tab in the toolbar. Click twice on the CPU% column header to display in descending order. If you find a process using a large amount of CPU time (>=70,) then select the process and click on the Quit icon in the toolbar. Click on the Force Quit button to kill the process. See if that helps. Be sure to note the name of the runaway process so you can track down the cause of the problem.
Try these in order testing your system after each to see if it's back to normal:
1. a. Resetting your Mac's PRAM and NVRAM
b. Intel-based Macs: Resetting the System Management Controller (SMC)
2. Restart the computer in Safe Mode, then restart again, normally. If this doesn't help, then:
Boot to the Recovery HD: Restart the computer and after the chime press and hold down the COMMAND and R keys until the Utilities menu screen appears. Alternatively, restart the computer and after the chime press and hold down the OPTION key until the boot manager screen appears. Select the Recovery HD and click on the downward pointing arrow button.
3. Repair the Hard Drive and Permissions: Upon startup select Disk Utility from the Utilities menu. Repair the Hard Drive and Permissions as follows.
When the recovery menu appears select Disk Utility. After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list. In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive. If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported click on the Repair Permissions button. Wait until the operation completes, then quit DU and return to the main menu. Select Restart from the Apple menu.
4. Reinstall Yosemite: Reboot from the Recovery HD. Select Reinstall OS X from the Utilities menu, and click on the Continue button.
Note: You will need an active Internet connection. I suggest using Ethernet if possible
because it is three times faster than wireless.
5. Reinstall Yosemite from Scratch:
Be sure you backup your files to an external drive or second internal drive because the following procedure will remove everything from the hard drive.
How to Clean Install OS X Yosemite
Note: You will need an active Internet connection. I suggest using Ethernet if possible
because it is three times faster than wireless. -
No Bluetooth even after PRAM and PMU resets, fully updated Leopard
Subject should explain pretty much everything. I reset the PRAM and PMU to try to get my Bluetooth back (it doesn't even appear in System Profiler). Still nothing. Leopard with all updates. Any suggestions, before I take it in?
Unlike the previous PowerBook G4 (15-inch Double-Layer SD), the AirPort Extreme and Bluetooth 2.0 functions are on separate cards.
If Bluetooth system preferences does not show up under Hardware system preferences...
1. Check for software/firmware updates on the web.
2. Check the Bluetooth card flex cable. Make sure the cable is not damaged and fully seated.
3. Check the hard drive flex to main logic board.
4. Replace the Bluetooth card.
5. Replace the hard drive flex.
6. Replace the logic board.
-Bmer
Mac Owners Support Group - Join us @ MacOSG.com
Mac611 Mobile Mac Support - about.Mac611.com
iTunes:MacOSG Podcast | YouTube.MacOSG.com
An Apple User Group
Have an iPhone or iPod touch? Enter Mac611.com in Safari on it for 'mobile Mac support.' -
Hi, I hope you can help. I'm sure this is something really basic that I should be able to fix myself, but.................
I was working on a photo calendar on my macbook off the battery and the battery suddenly ran out. So it wasn't shut down properly. Now when I open i photo the coloured wheel just keeps spinning and I can't get into it. Everything else on the computer seems to work. I've done forced quit and restarted it a few times and also left it running.
Jane
Here is the error report:
Date/Time: 2011-11-19 11:29:02 +0000
OS Version: 10.5.8 (Build 9L31a)
Architecture: i386
Report Version: 4
Command: iPhoto
Path: /Applications/iPhoto.app/Contents/MacOS/iPhoto
Version: 8.1.2 (8.1.2)
Build Version: 8
Project Name: iPhotoProject
Source Version: 4240000
Parent: launchd [97]
PID: 158
Event: hang
Time: 7.46s
Steps: 49
Process: iPhoto [158]
Path: /Applications/iPhoto.app/Contents/MacOS/iPhoto
ADDRESS BINARY
00001000 /Applications/iPhoto.app/Contents/MacOS/iPhoto
00b31000 /System/Library/Frameworks/DiscRecording.framework/Versions/A/DiscRecording
00c65000 /System/Library/Frameworks/DiscRecordingUI.framework/Versions/A/DiscRecordingUI
00cae000 /System/Library/Frameworks/ExceptionHandling.framework/Versions/A/ExceptionHand ling
00cb7000 /Applications/iPhoto.app/Contents/MacOS/../Frameworks/UpgradeChecker.framework/ Versions/A/UpgradeChecker
00ccb000 /Applications/iPhoto.app/Contents/MacOS/../Frameworks/MobileMe.framework/Versio ns/A/MobileMe
00dc9000 /System/Library/Frameworks/Message.framework/Versions/B/Message
01179000 /Applications/iPhoto.app/Contents/MacOS/eOkaoCom.dylib
0117d000 /Applications/iPhoto.app/Contents/MacOS/eOkaoDt.dylib
011b6000 /Applications/iPhoto.app/Contents/MacOS/eOkaoFr.dylib
01320000 /Applications/iPhoto.app/Contents/MacOS/eOkaoPt.dylib
0134b000 /Applications/iPhoto.app/Contents/MacOS/../Frameworks/ProXTCore.framework/Versi ons/A/ProXTCore
013d6000 /System/Library/PrivateFrameworks/iLifeSlideshow.framework/Versions/A/iLifeSlid eshow
013da000 /Applications/iPhoto.app/Contents/MacOS/../NetServices/Frameworks/NetServices.f ramework/Versions/A/NetServices
014bc000 /System/Library/PrivateFrameworks/AppleAppSupport.framework/Versions/A/AppleApp Support
014c0000 /System/Library/Frameworks/LatentSemanticMapping.framework/Versions/A/LatentSem anticMapping
014f9000 /System/Library/PrivateFrameworks/iLifeSlideshow.framework/Versions/A/Framework s/iLifeSlideshowCore.framework/Versions/A/iLifeSlideshowCore
0153b000 /System/Library/PrivateFrameworks/iLifeSlideshow.framework/Versions/A/Framework s/iLifeSlideshowProducer.framework/Versions/A/iLifeSlideshowProducer
016be000 /System/Library/PrivateFrameworks/iLifeSlideshow.framework/Versions/A/Framework s/iLifeSlideshowRenderer.framework/Versions/A/iLifeSlideshowRenderer
0183b000 /System/Library/PrivateFrameworks/iLifeSlideshow.framework/Versions/A/Framework s/iLifeSlideshowExporter.framework/Versions/A/iLifeSlideshowExporter
0184f000 /System/Library/Frameworks/CoreAudioKit.framework/Versions/A/CoreAudioKit
01880000 /Applications/iPhoto.app/Contents/MacOS/../NetServices/Frameworks/BDControl.fra mework/Versions/A/BDControl
01894000 /Applications/iPhoto.app/Contents/MacOS/../NetServices/Frameworks/BDRuleEngine. framework/Versions/A/BDRuleEngine
01fe1000 /Applications/iPhoto.app/Contents/PlugIns/FlickrPublisher.publisher/Contents/Ma cOS/FlickrPublisher
1676f000 /Applications/iPhoto.app/Contents/PlugIns/FacebookPublisher.publisher/Contents/ MacOS/FacebookPublisher
16791000 /Applications/iPhoto.app/Contents/PlugIns/MobileMePublisher.publisher/Contents/ MacOS/MobileMePublisher
167da000 /Applications/iPhoto.app/Contents/PlugIns/RSSPublisher.publisher/Contents/MacOS /RSSPublisher
16a19000 /System/Library/CoreServices/RawCamera.bundle/Contents/MacOS/RawCamera
17161000 /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ATS.framework/Versions/A/Resources/ATSHI.dylib
17183000 /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ CoreGraphics.framework/Versions/A/Resources/libCGXCoreImage.A.dylib
19dd8000 /Applications/iPhoto.app/Contents/NetServices/Bundles/BookService.NetService/Co ntents/MacOS/BookService
19df2000 /System/Library/TextEncodings/Unicode Encodings.bundle/Contents/MacOS/Unicode Encodings
19df9000 /Applications/iPhoto.app/Contents/NetServices/Bundles/CalendarsService.NetServi ce/Contents/MacOS/CalendarsService
19e0d000 /Applications/iPhoto.app/Contents/NetServices/Bundles/CardsService.NetService/C ontents/MacOS/CardsService
19e21000 /Applications/iPhoto.app/Contents/NetServices/Bundles/PrintsService.NetService/ Contents/MacOS/PrintsService
19e52000 /Library/Application Support/iLifeMediaBrowser/Plug-Ins/iLMBAppDefPlugin.ilmbplugin/Contents/MacOS/i LMBAppDefPlugin
19e59000 /Library/Application Support/iLifeMediaBrowser/Plug-Ins/iLMBFolderPlugin.ilmbplugin/Contents/MacOS/i LMBFolderPlugin
19ea4000 /Library/Application Support/iLifeMediaBrowser/Plug-Ins/iLMBAperturePlugin.ilmbplugin/Contents/MacOS /iLMBAperturePlugin
19ef0000 /Library/Application Support/iLifeMediaBrowser/Plug-Ins/iLMBGarageBandPlugin.ilmbplugin/Contents/Mac OS/iLMBGarageBandPlugin
1a35e000 /Library/Application Support/iLifeMediaBrowser/Plug-Ins/iLMBiMoviePlugin.ilmbplugin/Contents/MacOS/i LMBiMoviePlugin
1a392000 /Library/Application Support/iLifeMediaBrowser/Plug-Ins/iLMBiPhoto8Plugin.ilmbplugin/Contents/MacOS/ iLMBiPhoto8Plugin
1a3ad000 /Library/Application Support/iLifeMediaBrowser/Plug-Ins/iLMBiPhotoPlugin.ilmbplugin/Contents/MacOS/i LMBiPhotoPlugin
1a3bd000 /Library/Application Support/iLifeMediaBrowser/Plug-Ins/iLMBiTunesPlugin.ilmbplugin/Contents/MacOS/i LMBiTunesPlugin
1a3cd000 /Library/Application Support/iLifeMediaBrowser/Plug-Ins/iLMBMoviesFolderPlugin.ilmbplugin/Contents/M acOS/iLMBMoviesFolderPlugin
1a3d6000 /Library/Application Support/iLifeMediaBrowser/Plug-Ins/iLMBPhotoBoothPlugin.ilmbplugin/Contents/Mac OS/iLMBPhotoBoothPlugin
1a901000 /System/Library/PrivateFrameworks/iTunesAccess.framework/iTunesAccess
ba900000 /System/Library/CoreServices/Encodings/libJapaneseConverter.dylib
Thread id: 753b8b8
User stack:
49 ??? [0x3172]
49 ??? [0x124b80]
49 _NSApplicationMain + 574 (in AppKit) [0x9225d1d8]
49 -[NSApplication run] + 867 (in AppKit) [0x9228ffe7]
49 ??? [0x229973]
49 -[NSApplication sendEvent:] + 2939 (in AppKit) [0x923326a5]
49 -[NSWindow sendEvent:] + 5381 (in AppKit) [0x92365af7]
49 ??? [0x3ec62]
49 -[NSOutlineView mouseDown:] + 611 (in AppKit) [0x923beff1]
49 -[NSTableView mouseDown:] + 6867 (in AppKit) [0x923aebf8]
49 -[NSTableView _enableSelectionPostingAndPost] + 561 (in AppKit) [0x9237575d]
49 -[NSNotificationCenter postNotificationName:object:] + 56 (in Foundation) [0x95427ed8]
49 -[NSNotificationCenter postNotificationName:object:userInfo:] + 128 (in Foundation) [0x9541e680]
49 __CFXNotificationPostNotification + 179 (in CoreFoundation) [0x93ad5753]
49 ___CFXNotificationPost + 362 (in CoreFoundation) [0x93ad547a]
49 __nsnote_callback + 106 (in Foundation) [0x9542142a]
49 ??? [0x4e741]
49 ??? [0xa8f49]
49 ??? [0xa8f7d]
49 -[NSObject(NSThreadPerformAdditions) performSelectorOnMainThread:withObject:waitUntilDone:] + 184 (in Foundation) [0x954758e8]
49 -[NSObject(NSThreadPerformAdditions) performSelector:onThread:withObject:waitUntilDone:modes:] + 1115 (in Foundation) [0x9542232b]
49 -[NSNotificationCenter postNotification:] + 124 (in Foundation) [0x9544e9bc]
49 __CFXNotificationPostNotification + 179 (in CoreFoundation) [0x93ad5753]
49 ___CFXNotificationPost + 362 (in CoreFoundation) [0x93ad547a]
49 __nsnote_callback + 106 (in Foundation) [0x9542142a]
49 ??? [0x7ce32]
49 ??? [0x6f504]
49 ??? [0x13a800]
49 ??? [0x57b4d]
49 ??? [0x596e9]
35 ??? [0x59905]
14 ??? [0x5dc926]
6 _sqlite3Step + 17 (in libsqlite3.0.dylib) [0x91e2ed31]
3 _sqlite3Step + 221 (in libsqlite3.0.dylib) [0x91e2edfd]
2 _sqlite3Step + 208 (in libsqlite3.0.dylib) [0x91e2edf0]
1 _sqlite3Step + 41 (in libsqlite3.0.dylib) [0x91e2ed49]
1 _sqlite3Step + 9 (in libsqlite3.0.dylib) [0x91e2ed29]
1 _sqlite3Step + 25 (in libsqlite3.0.dylib) [0x91e2ed39]
7 _sqlite3Step + 0 (in libsqlite3.0.dylib) [0x91e2ed20]
4 _sqlite3_step + 11 (in libsqlite3.0.dylib) [0x91e2f54b]
3 _sqlite3_step + 134 (in libsqlite3.0.dylib) [0x91e2f5c6]
2 _sqlite3_step + 128 (in libsqlite3.0.dylib) [0x91e2f5c0]
2 _sqlite3Step + 225 (in libsqlite3.0.dylib) [0x91e2ee01]
1 _sqlite3_step + 20 (in libsqlite3.0.dylib) [0x91e2f554]
1 _sqlite3_step + 22 (in libsqlite3.0.dylib) [0x91e2f556]
1 _sqlite3_step + 4 (in libsqlite3.0.dylib) [0x91e2f544]
5 ??? [0x5dc91b]
3 ??? [0xae911e]
2 ??? [0x5dc940]
2 ??? [0x5dc94c]
2 _sqlite3_step + 0 (in libsqlite3.0.dylib) [0x91e2f540]
Kernel stack:
49 _PE_incoming_interrupt + 131 [0x44e416]
49 _lapic_interrupt + 121 [0x1b16c0]
49 _sync_iss_to_iks + 114 [0x1aa3ae]
Thread id: 9645208
User stack:
49 _thread_start + 34 (in libSystem.B.dylib) [0x96a9df12]
49 __pthread_start + 321 (in libSystem.B.dylib) [0x96a9e055]
49 ___NSThread__main__ + 308 (in Foundation) [0x954219a4]
49 -[NSThread main] + 45 (in Foundation) [0x95421dfd]
49 -[XTThread run:] + 387 (in ProXTCore) [0x1352363]
49 -[XTMsgQueue waitForMessage] + 49 (in ProXTCore) [0x1364201]
49 -[NSConditionLock lockWhenCondition:] + 69 (in Foundation) [0x95467b35]
49 -[NSConditionLock lockWhenCondition:beforeDate:] + 144 (in Foundation) [0x95467bd0]
49 -[NSCondition waitUntilDate:] + 236 (in Foundation) [0x95467dbc]
49 _semaphore_timedwait_signal_trap + 10 (in libSystem.B.dylib) [0x96a6d1c6]
Thread id: 7b12f20
User stack:
49 _thread_start + 34 (in libSystem.B.dylib) [0x96a9df12]
49 __pthread_start + 321 (in libSystem.B.dylib) [0x96a9e055]
49 ___NSThread__main__ + 308 (in Foundation) [0x954219a4]
49 -[NSThread main] + 45 (in Foundation) [0x95421dfd]
49 -[XTThread run:] + 387 (in ProXTCore) [0x1352363]
49 -[XTMsgQueue waitForMessage] + 49 (in ProXTCore) [0x1364201]
49 -[NSConditionLock lockWhenCondition:] + 69 (in Foundation) [0x95467b35]
49 -[NSConditionLock lockWhenCondition:beforeDate:] + 144 (in Foundation) [0x95467bd0]
49 -[NSCondition waitUntilDate:] + 236 (in Foundation) [0x95467dbc]
49 _semaphore_timedwait_signal_trap + 10 (in libSystem.B.dylib) [0x96a6d1c6]
Thread id: 75b2d60
User stack:
49 _thread_start + 34 (in libSystem.B.dylib) [0x96a9df12]
49 __pthread_start + 321 (in libSystem.B.dylib) [0x96a9e055]
49 ___NSThread__main__ + 308 (in Foundation) [0x954219a4]
49 -[NSThread main] + 45 (in Foundation) [0x95421dfd]
49 -[XTRunLoopThread run:] + 421 (in ProXTCore) [0x13538a5]
49 -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 213 (in Foundation) [0x954563d5]
49 _CFRunLoopRunInMode + 88 (in CoreFoundation) [0x93af4aa8]
49 _mach_msg_trap + 10 (in libSystem.B.dylib) [0x96a6d166]
Thread id: 9646128
User stack:
49 _thread_start + 34 (in libSystem.B.dylib) [0x96a9df12]
49 __pthread_start + 321 (in libSystem.B.dylib) [0x96a9e055]
49 ___NSThread__main__ + 308 (in Foundation) [0x954219a4]
49 -[NSThread main] + 45 (in Foundation) [0x95421dfd]
49 ??? [0x506841]
49 ___semwait_signal + 10 (in libSystem.B.dylib) [0x96a7434e]
Thread id: 96468b8
User stack:
49 _thread_start + 34 (in libSystem.B.dylib) [0x96a9df12]
49 __pthread_start + 321 (in libSystem.B.dylib) [0x96a9e055]
49 ___NSThread__main__ + 308 (in Foundation) [0x954219a4]
49 -[NSThread main] + 45 (in Foundation) [0x95421dfd]
49 +[NSURLConnection(NSURLConnectionReallyInternal) _resourceLoadLoop:] + 320 (in Foundation) [0x95485520]
49 _CFRunLoopRunInMode + 88 (in CoreFoundation) [0x93af4aa8]
49 _mach_msg_trap + 10 (in libSystem.B.dylib) [0x96a6d166]
Thread id: 9645998
User stack:
49 _thread_start + 34 (in libSystem.B.dylib) [0x96a9df12]
49 ___select + 10 (in libSystem.B.dylib) [0x96abc60a]
Thread id: 96477d8
User stack:
49 _thread_start + 34 (in libSystem.B.dylib) [0x96a9df12]
49 __ZN3***17TCMalloc_PageHeap15scavengerThreadEv + 824 (in JavaScriptCore) [0x92c0cd58]
49 ___semwait_signal + 10 (in libSystem.B.dylib) [0x96a7434e]
Thread id: 96455d0
User stack:
49 _thread_start + 34 (in libSystem.B.dylib) [0x96a9df12]
49 __pthread_start + 321 (in libSystem.B.dylib) [0x96a9e055]
49 __Z22CFURLCacheWorkerThreadPv + 388 (in CFNetwork) [0x919a018c]
49 _CFRunLoopRunInMode + 88 (in CoreFoundation) [0x93af4aa8]
49 _mach_msg_trap + 10 (in libSystem.B.dylib) [0x96a6d166]
Thread id: 9412a78
User stack:
49 _thread_start + 34 (in libSystem.B.dylib) [0x96a9df12]
49 __pthread_start + 321 (in libSystem.B.dylib) [0x96a9e055]
49 __ZN3***15ThreadCondition9timedWaitERNS_5MutexEd + 81 (in JavaScriptCore) [0x92a616b1]
49 ___semwait_signal + 10 (in libSystem.B.dylib) [0x96a7434e]
Thread id: 96464f0
User stack:
49 _thread_start + 34 (in libSystem.B.dylib) [0x96a9df12]
49 __pthread_start + 321 (in libSystem.B.dylib) [0x96a9e055]
49 ___NSThread__main__ + 308 (in Foundation) [0x954219a4]
49 -[NSThread main] + 45 (in Foundation) [0x95421dfd]
49 -[ILMediaBrowserPathWatcher(FSEvents) iLMBPathWatcherRunLoop] + 862 (in iLifeMediaBrowser) [0x956ced0e]
49 _CFRunLoopRun + 84 (in CoreFoundation) [0x93af4b04]
49 _mach_msg_trap + 10 (in libSystem.B.dylib) [0x96a6d166]
Thread id: 94148b8
User stack:
49 _thread_start + 34 (in libSystem.B.dylib) [0x96a9df12]
49 __pthread_start + 321 (in libSystem.B.dylib) [0x96a9e055]
49 _fe_fragment_thread + 54 (in QuartzCore) [0x97e65a09]
49 ___semwait_signal + 10 (in libSystem.B.dylib) [0x96a7434e]
Thread id: 7538000
User stack:
49 ??? [0x0]
Thread id: 9643b58
User stack:
49 ??? [0x0]
Process: ATSServer [113]
Path: /System/Library/Frameworks/ApplicationServices.framework/Frameworks/ATS.framewo rk/Support/ATSServer
ADDRESS BINARY
00001000 /System/Library/Frameworks/ApplicationServices.framework/Frameworks/ATS.framewo rk/Support/ATSServer
Thread id: 7d00ba0
User stack:
49 ??? [0x4b46]
49 ??? [0xdd21f]
49 _CFRunLoopRun + 84 (in CoreFoundation) [0x93af4b04]
49 _mach_msg_trap + 10 (in libSystem.B.dylib) [0x96a6d166]
Thread id: 7cff4f0
User stack:
49 _thread_start + 34 (in libSystem.B.dylib) [0x96a9df12]
49 __pthread_start + 321 (in libSystem.B.dylib) [0x96a9e055]
49 _mach_msg_trap + 10 (in libSystem.B.dylib) [0x96a6d166]
Process: AirPort Base Station Agent [104]
Path: /System/Library/CoreServices/AirPort Base Station Agent.app/Contents/MacOS/AirPort Base Station Agent
ADDRESS BINARY
00001000 /System/Library/CoreServices/AirPort Base Station Agent.app/Contents/MacOS/AirPort Base Station Agent
Thread id: 7b12790
User stack:
49 ??? [0x25ad]
49 ??? [0x2680]
49 _NSApplicationMain + 574 (in AppKit) [0x9225d1d8]
49 -[NSApplication run] + 795 (in AppKit) [0x9228ff9f]
49 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 128 (in AppKit) [0x92296f88]
49 __DPSNextEvent + 657 (in AppKit) [0x922976d5]
49 _BlockUntilNextEventMatchingListInMode + 106 (in HIToolbox) [0x9513df39]
49 _ReceiveNextEventCommon + 374 (in HIToolbox) [0x9513e0c5]
49 _RunCurrentEventLoopInMode + 283 (in HIToolbox) [0x9513e2ac]
49 _CFRunLoopRunInMode + 88 (in CoreFoundation) [0x93af4aa8]
49 _mach_msg_trap + 10 (in libSystem.B.dylib) [0x96a6d166]
Thread id: 7cfcb58
User stack:
49 _thread_start + 34 (in libSystem.B.dylib) [0x96a9df12]
49 ___select + 10 (in libSystem.B.dylib) [0x96abc60a]
Thread id: 7cfd2e8
User stack:
49 _thread_start + 34 (in libSystem.B.dylib) [0x96a9df12]
49 __pthread_start + 321 (in libSystem.B.dylib) [0x96a9e055]
49 ??? [0x1e458]
49 ??? [0x1a1cb]
49 ??? [0x1e759]Option 1
Back Up and try rebuild the library: hold down the command and option (or alt) keys while launching iPhoto. Use the resulting dialogue to rebuild. Choose to Rebuild iPhoto Library Database from automatic backup.
If that fails:
Option 2
Download iPhoto Library Manager and use its rebuild function. This will create a new library based on data in the albumdata.xml file. Not everything will be brought over - no slideshows, books or calendars, for instance - but it should get all your albums and keywords back.
Because this process creates an entirely new library and leaves your old one untouched, it is non-destructive, and if you're not happy with the results you can simply return to your old one. .
Regards
TD -
MBA 2013 screen crash and suddenly battery drains
Hello, I bought MacBook Air November 2013 in India. I am facing the same problem in my MBA after 6-7 days of buying date. Since it is my first device from Apple so I am following all instructions by the reseller and service center persons.
First I spoke to the reseller, he suggested me sometimes due to third party apps it may happen. When it happened again then he suggested me to go to service center. In between that I joined the discussion on Apple support community and started to get the comments about this issue. Then I chatted online with apple persons they instructed me to check settings of SMC and PRAM and suggested to go to service center. Then after, 3 times I have taken my MBA to service center:
1st time: they changed the settings in it and gave back to me by saying to observe the problem.
I observed it for 2 days and problem occurred. I informed to service center.
2nd time: they kept it for 4 days with them to observe and gave it back by saying that we have fresh installed the Mac OS10.9 since this issue was due to I have updated the Mac OS from 10.9 to 10.9.1
Within 4-5 days it happened again with one more problem of showing battery drain significantly by spot light. I continued to observe these issues for few more occurrences. In between that again I chatted with apple person and discussed both the issues.... amazing... again he told me the same settings as previously and observe.
3rd time: I took it to service center and told compete issue about the discussion with apple persons too. They kept it for two days and simply said that we have to chat with Apple technicians then only we say something. They chatted with Apple technicians and suggested me to keep the machine as it is till the Apple people update the firmware… When I asked… How much time it will take…? They said, “Do not know”!
Interesting point is that in front of service center person I showed this issue how screen crashes and how the battery drains happening and showing energy used significantly by spotlight. Even then those persons told me to wait for firmware update by Apple.
After take from service center, one more thing is happening with my MBA if I put my finger in front of webcam brightness of display goes dim. I do not know, how the service center persons are dealing?
When I asked to replace it or upgrade it to another machine then they simply raise their hand and we can do nothing for this. And told you have to speak with Apple persons
Now what to do? I am helpless…!!!After take from service center, one more thing is happening with my MBA if I put my finger in front of webcam brightness of display goes dim. I do not know, how the service center persons are dealing?
Thats 100% normal, thats auto-dim as it senses the light. All of them do that.
As for the rest, your Air is in for service, this is a users board, contact Apple Inc. about any issues regarding your service calls. -
I am using MBP 13" late 2010, after upgrade to 10.6.7 my battery is very weak. Battery has 59 cycles. I am using Safari, wifi is on and LCD is on 50% and my battery status is lower than 3 hours.
Calibrating battery did not help, reseting NVRAM and PRAM did not help too.I noticed the same, a lot less battery life just by upgrading to 10.6.7
Im using a Macbook Pro (mid 2010).
I had a very very good battery life before upgrading, now the battery last a lot less even if i leave it unplugged and turned off, the battery drains.
Ive already let the computer to drain the whole battery and recharged it to 100% and get the same results.
Next step is to reset PRAM to see if this helps.
I was on 74% when i started to type a reply once i finished this post i had 69% battery life it drains really fast!!!! :S -
My computer is 3 1/2 months old and my battery is dying really fast what can I do to increase the battery life?
Hi,
I asssume it's a laptop!
1st I would run it right down & then do a full recharge, then run it down again + a full recharge..
Check that you do not have any apps running in the background, reset PRAM..
When all's done I usually run a movie & time how long the battery lasts..if after that & no joy call Apple Help.. -
Filevault encryption paused, despite reset of PRAM and using terminal commands
I have been trying to partition my HDD but am unable to because file vault encryption is paused - and has been since October 2014.
I attempted making a new user to see if this would bypass it, but it didn't.
I have reset the PRAM and have repaired the HDD both in recovery and normal, neither work.
I have also used terminal command "sudo fdesetup disable" to attempt turning it off, but that doesn't work either.
Help please??
HarryIf you don't already have a current backup of all data, back up before proceeding. There are ways to back up a computer that isn't fully functional. Ask if you need guidance.
Start up in Recovery mode. When the OS X Utilities screen appears, select Disk Utility.
In the Disk Utility window, select the icon of the startup volume from the list on the left. It will be nested below another disk icon, usually with the same name. Click the Unlock button in the toolbar. When prompted, enter the login password of a user authorized to unlock the volume, or the alternate decryption key that was generated when you activated FileVault.
Then, from the menu bar, select
File ▹ Turn Off Encryption
Enter the password again.
You can then restart as usual, if the system is working. Decryption will be completed in the background. It may take several hours, and during that time performance will be reduced.
If you can't turn off encryption in Disk Utility because the menu item is grayed out, you'll have to erase the volume and then restore the data from a backup. Select the Erase tab, and then select
Mac OS Extended (Journaled)
from the Format menu.
You can then quit to be returned to the main Recovery screen. Follow these instructions if you back up with Time Machine. If you use other backup software, follow its developer's instructions.
Don't erase the volume unless you have at least two complete, independent backups. One is not enough to be safe. -
Resetting PRAM and NVRAM bring Bluetooth back
My MBP Bluetooth menu lost somehow and could not connect to
"Apple Wireless Keyboard" and "Microsoft Bluetooth mouse",
the following steps seemed working:
1. Resetting PRAM and NVRAM:
http://support.apple.com/kb/HT1379
note you have to "Hold the keys down until the computer restarts and you hear the startup sound twice".
2. Connecting to "Apple Wireless Keyboard":
http://support.apple.com/kb/ht1809
** "First unpair the keyboard If the unpaired Mac is within 33 feet
(10 meters) of the computer your keyboard is currently paired with"**
3. Connecting to "Microsoft Bluetooth mouse"
http://www.microsoft.com/hardware/mouseandkeyboard/features/bluetoothhow_toconnect.mspx
note you have to hold the connect button on the bottom of the mouse:)Most likely an issue with the system management controller interacting with the bluetooth host controller, it can be reset by doing 1 of these three depending on your situation:
If you have a desktop computer: Unplug it from the outlet and anything plugged into the firewire/usb ports, leave it that way for 45 seconds minimum check it again and see if it mounts in disk utility
If you have a laptop do one of these two steps and post back if it mounts:
Removable battery: Remove battery, disconnect charger(power adapter), hold down power button for 5 seconds, put back in battery should resolve
Embedded (non removable) battery: plug in the power adapter/charger, turn off computer, hold down on the LEFT side of the keyboard Shift-Control-Option. While your holding all of these press the power button once, let go of just the power button. Two seconds or so later let go of the rest of the buttons, you'll know this step was successful if it didn't turn on.
Maybe you are looking for
-
I use iTunes for Windows and the program is awful. Great if I'm looking to buy music, terrible for actually playing said music. It freezes the first time I open it every time I turn on my computer. I can't change it's audio output to play through the
-
I use Firefox v10.0.2 as default browser on Dell XPS8300 e/w Intel Core i5 & Windows 7 Ultimate and Compaq Presario CQ57 e/w Intel Core i3 & Windows 7 Home. More frequently on the (about 90% of attempts) than the Dell (50% of attempts) Firefox will n
-
Creating a task field list in c# project
Hi All, I am writing a small application to simply my monthly forecasting and reporting. I'm extracting data from my msProject file into a c# application with a local database. I want the user to be able to select which task data fields to extract
-
After downloading Itunes 7.6 I click and nothing happens
I have windows XP and a gateway laptop thats about 3 years old. I recently bought a nano 3rd generation and after downloading Itunes 7.6 SUCCESSFULLY I click on the Icon and I get an hourglass then it goes away and nothing happens! Keep in mind I had
-
Hello all. I get an error trying to recieve pick up a JMS message from a Websphere-MQ: Error while processing message 'a17728a0-99ba-11dc-af52-0017a4f51c91'; detailed error description: com.sap.aii.adapter.jms.api.channel.filter.MessageFilterExcepti