For one thing, it didn't at all care that the Indy's emulated memory controller didn't report the presence of an EISA bus. Just courteously shut off the video daemon and soldiered right along, not caring that part of the proverbial motherboard had been sawn off.
-
-
Näytä tämä ketju
-
For another thing, there's space in the Indy's memory map for an entire second peripheral controller. On real hardware, accesses cause a bus error because nothing is there. Map one there, and IRIX will happily reconfigure the kernel. It won't use it, but it won't fail.
Näytä tämä ketju -
Give it a faster CPU than ever existed? It'll detect the clock speed without complaint. Have mismatched FPU and CPU identifiers? No sweat. It's amazing how legitimately *bad* the emulation can be, yet IRIX will still boot and run as long as the CPU is good (within reason).
Näytä tämä ketju
Keskustelun loppu
Uusi keskustelu -
Lataaminen näyttää kestävän hetken.
Twitter saattaa olla ruuhkautunut tai ongelma on muuten hetkellinen. Yritä uudelleen tai käy Twitterin tilasivulla saadaksesi lisätietoja.