MobileRead Forums - View Single Post

theducks · 10-10-2015, 04:56 PM

I am NOT using 8.901 (i REVERTED TO 8.7)
That scrambled the split order for me on w10

I used to have this problem back in Valoric's reign. It was only happening (reported) to me which was why it took so long

If I started with a book from Calibre that was split only because a section exceeded 260K, it happened when I pressed F6

file1
file2
file3

resulted in
file1
file2
file3
file1_split 001
file1_split 002
file1_split 003
file1_split 004
file1_split 005
file2_split 001
file2_split 002
file2_split 003
file3_split 001
file3_split 002
file3_split 003
file3_split 004
file3_split 005

Always Use a file (re)naming convention that allows for a (right click) alphanumeric sort.
Random applied splits will result in the next available Section### being assigned, which lessens your chance of easy recovery

10-10-2015, 04:56 PM	#8
theducks Well trained by Cats Posts: 31,121 Karma: 60406498 Join Date: Aug 2009 Location: The Central Coast of California Device: Kobo Libra2,Kobo Aura2v1, K4NT(Fixed: New Bat.), Galaxy Tab A	I am NOT using 8.901 (i REVERTED TO 8.7) That scrambled the split order for me on w10 I used to have this problem back in Valoric's reign. It was only happening (reported) to me which was why it took so long If I started with a book from Calibre that was split only because a section exceeded 260K, it happened when I pressed F6 file1 file2 file3 resulted in file1 file2 file3 file1_split 001 file1_split 002 file1_split 003 file1_split 004 file1_split 005 file2_split 001 file2_split 002 file2_split 003 file3_split 001 file3_split 002 file3_split 003 file3_split 004 file3_split 005 Always Use a file (re)naming convention that allows for a (right click) alphanumeric sort. Random applied splits will result in the next available Section### being assigned, which lessens your chance of easy recovery