Paul Vriens wrote:
> James Hawkins wrote:
>> On Fri, May 23, 2008 at 3:10 AM, Paul Vriens
>> <[EMAIL PROTECTED]> wrote:
>>> James Hawkins wrote:
On Fri, May 23, 2008 at 2:59 AM, Paul Vriens
<[EMAIL PROTECTED]>
wrote:
> Alexander Morozov wrote:
>>> Can someone confirm that a
> I just had a check for the testRegisterAndGetDetail test on Vista (dunno
> about the other tests and platforms yet).
>
> I added the SetupDiRemoveDevice (as was suggested by Alexander) at the end
> of this test.
>
> On a clean registry this works out fine (one DeviceClasses key is left but
> that
James Hawkins wrote:
> On Fri, May 23, 2008 at 3:10 AM, Paul Vriens <[EMAIL PROTECTED]> wrote:
>> James Hawkins wrote:
>>> On Fri, May 23, 2008 at 2:59 AM, Paul Vriens <[EMAIL PROTECTED]>
>>> wrote:
Alexander Morozov wrote:
>> Can someone confirm that after running the devinst tests, the r
James Hawkins wrote:
> On Fri, May 23, 2008 at 3:10 AM, Paul Vriens <[EMAIL PROTECTED]> wrote:
>> James Hawkins wrote:
>>> On Fri, May 23, 2008 at 2:59 AM, Paul Vriens <[EMAIL PROTECTED]>
>>> wrote:
Alexander Morozov wrote:
>> Can someone confirm that after running the devinst tests, the r
On Fri, May 23, 2008 at 3:10 AM, Paul Vriens <[EMAIL PROTECTED]> wrote:
> James Hawkins wrote:
>>
>> On Fri, May 23, 2008 at 2:59 AM, Paul Vriens <[EMAIL PROTECTED]>
>> wrote:
>>>
>>> Alexander Morozov wrote:
>
> Can someone confirm that after running the devinst tests, the registry
> o
James Hawkins wrote:
> On Fri, May 23, 2008 at 2:59 AM, Paul Vriens <[EMAIL PROTECTED]> wrote:
>> Alexander Morozov wrote:
Can someone confirm that after running the devinst tests, the registry on
Wine still shows these:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Enum\ROOT\LEGA
On Fri, May 23, 2008 at 2:59 AM, Paul Vriens <[EMAIL PROTECTED]> wrote:
> Alexander Morozov wrote:
>>> Can someone confirm that after running the devinst tests, the registry on
>>> Wine still shows these:
>>>
>>> HKEY_LOCAL_MACHINE\System\CurrentControlSet\Enum\ROOT\LEGACY_BOGUS (and
>>> stuff belo
Alexander Morozov wrote:
>> Can someone confirm that after running the devinst tests, the registry on
>> Wine still shows these:
>>
>> HKEY_LOCAL_MACHINE\System\CurrentControlSet\Enum\ROOT\LEGACY_BOGUS (and
>> stuff below)
>>
>> HKEY_LOCAL_MACHINE\System\CurrentControlSet\Enum\USB\BOGUS (and stuff
> Can someone confirm that after running the devinst tests, the registry on
> Wine still shows these:
>
> HKEY_LOCAL_MACHINE\System\CurrentControlSet\Enum\ROOT\LEGACY_BOGUS (and
> stuff below)
>
> HKEY_LOCAL_MACHINE\System\CurrentControlSet\Enum\USB\BOGUS (and stuff
> below)
>
> HKEY_LOCAL_MACHINE\
Alexander Morozov wrote:
> I was mistaken. Enum/ROOT/LEGACY_BOGUS key can be deleted so:
>
> SetLastError(0xdeadbeef);
> set = pSetupDiGetClassDevsA(&guid, NULL, 0, 0);
> ok(set != INVALID_HANDLE_VALUE, "SetupDiGetClassDevsA failed: %08x\n",
> GetLastError());
> SetLastError(0xdeadbeef);
> ret =
Alexander Morozov wrote:
> В сообщении от Tuesday 20 May 2008 17:31:48 Paul Vriens написал(а):
>> Hi,
>>
>> On several windows boxes (VMware) I receive this nice message that Windows
>> will try to find a driver for an unknown device.
>>
>> This device is added by the setupapi/devinst test and is n
I was mistaken. Enum/ROOT/LEGACY_BOGUS key can be deleted so:
SetLastError(0xdeadbeef);
set = pSetupDiGetClassDevsA(&guid, NULL, 0, 0);
ok(set != INVALID_HANDLE_VALUE, "SetupDiGetClassDevsA failed: %08x\n",
GetLastError());
SetLastError(0xdeadbeef);
ret = pSetupDiEnumDeviceInfo(set, 0, &devInfo);
В сообщении от Tuesday 20 May 2008 17:31:48 Paul Vriens написал(а):
> Hi,
>
> On several windows boxes (VMware) I receive this nice message that Windows
> will try to find a driver for an unknown device.
>
> This device is added by the setupapi/devinst test and is not (or can't be?)
> properly remo
Juan Lang wrote:
>> I didn't find a way yet (and didn't look to hard) to make the subkeys
>> inherit these new permissions. Otherwise I have to do this for every key.
>
> I don't think you can if you don't actually create the key. The
> caller of RegCreateKeyEx is able to set the default DACL for
Hello Juan,
2008/5/21 Juan Lang <[EMAIL PROTECTED]>:
>> Are the tests in devinst.c supposed so be run in order? IOW are they
>> supposed to bee cleaned up after each subtest or do they rely on each other?
>
> I'm sure I didn't put that much thought into making the tests order
> dependent. I wrote
Juan Lang wrote:
> Hi Paul,
>
>> Are the tests in devinst.c supposed so be run in order? IOW are they
>> supposed to bee cleaned up after each subtest or do they rely on each other?
>
> I'm sure I didn't put that much thought into making the tests order
> dependent. I wrote them, ran them, made
> I didn't find a way yet (and didn't look to hard) to make the subkeys
> inherit these new permissions. Otherwise I have to do this for every key.
I don't think you can if you don't actually create the key. The
caller of RegCreateKeyEx is able to set the default DACL for the key,
and subkeys wil
Juan Lang wrote:
>> Now you tell me :-).
>>
>> I've something in place already to get rid of the stray registry keys. Just
>> needs some more thought and tweaking.
>
> Well that's even better! Feel free to send here for comments :)
> --Juan
>
It's a new function that just changes the permissions
> Now you tell me :-).
>
> I've something in place already to get rid of the stray registry keys. Just
> needs some more thought and tweaking.
Well that's even better! Feel free to send here for comments :)
--Juan
Hi Paul,
> Are the tests in devinst.c supposed so be run in order? IOW are they
> supposed to bee cleaned up after each subtest or do they rely on each other?
I'm sure I didn't put that much thought into making the tests order
dependent. I wrote them, ran them, made them into tests, and they
wor
James Hawkins wrote:
> On Tue, May 20, 2008 at 8:17 PM, Juan Lang <[EMAIL PROTECTED]> wrote:
>>> anyone knows the exact testing causing the creation of the dummy devices?
>> I believe it's testRegisterDeviceInfo. See my comment in it:
>> * FIXME: the key also becomes undeletable. How to get rid o
Juan Lang wrote:
>> anyone knows the exact testing causing the creation of the dummy devices?
>
> I believe it's testRegisterDeviceInfo. See my comment in it:
> * FIXME: the key also becomes undeletable. How to get rid of it?
>
> --Juan
>
Hi Juan,
Are the tests in devinst.c supposed so be run
James Hawkins wrote:
> It should be mentioned that the setupapi:devinst tests fail miserably
> on every platform. I'm working through the failing win2k3 tests, but
> it would be nice if someone could take a look at these, maybe even
> those that contributed to or wrote the tests.
>
> Thanks,
> Ja
Juan Lang wrote:
>> anyone knows the exact testing causing the creation of the dummy devices?
>
> I believe it's testRegisterDeviceInfo. See my comment in it:
> * FIXME: the key also becomes undeletable. How to get rid of it?
>
> --Juan
>
Deleting is not an issue if you use the native GUI's. Y
Maarten Lankhorst wrote:
>> The issue about the leftover registry keys after the tests still stands
>> though.
> I just keep hitting escape when booting, but it is a real problem that
> should be addressed, anyone knows the exact testing causing the
> creation of the dummy devices? Why 75 mouse cl
On Tue, May 20, 2008 at 8:17 PM, Juan Lang <[EMAIL PROTECTED]> wrote:
>> anyone knows the exact testing causing the creation of the dummy devices?
>
> I believe it's testRegisterDeviceInfo. See my comment in it:
> * FIXME: the key also becomes undeletable. How to get rid of it?
>
Another note: t
On Tue, May 20, 2008 at 8:08 PM, Maarten Lankhorst
<[EMAIL PROTECTED]> wrote:
> Hello Paul,
>
> 2008/5/20 Paul Vriens <[EMAIL PROTECTED]>:
>> Paul Vriens wrote:
>>> Hi,
>>>
>>> On several windows boxes (VMware) I receive this nice message that
>>> Windows will try to find a driver for an unknown de
> anyone knows the exact testing causing the creation of the dummy devices?
I believe it's testRegisterDeviceInfo. See my comment in it:
* FIXME: the key also becomes undeletable. How to get rid of it?
--Juan
Hello Paul,
2008/5/20 Paul Vriens <[EMAIL PROTECTED]>:
> Paul Vriens wrote:
>> Hi,
>>
>> On several windows boxes (VMware) I receive this nice message that
>> Windows will try to find a driver for an unknown device.
>>
>> This device is added by the setupapi/devinst test and is not (or can't
>> be
Paul Vriens wrote:
> Hi,
>
> On several windows boxes (VMware) I receive this nice message that
> Windows will try to find a driver for an unknown device.
>
> This device is added by the setupapi/devinst test and is not (or can't
> be?) properly removed after the tests.
>
> On NT/W2K I'm able
Hi,
On several windows boxes (VMware) I receive this nice message that Windows will
try to find a driver for an unknown device.
This device is added by the setupapi/devinst test and is not (or can't be?)
properly removed after the tests.
On NT/W2K I'm able to delete all the relevant registry k
31 matches
Mail list logo
