It's clear that a Cocoa port is going to be needed in the near future of the Mac. So if someone did that hack, I would credit them for making the Mac Cocoa port of Mini vMac, even if I still needed to do a lot work to polish it. How strong is that convention?Īnother question, how hard would it be to hack the iOS port to more or less run in Mac OS X? Having that to start from would make it much easier for me to get going with learning Cocoa and Objective C.
I guess the convention in Objective C is to have each class in its own file. One question I have, is it really necessary to have that many separate source files? For the other ports, there is basically one source file per port. VMac was an open source emulator for Mac OS on Windows, DOS, OS/2, NeXTSTEP, Linux-Unix, and other platforms. Open Mini vMac APK using the emulator or drag and drop the APK file into the emulator to install the app. Since these days "Mini" is not referring to the complete source code, just the binaries, I guess I could just include the entire iOS port in my version of the source, if I get to understand it well enough. VMac and Mini vMac emulate a Macintosh Plus and can run Apple Macintosh System versions 1. dsk file to this window would be as inserting a floppy disk. dsk file (bootable image) to the minivmac window. As I said, I'm not very familiar with the iOS port. A floppy disk with a question mark must be displayed. Mini vmac download install Mini vmac download upgrade Mini vmac download software From one Finder to another to access a disk image, just simply drag it into Mini vMac Software To load programs, you simply repeat the process you used to load the startup disk simply drag the disk image files into Mini vMac, where they will load. Superpete wrote:Other than drive sounds and the settings window, I'm not sure what you could strip out of the port and have it still functional under iOS. This would permit lower latency, at the discretion of the platform dependent code. In Mini vMac 3.2.3, the platform independent sound code also requests space in smaller chunks instead of a whole ticks worth of 370 bytes at a time. If it needs to write more than that, it is responsible for breaking up the write into two parts. The platform independent code requests space, and is told how much contiguous space is actually available. In Mini vMac 3.2.3, this hack is not needed. Since the ring buffer size is not a multiple of 370, this requires a hack, where the platform independent code actually writes past the end of the ring buffer, and the platform dependent code copies the excess to the beginning of the buffer. In Mini vMac 3.0.4, which Zydeco's iPhone port is based on, the platform independent code requests a 370 byte sound buffer every tick from the platform dependent code. The platform dependent code also adjusts how fast the emulation runs, adding or removing a tick every second, so as to keep the sound buffer filled to the desired amount, to keep latency as small as possible while avoiding buffer under run. It supports almost any Android device, starting from android version 1.6.
The basic idea is a ring buffer that the platform independent code writes to, and the platform dependent code reads. This is a port of the Mini vMac emulator for the Android platform. Now you can run the Mini vMac executable and when you see the blinking question mark, you can just drag 024M.dsk onto the screen to boot it.Superpete wrote:still getting my head around how the existing ports handle sound, they seem to be doing they're own queueing with TheSoundBuff.? Now you've got a disk image containing System 6 that Mini vMac can boot and that contains plenty of free space for applications. You will be asked for “System Startup” one more time before installation finishes - just drag the file from Windows to Mini vMac again.įigure two: About to Install System 6 on Mini vMac Click “OK” on the first prompt and then “Install” to install System 6 onto “untitled.” When asked for “System Additions” just drag that file from Windows on to the Mini vMac screen as you have done with the other disk images. Inside of the Mac OS double click on “System Startup” and then on “Installer” to begin installing the Mac OS. This disk should show up in the Mac OS as a disk called “untitled.” Run the Mini vMac executable and once again drag “System Startup” into the vMac screen. Extract the archive containing blank disk images that you downloaded at the start of this guide.