Thread

NEC V20 CPU: A bit of pep for an XT

11 points · 11 comments · jnord

Loading the complete thread in the background. This saved snapshot is available now. Refresh

rbanffy · 1789989988 · focus · HN ↗
I knew it was possible to run CP/M programs (and CP/M itself) on my PC with its V20, but I never found out how.
tom_ · 1789990531 · focus · HN ↗
I just got served a big chunk of JSON, not even pretty-printed, with the text in there... somewhere. Difficulty level: quite high, even in reader mode.
(same on macOS+Firefox and iPhone+Safari)
1. drcongo · 1789991560 · focus · HN ↗
  You're not alone.
2. glimshe · 1789992095 · focus · HN ↗
  I thought it was an error message but I can't tell from my phone using Brave.
  1. lproven · 1790076850 · focus · HN ↗
    General tip...
    <a href="https://www.spacebar.news/stop-using-brave-browser/" rel="nofollow">https://www.spacebar.news/stop-using-brave-browser/
3. vlasky · 1789992263 · focus · HN ↗
  I think it's a caching issue. I got it to render properly by adding a cache-busting query string to the URL:
  <a href="https://dfarq.homeip.net/nec-v20-cpu-a-bit-of-pep-for-an-xt/?v=1" rel="nofollow">https://dfarq.homeip.net/nec-v20-cpu-a-bit-of-pep-for-an-xt/...
4. bell-cot · 1789994112 · focus · HN ↗
  Appears to be fixed now.
  (If not - zoom way in, and it's relatively readable.)
5. lproven · 1790076905 · focus · HN ↗
  > Difficulty level: quite high, even in reader mode.
  Works fine in Firefox on macOS 15 here.
bell-cot · 1789994479 · focus · HN ↗
Not mentioned - the NEC V30 CPU, which was the V20's 8086-replacement near-twin:
<a href="https://en.wikipedia.org/wiki/NEC_V20#Variants_and_successors" rel="nofollow">https://en.wikipedia.org/wiki/NEC_V20#Variants_and_successor...
IIR, the V30 provided a notably better improvement (over the 8086), because the 16-bit memory bus meant it was less often starved for bandwidth.
mr_big_bowls · 1790070784 · focus · HN ↗
[dead]
1. lproven · 1790077393 · focus · HN ↗
  It worked well. I used a few V20 and V30 PCs.
  One very nice little win:
  If you had an NEC chip, then Windows 3.0 ran in colour VGA mode. If you had an Intel chip, it wouldn't.
  The VGA device driver was 286 code and the assumption was that VGA chips were only in 286 PCs.
  (IBM's own 8086 and later very-low-end 80286 PS/2 machines, both called the Model 30, did not have VGA which was only in Microchannel machines; they had the inferior MCGA instead.)
  If you had an 8088/8086 PC with VGA you couldn't run Win 3.0 in VGA mode. If you fit a V20 (instead of an 8088) or V30 (instead of an 8086), you could run Win 3.0 in colour VGA mode.
  In 1990 this was the first mass-deployed 286-specific code a lot of people ever encountered: a device driver.
  Lotus 1-2-3 r3 was 286-specific but it was niche; you could just stay on 1-2-3 r2 which worked fine on everything. Almost all other DOS apps were for 8088/8086.
  The 80186 was so rare it wasn't even mentioned: the distinction was 8086 code or 80286 code. So this was a rare instance of Real Mode 286 code -- plain old unextended DOS 16-bit code, as opposed to Protected Mode code that needed an actual 80286 chip.

Open on Hacker News to reply ↗

Unofficial Hacker News client; not affiliated with Y Combinator.