2 Replies Latest reply: Apr 26, 2011 9:51 AM by deemure

    If Your NC Won't Update with Sideloaded Update

      Ok, I keep seeing multiple posts regarding this.

       

      If you have tried everything and done everything correctly in sideloading the update and the NC goes to sleep, but never updates, you may try this.  It isn't necessarily suggested, but for many people this is the only thing that is working.

       

      Make sure you have set the screen timeout to a long enough time to get the file.  Again, connect to the PC and wake the NC up.  Download the file directly to the NC's main folder.  Follow the procedures for ejecting and safely remove hardware and then wait for the NC to go to sleep.  You might want to reset the screen timeout so it happens more quickly and saves your battery charge first.  It should update.

       

        • Re: If Your NC Won't Update with Sideloaded Update

          The thing I found that works is to eject the device from the pc.  If you're like me and not an ejector, you might find that this solves your problem.  I copied the file a second time and then ejected it. The update file was recognized within a few minutes and the update started.   For any naysayers who think you ALWAYS have to eject usb devices, I generally set my Write Caching and Safe Removal policy to Optimize for Quick Removal so that Windows doesn't cache data to the computer before writing it to any external discs that might be connected.  In this instance, Windows waits for you to click on Safely Remove Device before it will write any remaining data to the device.  By setting it to Optimize for Quick Removal, that step is skipped and all data will be written immediately to any external devices.  I just noticed that the machine I sideloaded from was not set properly.

            • Re: If Your NC Won't Update with Sideloaded Update

               


              mathia wrote:

              The thing I found that works is to eject the device from the pc.  If you're like me and not an ejector, you might find that this solves your problem.  I copied the file a second time and then ejected it. The update file was recognized within a few minutes and the update started.   For any naysayers who think you ALWAYS have to eject usb devices, I generally set my Write Caching and Safe Removal policy to Optimize for Quick Removal so that Windows doesn't cache data to the computer before writing it to any external discs that might be connected.  In this instance, Windows waits for you to click on Safely Remove Device before it will write any remaining data to the device.  By setting it to Optimize for Quick Removal, that step is skipped and all data will be written immediately to any external devices.  I just noticed that the machine I sideloaded from was not set properly.


               

              It is a requirement that you eject the NOOKcolor as well as any installed SD card from your PC by right-clicking on them in computer or my computer prior to safely removing them.  I do this each and every time.  If you do not you will risk corrupting files on the NC.  This was not my problem and is generally not the problem some others have had.  Many have stated they've followed the instructions fully including eject.  Some people do not follow the instructions and can have problems due to this.

               

              Eject and Safely Remove Hardware are 2 different functions.  If you read up on them on the Microsoft site it explicitly says that is the case.  Eject safely stops software processes related to files that are not in use in providing a connection between the 2 devices.  Safely Remove Hardware stops processes that revolve around the connection of the 2 devices and it stops power to the connection itself.  You can get away sometimes with not doing the Safely Remove Hardware, but should always eject to make sure no files being transferred or deleted or what have you are corrupted.  This is my understanding based on what Microsoft says.:smileyhappy: