bc76e9c79a
Three layers: v86 — src/vmware.js gains the legacy text-clipboard backdoor commands (GETSELLENGTH/GETNEXTPIECE/SETSELLENGTH/SETNEXTPIECE, 6–9). The host stages bytes via the vmware-clipboard-host bus event; the guest pushes via 8/9 and the device emits vmware-clipboard-guest when the buffer fills. Same wire protocol as open-vm-tools' pre-RPC copy/paste. Committed on the windows95-base fork branch; libv86.js rebuilt here. renderer — src/renderer/clipboard.ts polls Electron's clipboard (no change event exists), translates host UTF-8/LF ↔ guest CP-1252/CRLF, and bounces bytes through the two bus events. Echo-suppressed so a value we just wrote does not come back as a change. guest — guest-tools/agent/W95TOOLS.EXE is a 22 KB hidden-window agent that joins the Win32 clipboard-viewer chain (push-on-copy) and polls the backdoor on a 250 ms timer (pull-from-host). Win9x runs ring-3 with the I/O bitmap wide open, so a plain IN EAX,DX from a user process reaches the port — no driver needed. Named for growth: time sync and host-initiated shutdown will live here too. Built with Open Watcom v2 inside Docker (Makefile + Dockerfile alongside the source); subsystem 4.0, no msvcrt, runs on Win95 RTM. Install: copy \\HOST\TOOLS\agent\W95TOOLS.EXE into the guest and drop a shortcut in StartUp. Text only, 64 KB cap.
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.