A little bit more on "tricking" Calibre to do what you want. These tips refer to an html source file (it's how I roll) but it's all essentially the same process even if you use a different format.
For people who are having problems getting devices to recognise the "start" position for their text (the point the book should first open at, and the point it jumps to when you select "Beginning" from the guide menu:
Once you have converted the book in Calibre, open your Calibre Library and find the folder for that book. There will be a .zip file in there that contains all the resources used to build the .mobi file. Open this, and extract the file content.opf.
You should find either a pair of <guide> </guide> tags (if Calibre has placed any guide items in the file), or a self-closing <guide/> tag (if it hasn't).
In the first case you are fine to carry on, but if you have a self-closing <guide/> tag in there, change it to <guide> </guide>. Note the subtle difference in the placement of the / character!
Between the guide tags, add this line:
<reference type="text" title="Beginning" href="your_book_file.html#start" />
Save and close the file, and then drag it onto the zip file it came from to replace the version that's in there.
Then convert again. Calibre only builds the content.opf file once but references it each time you convert the book, so next time you convert your change will be reflected in the new .mobi file that is produced. You can check it works in the downloadable previewer or by sending it to your devices from Calibre. Please note that Amazon's online previewer might still ignore the start point even though it works on real devices! The built-in Calibre book viewer will also ignore it.
Note that you must have an anchor in your html file for the #start position.
Because I use a CSS style that places a page break before every top level heading tag, instead of using a real link anchor tag I just assign the property id="#start" to the H1 tag of the prologue or first chapter.
You can use the same sort of trick with the table of contents.
The Calibre help pages imply that you must use the Calibre-generated toc, or the world will end. Not so. You can get Calibre to use your own html table of contents to populate the ncx (which of course means that the "Table of Contents" entry in the device's "Go To" guide menu will point to it).
All you do is use the same method as above, and add this line to the content.opf file:
<reference type="toc" title="Table of Contents" href="your_book_file.html#TOC" />
Then when you go to convert the book, in the Table of Contents tab uncheck "Force use of generated table of contents" and set "Number of links to add" to zero. In the MOBI output tab, tick the box for "Do not add table of contents to this book". Again, when you reconvert, Calibre will check the content.opf file, see the reference tag, and in the output MOBI file it will reference your own table of contents as the guide item for devices.
Note that you must have the #TOC anchor in your html file pointing out the start of the Table of Contents page.
Also if you have made changes to your book's source file the easiest way to update it in Calibre before doing a conversion is to simply drag the new file onto the book's zip file in Calibre's library.
JTbigtoad many thanks for that info, I've followed this guide for creating a MOBI6 file . My book got published about 4 hours after the upload.
The perfect TOC was so very important for me >>thanks,thanks,thanks!
That was the point ,the Hand Build toc - since I haven't opted for a "Plane Jane" table of contents but for cpecial double meaning chapter titles. And it worked , a total navigation was obtained. Thanks again