←back to thread

I have released a 69.0MB version of Windows 7 x86

(twitter.com)
186 points rvnx | 1 comments | 30 Oct 25 18:05 UTC | HN request time: 0s | source
Show context
thunderbong ◴[30 Oct 25 18:41 UTC] No.45763632[source]▶
From the thread [0] -

> This was more of a fun proof of concept rather than something usable. Virtually nothing can run due to critical missing files such as common dialog boxes and common controls.

[0]: https://x.com/XenoPanther/status/1983579460906487835?t=7jLSz...

replies(3): >>45764147 #>>45766298 #>>45769741 #
happymellon ◴[30 Oct 25 19:22 UTC] No.45764147[source]▶
If it can't run Windows 7 software, is it really Windows 7?
replies(5): >>45764200 #>>45764296 #>>45764693 #>>45765247 #>>45766144 #
ronsor ◴[30 Oct 25 19:26 UTC] No.45764200[source]▶
It almost certainly can run basic CLI apps linked only to kernel32.dll
replies(2): >>45764308 #>>45766491 #
znpy ◴[30 Oct 25 19:33 UTC] No.45764308[source]▶
If this was a linux container, it would be a base image.

I wonder if this could be used to cobble together some duct-tape windows-7-based firecrackers vm thing.

replies(1): >>45765549 #
zokier ◴[30 Oct 25 21:23 UTC] No.45765549[source]▶
Windows containers are a thing, and MS has "Nano Server" base image.

Back in the day, MS did even release Nano Server as a standalone OS, from what I gather it was generally <500MB. Pretty decent for a Windows you could actually run applications on.

replies(2): >>45765637 #>>45770511 #
esseph ◴[30 Oct 25 21:32 UTC] No.45765637[source]▶
> Windows containers

Are people using these in production? I assume so, with libvirt handling them on k8s for a vmware transition option.

replies(2): >>45765893 #>>45766061 #
1. tecleandor ◴[30 Oct 25 22:16 UTC] No.45766061{3}[source]▶
Although I don't manage those, I've seen them at work. Running on EKS Windows nodes, for dotnet and SQL Server loads.