Setting DllOverrides by script

[Bill Medland]

I stopped concentrating for quite a few months and now the whole config system 
has changed.!!  Any chance of some help?

When we released the previous version of our product on Linux we included a 
couple of perl scripts etc. for setting up the Wine suitably, including 
adding a couple of drives, setting the path, modifying dll overrides.

Now I am trying to figure out how to do it all with the new config system.

Doing the drives is easy; a couple of symlinks.
Doing the path is easy; regedit /s /E and regedit /s <filename>

The problem I am having is with the DLL overrides.
I see that they are now based on HKLM\Software\Wine\Wine\DllOverrides.
How do I get them in?
It seems to me that the only way that works is to edit the config itself and 
then restart the wineserver.  Is that correct?  (If so the no big deal)
(I can't seem to import into the config using regedit nor can I actually edit 
the subtree under the GUI)

[Vincent Béron]

Le ven 01/10/2004 à 22:20, Bill Medland a écrit :
> I stopped concentrating for quite a few months and now the whole config system 
> has changed.!!  Any chance of some help?

I'll try, but not knowing what's your last known setup it might be not
that complete.
> When we released the previous version of our product on Linux we included a 
> couple of perl scripts etc. for setting up the Wine suitably, including 
> adding a couple of drives, setting the path, modifying dll overrides.
>
> Now I am trying to figure out how to do it all with the new config system.
>
> Doing the drives is easy; a couple of symlinks.

Drives and devices are symlinks in ~/.wine/dosdevices, pointing to the
Unix one. Devices names for drives (like cdrom) are of the "d::" format,
with a double colon, while other DOS devices are just the name ("com1",
"lpt1"), all pointing to the corresponding /dev entry.
> Doing the path is easy; regedit /s /E and regedit /s <filename>

Setting the path env-variable for Windows apps? Or app-specific paths?
If the latter, wouldn't it be easier to provide a .reg to do that
instead of exporting the whole registry?
> The problem I am having is with the DLL overrides.
> I see that they are now based on HKLM\Software\Wine\Wine\DllOverrides.
> How do I get them in?
> It seems to me that the only way that works is to edit the config itself and 
> then restart the wineserver.  Is that correct?  (If so the no big deal)
> (I can't seem to import into the config using regedit nor can I actually edit 
> the subtree under the GUI)

Those (dlloverrides) are still in config, look at
documentation/samples/config. You can set them globally or on a per-app
basis. They can also be set as a Unix env-var, WINEDLLOVERRIDES, for
quick one shot deals.

Vincent

[Bill Medland]

----- Original Message ----- 
From: "Vincent Béron" 
To: "Bill Medland" 
Cc: "Wine devel" 
Sent: Saturday, October 02, 2004 10:33 AM
Subject: Re: Setting DllOverrides by script
> Le ven 01/10/2004 à 22:20, Bill Medland a écrit :
> > I stopped concentrating for quite a few months and now the whole config

system
> > has changed.!!  Any chance of some help?
>
> I'll try, but not knowing what's your last known setup it might be not
> that complete.
> > Doing the path is easy; regedit /s /E and regedit /s <filename>
>
> Setting the path env-variable for Windows apps? Or app-specific paths?
> If the latter, wouldn't it be easier to provide a .reg to do that
> instead of exporting the whole registry?

Don't worry about this one;I have it all figured.  Of course I only export
HKCU\Environment; grep out the path, create a 4-line reg file and reimport.
(Surely one can't just provide a .reg for the path; additions have to be
merged into what is already there.)
(I also note that the
HKLM\System\CurrentControlSet\Control\SessionManager\Environment\Path
doesn't do anything yet)
> > The problem I am having is with the DLL overrides.
> > I see that they are now based on HKLM\Software\Wine\Wine\DllOverrides.
> > How do I get them in?
> > It seems to me that the only way that works is to edit the config itself

and
> > then restart the wineserver.  Is that correct?  (If so the no big deal)
> > (I can't seem to import into the config using regedit nor can I actually

edit
> > the subtree under the GUI)
>
> Those (dlloverrides) are still in config, look at
> documentation/samples/config.

Yes, and that is mounted into the registry as HKLM\Doftware\Wine\Wine.!!!
> You can set them globally or on a per-app
> basis. They can also be set as a Unix env-var, WINEDLLOVERRIDES, for
> quick one shot deals.

Yes,I understand that.

My question was to do with the mechanisms available for modifying them.  You
seem to be confirming my suspicion that the only way is to edit the config
file itself and restart the wineserver; we can't edit that branch of the
registry tree through regedit (either using the GUI or by import).
> Vincent

Thanks for the reply

Bill Medland

[Alexandre Julliard]

"Bill Medland"  writes:
> > Those (dlloverrides) are still in config, look at
> > documentation/samples/config.
>
> Yes, and that is mounted into the registry as HKLM\Doftware\Wine\Wine.!!!

This has always been the case, nothing has changed here.
> My question was to do with the mechanisms available for modifying them.  You
> seem to be confirming my suspicion that the only way is to edit the config
> file itself and restart the wineserver; we can't edit that branch of the
> registry tree through regedit (either using the GUI or by import).

Yes, you have to modify the config file and restart. That's clearly
not satisfying, and it's one of the major motivations for getting rid
of the config file and directly accessing the registry.

Setting DllOverrides by script - Thanks

[Bill Medland]

On October 3, 2004 10:44 am, Alexandre Julliard wrote:
> "Bill Medland"  writes:
> > > Those (dlloverrides) are still in config, look at
> > > documentation/samples/config.
> > My question was to do with the mechanisms available for modifying them. 
> > You seem to be confirming my suspicion that the only way is to edit the
> > config file itself and restart the wineserver; we can't edit that branch
> > of the registry tree through regedit (either using the GUI or by import).
>
> Yes, you have to modify the config file and restart. That's clearly
> not satisfying, and it's one of the major motivations for getting rid
> of the config file and directly accessing the registry.

Thanks guys