Quote:
Originally Posted by macsek
Oh, it is simpler, thanks for the tip!
When I was testing your KSM upgrade scripts I started nickel (because I enabled usb and then plugged the cable in so KOBOeReader did not appear in the file manager as usual. I realized since then, that usb enable.sh should be run while the cable is connected).
|
The sequence of enabling usb and connecting to the pc should not matter. Maybe your OS (I guess Windows) needed for some reason more time as you expected when you tried. The sequence is however important when disconnecting.
Quote:
Originally Posted by macsek
So I started nickel and it asked what language I want to use, then wanted me to log in my kobo or whatever else account  , which I disregarded and restarted the device.
...
But as I don't understand why the heck it thought that moment being not registered I am not really sure if everything is really correct inside the reader software internal settings. |
This happened because you started nickel while usb was enabled. When usb is enabled, the user partition is unmounted. Therefore nickel cannot find the database and the configuration files and tries to set them up newly. Maybe I should prevent the user from trying to start nickel, if usb is enabled. Thank you for this important observation. I would have never thought of starting nickel while usb is enabled. But, of course, such a situation can occur.
Quote:
Originally Posted by macsek
I checked the device database from KSM as I have written and it answered ok. Tested from Calibre KoboUtilities as well, also answered the database is correct.
|
Thank you for testing. This is quite reassuring.