Windows Archive

Windows 98 was released by Microsoft back in 1998 which means in 2022 today, it’s more than 20 years old and something that most have forgotten. However, a recent major announcement by the European Space Agency (ESA) has brought Windows 98 back to the spotlight once more. The Agency says that it is upgrading the software inside its MARSIS instrument in order to enhance its performance and capabilities. Carlo Nenna, an engineer who is developing and implementing the new change says that one of challenges holding back the performance of MARSIS was its old Windows 98-based software. Maybe that’s why aliens have been avoiding us.

After our post a few days ago about running Windows NT for MIPS with Qemu, I was once again reminded of just how much fun it would be to own a MIPS, Alpha, or PowerPC machine from the mid-’90s that can run Windows NT 4. However, after some trouble finding a hardware compatibility list, I decided to ask Twitter – Steven Sinofsky suggested looking through the .iso files of these exotic releases for this information, but I couldn’t find anything in the official documentation contained on the Windows NT 4 for MIPS .iso. Luckily, however, Angus Fox, who worked at Lotus at the time, clearly remembered that there was a very clear, fully detailed HCL on the Windows NT 3.51 for Alpha disc, and it turns out he was right – the HCL comes on the disc as a .hlp file, which is a help file readable by older versions of the Windows help viewer. The Windows NT 4 .iso, too, contained an updated version of this HCL, detailing all the hardware, workstations, and servers supported by the MIPS, Alpha, and PowerPC (and x86) versions of Windows NT 4. As he details on his website, it takes some work to read the .hlp file on Windows, but on my Linux machine, it was as easy as double-clicking the file – Wine’s own Windows help viewer loaded up the file without any issue. So, there you have it – if, like me, you are somehow interested in running these obscure version of Windows NT on real Alpha, MIPS, or PowerPC hardware, all the information you need is right on the disc. Sadly, a bigger problem to overcome is finding and buying the hardware in question. Like any other non-x86 hardware from the past 30 years (DEC, HP, SGI, Sun, etc.), it has become prohibitively expensive to buy, and pretty much only available in the US using eBay, adding hundreds to thousands of euros of shipping costs to the final price for us Europeans. I’m not entirely sure what is causing this massive surge in pricing, since rarity alone cannot possibly account for charging, for instance, over 6000 dollars (!) for an AlphaStation 255.

Today we will be looking at how to run Windows NT 4 for MIPS on the Qemu emulator. I didn’t really have a reason to try this but it seemed like a fun weekend project. In the process I’ve learned a lot about how some systems booted, got even more angry about how awful BIOS boot was on PC, and probably found a 25 year old bug in the ARC boot firmware. While I’m sure all MIPS server admins of yore knew about this I could not find any documentation on the problem, nor any solution to it. I suspect that most people playing with this today are totally fine installing Windows NT on a FAT partition. It is however very puzzling to me that this problem exists at all. What am I talking about? Read on! I find the non-x86 versions from the early days of Windows NT fascinating, and I definitely want to buy some old hardware at some point to run on of them on bare metal. In the meantime, this is a nice substitute.

Yesterday, Microsoft released Windows 11 build 22621 to Windows Insiders enrolled in the Release Preview Channel, marking another step towards general availability of Windows 11 22H2 which is scheduled for release sometime later this year. However, it seems from reports on Reddit, that users on unsupported hardware are being offered the upgrade as well, even those on Windows 10. The wrong bit was flipped.

The OS/2 Museum has made available the first version of a display driver disk for Windows 9x running on VirtualBox. The driver uses a linear framebuffer and supports 8/16/24/32bpp modes with resolutions up to 1920×1200 pixels. The driver is not accelerated but tends to be very speedy on modern hardware. I cannot wait to try this out. The linked article also includes a few notes about the development of the driver in question – it won’t come as a surprise that this wasn’t an easy process.

At its Build developer conference Tuesday, Microsoft made a few announcements aimed at bolstering Windows on Arm. The first is Project Volterra, a Microsoft-branded mini-desktop computer powered by an unnamed Qualcomm Snapdragon SoC. More relevant for developers who already have Arm hardware, Volterra will be accompanied by a fully Arm-native suite of developer tools. According to Microsoft’s blog post, the company will be releasing ARM-native versions of Visual Studio 2022 and VSCode, Visual C++, Modern .NET 6, the classic .NET framework, Windows Terminal, and both the Windows Subsystem for Linux and Windows Subsystem for Android. Arm-native versions of these apps will allow developers to run them without the performance penalty associated with translating x86 code to run on Arm devices—especially helpful given that Arm Windows devices usually don’t have much performance to spare. I actually wouldn’t mind one of these as an actual product for regular end users. Windows on ARM needs a big push, and while I’m not sure these announcements constitute such a big push, it’s at least something.

Microsoft’s upgrade to Windows 11 is largely considered the smoothest we’ve ever had. The Microsoft Digital Employee Experience team was able to upgrade 190,000 employee devices in just five weeks. We learned a lot so, in this post, I’m sharing our learnings with you to help with your deployment journey. Our success was built around several factors: far fewer app compatibility challenges than in the past, not needing to build out a plethora of disk images, and delivery processes and tools already that were greatly improved during the rollout of Windows 10. We divided our upgrade into three stages: plan, prepare, and deploy. It would be pretty pathetic if not even Microsoft itself could smoothly update its employees’ machines to the latest version of Windows, but that being said – I do not envy the people tasked with doing so.

Back when I reviewed Windows 11 for Neowin in 2021, I awarded it a score of 6.5/10, while saying that “simplification of UI isn’t a terrible idea but having it there in a half-baked manner doesn’t really make for an enticing user experience”. Although that was my opinion based on the launch version of the OS, unfortunately, it still hasn’t changed more than six months later. Microsoft seems intent on adding new features as we have seen in recent Insider releases, while ignoring all the UI inconsistencies and lack of basic functionalities in the existing release. The goal with Windows 11 was to make the UI more consistent, but as I predicted, it just seems Microsoft added yet another graphical layer atop the vast list of layers going back all the way to Windows 3.x in some places. Coming from the lovely visual and behavioural consistency of a Gtk+ desktop, seeing Windows 11 makes my brain hurt.

We need to talk about Windows priorities as a product. And I am saying this as someone who wants Windows to succeed – it’s a great OS that, despite it’s naysayers, is still one of the best when it comes to backwards compatibility and richness of functionality. I mean, I can literally run a game written for Windows 95 on Windows 11 without major issues (no, I am not going to open the SafeDisc can of worms this time). I can’t do that on macOS or Linux boxes reliably, and yet Windows is doing a-OK with this task. That being said, I am disappointed to see the direction that the OS is taking lately, and it feels like a very odd misplacement of priorities, especially given the advances that other Microsoft products are going through. A detailed post outlining all the problems on Windows – problems that are only getting worse. Using Windows these days feels like visiting Times Square in New York – it’s a cacophony of lights and colours and advertisements and noise that, while an experience worth having, I didn’t want to stay for much longer than a few minutes. It doesn’t have much to offer besides the lights and colours and advertisements and noise, because those are the very point of Times Square. There’s nothing else of value there. Windows is the same – it isn’t an operating system designed for its users, it’s an operating system designed to increase ad and services revenue. The people in charge at Windows clearly aren’t the people who care about a coherent, welcoming, pleasing, thorough, and well-crafted experience – it’s the advertisement bozos and cloudbros who run the Windows department. And that’s sad.

Microsoft appears to be testing a new type of ad inside File Explorer on Windows 11. Microsoft MVP and Twitter user Florian Beaubois discovered an ad in the latest test build of Windows 11, prompting users to check out the Microsoft Editor. While the ads might have appeared for some Windows 11 users, Microsoft says it was a mistake. “This was an experimental banner that was not intended to be published externally and was turned off,” says Brandon LeBlanc, senior program manager for Windows, in a statement to The Verge. Almost every week there’s a news story about something plain dreadful happening to Windows users, and this is just the latest in a long string of ads Microsoft is plastering all over its operating system. I really don’t understand how users just accept this – they sit back, get bombarded with ads in their operating system, and just… Accept it. Baffling.

This article is not intended to convince you to abandon your current antivirus solutions. In this post I would like to share my observations and ways to improve the effectiveness of Defender. But today, let’s focus on Defender for the home user. It does not have additional functions that are offered by other commercial solutions, but what it does is enough. However, it is worth enabling some additional functions that are not available from the graphical interface. Excellent article, and worth a read if you’re still using Windows.

If you’ve already installed Windows 11 on unsupported devices, you might soon notice a new watermark on the desktop. The watermark, which appears above the taskbar clock, is similar to the “Windows is not activated” error, but it won’t affect apps, windows or web browsers. The desktop watermark simply states “system requirements not met” and it may irritate some users, but it should not come as too much of a surprise, as Microsoft previously warned users of possible ‘damage’. You have to feel sad for Windows users. Windows 7 really seems to have been the high point of Windows – ever since then it’s been one mess after another.

They hid it very well, two-thirds down a long list of changes and screenshots, but what was already inevitable is now reality. Similar to Windows 11 Home edition, Windows 11 Pro edition now requires internet connectivity during the initial device setup (OOBE) only. If you choose to setup device for personal use, MSA will be required for setup as well. You can expect Microsoft Account to be required in subsequent WIP flights. In other words, installing Windows 11 Pro will now, just like 11 Home, also require a Microsoft Account and thus an internet connection. You didn’t think pro users would be safe from big tech’s data hunger, now, did you?

Next month we’re bringing new experiences to Windows that include a public preview of how you can use Android apps on Windows 11 through the Microsoft Store and our partnerships with Amazon and Intel, taskbar improvements with call mute and unmute, easier window sharing and bringing weather to the taskbar, plus the introduction of two new redesigned apps, Notepad and Media Player. Definitely some welcome changes for Windows users.