Thanks a lot for investigating this.

sequence of events haven't changed since very beginning of Maemo - I always wondered, how SMSCON is supposed to achieve that. I suppose, that no one tried this before

USB cable connection won't change that - lock code is persistent even after reflash (although, not asked on boot). there *is* a hackish - yet, 100% safe and working - way to reset lock code to default, by placing certain file in appropriate directory and running it - I don't remember exactly, as it was one of first things I was doing with my N900 (seller had no idea about code he set, and re-gaining it wasn't possible - DES encrypted hash wasn't present at all [!]), but it was something about writing actual asterisks as lock code. Could re-find that utility, if needed.

Although - while it, probably, would allow SMSCON to reset lock code and disable asking for it on boot - it still doesn't answer, how we may achieve that, as different SIM card is recognized (and enabled, at all) *after* prompt for lock code.
---

I really hope, that someone will get an ingenious idea, as for now, it makes - sadly - smscon quite unusable in pair with lock code. First thing thief/people buying is going to do, if prompted for lock code on boot, is to - probably - flash device, which get rids of smscon :/ Our only "chance" to fool them into running N900 with SMSCON, was by providing access to device functionality, when it's stolen.

On the other hand, lock code is *very* essential for other anti-thievery things, like keeping personal files/photos/whatever in encrypted partition, mounted on boot via truecrypt. Such partition is unmounted on every reboot, so short lock code time ensure that - no matter what, even after complete reflash - no one will have access to our encrypted partition/container.

Add to this other use cases for lock code, and we have serious dilemma :/

/Estel