View Single Post
Old 06-06-2013, 08:21 AM   #89
electristan
newbie reader
electristan ought to be getting tired of karma fortunes by now.electristan ought to be getting tired of karma fortunes by now.electristan ought to be getting tired of karma fortunes by now.electristan ought to be getting tired of karma fortunes by now.electristan ought to be getting tired of karma fortunes by now.electristan ought to be getting tired of karma fortunes by now.electristan ought to be getting tired of karma fortunes by now.electristan ought to be getting tired of karma fortunes by now.electristan ought to be getting tired of karma fortunes by now.electristan ought to be getting tired of karma fortunes by now.electristan ought to be getting tired of karma fortunes by now.
 
electristan's Avatar
 
Posts: 102
Karma: 2122142
Join Date: Jan 2008
Location: Oslo
Device: reMarkable, Boox T68, Kobo Mini, Nook STR, Sony PRS-505
Quote:
Originally Posted by davidfor View Post
My first thought was a path length issue. The cover images files names are generated using the full path of the book plus a suffix and extension for each size. It isn't hard to get close to the 260 character FAT32 limit. But, the name used for the sleep screen cover is actually the shortest.

But, this is faking a SD card? If so, the current firmware has a bug that for books on the SD card. if the cover image file used for the sleep doesn't exist, it just uses a text cover with the title and book type on it.
This is exactly what appears. What images is used for the sleep covers? could i just ad a .png or something with the same name as the file and it will show? not to well versed in how these things work.
electristan is offline   Reply With Quote