Startup Delay Due to Lock File

[Blech]

Hi,

I just updated to a new version of SMPlayer and like every other time I had to delete the smplayer.ini in C:\Program Files\... manually because otherwise SMPlayer takes forever to load because it spends 10s or so trying to create a lock file in Program Files.

This seems to be a general problem on any Windows (Vista and 7) that doesn't give users write access to Program Files and it's been an issue since I started using SMPlayer. Isn't there some way to solve this issue (e.g. no smplayer.ini in Program Files by default)? I love the player but it makes it hard to convert other people, especially the less technically inclined. =)

Is there a reason for this behavior? Google didn't find anything useful.

[rvm]

I'm not sure if it would help, but try to use the portable version instead.

[Blech]

Thx for the reply. If you mean smplayer_portable.exe, that's what I'm using.

As I said the fix is easy, just remove the system-wide smplayer.ini because then SMPlayer doesn't try to set a system-wide lock. (what's the point of the lock-file btw? I allow multiple instances, so what is it locking exactly? The per-file database? But that is a user specific setting, too)

I'm just saying that it is a annoying issue that has the side effect of making it harder to recruit new users (because the .ini reappears after updates and now and then for no reason I can discern). And as I see it, it *should* be easy to fix (no system-wide config in Program Files).

I just don't know if the file's there for a reason. =)

[rvm]

The lock is used to avoid several instances to initialize at the same time.

I'll take it a look because maybe the lock file it's not being created where it should.