Quote:
Originally Posted by j0el
HarryT, Thanks for moving my post. My instinct was to put it in developer, but I hate to bother developers.
encol, your instructions were perfect. I downloaded the zips, moved them into the root of the Kindle, then unzipped them by double clicking. I think the problem was that it created a new subdirectory first. Anyway, if there is not a post showing what the directory structure should look like when a few extensions are added, it would be nice for someone more expert than I to create one.
Thanks for getting me going. I appreciate your time and effort.
/joel
|
With the only exception that I can think of being kTerm and maybe KOreader, any of the archived KUAL extensions are packed so that they only have to be un-archived in the topmost, visible, level of the USB storage.
Each will create an extensions/<add-in name> sub-tree.
It does not need a diagram, only reading and following directions.
Any of our add-ins that are packaged in an update_*.bin name format must be installed using MrPI - -
Re-read Step #8 of the current jail break.
Those packages all have scripting that will do the thinking for you.
= = = =
That horrid mess you made a screenshot of is because you have your MAC OSx archive handler in "stupid" mode - so that it first creates a directory named the same as the source archive.
You should have an option to disable that overly helpful "feature".
Disable that feature of your archiver -
Delete that mess you added -
The just place the
Contents of the archive in the top level of visible USB storage.
No diagrams needed, just set the archiver so that it does not precede the content's directory structure with a directory named after the archive.
Check the download counts of the packages you download and the view counts of the threads that describe them - then think:
Could that many people have installed these without a diagram?
Or is there something local wrong with what I am doing? (PEBCAK)