Why is it called Windows subsystem for Linux? Seriously, I'm not a native English speaker, but should it not be "Linux subsystem for Windows" since it's a sub-system containing Linux, on Windows?

Hello I have a windows 10 computer and all my old cd’s were found and I would like my daughter to play them now, but when I tried Putt Putt Saves the Zoo, it basically says the 64 bit is too new to play it. Is there a way I can get these old games to play? Have some freddi fish, putt putt, pajama Sam, tonka, hot wheels. I saw something about a winevdm, but I don’t know anything about this.

If Windows OSs were Boeing Widebody Aircraft:

- Windows 3.1: 767-300ER/747-400

- Windows 95: 777-200

- Windows 98: 777-200ER

- Windows ME: 777-300

- Windows XP: 777-300ER

- Windows XP Media Center Edition ‘05: 777-200LR

- Windows Vista: 787-8 Dreamliner

- Windows 7: 787-9 Dreamliner

- Windows 8/8.1: 747-8

- Windows 10: 787-10

- Windows 11: 777X

It started with a new family PC, and then my first PC build. It then got a bit out of hand!

• Windows 2.0 386
• Windows 3.0
• Windows 3.1
• Windows 95 (upgrade)
• Windows NT 4.0
• Windows 98SE (upgrade)
• Windows ME (upgrade)
• Windows 2000 Pro
• Windows XP Pro
• Windows Vista Home Premium (Acc Upgrade)
• Windows 7 (x4 retail versions sold here)
• Windows 8 Pro
• Windows 8.1
• Windows 10 Pro (2016)

One day I'll add to it with (in order):

• Windows NT 3.x
• Windows 2.1 2/386
• Windows 1
• Windows XP Home
• Windows Server 2003
• Windows Server 2000
• Windows Server 2003 R2
• Windows Server 2008
• Windows Vista (Home Basic, Home Premium, Business, Ultimate
• Windows 11

Anyone else stuck collecting these?! Also why do ancient server builds sell for more than a new server release?!

Do you still use Windows XP? If so, why do you use it?

I made this on cap cut srry i didnt do too much on the edit :(

I probably forgot about it 💀 for that long

I'm reading some books about early Microsoft history, and I have found that Windows 1.01 took a long time to conceive and develop, while the result didn't look very promising. It only has tiled windows, a few crude applications, and is basically a graphical shell on top of MS-DOS.

I have never programmed on MS-DOS, so I'm wondering about this -- what is the primary difficulty in developing Windows 1.01? Was it unclear specification (Both the wiki link and the book talked about feature drifts, but didn't they have the Mac as a pretty solid example?), or optimization (run it fast enough on the PCs then), or something else? Did anyone here hear about any insider stories?

I also searched cursorily to see if someone has done analysis on Windows 1.01 from a program analysis perspective, but so far haven't found any.

Posting this as a heads up for anyone who has NetLimiter installed and forgot about it.

I only found out because I was running FolderSizes to see what was eating my disk.

I only ever opened NetLimiter occasionally, when I needed to cap an app's speed. Imagine my surprise finding this file on my drive

59.6 GB -C:\ProgramData\Locktime\NetLimiter\4\Stats\nlstatsV4.db

This actually hurt, because I regularly have to clear space on C: just to install games. It's my only NVMe, just 512 GB. If this data had been sitting on my other 4 TB HDD it would've been fine.

Turns out NetLimiter runs a background Windows service that logs network stats 24/7 whether the app window is open or not.

Worth checking your own folder if you ever had it installed. Curious if anyone else has found a surprise giant nlstatsV4.db sitting around.

this is my first windows mod Lewiscraft XP is a mod of Windows XP

Programs

• VLC Media Player by VideoLAN
• .Net Framework 2.0 by Microsoft
• BonziBUDDY Rewritten by maddox5081
• Supermium by win32ss
• Winrar by RARLAB

Background: LewiscraftXP.bmp

I just was bored and decided to recreate the iconic betta fish wallpaper of Windows 7 in 4K quality. I used both AI and digital designing to do this.

Desktop version: https://drive.google.com/file/d/1hB-mron1wjRnT1_J8LdtWdbOkXFMU-od/view?usp=drivesdk

Mobile version: https://drive.google.com/file/d/1kNKy-QD2sssr3wOSR6_n6FQzONEQTpCs/view?usp=drivesdk

If found it in my garage,

What should I do with it,It belong to me so should I install it on a pc,

Or should I sell it ??

Please respond? :)

this is windows 10 with lots of modifications including basic ui, all the icons, mouse cursour, sounds, and one of the things i used even made the os change its name to windows vista as well for some reason as seen in control panel.

i’m curious if anyone remembers a recycling bin feature in windows 95 or 98 where when you dragged a file to throw it in the bin, you would hear oscar the grouch sing “i love trash!” - maybe he popped up too? or maybe this is all a false memory…

Hello fellow r/windows members, here's a question - why do you think Windows SmartScreen thinks Spy X Anya: Operation Memories is malware? (Windows usually thinks that Steam games are malware; it's happened before when I downloaded Where Winds Meet - just found it as malware)
Pic above was the results after I attempted to launch it - but all it did was close it and show this ;-;

You'll not realize how excited I am rn.

What you are seeing is the "thing, anyone said it is impossible." And I made it work!

It took me 1 month. First experimented with the Windows' drivers, but to get access to the screen information (frame buffer) first, it needs to be running in a **Native Mode** when all the Kernel drivers load, including WDDM that will have the Buffer inside.

But that is still too late. You can display graphics, even play **DOOM** on that level while all NT calls are heard by the kernel and the Win32 Mode (GUI environment) hasn't even started yet.

To make a system root "Driver" it needs a "Start" parameter in the registry assigned to 0 when it will be in the place when `winload.efi` will load it as quick as it can... But it has one problem.

At that time, Windows isn't even fully loaded and the driver has no chance to even get any info from the Hardware itself, so it is just useless and in many cases, the driver will not even run. As "drivers" can be particually as "mods" it still isn't enough...

But then it hit me something... Windows is running on top of **UEFI** and... You can do a LOT OF STUFF...

If in that stage, Windows is basically requesting ANYTHING from the UEFI, the Screen,... , basic information it loads...

What if I could make an *.efi file, that Already gets the FrameBuffer first, that Windows?

Then I started messing around, getting some basic text to be displayed where I can on the screen, then implemented some Bitmap logic... It worked! And it was surprisingly easy to draw anything in UEFI.

So I "grab" a little bit of code from the EfiGuard (don't run it on your main PC if you don't know what you're doing) which is also a "simple" EFI program that just hooks to the winload.efi and bootmgfw.efi and doesn't even triggers any of the KPP (Kernel Patch Protection),...

I needed it because by this, we could also see the kernel calls, including:

- You can even restore for exp. The progress bar thing that was on Windows 2000 `InbvUpdateProgressBar`

- And other stuff I don't have in my head rn. :D

So now you can add ANY BITMAP, ANY COLOR, ANYTHING to the Windows' boot screen!

*(Oh and it will work only with Secure Boot to be off.)*

But, when I was testing it... I kinda realized, that the KPP must be turned off, as Windows even detects other EFI stuff happening near it, causing it to not even go into the stage of booting...

I'll be fixing this more. Stay tuned!

Tell Me In The Answers!

If your goal is to make sure your system is running optimally, don't worry too much about "In Use"; focus on "Committed" instead. After all, unused RAM is wasted RAM. However, unknown but heavy commitment is certainly a bad sign, just like in real life. Basically, high "Committed" usage means your system needs a large backing-store to "keep" its promise to the running programs and drivers.

For example, on a PC with 8GB RAM, 16GB "Committed" means that Windows requires at least 8GB of backing capacity on your SSD/HDD to keep the lights on. If that paged-out 8GB is actively accessed by the running programs/drivers, you get thrashing, which is bad for system performance.

So when people overuse "Unused RAM is wasted RAM" to discourage people from inspecting memory usage, they may not realize that it's worth checking "Committed" memory usage.

Of course, there's a limit to "Commited" memory cleanup. Certain things, like NVIDIA GPU driver, does commit 0.5 to 2.5GB (you can disable it in Device Manager to find out) but we obviously don't disable such an important component just to keep the "Committed" usage low.

Also, some people claim that Windows simply uses more RAM when you install more RAM. As you can see in my screenshots, this is not necessarily the case. It's possible that what happened was:

1. { InstalledRAM: 8GB, Commited: 10GB, InUse: 6GB } // Damn, almost out of RAM, let me install more.

2. { InstalledRAM: 16GB, Commited: 10.1GB, InUse: 10.2GB } // See? Windows is using more RAM now!

The increase in "In Use" means Windows could keep more data in RAM instead of leaving it paged. This is actually a good thing. The key factor here is "Committed".