the Native Config field should look like rom rom://PowerMac.ROM This step associates the newly imported ROM file to the environment.Ĭlick “Start”. Under “Native Config”, specify the name of the ROM file again where guided by the template: e.g. This step allows the EaaS server to import a new ROM file into the system for use with environments. “Apple PPC (8.x-9.0)”, which specifies a SheepShaver emulator configuration, appropriate for Mac OS 8.x up to 9.0 running on a PowerPC processor.Ĭheck the box that says “ROM File”, and in the text field enter the exact file name of the ROM file you copied into the roms folder - e.g. Otherwise, all further steps related to ROM and emulator configuration are the same.Ĭhoose an appropriate hardware template from the “Choose system” dropdown menu - e.g. If you have a bootable Mac operating system installer (floppy, CD-ROM image), use the “Create Environment” workflow to create a blank hard disk drive on which to install from scratch. If you have a bootable hard drive containing a Mac operating system, use the Import Environment workflow. Importing a new or custom ROM file into EaaSI in order to create or import a new Mac environment requires access to the top-level directory of Emulation-as-a-Service ( eaas-home):Ĭopy the desired ROM file into the roms directory inside eaas-home. We cannot distribute these files, except as internal assets within the EaaSI Network. ROM files are not provided along with emulators and templates in the open emulation-as-a-service/emulators repository because they contain proprietary Apple firmware. So in addition to the emulator container, hardware template, and bootable operating system that are necessary to create any environment in EaaSI, a ROM file must also be provided for Mac environments based on these emulators/templates to run correctly. In order to recreate a particular Mac machine, several of these emulators (including Mini vMac, BasiliskII, and SheepShaver) require a “ROM” (read-only memory) file, containing firmware dumped from an original machine’s motherboard. For instance, the Mini vMac emulator is designed rather specifically to emulate a Macintosh Plus and handle the operating systems available for that model, while BasiliskII can potentially recreate a slightly broader range of Motorola 68K-based Macs (Quadras, Performas, etc.) Apple operating systems and emulators are often tied to very particular Mac machines/models rather than being able to run on a “generic” emulated processor. Mac emulation presents additional challenges compared to general PC/x86 systems (e.g. Special Consideration for Mac/Apple Environments ¶
0 Comments
Leave a Reply. |