driver1998 retweeted
yeah okay thats just VoLTE for windows and there isn't even really a catch, it just works
VoLTE for pretty much any mbim (+QMI) modem on windows
(tested on windows on arm)
driver1998 retweeted
AndroMeld 新功能:屏幕摄像头。
投屏 Android App 到桌面时,不用拿起手机,也可以扫屏幕上的二维码了。
Mac App Store 新版已实装。
driver1998 retweeted
I rewrote the MIDL compiler for WinRT from scratch. 2.5x faster. Full LSP. Extensions for VS Code and Visual Studio.
I wanted better tooling for my own workflow and for every Windows dev's, so I built it.
driver1998 retweeted
Made a VS extension that adds XAML Designer support for modern UWP .NET 9+ projects
github.com/ahmed605/ModernUw…
driver1998 retweeted
The Windows App for Windows now supports connecting to Windows PCs directly 👇
$RegPath = "HKCU:\SOFTWARE\Microsoft\WindowsApp\Flights"
New-Item -Path $RegPath -Force -EA SilentlyContinue
New-ItemProperty -Path $RegPath -Name "PeerToPeerConnectionsEnabled" -Value 1 -Force
driver1998 retweeted
Microsoft needs to bring back annual Windows events.
I think it's important for tech companies to have a predictable moment in the year that everyone knows will be when we learn about what's next for these platforms.
Every year, without fail, Google will unveil the next wave of Android features in May as part of I/O. It's the same story for Apple in June at WWDC.
Windows? Who knows when you'll hear about what's next. It could be Build, or it might not be. It could be a random event in October, or it might not be. Some years, we don't get a Windows event at all!
I truly believe that this lack of an annual, predictable Windows event is doing damage to the platform, as Microsoft doesn't have a chance to set the narrative for what's next over the coming year.
An event would allow Microsoft a moment in the year to talk to its userbase about its plans for the next 12 months. It can highlight new features that are coming, and directly address criticisms and complaints.
Above all else, it generates hype around Windows. Having an expected month of the year where we know Microsoft is going to talk about what's next for Windows is an easy way to keep people talking.
Currently, it feels like Microsoft is ashamed of Windows. It doesn't want to talk about Windows unless it absolutely has to, and that really sucks. Be proud, bring back annual Windows events, and maybe people will start being excited about the platform again. windowscentral.com/microsoft…
driver1998 retweeted
I’ve seen a lot of pessimism today about reactos. So I’m going to drop some cool screenshots now that everything is in WIP PRs for it
Here’s 3D accel working on
Starting from left
INTEL GMA 945
NVIDIA 8800 GTS
AMD Radeon HD 7530G
All while WDDM continues in background.
driver1998 retweeted
The Mystery of MingKwai
stanfordmag.org/contents/the…
driver1998 retweeted
那么多年下来,葡萄🍇、樱桃🍒 都有自己的 Emoji,为啥"荔枝"却没 emoji 呢?
今年上半年,我和我司设计师按照标准流程,向 Unicode 协会提交了"litchi"的 emoji 设计稿 / 申请函,就是下图。
为什么是"litchi" 而不是"lychee"? 是因为 Unicode 协会规定被拒绝的 emoji 表情有 4 年的冷却期,而其他人申请的"lychee" 在 2022 年被拒绝。
万幸"荔枝"有两个英文单词!
Unicode 协会的官网上,明确将在 2025年11月30日公布 emoji 的申请结果,也就是未来 10 天。
希望大家转发点赞互动支持一下。
万一我们设计的"荔枝"emoji 真被收录了,发券!
driver1998 retweeted
In case you had missed it - I had. VirtualBox now supports Windows on Arm.
blogs.oracle.com/virtualizat…
Not a bad alternative to the departed Windows Services for Android.
driver1998 retweeted
Some Windows Pinball Lore:
The original Windows 95 version relied on WinG for fast 8-bit graphics blitting. WinG created a compatible DC and bitmap, but on NT we had no WinG runtime (or it performed poorly, if we had it).
I was on a MIPS box, not x86. To make it run on NT (and this cross-platform for Alpha/MIPS/PPC RISC CPUs), the graphics had to switch to standard GDI using CreateDIBSection(). That gives you a DIB that's directly mappable to video memory on good drivers, so you draw straight into the bits without slow GDI calls for every pixel, and then BitBlt the whole thing to the window DC each frame.
No more WinG-specific IngDC/IngBitmap nonsense — just pure DIBSection for the backbuffer. That was the big change to get decent performance on NT without hardware-specific hacks.
The sound engine of the original was all hand-crafted x86 assembly. Beautiful it might have been, but it wasn't going to run on my MIPS. Or the Alpha or PPC.
I figured out what it was trying to do and wrote my first C sound engine based on some sample code I stole, switched it over, and the sounds are still as iconic today as they were then!
The true art of the game - the original graphics, sound, and even code - I take no credit for, that's all Cinematronics/Maxis people.
I'm just the fun uncle who made it all work in Windows XP so that everyone could play it for free :-)
As far as I can recall at this point, it was all pure C and assembly language (ie, not C++). Most of the non-platform-related game code still survived to keep the experience authentic to the original.
I had a bug where I'd draw a new frame as soon as the CPU went idle, which got me 60-90 FPS on my MIPS box, plenty fast for nice gameplay.
The issue was that CPUs got a lot faster, and within a couple of years, Pinball was still burning a full CPU core, but now drawing 1000s of frames a second!
Raymond Chen fixed it after I was gone, I believe! He put some reasonable cap on the framerate, and now it uses 1% or so of a CPU, if that!
Replying to @davepl1968
Were the Microsoft Pinball games on Windows 95 Plus and Windows NT 4 managed as the same project or as different ones? How much of their code did they share across the two platforms? In pure C code?
driver1998 retweeted
Looking for AVX/AVX2 support in @Windows ARM? If you've got 25H2, you can enable this NOW for specific apps. Simply go into properties > compatibility > change emulation settings and enable "Show newer emulated CPU features"!



















































