“What's wrong with the computer - it has an nvme drive installed, but opening the explorer, if you haven't done it for a long time, takes about 10 seconds, opening the .zip file on the desktop takes about a minute, and when you press the“ Start ”key, you need to wait about 20 seconds? "
Around the end of January, I was shown a Twitter post in which a Windows user with a powerful machine talks about random freezes in Explorer. Many unscientific theories have been proposed. I don’t usually do the analysis of performance problems with strangers, but this case seemed interesting, so I decided to study it.
It is common practice not to like Windows. But, as a rule, phrase: “I haven't read the book but still condemn it” describes this situation well. Despite the tendency of not like Windows, there are still some things that are implemented well. I’d like to tell you about one of them.
I’ll review the embedded into OS implementation of the lock-free stack and its performance comparison with the cross-platform analogues.
The implementation of non-blocking stack on the basis of a singly linked list (Interlocked Singly Linked Lists, SList), has been available in WinAPI for quite a while. Operations on such list initializing and stack primitives over it have been implemented. Without going into details of implementing the SLists, the Microsoft just say that they use some non-blocking algorithm in order to implement atomic synchronization, increase performance and get rid of lock problems.
It turned blue, is something wrong with it?
BSOD is the kernel response to an unsolvable particular situation. If you see it, it means that something has happened and it is definitely wrong.
The kernel environment imposes many restrictions on the programmer's free hand: you consider IRQL, sync access to shared variables, and you do not stay too long in ISR, you should verify any data from the userland… Breaking at least one of the rules, you will receive a bunch of phrases in a standard VGA video with the poor palette.
In fact, this makes sense. If in the user mode the application simply closes without even removing a trail after itself (that the kernel will do that), so it will not break the integrity of the entire system.
How often do you have to see the Blue Screen of Death Windows (BSoD)? BSoD can occur in the different situations, for example, in the process of loading the operating system or during working with the OS. How do you determine what caused the occurrence of BSoD and fix this problem? The OS of Windows is capable to store a memory dump when an error occurs, and the system administrator can analyze the data dump and find the cause of BSoD.
There are two types of memory dumps, such as a minidump and a full dump. Depending on your operating system, it can store the full or small dumps, or take no actions when an error occurs.
The minidump is located in %systemroot%\minidump, and it has a name like Minixxxxxx-xx.dmp.
The full dump is located in %systemroot%, and it has a name like Memory.dmp.
Windows XP wallpaper is a famous image, showing a blissfully relaxing vista of green rolling hills and a bluer than blue sky. This default wallpaper is one of the most viewed images of all time that is called the “Bliss”. If you go to Google and search for the word “Bliss” and the first result will be the Windows default wallpaper.
However, Windows image is named Ireland for Dutch users, which has mistakenly led many to believe that that’s where the image was taken.
A small group of like-minded developers has introduced alpha version software that lets run Android applications on Windows.
The developer’s mission from the company BlueStacks is well expressed in a fun demo video, which can be viewed on the front page of the company: bluestacks.com/home.php. We strongly recommend watching the high quality demo.
Today was an imported day for the team of Windows. At the conference BUILD was introduced a new operating system of Windows 8. Broadcasting of the event was at http://buildwindows.com (the recording is available at this site).