Versions of WOL post 2.11.16 do not respect the -p option

[Moopere]

I just downloaded and checked this against: v2.11.18 and 2.11.17 beta 30.

I was previously on 2.11.14 and use the -p option to access the machines database on a network share. Worked fine with 2.11.14 and also works with 2.11.16, but with most recent version, and .17b30 WOL doesnt load up the list of machines and the list remains empty.

[basildane]

I removed the -p option in f2888926945e3a09aded3e8697ef51927d933076. The the command line program now reads the registry to know where the database is, it is set by the GUI program automatically. This was to simplify the program and eliminate some problems. Now if you change the location of the db in the GUI, the command line program will automatically go there.

Is this not good for you? I can add the -p back in if there is a reason for it.

[Moopere]

Thanks for the heads-up. I usually scan the changes.log but must have missed that one.

Keeping this setting in the registry is fine - if it adds sanity to the cmd line + gui experience then great.

From my end, it just means I'll have to push out the registry key rather than the preconfigured shortcut at logon time - no biggy.