INI and non-Administrator accounts

bluemouse · 2007-10-23 15:58

Please consider allowing the settings to be separately saved for each different user.

I understand the wish to keep the application executable portable.

Perhaps something like the zero-byte WinHex.RGT file which flags WinHex to save settings into the user's registry. Or, even saving into ReNamer.INI in user's APPDATA would be nice.

Thank you for this really useful software!

den4b · 2007-10-23 21:43

This has been already discussed on these topics:
Some suggestions for Shutter & Renamer
Vista vs ReNamer

I am considering adding this option in the future, but it is not a first one on the list...

bluemouse · 2007-11-16 16:03

Thank you for your positive response. I hope you can find a way to add this without too much effort.

As a workaround here, I thought about doing the following...

In another thread you mentioned that the INI file would automatically share the same basename as the EXE file.

So, instead of having multiple (per-user) copies of the whole installation folder, I thought I would just create multiple (per-user) NTFS hardlinks within the main (single) installation folder. This way, each user could invoke their own specially named EXE, and get a separate INI automatically. For example, RENAMER-A.EXE, RENAMER-B.EXE, etc. all hardlinked to RENAMER.EXE . Then User A gets RENAMER-A.INI, etc.

However, there is a slight difficulty in that it is not sufficient to make each INI file writeable (modify permission) for the corresponding user. I think the app will first delete an INI file, then attempt to create a new INI file, when saving modified settings. This fails, unless the whole installation folder has much loosened NTFS permissions, which allow ALL users to delete & create files in the installation folder.

Would it be possible (and hopefully trivial) to just zero an existing INI and re-write the new settings?

Just wondering...

Stefan · 2007-11-16 19:10

Hi bluemouse,

out of curiosity what is such an option good for?

With 2,5 MB ReNamer is small enough so each user could have his own ReNamer-folder,
even if you have 10 users on one PC you would have only 25 MBs spend.

Would you please enlighten me?
CY
Stefan

Fathom · 2007-11-16 19:51

Hey Stefan

I have many long complicated presets, requiring different option settings. Some presets when run with the wrong option setting have horrible catastrophic results.

I can not easily remember which presets need what settings and don't always remember to change them, change all the settings needed, or remember if I have already changed them, or changed them correctly.

One preset may operate on folder names, for another that may be catastrophic, same with system files, or whether to operate on sub folders or if Natural Sort is required, etc. For most advanced users one setting is NOT appropriate for all presets.

It would extremely nice to have the perquisite setting saved with each preset. Implementing this now is easier said than done.

Currently the way I "load ReNamer with specific preset with specific option/filter settings" is via a different batch file for each preset, described here http://www.den4b.com/forum/viewtopic.php?id=357. Another way I may eventually adapt is using AutoIt which can read and write specific .ini sections. It could also sort the name column if needed when I start a preset with Natural Sort from another application (otherwise I have to manually click a column to be sorted, then click preview before I can click rename, otherwise I may end up with an unrepairable mess and never realize it until I need those files).

I don't get why or how any of this would have to do with "users". It is the individual presets that are at issue, not who is using them, unless each user needs a different setting and that one setting works for all their presets.

Last edited by Fathom (2007-11-16 21:27)

Stefan · 2007-11-16 21:25

Fathom wrote:

Hey Stefan
I don't get why or how it would have to do with "users". It is the individual presets that are at issue, not who is using them.

Thanks for your answer, Fathom.

My curiosity was because bluemouse want to have different ini's for one installation.
For bigger applications this would make sense but i don't understood this for such an "private" tool
like an renamer which each individual would use in an other way with other (own) presets and scripts.

That settings should be stored along with filters and default start folder into the presets is logic and consistent
as i had agreed already by reading your posts in silence.
(i may had should post my opinion but i am not at this point of use right now)

So was your post an answer to my question to bluemouse (or are you bluemouse too?)

Sorry for my poor english if i had use not the right words.

Stefan

Last edited by Stefan (2007-11-16 21:27)

Fathom · 2007-11-16 22:31

So was your post an answer to my question to bluemouse (or are you bluemouse too?)

No Stefan, I'm just rambling, I have no good answers, just sharing some thoughts (and frustration)

I use a different .ini for each preset. I set that up after one disastrous experience with ReNamer.

I use a different "batch file" to load each given preset, (it "swaps out" my default settings for the one required by this preset, then swaps the default setting back in when I close ReNamer). I use one installation with multiple startup (batch) and initialization (.ini) files.

Just another way to get the same result. Each preset has its own specific option/filter settings. It is the only way I feel safe using most of my presets now. I absolutely refuse to rely upon memory and habit to check/set options correctly anytime I use a preset, that has proven unworkable for me.

Now you bring it to mind, multiple installations may have added benefits of having presets grouped by setting requirements AND the ability to use the "Send To" (Windows context menu) to a choice of these different ReNamer's. I might need only three installations of ReNamer for all the presets I have. I may give that a try.

I do not see the need for ReNamer to be portable... maybe in a large corporate environment? but I would think corporate software would be used (PowerGrep, TextPipe?). I DEFINITLY see the need for a preset to operate as intended. I vote for presets eventually [storing/embedding/linking] their settings. I am more than a little paranoid about using ReNamer after a couple of mishaps because of left over settings from some other preset.

delerious · 2011-03-26 04:25

I too would like to see the option to store all the ReNamer settings in the %APPDATA% directory. Is this any closer to being implemented?

Stefan · 2011-03-26 11:08

delerious wrote:

I too would like to see the option to store all the ReNamer settings in the %APPDATA% directory. Is this any closer to being implemented?

Why you wanna do that?

delerious · 2011-03-26 17:51

On my machine I have an Administrator user that I only use for installing apps, and a non-admin user that I use for everyday purposes. It's just a little more secure that way, since I typically don't need admin privileges to do things. But then if ReNamer keeps its settings in the install dir, which defaults to C:\Program Files\ReNamer, then my non-admin user does not have permission to change the settings. If the settings were stored in %APPDATA% though, then the non-admin user wouldn't have that problem.

den4b Forum

#1 2007-10-23 15:58

INI and non-Administrator accounts

#2 2007-10-23 21:43

Re: INI and non-Administrator accounts

#3 2007-11-16 16:03

Re: INI and non-Administrator accounts

#4 2007-11-16 19:10

Re: INI and non-Administrator accounts

#5 2007-11-16 19:51

Re: INI and non-Administrator accounts

#6 2007-11-16 21:25

Re: INI and non-Administrator accounts

#7 2007-11-16 22:31

Re: INI and non-Administrator accounts

#8 2011-03-26 04:25

Re: INI and non-Administrator accounts

#9 2011-03-26 11:08

Re: INI and non-Administrator accounts

#10 2011-03-26 17:51

Re: INI and non-Administrator accounts

Board footer