4 ms·
> Try to setup a windows 98 machine as a web server and see how it goes Windows 98 was a client OS, it was never intended for this. A proper test would be Wind
by morganvachon 6y ago
> Try to setup a windows 98 machine as a web server and see how it goes
Windows 98 was a client OS, it was never intended for this. A proper test would be Windows NT 4.0 Server. Or more realistically for the time frame, Solaris 7 or 8.
- anthk 6y agoW98 had a simple HTTP home server available for install, as did BeOS I think. Nothing comparable to Apache/IIS, but it was a thing. Obviously forget about any security.
- snowwrestler 6y agoAny web server software set up in 2000 and still running today unpatched could be pwned quickly. Including and especially NT 4.0. When you're running a server, TLS is not the only service you are dependent on; you're also dependent on security updates. If they're not backported, you'll need to make version upgrades. Arguably it's better to think of every piece of software running on a server like it's a service, to maintain security and performance in an Internet full of hostile actors. I don't even understand the mindset of wanting to run a live server on ancient software, aside from doing it as a hobby. In which case, it's pretty typical for such hobbies to require extra work and care. Driving around in a car from 1940s takes more maintenance work, and is less safe, than a modern car, and everyone gets that.
- morganvachon 6y agoI think you misunderstood my comment, I'm not advocating doing this. I was simply correcting the person above me who appears to be under the impression that web servers in the 90s ran on a client OS.