6" EZReader will not display EPUBs ?!?

[smallhagrid]

Correction/addition:
The problem seemed to revolve around the topmost folder being named #1.newest - and when that was cleaned up to 1newest instead, all but a single EPUB now open fine.

Apparently having 'illegal' characters in that folder name freaked the reader's OS and/or firmware out.

The EZReader remains the best choice for me...as long as I don't mess it up somehow out of ignorance.
Now it is fixed and all is well.
to All who replied here !!!

Original query follows:
I recently got an EZReader from another member here, and it appeared to work fine - but just a little while afterwards it refused to open any EPUB files at all - just sort of winks and goes back to the same menu.

This is the same no matter which EPUB I've tried.
(TXT files open fine though...)

Just put the latest Jinke f/w on there and it does the exact same thing.
Uh-oh, now I'm really worried...
Has anyone here had this problem and maybe knows how to correct it ?!?

Thanks.

[Greg Anos]

Originally Posted by smallhagrid

I recently got an EZReader from another member here, and it appeared to work fine - but just a little while afterwards it refused to open any EPUB files at all - just sort of winks and goes back to the same menu.

This is the same no matter which EPUB I've tried.
(TXT files open fine though...)

Just put the latest Jinke f/w on there and it does the exact same thing.
Uh-oh, now I'm really worried...
Has anyone here had this problem and maybe knows how to correct it ?!?

Thanks.

Are the epubs you tried to open all big omnibus editions? Try opening a small epub.

Also, are they DRM'ed? That may be the problem.

[smallhagrid]

Thanks for replying !!!
A very odd thing...the difficult titles were in a folder named #1.newest and after I tried renaming that folder to 1newest - all but one opened fine.
The single remaining EPUB that will not open (I assume...) has no DRM, but it is large - so since it begins with W I stuck it in that letter's folder & will worry about it later.
Now that the newest titles are working, it isn't any sort of emergency.

Best Wishes.

mark

[Greg Anos]

One of the quirks of epub is that different reading programs have different limitations. Most use Adobe Digital Editions for their reading software. It once had a limitation of 300K or so per file, requiring the breaking up of the text internally. Two major open source readers, Coolreader and FBReader, can't handle an Epub TOC (table of contents) greater than 50 entries. So if you reader is using one of those reading software, big omnibus will hang and then dump.

Most people are building to ADE specs and not Coolreader/FBReader specs....

[smallhagrid]

Thanks Ralph Sir Edward, for replying.
Frankly I have no idea what the EZReader uses internally to display EPUBs.
The problem persisted from the native Astak f/w to the Jinke f/w when I upgraded it - so I renamed the problematic directory as described above, and then all but a single title started working fine.
That single one I stuffed into another directory, and I'll deal with it later - much later, I hope !!!

Best Wishes.

[DaleDe]

Originally Posted by smallhagrid

Thanks Ralph Sir Edward, for replying.
Frankly I have no idea what the EZReader uses internally to display EPUBs.
The problem persisted from the native Astak f/w to the Jinke f/w when I upgraded it - so I renamed the problematic directory as described above, and then all but a single title started working fine.
That single one I stuffed into another directory, and I'll deal with it later - much later, I hope !!!

Best Wishes.

The problem you are having has nothing to do with any particular eReader but with a Unix file system. You are using illegal characters and they file names cannot be read. This can apply to folders and to files themselves. In general use ascii text for any file or directory name and you are better off if you don't use spaces, particularly in directory names. See ASCII in our wiki.

Dale

[smallhagrid]

Indeed:

Originally Posted by DaleDe

The problem you are having has nothing to do with any particular eReader but with a Unix file system. You are using illegal characters and they file names cannot be read. This can apply to folders and to files themselves. In general use ascii text for any file or directory name and you are better off if you don't use spaces, particularly in directory names. See ASCII in our wiki.

When upgrading the f/w failed to change the problem, illegal characters was my next wild guess, and did prove to correct the worst of it.

The remaining stubborn file has a very short/text-only/no spaces filename and is in a directory whose other EPUBS open flawlessly - so it is a mystery, and likely can remain so for a long time as I have much else I can read (and have that title as an audiobook as well).

As an old user from the DOS era, it took me a very long time to accept the 'enhanced' file naming ideas and I've habitually always avoided spaces in filenames because that was certain death in case of any errors back when 8dot3 was the rule...so naming the one folder #.newest was a stretch for me to start with, and will not be missed now that it has been fixed.

Thanks for replying.