Is there a link with more info (while we wait for the server to catch up)? Sorry if I missed it!
Edit: misread the CPU as a 486 somehow. I was wondering why the clock speed was so low.
2,500 continuous runtime hours on a 4.77Mhz DOS web server
31–40 of 92 posts
Re: 2,500 continuous runtime hours on a 4.77Mhz DOS web server
#32Is there a link with more info (while we wait for the server to catch up)? Sorry if I missed it! Edit: misread the CPU as a 486 somehow. I was wondering why the clock speed was so low.
486? Nah. 4.77Mhz NEC V20, which is just slightly faster than an 8088.
This should tide you over: http://www.brutman.com/PCjr/pcjr_web_server.html
The main page is the best link. You might want to try back later after the initial rush; the machine is getting pounded.
Re: 2,500 continuous runtime hours on a 4.77Mhz DOS web server
#33(Sorry, I forgot to preface this with Show HN) ** 2023-07-14 18:38 PDT The DOS machine is getting DoSed. It's still beeping and happy but it's busy. ** This website is hosted on a 39 year old PCjr running at 4.77Mhz and it has been running over 2,500 hours continuously now. No reboots or program restarts ... you can see the current runtime stats by visiting http://brutmanlabs.org/status . The machine specs are: - IBM…
I guess HTTPS is just a little bit too much processing power for it to handle?
Re: 2,500 continuous runtime hours on a 4.77Mhz DOS web server
#34Better press that Turbo button.
Re: 2,500 continuous runtime hours on a 4.77Mhz DOS web server
#35(Sorry, I forgot to preface this with Show HN) ** 2023-07-14 18:38 PDT The DOS machine is getting DoSed. It's still beeping and happy but it's busy. ** This website is hosted on a 39 year old PCjr running at 4.77Mhz and it has been running over 2,500 hours continuously now. No reboots or program restarts ... you can see the current runtime stats by visiting http://brutmanlabs.org/status . The machine specs are: - IBM…
I guess HTTPS is just a little bit too much processing power for it to handle?
Yeah, far too much for a little CPU like this. Never mind the horror of trying to port all of the libraries and keep them up to date.
Although there are people are using Apache in front of their vintage computers to terminate SSL for them while still having the vintage computer handle the request.
Re: 2,500 continuous runtime hours on a 4.77Mhz DOS web server
#36cf. https://fsturmat.net/blog/04202022/ on hosting a site running the same mTCP HTTPserv server under QEMU on a VPS, with SSL via Caddy reverse proxy.
Re: 2,500 continuous runtime hours on a 4.77Mhz DOS web server
#37cf. https://fsturmat.net/blog/04202022/ on hosting a site running the same mTCP HTTPserv server under QEMU on a VPS, with SSL via Caddy reverse proxy.
http://floppy.museum also running mTCP HTTPServ, but on 80286 class hardware.
(That was featured earlier this year on HN.)
Re: 2,500 continuous runtime hours on a 4.77Mhz DOS web server
#38He's dead, Jim.
It's still beeping ... busy != dead. Right now it's getting hammered pretty hard. I haven't implemented the clustering and load balancing yet. It can serve 8 concurrent connections but that slows it down. It will queue a few more too; be patient and you will be rewarded.
May be fun to listen to a recording of the beeps.
Re: 2,500 continuous runtime hours on a 4.77Mhz DOS web server
#39(Sorry, I forgot to preface this with Show HN) ** 2023-07-14 18:38 PDT The DOS machine is getting DoSed. It's still beeping and happy but it's busy. ** This website is hosted on a 39 year old PCjr running at 4.77Mhz and it has been running over 2,500 hours continuously now. No reboots or program restarts ... you can see the current runtime stats by visiting http://brutmanlabs.org/status . The machine specs are: - IBM…
One of my friends was way ahead of the rest of us in 1987, and bought a V20 to upgrade his Tandy computer. He works for a telcom now. Nice to see one still churning away.
Re: 2,500 continuous runtime hours on a 4.77Mhz DOS web server
#40I once ran most of a fish tank worth of water through an internet-facing 25MHz computer with at least that much uptime. It stayed up, but I had to replace the boot floppy. (Not the whole drive; just the $5 disk). No fish were harmed.
That is astonishing if water got on the motherboard