View Single Post
Old 01-22-2018, 04:09 PM   #15
ZodWallop
Gentleman and scholar
ZodWallop ought to be getting tired of karma fortunes by now.ZodWallop ought to be getting tired of karma fortunes by now.ZodWallop ought to be getting tired of karma fortunes by now.ZodWallop ought to be getting tired of karma fortunes by now.ZodWallop ought to be getting tired of karma fortunes by now.ZodWallop ought to be getting tired of karma fortunes by now.ZodWallop ought to be getting tired of karma fortunes by now.ZodWallop ought to be getting tired of karma fortunes by now.ZodWallop ought to be getting tired of karma fortunes by now.ZodWallop ought to be getting tired of karma fortunes by now.ZodWallop ought to be getting tired of karma fortunes by now.
 
ZodWallop's Avatar
 
Posts: 11,479
Karma: 111164374
Join Date: Jun 2015
Location: Space City, Texas
Device: Clara BW; Nook ST w/Glowlight, Paperwhite 3
Quote:
Originally Posted by Calenorn View Post
I can't point to any factor that causes the side-loaded material to be corrupted, other than that it happens after ejecting the NOOK from a computer.

I haven't succeeded in explaining the issue to B&N customer service.

One observation: after ejecting the NOOK, the thumbnails of the side-loaded books (both the newly added books AND those previously added) appear in the "New & Recent in My Library" area (top half of the home screen). They ALL seem to appear, flashing by in batches (which can take a few minutes, if you've added a lot of epubs). I suspect that the NOOK (for some reason) is recognizing all the side-loaded books as if they were brand new, which would explain why they don't show up on the previously created shelves.

It might be that interrupting this process messes up the NOOK's memory. Even when the PC tells me that it has safely ejected the NOOK, I try to wait a while before unplugging it. Personally, I wait for the NOOK to go back to its screen saver before unplugging or using it.
I've seen the same, with all books seeming to flash into the New & Recent in My Library.

If we take your guesswork and couple it with the fact that B&N obviously don't see sideloading as a main function (hence the partitioned memory), it begins to look like that's the problem.
ZodWallop is offline   Reply With Quote