Y
Yeo Kheng Meng
yeokhengmeng.com · Personal blog · on HN since 2017
Yeo Kheng Meng writes about retro and modern PC hacking, including DOS and Windows 3.1 apps, vintage hardware, and a Framework laptop review.
What HN saysHN links it for projects like a Windows 3.1 Slack client and DOS-era software, and a commenter notes a QR code issue he described has been fixed.
23HN people shared it
5linked it in comments
32stories submitted
1.2Kstory points
4 months agolast shared
2017people per year2026
Most-shared posts
- 1Modern Linux in an ancient PC5 people · 217 points · first shared 2018 · 126 comments on HN
- 2Llama 2 LLM on DOS4 people · 18 points · first shared 2025 · 1 comments on HN
- 3Building a DOS ChatGPT client in 20233 people · 5 points · first shared 2023 · 1 comments on HN
- 4Building a new Windows 3.1 app in 2019: A Slack Client2 people · 706 points · first shared 2019 · 236 comments on HN
- 5DOS's Last Stand on a Modern ThinkPad: X13 Gen 1 with Intel 10th-Gen Core CPU2 people · 18 points · first shared 2024 · 2 comments on HN
- 6Teardown of Aircraft Transponder2 people · 10 points · first shared 2020 · discussion on HN
- 7Modern 2024 PC with a vintage twist (ft. Ryzen 5 7600 and GeForce 4060 Ti)2 people · 6 points · first shared 2024 · discussion on HN
- 8Windows for Workgroups 3.11 on vintage and modern hardware in 20162 people · 1 points · first shared 2018 · discussion on HN
- 9Why I use the IBM Model M keyboard that is older than me1 people · 152 points · first shared 2018 · 167 comments on HN
- 10Installing Windows XP on a modern unsupported (Haswell) system in 20161 people · 43 points · first shared 2024 · 10 comments on HN
- 11How does MS Fight Simulator compare to real flights? (2020)1 people · 24 points · first shared 2024 · 6 comments on HN
- 12Bringing the Covox Speech Thing to 20171 people · 21 points · first shared 2018 · 4 comments on HN
- 13Bringing Swift to the Apple ][1 people · 4 points · first shared 2026 · discussion on HN
- 14My first chip with Tiny Tapeout 4: Covox Speech Thing clone1 people · 3 points · first shared 2024 · discussion on HN
- 15Review, usage and repair of the Framework laptop1 people · 2 points · first shared 2021 · discussion on HN
What HN people wrote when they linked it
josephcsible · 2024-07-21
The advice in this checklist is horrendously bad and nobody should follow it. Details:
> Restrict /usr partition mount options. Example: UUID=<...> /usr ext4 defaults,nodev,ro 0 2
Mounting /usr read-only will break system updates, and it's worthless from a security perspective, since nothing in /usr is writable by anyone but root, and root is capable of remounting it read-write. Ditto for the same advice about /boot. Also, nodev is only useful on things unprivileged users can mount, like external media, since on internal partitions like /usr, once again, only root can do mknod, and root can remove the nodev mount option too.
> Restrict /proc partition mount options. Example: proc /proc proc defaults,hidepid=2 0 0
Setting hidepid=2 is a really, really breaking change. I'd never even consider doing that on a production system without extensively testing every piece of it with that on first. And since it's only security-through-obscurity and not real security, it's approximately never worth doing so.
> Polyinstantiated directories
A really common use case of /tmp and /var/tmp is to transfer files between local user accounts, when your home directory is something like a Kerberized NFS mount where you can't give each other direct access. Polyinstantiating those directories breaks that.
> Protect Single User Mode with root password. Example: # Edit /etc/sysconfig/init. SINGLE=/sbin/sulogin
This is actively harmful for security, because now you need to give the root…
pmontra · 2026-07-15
Every car can brake, turn and accelerate much harder than any of us will even think to do especially turning and braking. But you pinpointed why we must not attempt to reach for the limit, not for us but for the others. And anyway a normal car won't lay long if driven like a racing car. Every single component is not designed for that.
The usual computer analogy /s
You don't run a LLM on a Core Duo 2, but of course https://yeokhengmeng.com/2025/04/llama2-llm-on-dos/
netsharc · 2023-03-13
The QR code bit interested me, but the issue he describes has been fixed, you can test it by scanning the QR code on this image:
https://yeokhengmeng.com/2021/09/review-usage-and-repair-of-the-framew…
The encoded information goes to a URL shorterner https://fr.mw/[removed_extra_characters] that redirects to a human-readable URL (e.g. guides.frame.work/Guide/Framework+Laptop+DIY+Edition+Quick+Start+Guide/57 ).
fr.mw seems to be owned by Framework so the chance of them independently disappearing should be low. And making it a redirect means if they ever do a restructuring of their website, they can just update where the redirect target of the fr.mw link.
ValentineC · 2021-12-07
yeokm1 · 2019-12-19
You are correct. My 390E has 384MB of RAM but only 256MB is accessible by Win 3.1.
An earlier blog post shows this http://yeokhengmeng.com/2016/09/windows-for-workgroups-3-11-on-vintage…