5 ms·
> Technically, the Am386 could run Windows 95, but it wasn’t a great experience. Technically not. It can run it. Was slow? Yes, but my Am386DX40 keep working
by Zardoz84 8mo ago
> Technically, the Am386 could run Windows 95, but it wasn’t a great experience.
Technically not. It can run it. Was slow? Yes, but my Am386DX40 keep working fine from 1991 to 1996. Running DR-DOS 6, MS-DOS 6.11, Windows 3.1 and finally Windows 95. And, of course, I could play DooM 2 on it. At some point, I got a math copro.
Finally, my father upgraded the machine with an AMD 486DX5 133MHz.
- iberator 8mo agoNETBSD still can run on it too :) Best and most portable os in the history
- messe 8mo ago> most portable os Eh... I think the Linux kernel + your choice of libc/userland has it beat these days.
- actionfromafar 8mo agoModern Linux dropped support for a lot of old and niche CPUs.
- messe 8mo agoAnd NetBSD is missing support for an order of magnitude more SoCs. I like NetBSD. I've run it on several systems in the past, and not just as a toy. I like the whole BSD family, and even deploy FreeBSD in production at work, and use OpenBSD on my home router. But NetBSD's claim as the most portable OS doesn't hold up these days.
- anthk 8mo agoModern Linux can't even scratch a 486 and some Motorola platforms. Or VAX. Heck, I run NetBSD 10.1 vanilla under simh 3.8 for 9front emulated on an amd64 laptop (old Celeron, 2GB). Slow, but enough to play Slashem. On portability on compilers, plan9/9front it's unbeatable. Do you now Go compiling from any OS to any arch? The same here, but just for an OS obviously. Albeit I can still run Golang under i386, and tools like Rclone under 9front i386. That's really cool.
- messe 8mo agoThat's a very limited view of what portability means. Driver support for a niche SoC? Good luck getting NetBSD on before Linux. The sheer amount of SoCs supported by the Linux kernel dwarfs anything NetBSD has to offer.
- spijdar 8mo agoYeah, NetBSD's support for modern hardware isn't amazing compared to Linux. I love it (and run my personal web server on it!), but the portability thing feels like a meme from the 4.4BSD days, where it ran on basically every workstation platform. Like sure, it runs on my VAX, my Sun4/75, and my Alpha box, but it doesn't run on my POWER9 workstation nor does it run my Amlogic A311D ARM device (at least in a usable capacity), and I couldn't even get i.MX 8M running. I didn't try super hard, to be fair, but why would I burn cycles getting an OS with less peripheral support running when Linux "just works"?
- hulitu 8mo agoI don't think Linux "just works" on VAX, Sun4/75, or Alpha. My experience with Linux on a Sun Sparcstation 20 circa 2000 was that it was slow as hell compared to Net or OpenBSD.
- messe 8mo agoI doubt NetBSD "just works" fully on those systems either. I see a lot of rose tinted glasses when NetBSD portability comes up. Those older systems barely get stress tested, as the system has become too large to be self-hosted on them anymore and has to resort to using cross compilation to build a working base. At least OpenBSD, when it says it supports a platform, _actually supports that platform_, and the system is stable enough that it can build itself.
- accrual 8mo ago> At least OpenBSD, when it says it supports a platform, _actually supports that platform_ I always thought it was cool OpenBSD compiled on each arch itself. IIRC, there is or was a rack of servers, each with a unique architecture that all built their respective release files. The various targets could help catch arch-specific bugs leading to more portable code. VAX was always last and the slowest, which was part of why VAX support was dropped some time ago.
- lproven 8mo agoThe Linux kernel dropped 386 support fourteen years ago. https://www.theregister.com/2012/12/12/linux_no_longer_runs_on_386_cpus/ https://www.theregister.com/2012/12/12/linux_no_longer_runs_...
- messe 8mo agoI'm well aware, thank you. I'm not contesting ability to run on a 386, I'm contesting the title of "most portable OS".
- lproven 8mo agoOK. In context -- discussing an article talking specifically about AMD 386 chips -- that was not at all clear. I was at a talk celebrating NetBSD's 30th anniversary. I wrote about it: https://www.theregister.com/2024/04/17/30yo_netbsd_releases_v10/ https://www.theregister.com/2024/04/17/30yo_netbsd_releases_... They're well aware of this. But as Linux edges closer to dropping 32-bit x86 completely -- most distros already have -- I think NetBSD may suddenly regain some relevance in this specific area. There's also a new initiative to improve its jails facility: https://netbsd-jails.petermann-digital.de/ https://netbsd-jails.petermann-digital.de/
- Zardoz84 8mo agoI have a 486DX2 at 66 that I have as pet project to mess with Windows 95, MSDOS and S.u.S.E. Linux 5.3 . SuSE 5.3 was my first full distro (the whole pack of 6 cdroms), and I had good memories of how was easy to install stuff with YaST. I could try to upgrade to the mighty Am486DX5 at 133. I managed to get one, but I need to mod the MBO to give the low voltage required by it. The MBO it's prepared to it, but don't have populated the regulator...
- accrual 8mo agoVery cool! I have a DX4-100 system with an empty CF card calling for Linux, I'll have to give SuSE 5.3 a try. I see it has KDE 1.0 which will be fun to explore. I had similar experiences with the Am486DX5, I could only run it at 100MHz and I also suspect it's voltage related.
- killerstorm 8mo agoMy father got me a second-hand computer with Am386DX-40 somewhere around 1997, IIRC. An upgrade to older 286. It was two generations old at that time but still a lot of fun: it could run a lot of games (incl. DOOM, of course), programming (largely Turbo Pascal 7), and some word processing under Windows 3.11. I didn't bother with Win95, though. I've been using it up until 1999, when I finally got a then-modern computer with Windows 98. But in some ways MS-DOS felt more capable - I really knew what each file is for, what computer is doing, etc. I.e. the entire machine is fully comprehensible. You really don't get it with Windows unless you're Russinovich or something. So in a way 386 was a peak computer for me
- snarfy 8mo agoWhich math copro? If you had a 386DX then I believe you had the math copro? The 386SX did not have an FPU and needed the additional 387SX.
- to11mtm 8mo ago> If you had a 386DX then I believe you had the math copro? The 386SX did not have an FPU and needed the additional 387SX. Neither had FPUs... Closest you can get is RapidCAD (which is really a 486DX adapted to 386 bus, IIRC it uses a 'jumper' for the 387 slot.) For 386, the difference between SX and DX was whether it was a 16 or 32 bit data bus. Where things can get more curious, is that some early 386 motherboards actually took a 287 instead of a 387...
- dragonwriter 8mo ago> If you had a 386DX then I believe you had the math copro? The 386SX did not have an FPU and needed the additional 387SX. The 386DX/386SX distinction was the external databus (32-bit on the DX, 16-bit on the SX) DX was “Double word eXternal", SX was “Single word eXternal”. Neither had an FPU builtin, and there were corresponding 387DX and 387SX coprocessors. Then Intel used the same naming split (despite the abbreviations not applying) for high-end vs low-end of the 486 where the DX had a builtin FPU and the SX required a “487SX coprocessor” to get an FPU (which IIRC was internally just a 486DX processor which went into a separate “coprocessor slot” which just bypassed the “main” processor when populated.)