anyfoo

25 ms·

361.
by anyfoo 2y ago
> and 95 (surpisingly) ran faster with smartdrv preloaded. 95’s default cache for some reason was worse than smartdrv My (weak) guess is that you "32 bit disk access" and "32 bit file access" wasn't active then,
362.
by anyfoo 2y ago
And that was achieved?
363.
by anyfoo 2y ago
Always a joy when os2museum updates. I, too, remember the trifecta of APPEND, JOIN, and SUBST. And while I always thought they were interesting, I was also wondering for most of them when I would ever use that. At the time, DOS versions and
364.
by anyfoo 2y ago
Fair, Windows was more subtle there. Maybe in other regards and overall as well, it's hard to do just from memory.
365.
by anyfoo 2y ago
Still simplistic. "Breached" can mean a number of things, and the incentives here are very different.
366.
by anyfoo 2y ago
The comments you pasted in particular are about stuff that makes sense and that someone who wants to fully understand some source code can readily figure out, if they put their mind to it. It's when things don't make sense that
367.
by anyfoo 2y ago
They do, but you usually need to put some effort in.
368.
by anyfoo 2y ago
Well, either the standard model is right, or it isn't, isn't it? They asked for indication of an "early phase", not that we're ready to throw the standard model out (which, boringly, held up extremely well so far).
369.
by anyfoo 2y ago
That is far from the only thing that would be relevant for such a metric. (For one thing, you also have to ask which kernel.)
370.
by anyfoo 2y ago
Yep. I don't think P&G implies that the VM needs to run with exactly the same capabilities and characteristics as the host architecture. If that were true, then probably a large amount of modern virtualized machine are suddenly not
371.
by anyfoo 2y ago
Hah. It is pretty crazy that the Acorn Archimedes chip won.
372.
by anyfoo 2y ago
Hardware virtualization with feature parity came very late. Hardware virtualization limited to real mode VMs came with the 386 itself, as the commenter you replied to mentioned. It was absolutely crucial to its success. The 286's pro
373.
by anyfoo 2y ago
> The generous use of colors in OS/2 made it look like a kindergarten scrapbook Are we still talking about OS/2 2.x? I somehow remember it to be more "somber", and a very quick search seems to confirm that, though it&
374.
by anyfoo 2y ago
Win95 (and beyond, and somewhat before) DOS boxes also allowed to run DOOM and other protected mode software. But pretty much only if the software was written for "DPMI" ("DOS Protected Mode Interface")[1], which abstrac
375.
by anyfoo 2y ago
Heh, I assume you just read https://news.ycombinator.com/item?id=42414817 and stumbled upon XOR textures as well?
376.
by anyfoo 2y ago
I think 386+ Windows did the same, all through at least Windows 95. I even remember some goose chasing trying to enable the coveted "32 bit disk access" (which IIRC meant using native protected mode Win drivers for disk access) in
377.
by anyfoo 2y ago
I don't think they're mistaking anything. 386-era Windows and OS/2 versions used the CPU's v86 task support, which, while having some severe warts[1], can well and truly be called "virtualization". [1] Most of
378.
by anyfoo 2y ago
Hmm, tough call. I remember it looking "more professional", in some ways even more logical, but overall I'd say Windows 3 (and yeah, especially 3.1/WfW 3.11) was more "pleasing". That was mostly the color schem
379.
by anyfoo 2y ago
I don't really doubt that that's true for business or marketing decisions, but what exactly were the technical reasons? I don't know too much about OS/2 internals, but what made it worse than, say, NT?
380.
by anyfoo 2y ago
From hands-on experience, I've learned that v86 initially had some severe, ugly warts, which made writing a v86 "hypervisor" way more tedious, and make it run slower, than what seemed reasonable. These limitations were addres
381.
by anyfoo 2y ago
As some added context, that is probably[1] true for any Windows version that uses v86 (which implies at least a 386 and enhanced mode windows), not so much for any earlier, non-enhanced Windows, or any Windows running on anything less than
382.
by anyfoo 2y ago
So called "post-exploit" mitigations are practically always only hardening, i.e. making subsequent attacks harder (and fewer). Ideally much harder. But if you want an absolutely, provably (within limits, i.e. halting problem etc.)
383.
by anyfoo 2y ago
My order is, and has been for decades: foo, bar, baz... and then I don't know anymore and make stuff up.
384.
by anyfoo 2y ago
Sonic (beloved Bay Area ISP) got pestered with requests for IPv6, until they finally natively implemented it for their fiber, even though they had 6rd tunnels before. But granted, Sonic is favored by enthusiasts, so they likely have a highe
385.
by anyfoo 2y ago
> Transmission lines alone would be huge. Or small! :D
386.
by anyfoo 2y ago
True.
387.
by anyfoo 2y ago
If it’s only combinatorial logic, without any flip-flops or anything else you can consider “state”, it depends on how many inputs it has. 16 inputs is 65536 combinations. Even at a very low clock it takes you no time to just try all of them
388.
by anyfoo 2y ago
Is that still the case? IOMMUs have been a thing for a very long time, and nowadays you don’t trust random devices anymore. Certainly a Thunderbolt port (which is PCIe-via-string) does not want to expose memory unrestricted, and while you m
389.
by anyfoo 2y ago
The problem though is that while serial is indeed much more commonplace than you might think (look at any device in your household, chances are high that it contains at least one internal serial port that was used for development), it’s a
390.
by anyfoo 2y ago
Ah, thanks. Here I thought that the distance that you’re not driving at full speed would be equal in both cases, in which case you want to “minimize the minimum speed time”, but the situation you present, where the distance you drive at min

More ›