The fetch network adapter only intercepts port 80 (parsed as HTTP and replayed via fetch). Everything else was RST'd. This adds a second tcp-connection bus listener that bridges any other destination port straight to a Node net.Socket in the renderer — no extra process, no WebSocket relay, no new dependencies. - net/tcp-relay.ts: hook v86 tcp-connection, accept SYN synchronously, open a real socket to conn.psrc:conn.sport, buffer until connect, pipe both directions, tear down on either side closing. Loopback, link-local and multicast are refused; the rest of RFC1918 is left reachable so the guest can still talk to LAN devices. - net/dns-shim.ts: dns_method is now "doh" so the guest gets real IPs for the relay to dial, but Cloudflare can't answer single-label names like "windows95" or the NNN.external localhost magic. The shim wraps global fetch, spots /dns-query POSTs for those names, and answers with the same 192.168.87.1 placeholder the static resolver used to hand out — the port-80 fetch path then takes over via the Host header exactly as before. - emulator.tsx: wire both in next to the SMB hook; set dns_method. - debug-harness.ts: WIN95_PROBE_RUN/_RUN_AFTER/_RUN_WAIT to type an arbitrary command into Start→Run (used to e2e-test the relay with telnet against a host echo server).
windows95
This is Windows 95, running in an Electron app. Yes, it's the full thing. I'm sorry.
Downloads
|
Windows |
32-bit
💿 Installer
|
📦 Standalone Zip
64-bit 💿 Installer | 📦 Standalone Zip ARM64 💿 Installer | 📦 Standalone Zip ❓ Don't know what kind of chip you have? It's probably `x64`. To confirm, on your computer, hit Start, enter "processor" for info. |
|
macOS |
Apple Silicon Processor
📦 Standalone Zip
Intel Processor 📦 Standalone Zip ❓ Don't know what kind of chip you have? If you bought your computer after 2020, select "Apple Silicon". Learn more at apple.com. |
|
Linux |
64-bit
💿 rpm
|
💿 deb
|
|
|
|
Does it work?
Yes! Quite well, actually - on macOS, Windows, and Linux. Bear in mind that this is written entirely in JavaScript, so please adjust your expectations.
Should this have been a native app?
Absolutely.
Does it run Doom (or my other favorite game)?
You'll likely be better off with an actual virtualization app, but the short answer is yes. In fact, a few games are already preinstalled - and more can be found on the Internet, for instance at archive.org. Thanks to @DisplacedGamers I can recommend that you switch to a resolution of 640x480 @ 256 colors before starting DOS games - just like in the good ol' days.
Credits
99% of the work was done over at v86 by Copy aka Fabian Hemmer and his contributors.
Contributing
Before you can run this from source, you'll need the disk image. It's not part of the
repository, but you can grab it using the Show Disk Image button from the packaged
release, which does include the disk image. You can find that button in the
Modify C: Drive section.
Unpack the images folder into the src folder, creating this layout:
- /images/windows95.img
- /images/default-state.bin
- /assets/...
- /bios/...
- /docs/...
Once you've done so, run npm install and npm start to run your local build.
If you want to tinker with the image or make a new one, check out the QEMU docs.
Other Questions
- MS-DOS seems to brick the screen
- Windows 95 is stuck in a bad state
- I want to install additional apps or games
- Running in Docker
- Running in an online VM with Kubernetes and Gitpod
License
This project is provided for educational purposes only. It is not affiliated with and has not been approved by Microsoft.