[svn:fx-trunk] 9287: Fixes bug with shader-transition effects ( AnimateTransitionShader, Wipe, and CrossFade) when acting on targets that either have filters or are inside a hierarchy with filters .

Revision: 9287
Author:   [email protected]
Date:     2009-08-13 15:53:43 -0700 (Thu, 13 Aug 2009)
Log Message:
Fixes bug with shader-transition effects (AnimateTransitionShader, Wipe, and CrossFade) when acting on targets that either have filters or are inside a hierarchy with filters. Fix was to capture the bitmap snapshot of the target without any of its own filters applied and to then use the ShaderFilter in conjunction with the target's filters during the animation.
QE notes: Probably need more tests in this area, now that we handle it
Doc notes: none
Bugs: sdk-20250
Reviewer: Jason
Tests run: Checkintests, Mustella (spark/effects/[AnimateTransitionShader|Wipe|CrossFade])
Is noteworthy for integration: No
Ticket Links:
    http://bugs.adobe.com/jira/browse/sdk-20250
Modified Paths:
    flex/sdk/trunk/frameworks/projects/spark/src/spark/effects/AnimateTransitionShader.as
    flex/sdk/trunk/frameworks/projects/spark/src/spark/effects/supportClasses/AnimateTransiti onShaderInstance.as

Lots to be excited about. BUT...Just updated to 8.1 on one of my computers to test it out...
Sadly, the following issue is NOT fixed for me. Is it with new projects only?  I haven't started a new project on 8.1 I've only opened an old project but the issue that I'm referring to which involves also a delay/freeze of anywhere from a few seconds to a MINUTE while the render bar goes from yellow to red and then back to yellow is still there. Boo.
On the list above...
Switching between sequences can turn the render bar red.
This issue is incredibly easy to replicate. I really do hope it gets fixed. Here are the steps:
1) Create two sequences with multiple short clips (the more clips the better)
2) Make sure GPU acceleration is enabled.
3) Add warp stabilizer to the clips in both sequences. Again, the more clips the longer the delay/freeze will be as the render bar goes from YELLOW to RED and then eventually back to YELLOW again.
4) Hit SAVE.
5) Now, toggle between sequences. You'll hit a short delay with a few clips stabilized and a LONG delay with lots stabilized. In my case this delay is around a full minute. The render bar will go from YELLOW to RED and then back to yellow...eventually.
6) Toggle back to the original sequence and the delay occurs again.
7) Once you've toggled between sequences and have gone through this delay, that's it, there is no longer a delay...UNTIL...(and here's the big kicker)...until the project is SAVED again. After that the issue returns when you toggle between sequences. Both saving manually and AUTOSAVING cause this issue. No way around it except not editing with GPU acceleration.
Not sure what the issue is...caching issue when saving maybe? Either way, it stinks and it's still there in 8.1. Big bummer.
Again, lots to be excited about with this release but I really was hopefully this specific issue was resolved.
Sigh.

Similar Messages

  • [svn:fx-trunk] 12786: Fixed bug with state property value assignments.

    Revision: 12786
    Revision: 12786
    Author:   [email protected]
    Date:     2009-12-10 07:35:43 -0800 (Thu, 10 Dec 2009)
    Log Message:
    Fixed bug with state property value assignments. SetProperty pseudonym values (width/explicitWidth, height/explicitHeight) were not getting set correctly, causing values to be incorrectly assigned to 0 in some cases.
    QE notes: -
    Doc notes: -
    Bugs: sdk-24446
    Reviewer: Corey
    Tests run: checkintests, Mustella tests/States, tests/mx/states
    Is noteworthy for integration: Yes (fix requested by tools)
    Ticket Links:
        http://bugs.adobe.com/jira/browse/sdk-24446
    Modified Paths:
        flex/sdk/trunk/frameworks/projects/framework/src/mx/states/SetProperty.as

    Add this to the end of your nav p CSS selector at Line 209 of your HTML file, after 'background-repeat...':
    margin-bottom: -2px;
    Your nav p will then look like this:
    nav p {
              font-size: 90%;
              font-weight: bold;
              color: #FFC;
              background-color: #090;
              text-align: right;
              padding-top: 5px;
              padding-right: 20px;
              padding-bottom: 5px;
              border-bottom-width: 2px;
              border-bottom-style: solid;
              border-bottom-color: #060;
              background-image: url(images/background.png);
              background-repeat: repeat-x;
              margin-bottom: -2px;

  • [svn:fx-trunk] 7891: Fixed bug in effects  that was fallout from renaming offsets property to postLayoutTransformOffsets .

    Revision: 7891
    Author:   [email protected]
    Date:     2009-06-16 13:38:37 -0700 (Tue, 16 Jun 2009)
    Log Message:
    Fixed bug in effects  that was fallout from renaming offsets property to postLayoutTransformOffsets.
    QE Notes: none
    Doc Notes: None
    Bugs: SDK-21839
    Reviewer: Evtim
    Tests: checkintests
    Ticket Links:
        http://bugs.adobe.com/jira/browse/SDK-21839
    Modified Paths:
        flex/sdk/trunk/frameworks/projects/flex4/src/spark/effects/supportClasses/AnimateTransfor mInstance.as

    Lots to be excited about. BUT...Just updated to 8.1 on one of my computers to test it out...
    Sadly, the following issue is NOT fixed for me. Is it with new projects only?  I haven't started a new project on 8.1 I've only opened an old project but the issue that I'm referring to which involves also a delay/freeze of anywhere from a few seconds to a MINUTE while the render bar goes from yellow to red and then back to yellow is still there. Boo.
    On the list above...
    Switching between sequences can turn the render bar red.
    This issue is incredibly easy to replicate. I really do hope it gets fixed. Here are the steps:
    1) Create two sequences with multiple short clips (the more clips the better)
    2) Make sure GPU acceleration is enabled.
    3) Add warp stabilizer to the clips in both sequences. Again, the more clips the longer the delay/freeze will be as the render bar goes from YELLOW to RED and then eventually back to YELLOW again.
    4) Hit SAVE.
    5) Now, toggle between sequences. You'll hit a short delay with a few clips stabilized and a LONG delay with lots stabilized. In my case this delay is around a full minute. The render bar will go from YELLOW to RED and then back to yellow...eventually.
    6) Toggle back to the original sequence and the delay occurs again.
    7) Once you've toggled between sequences and have gone through this delay, that's it, there is no longer a delay...UNTIL...(and here's the big kicker)...until the project is SAVED again. After that the issue returns when you toggle between sequences. Both saving manually and AUTOSAVING cause this issue. No way around it except not editing with GPU acceleration.
    Not sure what the issue is...caching issue when saving maybe? Either way, it stinks and it's still there in 8.1. Big bummer.
    Again, lots to be excited about with this release but I really was hopefully this specific issue was resolved.
    Sigh.

  • [svn:fx-trunk] 7868: Fixed bug in flex4test testWheel app; it needed to be updated to the latest effects API after motionPaths changed from an Array to a Vector . MotionPath

    Revision: 7868
    Author:   [email protected]
    Date:     2009-06-15 16:37:33 -0700 (Mon, 15 Jun 2009)
    Log Message:
    Fixed bug in flex4test testWheel app; it needed to be updated to the latest effects API after motionPaths changed from an Array to a Vector.
    Modified Paths:
        flex/sdk/trunk/development/eclipse/flex/flex4test/src/testWheel.mxml

    Walter Laan wrote:
    almightywiz wrote:
    Walter Laan wrote:
    The security popup really messes with the focus in Firefox (3.6.16) though.Not saying you're wrong, but I'm using FireFox 3.6.16, as well, and I have none of the focus troubles you've described.Cannot reproduce it now either. Weird.I got the impression you were referring to keyboard focus, so I did some further tests on focus behavior. The test results are listed in the Accumulated Results table on the 1st post.
    The only browser so far that works as I'd expect, or at least as I'd like, is IE.
    Applets and keyboard navigation have always been a PITA. Some time ago I vaguely recall seeing an update involving a new parameter to regulate initial focus (applet or page, ..or another applet), but for the life of me I cannot locate it now. Given that it was a parameter for initial focus, I doubt it would help in this case.
    Edited by: Andrew Thompson on Mar 26, 2011 6:18 PM
    Removed table which has now been expanded & added to 1st post.

  • [svn:fx-trunk] 5831: Fix bug Fix SDK-19800 FxButton doesnt resize itself to display all text when lineBreak == toFit

    Revision: 5831
    Author: [email protected]
    Date: 2009-03-31 16:50:47 -0700 (Tue, 31 Mar 2009)
    Log Message:
    Fix bug Fix SDK-19800 FxButton doesnt resize itself to display all text when lineBreak == toFit
    Fix: implement text reflow support for TextGraphicelement.
    QE Notes: None
    Doc Notes:
    Bugs: SDK-19800
    Reviewer: Carol, Gordon
    tests: checkintests, mustella
    Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-19800
    http://bugs.adobe.com/jira/browse/SDK-19800
    Modified Paths:
    flex/sdk/trunk/frameworks/projects/flex4/src/spark/primitives/supportClasses/TextGraphicE lement.as

  • [svn:fx-trunk] 9890: Fix bug involving changes to tabbing related properties

    Revision: 9890
    Author:   [email protected]
    Date:     2009-09-01 15:57:01 -0700 (Tue, 01 Sep 2009)
    Log Message:
    Fix bug involving changes to tabbing related properties
    QE Notes: None
    Doc Notes: None
    Bugs: SDK-19577
    Reviewer: Corey
    API Change: No
    Is noteworthy for integration: No
    tests: checkintests mustella/managers/FocusManager
    Ticket Links:
        http://bugs.adobe.com/jira/browse/SDK-19577
    Modified Paths:
        flex/sdk/trunk/frameworks/projects/framework/src/mx/managers/FocusManager.as

  • [svn:fx-trunk] 9225: Fix bug: Rows disappear in Spark List when using negative gap in layout and using virtualization

    Revision: 9225
    Author:   [email protected]
    Date:     2009-08-11 11:36:09 -0700 (Tue, 11 Aug 2009)
    Log Message:
    Fix bug: Rows disappear in Spark List when using negative gap in layout and using virtualization
    Fix: Change H/V layouts first-visible-element lookup logic to accommodate negative gaps.
    QE notes: None
    Doc notes: None
    Bugs: SDK-22497
    Reviewer: Hans
    Tests run: checkintests,
    Is noteworthy for integration: No
    Ticket Links:
        http://bugs.adobe.com/jira/browse/SDK-22497
    Modified Paths:
        flex/sdk/trunk/frameworks/projects/spark/src/spark/layouts/HorizontalLayout.as
        flex/sdk/trunk/frameworks/projects/spark/src/spark/layouts/VerticalLayout.as

    sorka;
    You can check the LabVIEW Support page.
    There is a troubleshooting section called LabVIEW Installation/Getting Started Resources. It also includes a LabVIEW 7.x Frequently Asked Questions that has a link that reads Issues Fixed in LabVIEW 7.1. However, not much information is provided there.
    Other places where you can post your findings is at the LAVA Forum (check the Bug list forum) and the Info-LabVIEW mailing list. These are not official places, but usually they li
    sten
    Enrique
    www.vartortech.com

  • [svn:fx-trunk] 9284: Fix bug: Spark BasicLayout should throw error/ RTE when setting useVirtualLayout

    Revision: 9284
    Author:   [email protected]
    Date:     2009-08-13 15:33:07 -0700 (Thu, 13 Aug 2009)
    Log Message:
    Fix bug: Spark BasicLayout should throw error/RTE when setting useVirtualLayout
    QE notes: None
    Doc notes: None
    Bugs: SDK-22211
    Reviewer: Hans
    Tests run: checkintests, gumbo/core/Group, gumbo/core/DataGroup, gumbo/core/List
    Is noteworthy for integration: No
    Ticket Links:
        http://bugs.adobe.com/jira/browse/SDK-22211
    Modified Paths:
        flex/sdk/trunk/frameworks/projects/spark/bundles/en_US/layout.properties
        flex/sdk/trunk/frameworks/projects/spark/src/spark/layouts/BasicLayout.as

    This bug figures out also when creating a custom spark ComboBox, then trying to programatically update the userProposedSelectedIndex property. The proposed selected index is selected, but does not apply the same skin as when mouse is on rollover or item is selected due to up and down keys.
    The issue seems like updating the status of the item renderer to rollover or selected to get the same skin applied.
    Please could you attach DropDow nList.as that you edited ?
    Thank you so much.

  • [svn:fx-trunk] 9324: Fix bug: orientation/verticalAlign/ horizontalAlign properties of TileLayout should not be bindable

    Revision: 9324
    Author:   [email protected]
    Date:     2009-08-14 15:04:23 -0700 (Fri, 14 Aug 2009)
    Log Message:
    Fix bug: orientation/verticalAlign/horizontalAlign properties of TileLayout should not be bindable
    Fix: remove metadata, we were not dispatching events anyway.
    QE notes: None
    Doc notes: None
    Bugs: SDK-22715
    Reviewer: Hans
    Tests run: build
    Is noteworthy for integration: No
    Ticket Links:
        http://bugs.adobe.com/jira/browse/SDK-22715
    Modified Paths:
        flex/sdk/trunk/frameworks/projects/spark/src/spark/layouts/TileLayout.as

    to put it simple, the DataGrid supposely changes the dataProvider on each page (page here is actually the selection in the list. since the list displays only one item at one time, I just called each selection as page) . So, I was thinking to refresh the itemRenderer on each swipe. could be there are any other way to do this so appreciate any help and ideas. Thanks!

  • [svn:fx-trunk] 9275: Fix bug: GraphicElement.getStrokeExtents needs ASDoc

    Revision: 9275
    Author:   [email protected]
    Date:     2009-08-13 12:05:09 -0700 (Thu, 13 Aug 2009)
    Log Message:
    Fix bug: GraphicElement.getStrokeExtents needs ASDoc
    Fix: Add comment, while at it, updated the API to return a Rectangle instead.
    QE notes: None
    Doc notes: None
    Bugs: FLEXDOCS-1032
    Reviewer: Deepa
    Tests run: checkintests, spark/primitives, gumbo/layout/graphicElements
    Is noteworthy for integration: No
    Ticket Links:
        http://bugs.adobe.com/jira/browse/FLEXDOCS-1032
    Modified Paths:
        flex/sdk/trunk/frameworks/projects/spark/src/spark/primitives/Ellipse.as
        flex/sdk/trunk/frameworks/projects/spark/src/spark/primitives/Path.as
        flex/sdk/trunk/frameworks/projects/spark/src/spark/primitives/Rect.as
        flex/sdk/trunk/frameworks/projects/spark/src/spark/primitives/supportClasses/GraphicEleme nt.as
        flex/sdk/trunk/frameworks/projects/spark/src/spark/primitives/supportClasses/StrokedEleme nt.as

  • [svn:fx-trunk] 9127: Fixes bug in Slider animation where we would set the actual value during the animation , ignoring any snapInterval setting.

    Revision: 9127
    Author:   [email protected]
    Date:     2009-08-05 17:25:39 -0700 (Wed, 05 Aug 2009)
    Log Message:
    Fixes bug in Slider animation where we would set the actual value during the animation, ignoring any snapInterval setting. The fix uses the pendingValue property to hold the animated value, which makes the slider look correct, but no actual value update is sent until the animation completes.
    QE notes: None
    Doc notes: None
    Bugs: SDK-21776
    Reviewer: Hans
    Tests run: checkintests, Mustella (gumbo/components/Slider)
    Is noteworthy for integration: No
    Ticket Links:
        http://bugs.adobe.com/jira/browse/SDK-21776
    Modified Paths:
        flex/sdk/trunk/frameworks/projects/spark/src/spark/components/supportClasses/Slider.as

    Revision: 9127
    Author:   [email protected]
    Date:     2009-08-05 17:25:39 -0700 (Wed, 05 Aug 2009)
    Log Message:
    Fixes bug in Slider animation where we would set the actual value during the animation, ignoring any snapInterval setting. The fix uses the pendingValue property to hold the animated value, which makes the slider look correct, but no actual value update is sent until the animation completes.
    QE notes: None
    Doc notes: None
    Bugs: SDK-21776
    Reviewer: Hans
    Tests run: checkintests, Mustella (gumbo/components/Slider)
    Is noteworthy for integration: No
    Ticket Links:
        http://bugs.adobe.com/jira/browse/SDK-21776
    Modified Paths:
        flex/sdk/trunk/frameworks/projects/spark/src/spark/components/supportClasses/Slider.as

  • [svn] 4840: Fix bug SDK-18904 Redudant APIs on UICompoennt and GraphicElement, SDK-17508 Applying a translation to a Rect causes shape to be scaled

    Revision: 4840
    Author: [email protected]
    Date: 2009-02-04 13:20:07 -0800 (Wed, 04 Feb 2009)
    Log Message:
    Fix bug SDK-18904 Redudant APIs on UICompoennt and GraphicElement, SDK-17508 Applying a translation to a Rect causes shape to be scaled
    Fix: remove layoutMatrix, layoutMatrix3D properties, add a parameter to the setLayoutMatrix, setLayoutMatrix3D methods to designate whether to trigger a layout pass after the transformation is applied.
    QE Notes: None
    Doc Notes: None
    Bugs: SDK-18434
    Reviewer: Jason
    tests: checkintests, mustella flash component kit
    Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-18904
    http://bugs.adobe.com/jira/browse/SDK-17508
    http://bugs.adobe.com/jira/browse/SDK-18434
    Modified Paths:
    flex/sdk/trunk/frameworks/projects/flash-integration/src/mx/flash/UIMovieClip.as
    flex/sdk/trunk/frameworks/projects/flex4/src/mx/graphics/graphicsClasses/GraphicElement.a s
    flex/sdk/trunk/frameworks/projects/framework/src/mx/core/ILayoutElement.as
    flex/sdk/trunk/frameworks/projects/framework/src/mx/core/UIComponent.as

  • Ipad 2 upgraded to iOS 8.0.2 and the cellular signal doesn't work. Have to restart the unit to work with cellular signal. After a while it goes off and no service indication appears.

    Ipad 2 upgraded to iOS 8.0.2 and the cellular signal doesn't work. Have to restart the unit to work with cellular signal. After a while it goes off and no service indication appears.

    iPad 2, Since upgrading to iOS 8.0.2  the cellular signal indicates I do not have a SIM card. Monday spent hours on the phone with Apple support, backed up my iPad, reset all settings, reloaded my iPad and it still tells me I don't have a SIM card. Tuesday went to AT&T and got a new SIM card on the advice of apple support. It worked perfect until this morning and the NO SIM CARD notice reappeared. Never ever had any problem until the upgrade. I find it inexcusable that Apple refuses to address the issues they caused, iOS 8.0.2 is the Ebola of iPad 2 world. I dont have any cellular service after wasting two days trying to address and fix a problem Apple is responsible for. It's obvious Steve Jobs is no longer running the company. Furious & fustrated. How does Apple expect anyone who uses an iPad 2 for work, to remain a customer who will return to their products?

  • Last night I did an update and now when I turn on my macbook it just goes to the white screen with the apple and stays like that.

    Last night I did an update and now when I turn on my macbook it just goes to the white screen with the apple and stays like that. How do I fix this issue?

    Take each of these steps that you haven't already tried. Stop when the problem is resolved.
    To restart an unresponsive computer, press and hold the power button for a few seconds until the power shuts off, then release, wait a few more seconds, and press it again briefly.
    Step 1
    The first step in dealing with a startup failure is to secure the data. If you want to preserve the contents of the startup drive, and you don't already have at least one current backup, you must try to back up now, before you do anything else. It may or may not be possible. If you don't care about the data that has changed since the last backup, you can skip this step.
    There are several ways to back up a Mac that is unable to start. You need an external hard drive to hold the backup data.
    a. Start up from the Recovery partition, or from a local Time Machine backup volume (option key at startup.) When the OS X Utilities screen appears, launch Disk Utility and follow the instructions in this support article, under “Instructions for backing up to an external hard disk via Disk Utility.” The article refers to starting up from a DVD, but the procedure in Recovery mode is the same. You don't need a DVD if you're running OS X 10.7 or later.
    b. If Step 1a fails because of disk errors, and no other Mac is available, then you may be able to salvage some of your files by copying them in the Finder. If you already have an external drive with OS X installed, start up from it. Otherwise, if you have Internet access, follow the instructions on this page to prepare the external drive and install OS X on it. You'll use the Recovery installer, rather than downloading it from the App Store.
    c. If you have access to a working Mac, and both it and the non-working Mac have FireWire or Thunderbolt ports, start the non-working Mac in target disk mode. Use the working Mac to copy the data to another drive. This technique won't work with USB, Ethernet, Wi-Fi, or Bluetooth.
    d. If the internal drive of the non-working Mac is user-replaceable, remove it and mount it in an external enclosure or drive dock. Use another Mac to copy the data.
    Step 2
    If the startup process stops at a blank gray screen with no Apple logo or spinning "daisy wheel," then the startup volume may be full. If you had previously seen warnings of low disk space, this is almost certainly the case. You might be able to start up in safe mode even though you can't start up normally. Otherwise, start up from an external drive, or else use the technique in Step 1b, 1c, or 1d to mount the internal drive and delete some files. According to Apple documentation, you need at least 9 GB of available space on the startup volume (as shown in the Finder Info window) for normal operation.
    Step 3
    Sometimes a startup failure can be resolved by resetting the NVRAM.
    Step 4
    If a desktop Mac hangs at a plain gray screen with a movable cursor, the keyboard may not be recognized. Press and hold the button on the side of an Apple wireless keyboard to make it discoverable. If need be, replace or recharge the batteries. If you're using a USB keyboard connected to a hub, connect it to a built-in port.
    Step 5
    If there's a built-in optical drive, a disc may be stuck in it. Follow these instructions to eject it.
    Step 6
    Press and hold the power button until the power shuts off. Disconnect all wired peripherals except those needed to start up, and remove all aftermarket expansion cards. Use a different keyboard and/or mouse, if those devices are wired. If you can start up now, one of the devices you disconnected, or a combination of them, is causing the problem. Finding out which one is a process of elimination.
    Step 7
    If you've started from an external storage device, make sure that the internal startup volume is selected in the Startup Disk pane of System Preferences.
    Start up in safe mode. Note: If FileVault is enabled in OS X 10.9 or earlier, or if a firmware password is set, or if the startup volume is a software RAID, you can’t do this. Post for further instructions.
    Safe mode is much slower to start and run than normal, and some things won’t work at all, including wireless networking on certain Macs.
    The login screen appears even if you usually log in automatically. You must know the login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.
    When you start up in safe mode, it's normal to see a dark gray progress bar on a light gray background. If the progress bar gets stuck for more than a few minutes, or if the system shuts down automatically while the progress bar is displayed, the startup volume is corrupt and the drive is probably malfunctioning. In that case, go to Step 11. If you ever have another problem with the drive, replace it immediately.
    If you can start and log in in safe mode, empty the Trash, and then open the Finder Info window on the startup volume ("Macintosh HD," unless you gave it a different name.) Check that you have at least 9 GB of available space, as shown in the window. If you don't, copy as many files as necessary to another volume (not another folder on the same volume) and delete the originals. Deletion isn't complete until you empty the Trash again. Do this until the available space is more than 9 GB. Then restart as usual (i.e., not in safe mode.)
    If the startup process hangs again, the problem is likely caused by a third-party system modification that you installed. Post for further instructions.
    Step 8
    Launch Disk Utility in Recovery mode (see Step 1.) Select the startup volume, then run Repair Disk. If any problems are found, repeat until clear. If Disk Utility reports that the volume can't be repaired, the drive has malfunctioned and should be replaced. You might choose to tolerate one such malfunction in the life of the drive. In that case, erase the volume and restore from a backup. If the same thing ever happens again, replace the drive immediately.
    This is one of the rare situations in which you should also run Repair Permissions, ignoring the false warnings it may produce. Look for the line "Permissions repair complete" at the end of the output. Then restart as usual.
    Step 9
    If the startup device is an aftermarket SSD, it may need a firmware update and/or a forced "garbage collection." Instructions for doing this with a Crucial-branded SSD were posted here. Some of those instructions may apply to other brands of SSD, but you should check with the vendor's tech support.  
    Step 10
    Reinstall the OS. If the Mac was upgraded from an older version of OS X, you’ll need the Apple ID and password you used to upgrade.
    Step 11
    Do as in Step 9, but this time erase the startup volume in Disk Utility before installing. The system should automatically restart into the Setup Assistant. Follow the prompts to transfer the data from a Time Machine or other backup.
    Step 12
    This step applies only to models that have a logic-board ("PRAM") battery: all Mac Pro's and some others (not current models.) Both desktop and portable Macs used to have such a battery. The logic-board battery, if there is one, is separate from the main battery of a portable. A dead logic-board battery can cause a startup failure. Typically the failure will be preceded by loss of the settings for the startup disk and system clock. See the user manual for replacement instructions. You may have to take the machine to a service provider to have the battery replaced.
    Step 13
    If you get this far, you're probably dealing with a hardware fault. Make a "Genius" appointment at an Apple Store, or go to another authorized service provider.

  • My macbook pro won't turn on. it just stays stuck on a white screen with a little circle spinning around and around when you power it on.

    my macbook pro won't turn on. it just stays stuck on a white screen with a little circle spinning around and around when you power it on. i don't know how to get it to progress past this loading page.

    Resetting your Mac's PRAM and NVRAM
    Intel-based Macs: Resetting the System Management Controller (SMC)
    Restart the computer in Safe Mode, then restart again, normally. If this doesn't help, then:
    Reinstalling Mavericks, Lion/Mountain Lion Without Erasing the Drive
    Boot to the Recovery HD: Restart the computer and after the chime press and hold down the COMMAND and R keys until the 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.
    Repair the Hard Drive and Permissions: Upon startup select Disk Utility from the main 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.
    Reinstall Lion/Mountain Lion, Mavericks: Select Reinstall Lion/Mountain Lion, Mavericks 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.
    If you are not using Lion, Mountain Lion, or Mavericks then use the following procedure:
    Resetting your Mac's PRAM and NVRAM
    Intel-based Macs: Resetting the System Management Controller (SMC)
    Restart the computer in Safe Mode, then restart again, normally. If this doesn't help, then:
    Reinstall OS X without erasing the drive
    1. Repair the Hard Drive and Permissions
    Boot from your Snow Leopard Installer disc. After the installer loads select your language and click on the Continue button. When the menu bar appears select Disk Utility from the Utilities menu. 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 installer.
    If DU reports errors it cannot fix, then you will need Disk Warrior and/or Tech Tool Pro to repair the drive. If you don't have either of them or if neither of them can fix the drive, then you will need to reformat the drive and reinstall OS X.
    2. Reinstall Snow Leopard
    If the drive is OK then quit DU and return to the installer.  Proceed with reinstalling OS X.  Note that the Snow Leopard installer will not erase your drive or disturb your files.  After installing a fresh copy of OS X the installer will move your Home folder, third-party applications, support items, and network preferences into the newly installed system.
    Download and install Mac OS X 10.6.8 Update Combo v1.1.

Maybe you are looking for

  • How to print selected parts of a webpage

    How can I print selected parts of a webpage (or more than one), without printing whole pages? Screen shot is nor effective for what I want.

  • 11gR2 Data Pump. Import table in one schema into a different schema

    I stady oracle. I export shema HR into file hrexport.dmp. When I import tables from this file I had trouble. I used Enterprise Manager: 1. connected by user SYSTEM as NORMAL 2. selected file, chosen import type - tables 3. data from file was imported

  • How do i get email messages back into mail

    hi, i recently deleted some email accounts that i no longer use but forgot to save the email messages first. i managed to locate the emails on a backup that i made. i now have lots of .emix files, each of which if i double click them open up so i can

  • I want to be a java web programmer

    Hi I'm not new to java desktop programming, but I haven't had a lot of experience and it was a few years ago now. But I am absolutely new to java web programming. Anyway, I want to get a web programming job, and not only that I want to make a couple

  • Can't deactivate due to broken Mac

    Hi, My macbook has broken and won't turn on. Therefore I am getting a new macbook pro. I have CS5 Creative suite on my old macbook, obviously couldn't deactivate due to having no idea it would stop working! I have the serial number for my creative su