UPDATE (04/06/2008): I have some very good news for you all.
1. Several of my readers have asked (see for example
THIS) whether it’s possible to change the page save directory in Opera Mini 4.1 after you’ve set it first. Contrary to the popular belief (you must reinstall it from scratch), it’s actually very easy to do this:
a. if you have originally selected a removable storage card as the target media, you only need to remove it before trying to save any page on it. Then, you’ll be prompted an error message and, on the next page saving attempt, you’ll be offered the chance of setting the new save directory. That is, if you’ve originally given Opera Mini a storage card, you can change the save path without any need for hexediting files.
b. if you have provided it with a movable / deletable directory in the built-in storage (or, for that matter, on the storage card), just move (cut / paste) the entire directory somewhere else on your device – or on your storage card. That is, if you’ve given
\My Documents to it, just cut it with the built-in File Explorer and paste it to in any other subdirectory. (Of course, you’ll need to paste the directory back once you’re ready with the – failed – page saving attempt if it’s a directory used by other apps too – like
\My Documents.)
3, if, for some reason, neither of the above-listed ways works, you’ll need to do some hexediting. To do this, search for the in the name of the directory in the
\Windows\appdb\s?__d?.db files with, say, Total Commander (Alt-F7) on the desktop Windows and just change this occurrence to another directory with a hexeditor. An example showing changing
\My Documents to
\Storage Card with a hexeditor:
Again, it’ll be FAR easier to temporarily remove / move the directory than hexediting – only do the latter if you simply can’t (temporarily) delete the directory because you’ve given it, say, \Windows or some other, undeletable directory.
2. the native C++ version of the invocation script
has been updated to be compliant with 4.1. In addition,
badbob001 has updated his MortScript to be compatible with 4.1 and he is also doing automatic (!!!) descriptor parsing & discovery to automatically find the current position of the OM deployment (just like the
JZ SmartMort's brand new script I've reported on above), which, so far, needed to be done (once) by hand. See his updated script
HERE. Both advancements are discussed
HERE, starting with page 10 (post #91).