Re: [Wine]june 2005 release and 'registry' ?
--- Dan Sawyer <dansawyer(a)earthlink.net> wrote:
All,
I am testing with the wine 2005 release. The release notes state config file control has been moved to the registry and that winecfg is active. winecfg does not seem to recognize dll overrides. Has anyone else seen this? If so were you able to work around it?
Thanks, Dan
I'd be interested to know as well! I could not find how to do DLL overrides with winecfg. I believe that some portions of the config file will still work, but I didn't know what parts were referred to. I'm adding the wine-devel alias to this email; maybe someone there can help. How are DLL overrides done in winecfg? Hiji __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Hiji schreef:
--- Dan Sawyer <dansawyer(a)earthlink.net> wrote:
All,
I am testing with the wine 2005 release. The release notes state config file control has been moved to the registry and that winecfg is active. winecfg does not seem to recognize dll overrides. Has anyone else seen this? If so were you able to work around it?
Thanks, Dan
I'd be interested to know as well! I could not find how to do DLL overrides with winecfg. I believe that some portions of the config file will still work, but I didn't know what parts were referred to. I'm adding the wine-devel alias to this email; maybe someone there can help.
How are DLL overrides done in winecfg?
Hiji
Open winecfg (obviously ;-) ) and then on the first tab, if you want to make the override for only a particular application, click the "Add application" button, browse to the *.exe in question, and select it. It will now appear in the list, and if you select (highlight) it, when you go to the next tab, you will see that the titlebar now says "Wine configuration for [your app]". If you want the settings to be default, then just leave "Default settings" selected when you go to the "Libraries" tab. In the "Libraries" tab, type the name of the dll you want to override in the only field that is available to you. Choose what you want to do with the dll using the radio buttons, which will now become active, since they have a dll name to work with, then click the "Add Override for" (or something similar, my winecfg is in Dutch, because my desktop is in Dutch -- nice touch, btw, guys!), and the override will appear with the settings you chose. Hit Apply to write the settings, and OK to exit the program, and you're done. The overrides should apply normally when you next run the application in question. It works for me, anyway. Hope this helps. Holly Ho
On 7/8/05, Hiji <hijinio(a)yahoo.com> wrote:
How are DLL overrides done in winecfg?
What may not be obvious is the "Applications" tab in winecfg is tied to the other tabs. We should probably add a sentence in the description of that tab to briefly explain it links to other ones (inc. "Graphics"). In fact, I'm procrastinating, so maybe I'll just try to submit a patch for that. So if you want to change systemwide overrides: 1) Select "Default Settings" in the Applications tab. 2) Then move to the "Libraries" tab and enter the name of the DLL in "New override" box, such as "msi.dll" and click on "Add". 3) "Edit" the load order as necessary in the box below. If you want to change the override for one application, "Add" the new application in the "Applications" tab, select it on that tab, and then move to "Libraries" to create an override. If you update to the latest CVS you'll see a different Libraries tab than what was in wine-20050628 and it follows what I described above. The layout is different in wine-20050628, but it's essentially the same concept. -Brian
Brian Vincent wrote:
What may not be obvious is the "Applications" tab in winecfg is tied to the other tabs.
The current design is totally braindead from a usability standpoint: * As you pointed out it's not very intuitive that selecting an item in the first tab affects the semantics of the other tabs (even if it would be documented). * It's not clear which settings are global-only - we could disable the controls but it would still be confusing IMHO. Also the drives tab will probably never contain any per-app settings so we would have to disable the whole tab. Silly. * All per-app settings really need exactly one more option - "don't override" (inherit from global). This is not doable with the current design. I'll submit a preliminary patch (introducing the not yet configurable DSound settings) showing how I think this should be done later today. Felix
On Sat, 09 Jul 2005 07:01:16 +0200, Felix Nawothnig wrote:
I'll submit a preliminary patch (introducing the not yet configurable DSound settings) showing how I think this should be done later today.
Felix and I talked this stuff over on IRC, I think we came to some understanding on where winecfg is going and why it's designed the way it is. For everybody: generally, we should resist the temptation to do yet more UI overhauls. Yes, the linked tabs thing is not ideal. It's more an artifact of the Property Sheet control than anything else. However, a few things which are less ideal are: a) Treeviews: tried, didn't work very well. Treeviews have generally poor usability anyway b) Tri-state checkboxes: not really clear what the third state means, but for now it may be a quick fix c) Opening up new windows for each app: hard to implement in the code. A much better way forward is simply to fix the damn bugs that winecfg settings invariably exist to work around :) Eg, even "Windows Version" will hopefully be fixed sometime later this year (?) by switching us to 2K/XP mode by default and by nailing the last DCOM problems. Desktop mode will eventually (I hope) become the "winedesktop" program that was done years ago, I'm not sure what AJ plans are here though. Eventually nobody should have to use winecfg for anything. Let's spend our time fixing the bugs and increasing automation rather than arguing about the best way to represent a list of hacks in the UI :) thanks -mike
Mike Hearn <mh(a)codeweavers.com> writes:
Eg, even "Windows Version" will hopefully be fixed sometime later this year (?) by switching us to 2K/XP mode by default and by nailing the last DCOM problems.
Actually we probably want to do that before 0.9, which means real soon now...
Desktop mode will eventually (I hope) become the "winedesktop" program that was done years ago, I'm not sure what AJ plans are here though.
It should be part of the new explorer process. Working on it... -- Alexandre Julliard julliard(a)winehq.org
Mike Hearn wrote:
Eventually nobody should have to use winecfg for anything. Let's spend our time fixing the bugs and increasing automation rather than arguing about the best way to represent a list of hacks in the UI :)
I think the reality is that winecfg is going to hang round for a while. I only see patches adding to its functionality, and nobody is removing config options. Having a configurationless Wine is a lofty goal, but not one that's achieveable in the short term. It would be nice to spend a little bit of time to fix up the usability issues that Felix has pointed out. Opening a new window for app specific overrides might be hard, but it would make alot more sense. Mike
I was just wondering about this new system of doing things. I quite like the new config method. It doesn't allow the indepth configuration that the old .config file did but I'm sure thats not going to be a problem. I was thinking though, will windows programs have access to these configuration registry entries? Or are they somehow protected. If any windows program can view these entries then they could perhaps refuse to install. i.e. Valve decide HL3 shouldn't run under wine and so don't let it. Thanks -- Adam Cooper <adam.cooper(a)port.ac.uk>
On Mon, 2005-07-11 at 13:09 +0100, Adam Cooper wrote:
I was thinking though, will windows programs have access to these configuration registry entries? Or are they somehow protected. If any windows program can view these entries then they could perhaps refuse to install. i.e. Valve decide HL3 shouldn't run under wine and so don't let it.
If they want to do that, there are more reliable means of doing so. -- Dimi Paun <dimi(a)lattica.com> Lattica, Inc.
It seems that the native only choice doesnt work into winecfg - I tried to set one dll as 'Native(Windows)' and got "native,builtin" into the registry. Could you have a look for this ? --- Felix Nawothnig <felix.nawothnig(a)t-online.de> a écrit :
Brian Vincent wrote:
What may not be obvious is the "Applications" tab in winecfg is tied to the other tabs.
The current design is totally braindead from a usability standpoint:
* As you pointed out it's not very intuitive that selecting an item in the first tab affects the semantics of the other tabs (even if it would be documented).
* It's not clear which settings are global-only - we could disable the controls but it would still be confusing IMHO. Also the drives tab will probably never contain any per-app settings so we would have to disable the whole tab. Silly.
* All per-app settings really need exactly one more option - "don't override" (inherit from global). This is not doable with the current design.
I'll submit a preliminary patch (introducing the not yet configurable DSound settings) showing how I think this should be done later today.
Felix _______________________________________________ wine-users mailing list wine-users(a)winehq.org http://www.winehq.org/mailman/listinfo/wine-users
Kind regards, Usurp (aka Sylvain Petreolle) humans are like computers, yesterday the BIOS was all - today its just a word
Sylvain Petreolle wrote:
It seems that the native only choice doesnt work into winecfg - I tried to set one dll as 'Native(Windows)' and got "native,builtin" into the registry. Could you have a look for this ?
Works fine for me... Felix
Is there a way to cause winecfg to assume the contents of the config file on initiation? Brian Vincent wrote:
On 7/8/05, Hiji <hijinio(a)yahoo.com> wrote:
How are DLL overrides done in winecfg?
What may not be obvious is the "Applications" tab in winecfg is tied to the other tabs. We should probably add a sentence in the description of that tab to briefly explain it links to other ones (inc. "Graphics"). In fact, I'm procrastinating, so maybe I'll just try to submit a patch for that.
So if you want to change systemwide overrides:
1) Select "Default Settings" in the Applications tab. 2) Then move to the "Libraries" tab and enter the name of the DLL in "New override" box, such as "msi.dll" and click on "Add". 3) "Edit" the load order as necessary in the box below.
If you want to change the override for one application, "Add" the new application in the "Applications" tab, select it on that tab, and then move to "Libraries" to create an override. If you update to the latest CVS you'll see a different Libraries tab than what was in wine-20050628 and it follows what I described above. The layout is different in wine-20050628, but it's essentially the same concept.
-Brian
participants (11)
-
Adam Cooper -
Alexandre Julliard -
Brian Vincent -
Dan Sawyer -
Dimi Paun -
Felix Nawothnig -
Hiji -
Holly Bostick -
Mike Hearn -
Mike McCormack -
Sylvain Petreolle