this CPU seems like a buggy one, sad https://github.com/86Box/86Box/issues/1192
OK so here’s my brief guide into computering on 86box
Socket 8 machineIntel VS440FX
Intel Pentium II Overdrive @ 333 Mhz
192 MB of RAM (max supported ootb by Rhapsody DR2, feel free to raise)
HDD with up to 1023 cylinders, 2GB or higher recommended
Diamond Stealth 3D 3000 PCI (S3 ViRGE/VX)
Creative Sound Blaster 16
SLiRP with Novell NE2000 ISA16 network card
Standard PS/2 mouse (haven’t played with this yet)
If you want OS/2:
Install in orderOS/2 Warp 4.52Leave the default graphics driver or pick SciTech Display Doctor
Add Sound Blaster 16 manually (configure IRQ correctly!)
NE2000 Microsoft driver (configure IRQ correctly!)
Enable DHCP, leave DDNS disabled
Some software might only reliably work with up to 256 colors
Object Desktop 2.0 (see https://www.stardock.com/support_old/os2/od/odbug20/sec1.htm#question2 for errors!)
Latest version of WarpIN
this will go into a proper webpage later someday eventually anytime sometime
ok heya back
so far: just realized the K6-2+ can be upgraded to 550MHz aaaaaaaand… seems to behave just as fast as lower frequencies? also sound stutters? Weird
the K6-III+ ALSO works at 500MHz under certain motherboards… and yup, this one is DEFINITELY faster… except compile times remain the exact same so it’s not. Maybe I/O bottleneck?
I should have used some actual benchmarks, but I’m pretty sure a 500MHz K6-III+ should be faster than a Pentium II Overdrive at 333MHz, so I’m keeping it even if not recommending it due to the stutter (even if it only affects startup and shutdown for me)
Think about this for a second.
Everything works in the exact same way. Everything is objects, created with templates, and with a properties panel. Every object can talk to each other through SOM. Objects talking to each other lets you extend objects themselves, adding functionality. Apps are objects made of objects too, so everything about this applies.
You see where I’m going?
There’s one point at which you realize, why shouldn’t all documents work like this? Standardize it all so you can have documents made of objects that can do anything, on an app that is made of objects that can be extended at will.
That’s OpenDoc.
This is something I already talked about… on the Apple side of things. If you have a good eye, you’ll spot SOM around there https://fedi.xerz.one/notice/A5s6APMK9A5Ab2a5AW
Anyway, this is ultimately what IBM and Apple aspired to do: after Microsoft betrayed IBM by stealing VMS and making their own kernel, IBM immediately called Apple and Motorola to join forces. The idea was that they could make their own standards that made all computers work the same transparently, and Apple and IBM would be on top of it all, hoping wide support and competition would make Microsoft and Intel’s efforts fail.
IBM would provide OS/2, SOM and POWER. Apple would provide Taligent and OpenDoc. Motorola would act as a fab for IBM. And they would all work towards a PC standard, CHRP.
No more worrying about CPU architectures. No more worrying about OSes. No more worrying about apps. The AIM alliance would do it all, and make it all work together for everyone.
So for instance, just take this article’s intro to see how important OpenDoc was.
“‘And God went to say: “it is not good for the man to continue in a sea of Windows. I am going to create OpenDOC for him…’ “
https://www.os2world.com/wiki/index.php/OpenDOC,_a_Forgotten_Technology
@WomanCorn yeah I feel the same, when you got Cyberdog you were thinking about getting a web browser, not a document editor