PhD Student at the Budapest University of Technology and Economics and research fellow at the Computer and Automation Research Institute, Hungarian Academy of Sciences. In my research I have to deal with changes and disturbances in manufacturing by using techniques like AI, neural network, multi-agent system, game theory, etc.
I usually click on send report when the crash details contain an access violation.
I think the reason for a single threaded UI is to avoid deadlocks. Usually there are two directions competing in an UI scenario: user input events and gui redraw events. One might create a clever multi-threaded gui but there are too many pitfalls for general
Nice video. However, I never understood why there aren't any minidump created in case the swap file is moved to a differend partition/hard disk in WinXP? (In my case, I play 3D games and the videocard driver sometimes crashes my system and I cannot hope
to send that crash dump to its manufacturer.)
The UAC is indeed a big leap forward. But I understand 'her' issues as well. Apart from the user experience clicking many times on 'Do you accept...' dialog boxes, I would feel much safer when running an installer there were much finer grained acceptance
rules. For example: extra warning if installer wants to add a service or kernel mode component - not just a complete or none elevation.
It was very interresting. However I have a question, more like a typical situation in XP. Installing Windows on a new machine/laptop usually windows is not able to use immediately the network card (Which is the on board 10/100 Ethernet adatpter from random
supplier). So it pops up the install driver and would like to search for the driver on the internet...- and the manufactured didn't include driver disk You need a network card driver to install the network card. Did this change in Vista? Or I still need another computer to download the driver?