What is the best option for a better Ereader?

[davidfor]

Originally Posted by GoldThreader

Well my plan is to be carrying everything on one device. I will keep the Kobo Aura HD in mind but it looks like it might just offer a higher resolution from what I have now.

The Kobo devices don't support a 64GB card. It is possible a firmware update will change that but I doubt that Kobo will be hurrying to do it. They are marketed as reading devices, and even 32GB is a lot of books.

As you know, they use FAT32 for the card. There is a fairly easy hack to allow EXT3 or EXT4. I don't know if anyone has tried NTFS, but it might work depending on what was compiled into the kernel. You would be able to try this on your Glo.

[ilovejedd]

Originally Posted by davidfor

The Kobo devices don't support a 64GB card. It is possible a firmware update will change that but I doubt that Kobo will be hurrying to do it. They are marketed as reading devices, and even 32GB is a lot of books.

Books, sure. Graphic novels, not so much. I can easily read a 200-page, 100-150MB volume of manga in 15 minutes or so. Sure, 32GB is still a considerably amount but likely not enough if you want to always have multi-volume favorites readily available. Heck, I carry a credit card-sized 8-slot microSD card holder with me because even 64GB isn't enough to hold all my favorites as well as my TBR pile.

[PeterT]

I'm not sure why NTFS support is a requirement. Since NTFS is a proprietary, undocumented, Microsoft format, ANY Linux / BSD support for it is risky.

Even Microsoft don't really support it on flash device.

[HarryT]

For any device which mounts as a USB mass storage device, use of the FAT32 file system is mandated - it's a requirement imposed by the standard.

[GoldThreader]

Originally Posted by PeterT

I'm not sure why NTFS support is a requirement. Since NTFS is a proprietary, undocumented, Microsoft format, ANY Linux / BSD support for it is risky.

Even Microsoft don't really support it on flash device.

NTFS is not a requirement it is something I would like though because i wont be limited to what size fie the device can read

[HarryT]

Do you have many books which are more than 4GB in size?

[mbovenka]

Originally Posted by HarryT

Do you have many books which are more than 4GB in size?

Quite :-). There is another extreme corner case where NTFS is useful, though: lots and lots of files.

I ran into it myself a while ago: I back up my Calibre library to a 128GB USB stick (FAT32 formatted, originally), and FreeFileSync suddenly started throwing errors that seemed to imply that the thing was full. It wasn't, so I was puzzled as to where the problem was. CHKDSK gave it a clean bill of health, so it wasn't file system corruption either.

Turned out it was a LFN -> 8.3 filename mapping collision.

Converting the stick to NTFS fixed it.

[Zetmolm]

Originally Posted by mbovenka

Quite :-). There is another extreme corner case where NTFS is useful, though: lots and lots of files.

I ran into it myself a while ago: I back up my Calibre library to a 128GB USB stick (FAT32 formatted, originally), and FreeFileSync suddenly started throwing errors that seemed to imply that the thing was full. It wasn't, so I was puzzled as to where the problem was. CHKDSK gave it a clean bill of health, so it wasn't file system corruption either.

Turned out it was a LFN -> 8.3 filename mapping collision.

Converting the stick to NTFS fixed it.

Another possible solution: back up your library to a folder rather than the root of your USB stick. The root supports only so many entries (files or folders) but that restriction does not apply to the number entries in a folder.

[HarryT]

Originally Posted by Zetmolm

Another possible solution: back up your library to a folder rather than the root of your USB stick. The root supports only so many entries (files or folders) but that restriction does not apply to the number entries in a folder.

The root, though, only holds 64 files. I don't think the previous poster was running into that limit.

[mbovenka]

Originally Posted by HarryT

The root, though, only holds 64 files. I don't think the previous poster was running into that limit.

No, I wasn't; the only entry in the root of the drive is my Calibre directory. And the 'maximum number of root file entries' comes from FAT16 (where it was 512); FAT32 does not have that limit, as the root directory is not a fixed structure as it was in FAT16, but an ordinary cluster chain, just like subdirecties.

What I ran into was akin to a hash collision, as the 8.3 name is in effect a hash of the long name and thus subject to the same potential problems.

[HarryT]

Originally Posted by mbovenka

No, I wasn't; the only entry in the root of the drive is my Calibre directory. And the 'maximum number of root file entries' comes from FAT16 (where it was 512); FAT32 does not have that limit, as the root directory is not a fixed structure as it was in FAT16, but an ordinary cluster chain, just like subdirecties.

Thanks for the correction!

[Zetmolm]

Originally Posted by mbovenka

No, I wasn't; the only entry in the root of the drive is my Calibre directory. And the 'maximum number of root file entries' comes from FAT16 (where it was 512); FAT32 does not have that limit, as the root directory is not a fixed structure as it was in FAT16, but an ordinary cluster chain, just like subdirecties.

What I ran into was akin to a hash collision, as the 8.3 name is in effect a hash of the long name and thus subject to the same potential problems.

Yes, I was a bit confused. Thanks for the correction indeed.

[GoldThreader]

Originally Posted by mbovenka

Quite :-). There is another extreme corner case where NTFS is useful, though: lots and lots of files.

I ran into it myself a while ago: I back up my Calibre library to a 128GB USB stick (FAT32 formatted, originally), and FreeFileSync suddenly started throwing errors that seemed to imply that the thing was full. It wasn't, so I was puzzled as to where the problem was. CHKDSK gave it a clean bill of health, so it wasn't file system corruption either.

Turned out it was a LFN -> 8.3 filename mapping collision.

Converting the stick to NTFS fixed it.

I personally really hate calibre. Too many files or too large a file and he program takes hours to load up or do anything. I have tried to fiddle with it and it just doesn't like to run with my library of books despite the formats being supported.

[GoldThreader]

Originally Posted by Zetmolm

Another possible solution: back up your library to a folder rather than the root of your USB stick. The root supports only so many entries (files or folders) but that restriction does not apply to the number entries in a folder.

Well my goal is to get it all onto one device so I don't have to fiddle with the computer or exchange micro sd cards. While putting them all into folders is easy to do it isnt exactly ideal. I want to be able to just pull my ereader out and my whole library is ready to go.

[GoldThreader]

Originally Posted by HarryT

Do you have many books which are more than 4GB in size?

I have a few yes one ran over 7GB thats when I discovered the whole FAT32 thing when I tried to stuff it onto the card. Also, even though the limit is 4GB for FAT32 it seems anything over 2 GB and my device cant read it. Once I cut it into pieces it reads it no problem but anything larger is a no go.