I too am having keyboard/mouse lock ups for no apparent reason and I am sure
Vista has some blame. But I am not ready to rule out Motherboard problems or
for that matter Bios problems just yet. I can remember when XP first came
out and I had to update bios twice before hardware conflicts were resolved.
I know that at least one of my problems is related to bios because my
keyboard (USB) will not function if a PS/2 mouse is plugged into the
machine. Nor will a USB mouse work if a PS/2 keyboard is plugged in, all
before Vista even starts. No problem doing this in XP.

GWL

"Ivan Brugiolo [MSFT]" <ivanbrug@online.microsoft.com> wrote in message
news:OlJaBfUpHHA.4188@TK2MSFTNGP02.phx.gbl...
> The general idea is:
> Virtualization of files are implemented with a Mini-File-System-Filter
> driver.
> Virtualization of registry is implemeted with internal KEY properties.
> The mandatory integrity labels set on the token triggers the whole
> process.
>
> Why is reversing virtualization interesting ?
>
> --
> --
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> Use of any included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
>
>
> "Scott" <smbaker@gmail.com> wrote in message
> news:1180635057.053728.208920@o11g2000prd.googlegr oups.com...
>>> These Vista.public groups are focused on the end user. There is a very
>>> good
>>> resource for developers on the MSDN forums. These forums are staffed by
>>> Microsoft Developers and they are focused on problems with developing
>>> applications for Vista. You can access them here:
>>
>> I gave it a shot there too, but nobody ever replied. So I guess:
>>
>> 1) Microsoft never implemented a function to resolve these
>> virtualizations
>>
>> or
>>
>> 2) Microsoft did, but nobody knows what it is
>>
>> Is there any sort of "Windows Vista Internals" book? I seem to
>> remember such things existed for XP and covered hidden facets of the
>> operating system such as the process tables, etc.
>>
>> Scott
>>
>
>