I have a program that fails when it can't find HKEY_DYN_DATA\Config Manager\Enum in the registry. Any pointers on where to start?
Isn't that Plug'n'Play/hardware information? We may need to just fill out a few dummy entries.
On Tue, 06 Jul 2004 18:30:12 -0400, Robert Reif wrote:
I have a program that fails when it can't find HKEY_DYN_DATA\Config Manager\Enum in the registry. Any pointers on where to start?
Mike Hearn wrote:
Isn't that Plug'n'Play/hardware information? We may need to just fill out a few dummy entries.
On Tue, 06 Jul 2004 18:30:12 -0400, Robert Reif wrote:
I have a program that fails when it can't find HKEY_DYN_DATA\Config Manager\Enum in the registry. Any pointers on where to start?
Where and how. It looks like wine/misc/registry.c _allocate_default_keys is creating HKEY_DYN_DATA\PerfStats but adding code for a new key doesn't get called. How and when does this code get called.
I added HKEY_DYN_DATA support to regedit and I can see PerfStats but I can't see the key I added.
On Wed, 07 Jul 2004 21:05:58 -0400, Robert Reif wrote:
Where and how. It looks like wine/misc/registry.c _allocate_default_keys is creating HKEY_DYN_DATA\PerfStats but adding code for a new key doesn't get called. How and when does this code get called.
Make sure the wineserver shuts down between runs. If you have regedit running in the background that won't happen. Default key initialization only takes place when the client is the first to connect to the server.
wineserver -k can be used to force it to shut down.
thanks -mike
-
Mike Hearn -
Robert Reif