XYplorer Beta Club

highend wrote: ↑09 Sep 2024 09:51 Doing the same from an ancient 26.20.0000 changes the values but I have no time to test dozens of versions to see on which one the change actually happens...

If by "Doing the same" you mean upgrading (via self-update) from 26.20.0000 to 26.40.0000, I cannot confirm this. So, it's getting weirder.

They do change from (both) 1 to 0 when upgrading but I'm not sure if the screenshot from the first post does really reflect the situation.
The latest version is on the right (at least that's what the left / right title states) and then it would have changed from 0 to 1 which I can't confirm...

I checked it for the example of ShowCDROMDrives
This entry is 0 for me, and it wasn't changed with any update.
I have a ZPAQ backup with many versions for all files of XY.

No change here, not from 1 to 0 nor from 0 to 1.

Try with portable version.

Also, you can try checking after removing the files in auto backup folder in the application data.

There is no "portable version" that makes any difference here. The executables are the same no matter how portable they are installed.

SaiKarthik wrote: ↑09 Sep 2024 12:43 Try with portable version.

Also, you can try checking after removing the files in auto backup folder in the application data.

I always use the portable version, but this doesn't make any difference here.
The Auto backup folder only gives you the diff from previous day or version.
My ZPAQ archive gives me any previous version of any XY file.

OP: Can you send me the original pre-v26.40.0000 XYplorer.ini file from your backup folder? I suspect there may be a particular value that caused an error after which other values reverted to defaults.

attached the ini file.

Thanks. This explains it. Your backup INI has the LastVer field empty (it should contain the XY version number when this INI was last saved): This causes lots of upgrade (starting with v16.00.0232) compatibility codes to kick in.

The question is: Why is the LastVer field empty?

But I just refer this main setting values like custom buttons and some enable/disable options.

But the actual settings file has 23.30.4000 as value.

SaiKarthik wrote: ↑11 Sep 2024 13:37 But the actual settings file has 23.30.4000 as value.

Of course, I need the actual settings file. Why should I run a test with some non- actual settings file?

here is the file

Thanks.

Yes, some INI values are changed by upgrade compatibility measurements (and a few of them are indeed incorrectly changed -- I will fix that ), but the values you were talking about (ShowCDROMDrives, WatchDevices) are NOT changed. So, there remains a bit of a mystery, but some little bugs can be removed.

Thanks for the help and very quick responses. Really appreciate that.

Is there a way that I can have guide for these settings.