TE
TechEcho
Home24h TopNewestBestAskShowJobs
GitHubTwitter
Home

TechEcho

A tech news platform built with Next.js, providing global tech news and discussions.

GitHubTwitter

Home

HomeNewestBestAskShowJobs

Resources

HackerNews APIOriginal HackerNewsNext.js

© 2025 TechEcho. All rights reserved.

How I fixed the infamous Basilisk II Windows “Black Screen” bug in 2013

72 pointsby zdw3 days ago

4 comments

RJIb8RBYxzAMX9uabout 13 hours ago
Very interesting article, but this stood out to me:<p>&gt; To re-familiarize myself with this bug [...] I downloaded the broken version [...] and tried it out in some virtual machines. Windows 2000 and XP ran it without any trouble on the first try, but Vista and 7 didn’t [...]<p>Amazing. Emulating an older system in order to debug emulating <i>an even older</i> system. The amount of compute &#x2F; memory &#x2F; storage readily available at our fingertips today is astounding. My first computer was a 68k Mac, and back then, I would never imagine such scenarios would be possible!
评论 #44018518 未加载
评论 #44018817 未加载
MBCookabout 19 hours ago
Allocations moving around sounds a lot like the Address Space Layout Randomization (ASLR) that was added to Vista as part of the large increase in security hardening MS went through during development.<p>Great article. I’d love to know why the memory was allocated that way initially.
评论 #44017562 未加载
rcarmoabout 15 hours ago
This reminds me that I cannot run BasiliskII at a decent resolution under GNOME at 125% - the thing apparently tries to set the window size several times, then goes into a black-bordered resolution mode that is _not_ what I asked for (and I&#x27;m used to setting the prefs directly, so I have mag_rate, scale_nearest, etc. all set &quot;correctly&quot;
cardanomeabout 20 hours ago
I remember running Basilisk 2 on a PlayStation Portable.<p>Not sure what the point was but I was happy I could.