[inireloc 20040916] Issues related to inireloc

[white]

Filename for wcx_ftp.ini file defaults to wincmd.ini

1. Export registry keys:
   • HKEY_CURRENT_USER\Software\Ghisler
   • HKEY_LOCAL_MACHINE\SOFTWARE\Ghisler
   • HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Ghisler
2. Delete registry keys mentioned above.
3. Start inireloc tool.
4. Choose "Yes" to assign different locations of wincmd.ini and wcx_ftp.ini
5. Choose locations and continue. In the final screen you see that the wcx_ftp.ini file is named wincmd.ini (screenshot)
6. Restore registry by importing the exported keys in step 1.

[ghisler(Author)]

The tool was meant to change the ini locations, it doesn't work when there are no locations at all. I will check whether I can add it, thanks.

[white]

Moderator message from: white » 2023-02-09, 11:59 UTC

Reply seems to have been posted in wrong thread. Moved it from [inireloc 20040916] Filenames of ini files not always displayed to here.

[ghisler(Author)]

This should be fixed in inireloc 2 beta 1, please test it:
https://www.totalcommander.ch/beta/inireloc2_beta1.zip

I have made the following changes:
20241121 Fixed: Long paths were cut in final confirmation dialog
20241121 Fixed: When saving ini file locations for all users, save them both for 32-bit and 64-bit versions
20241121 Fixed: When running the tool before the Total Commander installer (no registry entries present), both ini files were set to wincmd.ini

[white]

20241121 Fixed: When saving ini file locations for all users, save them both for 32-bit and 64-bit versions
20241121 Fixed: When running the tool before the Total Commander installer (no registry entries present), both ini files were set to wincmd.ini

Confirmed fixed with fixed in inireloc 2 beta 1.

You also changed the default location for the ini files. Shouldn't that be in the changelog as well?

I encountered other bugs and issues. Do you want separate bug reports for that? Or do you want 1 thread about inireloc issues?

[ghisler(Author)]

You also changed the default location for the ini files. Shouldn't that be in the changelog as well?

I will add it.

I encountered other bugs and issues. Do you want separate bug reports for that? Or do you want 1 thread about inireloc issues?

I prefer if you posted them in this thread to not clutter the forum about the Total Commander beta test with unrelated reports.

Also I'm busy with the main beta test, so I prefer if you didn't report unimportant things like a line being one pixel too high or low.

[white]

2 radio buttons can be enabled at the same time.

Steps to reproduce:

• Start inireloc and click Next until you reach the dialog to set the new location for wincmd.ini and wcx_ftp.ini
• The radio button for "Application data" is the default now.
• Don't change it, but click the "..." button to select a user defined folder.
• Select a folder and click OK.

Screenshot

[ghisler(Author)]

Confirmed, it's because I added one extra button "Application data".

[white]

Moderator message from: white » 2024-11-26, 08:59 UTC

Split posts to new topic: Add version info to Inireloc tool

Moved this topic back
» from TC suggestions (English) to TC11.x bug reports (English)

[ghisler(Author)]

Here is beta 2 where I fixed the two selected radio buttons:
https://www.totalcommander.ch/beta/inireloc2_beta2.zip

[white]

You also changed the default location for the ini files. Shouldn't that be in the changelog as well?

I will add it.

Not added to readme.txt

20241124 Fixed: Ini location page: More than one radio button could get selected

Tested OK using inireloc 2 beta 2.

[ghisler(Author)]

I have added the missing line to the readme file now:

20241121 Fixed: Changed default ini locations to match the main installer

[white]

I have added the missing line to the readme file now:

20241121 Fixed: Changed default ini locations to match the main installer

Confirmed.

[ghisler(Author)]

Thanks! Any other problems? Otherwise I will release the final version of inireloc 2.

[white]

Thanks! Any other problems? Otherwise I will release the final version of inireloc 2.

Well, you said not to bother you with unimportant things so I kept my mouth shut about other things. But since you're asking..

1. The second dialog has a duplicate access key (N) which causes a bit of a strange behavior. I suggest to use access key o for "No", if possible.

2. In the dialog where you set the location of the ini files, the location of the Help button is unusual. It may have been appropriate at the time to give it a prominent place and the receive focus when the dialog opens, but not anymore. I think moving the Help button to the bottom where the other buttons are, is better. Furthermore, the Help button opens a warning dialog (with a bell sounding) instead of an information dialog.

3. In the dialog where you set the location of the ini files, the tab order deviates from the other dialogs. In this dialog the tab order is from top to bottom and from left to right, which is common for programs, including installers. In the other dialogs the Initool uses tab order: Next, Cancel, Back, Options. Most installers use a normal tab order and the Next button as default button. I recommend to do the same for all dialogs. I suggest to use that too for the TC installers, which behave similar to the Initool (and contain bugs in the tab order as well).

4. "<< Back" and "Next >>" are unusual too. Most installers use a single < or >.

5. The ">>" indicates that more dialogs will follow before the installation is started. With most installers the "Next >" button in the last dialog changes into a "Install" button (without >). The Initool and the TC installers behave incorrectly in that regard.

6. In the last dialog before the actual changes are applied, an overview is given of the changes to be made. This overview should mention, per location, if the location is set for the current user or all users. And it should also mention the location of the install folder that is about to be written to the registry and wincmd.ini file.

7. Why would the Initool add a location of the install folder if there is none?

8. The location of the install folder in wincmd.ini gets overwritten by the location set in registry, or the default location if there is no location set in registry. This seems problematic to me.