Windows Archive
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.
Are you a fervent user of WordPad? Are your company’s finances run through a document only WordPad can deal with? Do you run your Kinder egg smuggling side hustle through WordPad? You better find an alternative, because WordPad has just been deprecated. WordPad is no longer being updated and will be removed in a future release of Windows. We recommend Microsoft Word for rich text documents like .doc and .rtf and Windows Notepad for plain text documents like .txt. A moment of silence for WordPad. It has been included in Windows since Windows 95, as a replacement for Microsoft Write, which was included in Windows from Windows 1.0 until Windows NT 3.51. Definitely a long history, but one has to wonder if this deprecation will actually affect anyone.
Microsoft is testing an incredibly welcome feature in Notepad. With this update, Notepad will start automatically saving your session state allowing you to close Notepad without any interrupting dialogs and then pick up where you left off when you return. Notepad will automatically restore previously open tabs as well as unsaved content and edits across those open tabs. Saved session state does not impact any of your files, though, and it is still your choice whether to save or discard unsaved changes to files anytime you close a tab. You can turn this feature off in app settings if you would prefer to have a fresh start every time you open Notepad. I’m not exactly impressed by Microsoft’s handling of Windows as of late, but the few things they are doing right are the more frequent, sometimes constant updates to core applications like Notepad, the terminal, and so on. Features like these are table stakes in better-managed platforms like GNOME or KDE, but it’s welcome to see Windows play catch-up, if at least when it comes to a notepad application.
Currently, in Windows 11, links contained in Windows system components, like, say, in the Settings application, are always opened in Edge, completely disregarding your default browser setting. Well, thanks to the European Union’s new Digital Services Act, this is going to change – but only for users in the European Economic Area. The latest Insider Preview changelog states: In the European Economic Area (EEA), Windows system components use the default browser to open links. It’s remarkable how quickly things can change when the full might of the EU’s and member states’ legal systems can come bearing down on you if you don’t comply. We’re already seeing the first few signs of users in the EU getting a better experience than users elsewhere.
By far, the most popular so-called DOS Extender in the early 1990’s was DOS/4GW. MS-DOS game compatibility occupied a very large portion of my time during Windows 95 development, so I saw a lot of DOS Extender banners, most frequently the DOS/4GW banner. Now, you might wonder, “How did these games even run in Windows 95 if they came with a DOS Extender? Wouldn’t the extender try to enter protected mode and fail, because Windows was already managing protected mode?” When Raymond Chen speaks, we listen. That’s the rules.
Microsoft has just paused Bing ads targeting Chrome users who have set Google as the default search engine. Windows 11 (and 10) users are seeing more Bing and Edge of late, and the most recent ad appears on top of games as the tech giant trying to push folks to use Bing rather than Google search in Chrome. As I reported on Sunday, Microsoft aggressively pushed Bing to Chrome users with Google or other search engine as default. This campaign involved a pop-up on the desktop’s lower right side, hovering above all apps and games. The advert reminded users of the benefits of using Bing, such as AI chat and Microsoft Rewards. People will keep using this garbage, so why would Microsoft no spam Windows users with ads? It’s not like Windows users care.
Meanwhile, if you are on Windows 11 and wondering about its compatibility with your system, a document from Intel, spotted by Twitter (X) user Chi11eddog, seemingly confirms that Windows 11 is going to be supported. And although the document does not mention Windows 12, which is expected given that the product has not even been officially announced yet (Microsoft recently revealed the release date for Windows 11 23H2). While this is certainly expected, users who would have stuck to their Windows 10 PCs, either due to the hardware being not on the support list or simply because they prefer the older OS over the new ones, are likely going to be out of luck as the supported OS does not mention Windows 10. I mean, at the time Wi-Fi 7 comes out, Windows 10 will be almost a decade old. I’m all for a good Microsoft thrashing, but expecting them to go back and add support for Wi-Fi 7 to a decade-old operating system seems a bit unrealistic.
You can still do a clean install of Windows, and it’s arguably easier than ever, with official Microsoft-sanctioned install media easily accessible and Windows Update capable of grabbing most of the drivers that most computers need for basic functionality. The problem is that a “clean install” doesn’t feel as clean as it used to, and unfortunately for us, it’s an inside job—it’s Microsoft, not third parties, that is primarily responsible for the pile of unwanted software and services you need to decline or clear away every time you do a new Windows install. You mean you don’t want Candy Crush Saga and Instagram ads on your freshly installed PC?
Despite all of the litigation, Windows 2 made it to market, gained 3rd party support, and signaled a massive transition in computing that all of the competition had failed to do. With Windows 2, millions of people were using a graphical desktop with graphical applications. The mouse was made a standard tool. PCs were now being urged to adopt powerful graphics adapters. Many people claim Windows 2 to be a failure, but this is not an accurate assessment. While it didn’t sell to the level of later releases, the market hadn’t really become accustomed to buying an operating system on a store shelf. People typically received an OS as part of a computer purchase. That Microsoft was able to sell over 2 million copies of Windows 2 shows a serious change; MS-DOS’s days were now numbered. I’ve always considered Windows 1.0 and 2.0 to be false starts, failed attempts at what would become Windows 3.x. This article makes the case that Windows 2.0 was more important and successful than we give it credit for today.
Unfortunately for me, I couldn’t just let this one go. I tested all the popular Windows uninstallers and I didn’t like what I saw. I thought many of these programs had some rudimentary issues with their user interface, and they just didn’t work that well. How difficult could it really be to do something better? As it turned out, it was very difficult, actually. It’s 2023, and Windows users still cannot centrally manage their software. People have to create multiple uninstaller programs to finally make a decent one, and not only does it need to uninstall applications, it also needs to somehow find all the garbage files and registry keys these applications barf all over the system. We deserve so much better than this trash.
Microsoft is making it possible to remove a few more of the preinstalled Windows 11 applications. In the release notes for a recent Insider Preview, build 25931, the company notes: In addition to the Camera app and Cortana, the Photos app, People app, and Remote Desktop (MSTSC) client can be uninstalled. In addition, this build also deprecates Windows Internet Name Service (WINS) and Remote Mailslots.
I have struggled, literally for years, with Quicken being dog slow to start. It could take 30+ seconds to start. From what I could remember, this problem has existed since I first installed Windows 10. The title gives the answer away, but yes, it’s exactly what it says – some applications on Windows will load every single font on the system before loading the rest of the application. If you have a lot of fonts – say, because you’re a designer or illustrator or whatever – you’re going to feel this.
Installing Windows 11 without third-party bloatware like Candy Crush in just two clicks is possible, and all it takes is setting your region to English (World). No, we’re not kidding, and Microsoft said it’s aware and looking into the reports after we asked the company about the situation. A Microsoft spokesperson confirmed to Windows Latest. “Microsoft is aware and is looking into it,” a Microsoft spokesperson told me over email. Why would you let Microsoft know?
While casually looking for updates in the Microsoft Store, I noticed a new update for Cortana after a long time. But, instead of improving things, the latest update caused the app to stop working on Windows 11. This shouldn’t surprise anyone, considering that Microsoft’s assistant hasn’t received a single feature update in the past two years Microsoft has finally killed Cortana on Windows 11 – its Windows Phone-era assistant that debuted on desktop with Windows 10. Cortana app was the tech giant’s response to Siri in 2014, and Microsoft published a series of advertisements targeting Apple’s powerful assistant. Did anyone even use this feature? It always felt like an awful “me too!” feature trying to be edgy.
Microsoft has accidentally leaked its internal “StagingTool” app that is used by employees to enable secret unreleased Windows 11 features. The software giant typically tests experimental or hidden Windows 11 features in public builds of the operating system, but Windows enthusiasts have until now had to rely on third-party tools to get access to secret features that Microsoft hasn’t yet enabled for all testers. StagingTool is a command line app that lets you toggle feature IDs that enable certain unreleased parts of Windows 11. It’s particularly useful for when Microsoft uses A/B testing for features, where only a small subset of Windows Insiders will get access to a feature before Microsoft rolls it out more broadly to testers. Useful, but similar third-party tools already exist, such as ViVe.
Windows has some pretty amazing backwards compatibility. In many cases, you can run ancient 32-bit Win32 applications just fine on your current system. However, there’s one issue: If you ever tried to run a 16-bit application from the Windows 3.x days, any 64-bit Windows version (starting from Windows XP) will refuse to run the application with an error message indicating that you should ask the vendor for a compatible version. On the other hand, the modern 32-bit versions of Windows run these applications just fine. Thanks to two amazing open-source projects, you can bring back 16-bit compatibility to the 64-bit Windows era. This one’s from 2022, but apparently, I never mentioned it here on OSNews.
In my previous article, I described how I managed to install Windows 2000 in DOSBox-X. Even though this experiment was successful, I was not really with the results. While I got Windows 2000 working, I didn’t want to stop there. The final goal for the project was to get Windows XP running instead. However, after multiple attempts I gave up, thinking that Windows XP was impossible to use. Well – I was wrong. I can’t believe this works.
Starting in Windows 11, version 22H2, Enhanced Phishing Protection in Microsoft Defender SmartScreen helps protect Microsoft school or work passwords against phishing and unsafe usage on sites and apps. We are trying out a change starting with this build where users who have enabled warning options for Windows Security under App & browser control > Reputation-based protection > Phishing protection will see a UI warning on unsafe password copy and paste, just as they currently see when they type in their password. This actually seems like a cool and useful feature. The basic gist – which is a bit unclear from the short blurb above – seems to be that if, e.g., a child using a school account copies and pastes that school account password to use somewhere else, this feature will warn them about it. Usefulness of warning dialogs aside, I can see this being quite useful in large organisations.
Microsoft ended Windows Server 2003’s Mainstream Support on July 13, 2010, and Extended Support on July 14, 2015. This means it would no longer provide security updates, technical support, or software updates for this server-based operating system. Windows Server 2003 is probably my favourite Windows release. I never liked Windows XP, and Server 2003, with its updated codebase and various fixes compared to XP, provided a more solid alternative at the time. There was this whole cottage industry of people aiding each other in converting Windows Server 2003 into a more desktop-friendly operating system through reactivating services, installing additional components, applying registry changes, and so on. It was a bit of work post-install, but once done, you had a more stable, more solid, and safer “version” of Windows XP. At least, that was the theory. I have no idea if this was actually true, or if a fully updated Windows XP installation was, in fact, functionally equivalent and that Server 2003 provided zero material benefit.
This is a community-based project and is actively updated. This project aims at restoring the legacy Windows Update websites, and allows older operating systems (Windows 95, NT 4.0, 98, Me, 2000, and XP) to obtain updates like they used to. Ever since 2011 when Microsoft pulled the plug on nearly all the Windows Update websites, the Windows Update feature for older Windows operating systems was no longer functional. The only way to install updates after that point was through external third-party installers which didn’t cover all the updates that the operating system would fully support. So, with this project, we can now update operating systems as old as Windows 95 all the way through Windows XP RTM like we used to back in the day. IT’s still a work-in-progress, as sourcing the various update packages and installers is proving to be quite difficult in some cases, and not all versions of Windows/Microsoft Update have been recreated yet. However, as the ever awesome Michael MJD notes in his video overview of the project, it already works quite well for Windows 95 and Windows 98 and 98SE.
