I ported THOUSANDS of apps to Windows 95

Windows 95❌ A fucking movie:✅

This is a phenomenal piece of cinematography you've produced here. It doesn't even look low-budget! (well, except for my 2 second cameo)

i’m a game developer, and the workaround for printing the unhandled exception to the gui made me CRY laughing. genius.

Neighbor Discovery Protocol Helper and 0x40 means "NDP_NEIGHBOUR_SOLICITED" A network mode to connect 2 computers without a router. And this step announces the computer on this network.

Program: eldritch screeching Matt: "40" Program: purring

A wise man once said DEVELOPERS DEVELOPERS DEVELOPERS DEVELOPERS

I worked at a tape manufacturer not long ago that has all the lab testing equipment still on 95. Youll be making some very happy people out there.

I write NET 2.0 projects all the time. You'd be shocked the private companies, cities, government, and other projects that all still run on dinosaur technology. Though, the depressing part is so little people utilize NET 2.0 and they continue making their ever expanding code/framework in the old framework that will never translate to the new one. It's such a pain to force clients to move to NET 2.0 because I've got to tell them, "Your code won't last forever. Use Net 2.0 because then you can continue coding but the library will translate to newer projects". Because in the NET world, there was an apocalyptic event that split the NET environment. Anyone who was on the 4.7 (or now 4.8) NET framework got completely dropped by Microsoft for the newer NET core framework. The newer one is millions of times better, but it screwed everyone on the old framework. So I've basically been employed for a long time simply helping project after project after project get off of 4.7 and onto the newer core. That's my developer rant. Your welcome. You're weird if you read this. But if you did. Remember. USE NET 2.0 IF YOU ARE STUCK ON THE OLD FRAMEWORK! Please!

Imagine if every time you put a project on GitHub, you had to spend six months making a parody film explaining your process.

Fun fact, the installer has more registry keys than there are seconds in this video. Can't believe the amount of effort that went into this whole thing! Utterly incredible.

I used to work in IT in the meat industry, we had multiple machines in factories across the world that still ran on 95 or 98 and had zero upgrade paths. When one went down if the spare didn't work (or just didn't exist) we would frantically scramble to bring up a VM backup of the machine and fight for ages to get it to talk with the old hardware. I can think of many situations where having this solution would have been useful. You sir, are a genius!

I hope Dave from Dave's Garage sees this. Reckon he'd love to see it being one of the devs of Windows' OS back in the 90s. Great effort mate. Was a pleasure to watch your journey and inspiring as a neat project for software devs to try it for fun that isn't just another 'portfolio piece'.

As a .net dev I really, really enjoyed seeing you get it working on an operating system it was never meant to run on! I haven't enjoyed a video as much as I did this one in a long time - well done Matt!!!

Dude the fact that you did this project is insane on its own, but you also just MADE A FILM NOIR IN THE MIDDLE OF THIS VIDEO? So nuts dude, amazing work

I have to say, I am very surprised to not only see such a technical feat of backporting, but a good noir parody film. I've made movies with people, it's a lot of work. But you're also debugging. You are an inspiration!

Sometimes it actually might matter more than we think. When I was doing my thesis in chemistry less than 10 years ago, we had this chromatograph that needed to be connected to a computer with win 95. Mostly because of the port used to connect the machine to the PC, but also the software wouldn't properly run on more modern versions. While a bit older than two other models we owned, the fact was that this was the best chromatograph we owned - not as versatile or flexible, but it was the one less prone to weird malfunctions and was very reliable (while the more modern one, I spent more time "debugging" - ergo, moving screws and valves around - than actually working) and cheap to run thousands of analysis. This meant that my working process was: - Run stuff on 95 and save to a floppy disk. I could only save 2 or 3 runs (my thesis involved thousands) per floppy due to file size. - Get the floppy on another computer with XP, because it had both floppy disk and support USB. This PC does not support either the modern software I needed to run analysis on, neither the old software from the other PC. It also didn't have internet, presumably, because the USB was connected to a PCI port instead of network card. Realise that most modern usbs aren't recognised by the PC for some odd reason, needed to find a 1Gb drive to be able to make it work. Save to usb. - Take the USB across the hall to a modern computer running (at the time) Win 8.1 and finally shove the files into my analysis software and upload them to the cloud. - Repeat this 10x a day. Everyday. For two years. While I'm not sure backporting would've solved anything here (but probably we would've been able to transfer that port into a more modern computer if we had been able to run the software), this just goes to show that there is still a lot of specialised equipment still to this day running on win95 and good will (because I very much doubt they bought a 20k equipment - 20k is considered economical by this equipment standards - to replace a fully functioning old one).

I checked ndphlpr.vxd file with a disassembler and it's really just a simple wrapper to get and set the thread context. Presumably on Windows 9x they could not use GetThreadContext and SetThreadContext because of some quirk. On newer versions they do not load that driver (obviously) and use GetThreadContext and SetThreadContext directly. Judging by paths in the .NET dlls (such as "f:\rtm\ndp\clr\src\debug\ee\debugger.cpp") ndp is just an internal codename or abbreviation for .NET. EDIT: I looked at the Win9x kernel and I think I understand why this is needed. In Win9x SetThreadContext changes the context immediately regardless of whether it's the current thread or another thread, while on newer versions an APC is used when changing the context of another thread. Presumably .NET needs the latter and it implements it through ndphlpr.vxd, also using an APC.

why is this a cinematic masterpiece? i expected a documentary on how some guy ported some modern windows apps to windows 95

The cinematography in this is amazing. Not only did you produce a genuinely informative and entertaining retro-tech video but you also made a FILM out of it. The sheer quality of it absolutely knocked my socks off and I loved the take on noir you added in the mix. Big W's all around man, this was a masterpiece.

Back in the late 80's I tried learning assembly by just using the C128 monitor and not an actual compiler program. You stepping through the program line by line brought nightmare flashbacks.