Harddive images for mac emulator software#

ThatвЂ™s partly because, as open source software, each of these programs is *potentially* capable of a hell of a lot вЂ“ but might require a lot of futzing in configuration files and compiling of source code to actually unlock all those potentials (which, those of us just trying to load up Nanosaur for the first time in 15 years arenвЂ™t necessarily looking to mess with). In particular, while each Mac emulator has some pretty good information available to troubleshoot it (if youвЂ™ve got the time to find it), IвЂ™ve never found a really satisfying overview, that is, an explanation of why you might choose X program over Y.

Harddive images for mac emulator software#

ThatвЂ™s also not something that to hold against them in the least, mind you вЂ“ when you are a relatively tiny, all-volunteer group of programmers keeping the software going to maintain decadesвЂ™ worth of content from a major computing company thatвЂ™s notoriously litigious about intellectual propertyвЂ¦.some of the details are going to fall through the cracks, especially when youвЂ™re trying to cram them into a forum post, not specifically addressing the archival/information science community, etc. The tinkering enthusiast communities that come up with emulators for Mac systems, in particular, are not always the clearest about self-documentation (the free-level versions of PC-emulating enterprise software like VirtualBox or VMWare are, unsurprisingly, more self-describing). I elided much of the technical process of setting up a legacy operating system environment in an emulator, since my focus for that post was on general strategy and assessment вЂ“ but there are aspects of the technical setup process that arenвЂ™t super clear from the Emaculation guides that I first started with. Last fall I wrote about the collaborative technical/scholarly process of making some вЂ™90s multimedia CD-ROMs available for a Cinema Studies course on Interactive Cinema.