View Single Post
Old 06-08-2011, 11:03 PM   #395
Jad
Groupie
Jad has learned how to read e-booksJad has learned how to read e-booksJad has learned how to read e-booksJad has learned how to read e-booksJad has learned how to read e-booksJad has learned how to read e-booksJad has learned how to read e-books
 
Jad's Avatar
 
Posts: 152
Karma: 772
Join Date: Mar 2008
Location: Perth, Western Australia
Device: Cybook Gen3
Mobi2MobiGUIv10beta - Null DATABASENAME fix for AZWs

Okie doke.. Thanks to my handy HexEditor I was able to replicate the missing DATABASENAME error in the AZW files. The way the GUI works is that it creates a temporary working copy of the PRC/AZW/MOBI file when you initially open the original. It creates a text dump of the Mobi2Mobi output and parses that information. Because the dodgy AZWs can't be output to a new file without a valid DATABASENAME entry the various files don't get created and the parsing routines all die and create and exception error. I've created a workaround that checks to see if the Mobi2Mobi output file has any data, if its empty and the file type is AZW then it assumes the DATABASENAME is dodgy and fixes it by using the AZW filename as the default. It then re-runs all the parsing on the updated file and it all works. Can those with issues please give this ago and let me know if it sorts out your problems. I'll probably need to add an option in somewhere to allow modifying the DATABASENAME entry so you can change it to something else if you don't like the default.

Edit: Oops.. Just unzip the new EXE into the same location as your original Mobi2MobiGUI_VB.EXE and run it.
Attached Files
File Type: zip Mobi2Mobi_GUI_VB_10beta.zip (25.8 KB, 523 views)

Last edited by Jad; 06-08-2011 at 11:16 PM.
Jad is offline   Reply With Quote