Hi Alexandre,
What is the thinking behind this patch? If we don't load the Windows registry on startup where should it be loaded? Will this code re-appear at any point in the future? A significant number of users still expect to be able to point Wine at an actual Windows install despite what we recommend.
thanks -mike
On Fri, 11 Mar 2005 07:10:25 -0600, Alexandre Julliard wrote:
ChangeSet ID: 16565 CVSROOT: /opt/cvs-commit Module name: wine Changes by: julliard@wine.codeweavers.com 2005/03/11 07:10:25
Modified files: misc : registry.c documentation/samples: config
Log message: Get rid of the Windows registry loading on startup, this needs to be done differently.
Patch: http://cvs.winehq.org/patch.py?id=16565
Old revision New revision Changes Path 1.149 1.150 +6 -1498 wine/misc/registry.c 1.73 1.74 +0 -2 wine/documentation/samples/config
Mike Hearn mike@navi.cx writes:
Hi Alexandre,
What is the thinking behind this patch? If we don't load the Windows registry on startup where should it be loaded? Will this code re-appear at any point in the future? A significant number of users still expect to be able to point Wine at an actual Windows install despite what we recommend.
There should be an "import existing Windows drive" function in winecfg, or something along those lines, that would create symlinks to the Windows install and import the registry.
On Sat, 12 Mar 2005 16:20:42 +0100, Alexandre Julliard wrote:
There should be an "import existing Windows drive" function in winecfg, or something along those lines, that would create symlinks to the Windows install and import the registry.
You mean by moving the native registry loading code out of the Wine core?
Is anybody working on this, or will it just be a feature regression until somebody changes the way we use native drives?
Mike Hearn wrote:
On Sat, 12 Mar 2005 16:20:42 +0100, Alexandre Julliard wrote:
There should be an "import existing Windows drive" function in winecfg, or something along those lines, that would create symlinks to the Windows install and import the registry.
You mean by moving the native registry loading code out of the Wine core?
Is anybody working on this, or will it just be a feature regression until somebody changes the way we use native drives?
If we just let that "feature" die a quiet death, it would encourage people to use Wine with builtin dlls, test them more, encourage bug reporting and development of Wine code.
People would moan and complain, but in the end Wine and Wine users would be better off, as they would no longer depend on anything but Wine to run their Windows software.
Mike
Mike Hearn mike@navi.cx writes:
Is anybody working on this, or will it just be a feature regression until somebody changes the way we use native drives?
Nobody's working on it, so it won't be supported until someone cares enough to do it. I encouraged a few people to start working on it but nobody did, so taking out the existing support is a way to provide more encouragement. If that's not enough then the feature simply won't be supported anymore.
On 12 Mar 2005 17:04:38 +0100, Alexandre Julliard julliard@winehq.org wrote:
Mike Hearn mike@navi.cx writes:
Is anybody working on this, or will it just be a feature regression until somebody changes the way we use native drives?
Nobody's working on it, so it won't be supported until someone cares enough to do it. I encouraged a few people to start working on it but nobody did, so taking out the existing support is a way to provide more encouragement. If that's not enough then the feature simply won't be supported anymore.
I'm not sure if this is directly related, but my implementation of RegLoadKeyA/W, NtLoadKey and the server counterpart is almost complete. I'll be gone for a week for spring break, but I will finish it up the following week.
-
Alexandre Julliard -
James Hawkins -
Mike Hearn -
Mike McCormack