> At 18:25 15-05-09, John Adcock wrote:
>>1) Modify the installer to create a DScaler directory under All
>>Users\Application Settings with appropriate permissions so that
>>interactive users have full access to it
> Should this be under "All users"?
> Do we want one configuration for all users or not?
I thought that this would mirror the curnet behaviour and prevent each user
from having to setup the cards on the machine. I also didn't want to split
the per-user from the machine settings. It might make sense to do all
settings as per-user as at least the security will be easier. Would you see
per user settings being more expected for this kind of app? I suppose we can
say the ini's can be copied if required.
>>5) Maybe automate zipping of crashdumps, log and inis for support,
>>could be seperate tool
> I am not sure if this would really help. Most questions are asked on
> the forum, where it is easier to just add the contents of the files.
The new crashdumps are quite big unzipped, but they contain more state and
more useful for diagnosing problems.
>>6) On startup if we find an ini in the old location, move it to the
>>new one but only do this once, if we can't delete old one inform
>>user, if we can't write to this ini then inform user that it needs
>>to be removed
> I guess this can be handled best by the installer. The installer is
> (with > XP) the only time that anything under our control runs with
> the required privileges.
You're probably right.
> It would probably be best (when we decide to not have one
> configuration for all users) to move the ini file to the "All users"
> directory. On startup, DScaler looks in the user specified
> Application Settings directory. When there is no ini file in that
> directory, DScaler should look in the "All users" directory.
I wasn't sure how to do this with the scripts we use, I'll have another