Mini vMac requires a ROM image file to run, and so can be legally used only by those who own a 680x0 based Macintosh. Work is in progress on Macintosh II emulation. Besides the Macintosh Plus, there are also emulations of the Macintosh 128K, 512K, 512Ke, SE, Classic, and SE FDHD. The meta program and data that generate the emulators (the Mini vMac build system) are rather bigger. The “Mini” in the name now means that each emulator in the collection is as small and simple as possible. But vMac hasn’t been updated in many years, so Mini vMac may now be considered its continuation. It was originally intended to be of limited interest, a simpler version to serve as a programmers introduction to vMac.
Mini vMac began in 2001 as a spin off of the program vMac.
The first member of this collection emulates the Macintosh Plus. I know BasiliskII has kind of a steep learning curve to get started and it can be a pain to find a stable build but it's really a much more capable emulator.The Mini vMac emulator collection allows modern computers to run software made for early Macintosh computers, the computers that Apple sold from 1984 to 1996 based upon Motorola's 680x0 microprocessors.
If you want gigantic true-color visuals in a 68k Mac emulator BasiliskII is probably your best bet unless there's some specific piece of software you're trying to use that works better under vMac. (I see the "Variations" service does allow high/true color screens, and technically since it's an emulator it might potentially be able to assign up to 6MB into a linear framebuffer, but that would seem to be pointless if you can only have up to 8MB of system RAM.) I'm not *100%* sure of that, but if I am that would seem to preclude using resolutions much in excess of color.
I've been looking at the Mini vMac mailing archives and the variations service, and it looks to me like vMac II still only supports 24 bit addressing? (IE, Mac II 68020 with up to 8MB of RAM) With only 24 bit addressing I *think* it becomes difficult to use more than 1MB of video RAM because of limitations in how the slot manager divvies up RAM address spaces.
0 kommentar(er)
