I do not use duokan as it is closed source thus problems like this are only possible to trace via trial and error rather than simply looking in the source code.

I am perfectly happy to put "DUOKAN NOT SUPPORTED" in the top link... but others have reported using Duokan in conjunction with KUAL with no problems.

Perhaps it is the order of installation that is important.
That fact remains that personally I shall not now, nor at any time in the future, be offering support that involves DUOKAN for the reasons stated above.

Perhaps it is the order of installation that is important.
That fact remains that personally I shall not now, nor at any time in the future, be offering support that involves DUOKAN for the reasons stated above.

That was my assumption too. The order of installation made the difference.

So the KUAL Launcher works now after installing it AFTER Kual. The Kual always start as a "mobi" book and not as a menu item within the Kindle OS. Is that the correct behavoiurs? Just making sure.

Quote:

Originally Posted by twobob

And frankly this is just another nail in that coffin.

Understandable. I would definitely put a disclaimer in the instructions stating that there can be issues with Duokan and KUAL

I searched my fingers off (currently I have 15 tabs open ), but I can't seem to find instructions on how to install Extensions. Can you point me to the instructions? I do NOT have an extensions folder in my root, that's why I'm asking. Do I need to create one?

I searched my fingers off (currently I have 15 tabs open ), but I can't seem to find instructions on how to install Extensions. Can you point me to the instructions? I do NOT have an extensions folder in my root, that's why I'm asking. Do I need to create one?

Again, maybe this is related to Duokan somehow. I did open the KUAL launcher but I don't remembering it creating that folder. But it's not that important, as long as I know to create it if it's not there Thx again to you guys for the awesome support!

We "shouldn't" have a bug, but... I just tested KUAL2 (front-end only) and it seems to work correctly. Unlike what I wrote before, when the extensions folder's missing KUAL2 warns the user but does not auto-create the folder. I have amended my previous post with the details http://www.mobileread.com/forums/sho...&postcount=786.

@readandread, @jacksonb, did you not see the display that I have added to #786? If you didn't then we have a bug. If you did, what part of it was confusing to you?

Hello reaper, welcome to the forum.
Create folder /mnt/us/extensions - this will be the home for all your extensions. If you connect your kindle via USB then create folder "extensions" (all lower-case letters, no quotes) in the root of your USB-mounted kindle.
If you can run KUAL then KUAL warns you when it can't find the extension folder. KUAL displays

Code:

KUAL  1
 No extensions found
Save and reset KUAL log
×Quit

where the indented items show up when you select and press the "KUAL  1" button in KUAL. If you then click the " No extensions found" button KUAL displays "help @ http://bit.ly/UW3v8V" - the bit.ly link points to this very thread.

OK. After you have managed to create the extensions folder find some extensions you like and that are compatible with your kindle model.
Follow the links in the first post to find some extensions.
Got the extensions?
Each extension is an archive file. Unpack it in a folder under /mnt/us/extensions a.k.a. folder "extensions" (all lower-case letters, no quotes) in the root of your USB-mounted kindle.
Start KUAL (again).

Hmm... I really need to overhaul the docs today to reflect this stuff...

I didn't know some of these points myself.

http://bit.ly/kualit works just fine for the link.

Got a blinder of a headache right now. Will bump heads with KNC1 later on and see about centralising the docs I think now then.