News

The history of Windows NT 3.1

by
Cutler and his team had nearly zero experience with either OS/2 or with PCs. They did, however, have ample experience with both portable code and with varied hardware platforms. Similar to his experience at DEC, Cutler was very quickly placed as the lead of the NT project. NT needed to have some compatibility with MS-DOS, OS/2, and UNIX (all systems Microsoft supported, sold, and developed at some level at the time ). As a result, NT was a fully 32 bit microkernel operating system with paged virtual memory and the win32 API operating in protected mode with fully pre-emptive multitasking. It also had the NTVDM for MS-DOS compatibility, the win16 WOW system for older Windows compatibility, an OS/2 compatibility subsystem, and a POSIX subsystem for UNIX compatibility. For Cutler and his team, “WNT” was the working name for the OS (increment each letter by one from VMS). The similarities between VMS and NT are striking. The VMS Interrupt Priority Level became the Interrupt Request Level in NT, the Asynchronous System Trap became the Asynchronous Procedure Call, a Fork Procedure became the Deferred Procedure Call, while some other terminology was copied verbatim. NT and VMS share similarities in many ways, but unlike VMS, NT processes can contain more than one thread of execution, NT uses access control lists for object security, NT uses its own NTFS, and NT uses the registry (a centralized hierarchical configuration database) allowing the configuration of computers over a network, among many other major differences. Dave Cutler has had such a massive impact on the world of computing, yet relatively few people know his name or are aware of his accomplishments. He still works at Microsoft today, and has worked on both Azure and Xbox One’s hypervisor.

Minecraft Hayran Haritaları Bölüm 13 – Çok’lu Parkur Haritası

by
Minecraft Efsane Parkur Haritası
Ayrıcalıklardan yararlanmak için bu kanala katılın:
https://www.youtube.com/channel/UCpcHFJwDFlrnbCw3yD-4Wzg/join

CANIM HANDAŞ AİLEM BİZLERİ DESTEKLEDİĞİNİZ HER GÜN GELEN VİDEOLARIMIZI İZLEYİP LİKE ve YORUM ATTIĞINI İÇİN HEPİNİZE SONSUZ TEŞEKKÜR EDİYORUM.
SİZLER SAYESİNDE BURADAYIZ VE SİZLER SAYESİNDE HEDEFİMİZE ULAŞACAĞIZ 10 MİLYON HANDAŞ AİLESİNE ULAŞMAK İÇİN ELİMİZDEN GELENİ YAPACAĞIZ.
SİZLERDE HANDAŞ AİLEMİZE KATILMAYI VE BİZLERE DESTEK VERMEYİ LÜTFEN UNUTMAYIN
—————————————————————————————————————————————-
– SOSYAL MEDYA HESAPLARIM –
-Discord : https://discord.gg/sttQ7WUJ
– Katılmak için: https://bit.ly/3w2a5TV
-İnstagram : https://bit.ly/37ftx50
-Tiktok : https://bit.ly/3CEky95
-2.Kanal : https://bit.ly/3hZrggC
– HAN KANAL DİĞER VİDEO SERİLERİM –
– PoppyPlayTime: https://bit.ly/3JdC9r1
– Roblox: https://bit.ly/3KC7kfZ
—————————————————————————————————————————————-

The technical merits of Wayland are mostly irrelevant

by
Today I read Wayland breaks your bad software, which is in large part an inventory of how Wayland is technically superior to X. I don’t particularly disagree with Wayland’s general technical merits and improvements, but at this point I think that they are mostly irrelevant. As such, I don’t think that talking about them will do much to shift more people to Wayland. (Of course, people have other reasons to talk about Wayland’s technical merits. But a certain amount of this sort of writing seems to be aimed at persuading people to switch.) I say that the technical merits are irrelevant because I don’t believe that they’re a major factor any more in most people moving or not moving to Wayland. There’s always multiple angles to things like this, and I would prefer to highlight them when I can.