MobileRead Forums - View Single Post

NiLuJe · 10-27-2018, 02:11 PM

@davidfor: Yeah, the switch to WAL was generally a Great Thing(TM), for a whole lotta reasons

.

That leaves onboard's FS as a weak link, but switching away from FAT32 is kind of unrealistic (at least for the masses), unfortunately

.

Amazon's approach was to hide the db away in a separate ext* partition, which is great for reliability and performance, but absolutely terrible for customization, since we lost direct access to the db during USBMS.

----

To get back to the issue at hand, while I did encounter some weird USB being terrible issues at one point or another, I don't think I've *ever* had any issue since switching motherboard a while ago.
I've been using USB 2.0 ports in both cases, FWIW, and my issues were pretty much tied to the mxc platform in general, so, Kobo, Kindle, whatever, didn't make much difference

.

10-27-2018, 02:11 PM	#30
NiLuJe BLAM! Posts: 13,506 Karma: 26047202 Join Date: Jun 2010 Location: Paris, France Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E	@davidfor: Yeah, the switch to WAL was generally a Great Thing(TM), for a whole lotta reasons . That leaves onboard's FS as a weak link, but switching away from FAT32 is kind of unrealistic (at least for the masses), unfortunately . Amazon's approach was to hide the db away in a separate ext* partition, which is great for reliability and performance, but absolutely terrible for customization, since we lost direct access to the db during USBMS. ---- To get back to the issue at hand, while I did encounter some weird USB being terrible issues at one point or another, I don't think I've ever had any issue since switching motherboard a while ago. I've been using USB 2.0 ports in both cases, FWIW, and my issues were pretty much tied to the mxc platform in general, so, Kobo, Kindle, whatever, didn't make much difference . Last edited by NiLuJe; 10-27-2018 at 02:18 PM.