On 9/23/2011 11:56 AM, AnneL wrote:
> I could use some help from any of you GoodReader folks out there!
>
> I use GoodReader as my central clearinghouse for all of my several hundred
> ebooks to keep them organized, since GoodReader has such an outstanding
> category system, using the "open in" feature to read other formats of eBooks
> in whatever app they need to, i.e. Kindle. However, the more books I have
> in the GoodReader app (and I freely admit, I have a LOT), the more often the
> following occurs: When I'm transferring books onto my iPad by dragging and
> dropping into the GoodReader app in iTunes, GoodReader seems to lock up,
> taking iTunes with it. I then get a message saying I have insufficient
> memory, although I've used less than 25% of the memory on my iPad TOTAL.
> iTunes then rebels at doing *anything* further, and if I close it, it won't
> open again. I then have to reboot my desktop computer to get things working
> again.
>
> I honestly don't know whether this is a GoodReader problem or an iTunes
> problem. I've contacted GoodReader support but haven't heard back. Nothing
> I can find in the GoodReader manual mentions a limit on the number of files
> I can have in GoodReader. I have *tons* of memory left on my iPad. And
> before anybody suggests otherwise, yes, I *do* want to keep all my ebooks on
> my iPad. It would be a different matter if I could keep them on a memory
> stick and just plug them in, but Apple has seen fit to make that impossible,
> so my library has to stay ON the iPad.
>
> Has anybody had this problem and can offer any insight?
>
I have this problem when I am loading a lot of files into ForScore, so
I'm pretty sure it's an iOS/iTunes problem and not specific to GoodReader.
What I have to do is to reset my iPad (homebutton plus power switch held
until the Apple logo comes up) and then all is well and I can keep on
loading files. If I have a lot to load, it will happen several times
before I get them all loaded.
I had contacted the ForScore tech support people and they said it was an
iOS problem and they've been trying to resolve it.
You are not alone in your frustration.
--
David H. Bailey
dhbailey@davidbaileymusicstudio.com
