View Single Post
Old 12-29-2017, 10:12 AM   #136
raindog89
Connoisseur
raindog89 can successfully navigate the Paris bus system.raindog89 can successfully navigate the Paris bus system.raindog89 can successfully navigate the Paris bus system.raindog89 can successfully navigate the Paris bus system.raindog89 can successfully navigate the Paris bus system.raindog89 can successfully navigate the Paris bus system.raindog89 can successfully navigate the Paris bus system.raindog89 can successfully navigate the Paris bus system.raindog89 can successfully navigate the Paris bus system.raindog89 can successfully navigate the Paris bus system.raindog89 can successfully navigate the Paris bus system.
 
Posts: 52
Karma: 36726
Join Date: Nov 2017
Location: New York City
Device: Kobo Clara HD & Nook Glowlight 3
Quote:
Originally Posted by aronchav View Post
I just wanted to update this USB issue now that I've had a few days to play with it. I noticed that on the eject menu for windows, there are two items: Eject BNRV520, then under that Eject USB Drive (F). File explorer is listing the device as USB Drive (F).

If I eject BNRV520, I get the problem we've mentioned -- the usb screen does not go away and the device is not removed reliably. But if I eject USB Drive (F), everything is fine and the usb connection screen goes away as it should.
Yes I have verified this is the case, in Windows at least. Actually, from the System Tray (on the bottom left) I only have one option, as the lower item, the USB Drive, is grayed out and not selectable. But from within Windows Explorer, I see two enumerations of the drive, one under My Computer, and one as an independent drive. They both have Eject menu items, If I use the Eject function from the independent drive, the regular screen on the Nook comes back quickly.

But that reinforces my belief that their is some "kluge" in how they removed the partitioning. With my experience with drive partitions, I was surprised to see they could address this with a software update. And my nook drive has gotten corrupted twice already. (Fixable by a factory reset.) This happened for the second time last night after the battery totally discharged itself quite rapidly. I am left to think that there is some duct tape workaround where they are somehow sharing an otherwise still hidden partition.

A more thorough expert on partitioning and file access can weigh in, but I am starting to appreciate the delay B&N is having on releasing this update publicly and that they are actually doing real testing.

I almost wish I had the last official update (4.8.2 ?)to load again, until they work out the kinks. Anybody here manage to snag it?

Last edited by raindog89; 12-29-2017 at 11:15 AM.
raindog89 is offline   Reply With Quote