Ditching the config file

[James Liggett]

Hi all,
Now that we've ditched the config file, I'm finding myself migrating all
of my DllOverride settings to Winecfg. I have a lot of them, so this is
getting very tedious. So, I was wondering, why don't we just make it so
that if a config file is found it will read the existing overrides into
the new location, and then delete the config file? Where is the code for
reading the config file located? I'd like to get started on it--I think
it could make upgrades a lot easier.

Regards,
James Liggett

[James Hawkins]

On 7/13/05, James Liggett  wrote:
> Hi all,
> Now that we've ditched the config file, I'm finding myself migrating all
> of my DllOverride settings to Winecfg. I have a lot of them, so this is
> getting very tedious. So, I was wondering, why don't we just make it so
> that if a config file is found it will read the existing overrides into
> the new location, and then delete the config file? Where is the code for
> reading the config file located? I'd like to get started on it--I think
> it could make upgrades a lot easier.

You should be able to convert your dlloverride entries into a .reg
file and import that using regedit.  AFAIR the code for reading the
config file has been removed from wine cvs.