[HN Gopher] How I fixed the infamous Basilisk II Windows "Black ...
       ___________________________________________________________________
        
       How I fixed the infamous Basilisk II Windows "Black Screen" bug in
       2013
        
       Author : zdw
       Score  : 50 points
       Date   : 2025-05-15 14:31 UTC (2 days ago)
        
 (HTM) web link (www.downtowndougbrown.com)
 (TXT) w3m dump (www.downtowndougbrown.com)
        
       | cardanome wrote:
       | I remember running Basilisk 2 on a PlayStation Portable.
       | 
       | Not sure what the point was but I was happy I could.
        
       | MBCook wrote:
       | 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.
       | 
       | Great article. I'd love to know why the memory was allocated that
       | way initially.
        
         | fredoralive wrote:
         | The two memory allocations makes sense, ROM and RAM are
         | separate chunks of memory, and in the Mac memory map(s) they're
         | non-contiguous, so why not two allocations?
         | 
         | It's only once the C classic of optimising through FUN(tm) with
         | pointers, and then weird issues with bits of the Mac ROM not
         | liking being mapped into random high memory addresses that we
         | end up with lockups.
        
       ___________________________________________________________________
       (page generated 2025-05-17 23:00 UTC)