jwx51v

Hopefully one of you can help me with this, it's driving me nuts.

Problem: MS Reader gives this error 'Microsoft Reader is no longer able to access the book', when I press the button to turn the page. The only way to progress past this page is to return to the library, reselect the title, then return to farthest read. This only happens if the unit has been in stanby. Once I have gone out to the library and back into the book, I can read as long as I like (I have tested this up to 1.5 hours) with no problem. If I go into standby, even briefly, the error will return anywhere from immediately to 5 minutes.

Device and software info: This is a relatively new (about 6 weeks) x51v running WM5 (5.1.70 Build 14410.1.1.3). MS Reader is 2.4.1 (build 5323). It is running the A06 firmware. I have enabled the 'server fix' that is required for WM5. The card I am currently using is a SanDisk 512mb, although problem has happend with multiple SD and CF cards. Problem does not happen when book is loaded into onboard storage (I have way too many titles to keep them all onboard).

I'm not willing to load the book I am currently reading into onboard storage from the card everytime. Just call me stubborn. I have read eBooks for years on two x5's and an x50 with no problems; I should be able to make it work here as well.

Let me be clear on one thing: I am not an WM5/x51v hater. Other than this problem, and a disppointing lack of compatiblity in the Bluetooth stack, I really like this PDA. I feel confident that one day Dell and Microsoft will get their (expletive deleted) together. In the meantime, we have only each other.

TIA,
James

aximn00b

I had a similar problem when I first started using MS Reader and the book was on the SD card. I couldn't read more than a 100 pages before getting that message. My problem was that I had to soft-reset because I couldn't restart MS Reader after exiting -- tapping the icon would do nothing, and there was nothing running in memory.

Long story short, I followed the directions in here: http://www.microsoft.com/reader/info...c.asp#nolonger and deleted the proper EBO file. Then I loaded the book back up and let it paginate until it was complete without going into standby. I'm not sure but maybe I turned it off/standby before it was done the first time so it was a corrupt file? Anyway, the next time I read it, I didn't get the message, so it worked for me. I don't know the root of the problem, but I hope that helps

fclifton

I have the same thing happening with eReader.

arshield

There is a similar problem with Mobipocket. It is not a reader problem it is a WM5 problem. It seems to bring everything back after standby, but there is a hickup with the storage cards and they come back just a few seconds after the standby brings everything else. I solve the problem by storing books to read on storage cards and then moving them to the main memory when I am actually reading a book. That seems to solve the problem.

kevingamin

Originally Posted by arshield

There is a similar problem with Mobipocket. It is not a reader problem it is a WM5 problem. It seems to bring everything back after standby, but there is a hickup with the storage cards and they come back just a few seconds after the standby brings everything else. I solve the problem by storing books to read on storage cards and then moving them to the main memory when I am actually reading a book. That seems to solve the problem.

I've had this problem with Microsoft Reader on my Axim x30 with Windows Mobile 2003 SE so it's not a WM5 issue.

jwx51v

Thanks for the replies, guys.

I would be very interested in hearing msreadergirl's thought on this. Are you out there, Chrinstine?

w3iner

Put them on a CF, that is where I keep mine.

__________________
Freedom means learning to deal with being offended!


To view links or images in signatures your post count must be 10 or greater. You currently have 0 posts.


Love Sudoku? Try
To view links or images in signatures your post count must be 10 or greater. You currently have 0 posts.
.

I am studying MS VB05 right now, so if you can give me any tips or need some help on something I would be glad to help(or try).


To view links or images in signatures your post count must be 10 or greater. You currently have 0 posts.



To view links or images in signatures your post count must be 10 or greater. You currently have 0 posts.

Don't Panic!

It's the pagination thing. IF that doen't complete before you turn Reader off you'll have that problem. So just be patient and let the book load. Hold your sty;us down on a page of a book you just loaded but haven't read before to see pagination in action.

__________________
Don't Panic!
Bobby
42
Soft-reset is our Friend
To view links or images in signatures your post count must be 10 or greater. You currently have 0 posts.

msreadergirl

Originally Posted by jwx51v

Thanks for the replies, guys. I would be very interested in hearing msreadergirl's thought on this. Are you out there, Chrinstine?

I'm here :) Everyone here has given great suggestions. When this issue pops up on WM 5.0 I most often point folks to their .ebo files and the hidden litpath.lpt file. Often these files are copied along with a bulk copy from their desktop directory to their sd card. As we all know when you purchase a title most often it will open your book on your desktop first as a means of confirming the download. When this happens it creates an EBO file and a history in the litpath.lpt file. When you copy this file to you sd card your ppc reader will try to reference these desktop points which do not exist on your PPC. Thus the error. Best policy is to copy only your books and not the annotations or litpath.lpt file. If you do just delete them. A new one will be created when you first open your titles. There are addtional suggestions up on the Microsoft Reader website.

Hope this helps!
Christine - Microsoft Reader Team