Changes to V5.4 (07/31/95) -------------------------------------------------------------------------- * Added checking for devices that should not be used as virtual hard drives (e.g. anything controlled by mfm.device, multidos, messydos, etc.). * New empdisc.device. Due to various problems with users trying to setup a controlling SCSI device with empdisc.device, things have changed to make it easier. In your s:startup-sequence, locate the line 'BindDrivers' and add the following line BEFORE it. SetEnv CD_Control "xxxx.device" ...where the "xxxx.device" is the name of your SCSI controller's device driver. Examples would be: setenv CD_Control "warpdrive.device" ...for WARP Engine boards setenv CD_Control "gvpscsi.device" ...for GVP SCSI controllers setenv CD_Control "IVS_SCSI.device" ...for IVS SCSI controllers setenv CD_Control "scsi.device" ...for CBM SCSI controllers It is VERY IMPORTANT that you put double-quote ("") marks around the device name. Along with 'CD_Control', we also have 'CD_Type'. Some discs have both MAC and PC formats. Currently, empdisc.device trys to find HFS (MAC) format first. So, if a disc has two formats, you would not normally be able to see the PC compatible files. By setting the environment variable to "PC", all HFS (MAC format) data disc files are ignored. The syntax for the set environment is: SetEnv CD_Type "PC" Place this line in your startup-sequence (after 'SetEnv CD_Control "xxxx.device' shown above). If you do not set the environment variable, then empdisc.device will look for HFS format first, then ISO9660 format. * New multi-os.device. If a single sector was accessed and it had an error, the error was not being returned. * New amia.device. * New emphf.device. * New empser.device. Attempted to help out with 230.4K connections. * New jam.library * Fully 68060 compatible. We re-wrote the MAC's OS so that it can use ALL features of the 060 (CPU, FPU, MMU). * New HardKickMMU program. 68060 support code added. * New RsrvMem. Removed multitasking patch code from RsrvMem. Only when the MAC is running does the Amiga's multitasking get patched (this was necessary because of the extensive changes to the Amiga's and the MAC's OS when an 060 is used). * Corrected problems with refreshed video drivers leaving garbage on the screen (040 and 060 problems). * Corrected problem with ReStart when using System 7.5.1. ********************************************************************* * * * * * * * W A R N I N G ! ! ! ! ! * * * * * ********************************************************************* V5.x of EMPLANT's MAC emulation is the LAST version that does NOT require you to have an MMU. V6.0 of EMPLANT's MAC emulation *WILL* require a processor with an MMU. There will be no exceptions. V6.0 will run the MAC in a virtual environment, meaning that it will have it's own space in memory completely disassociated with the Amiga. The MMU will be shared completely so that you can use the MMU for whatever task you want on the Amiga side. The MAC will definately be using the MMU as we are going to turn on virtual memory. You will also be able to switch between 24 bit and 32 bit addressing modes using the control panel (instead of our HardKickMMU/gadget selection). You will be able to run in 24 bit mode reguardless of what your system configuration is... and you will be able to use up to 8 megs of memory for 24 bit mode (just like a real MAC) without any type of penalty for various system memory sizes. RsrvMem will no longer be necessary with the new version. You will have a real MAC inside your Amiga, in a virtual environment... and it will be faster than before! We are working on v6.0 in our spare time.. which is not a lot right now. V2.2 of the PC emulation is due to be released shortly, which will give us some more time to finish the new version of the MAC emulation. We are VERY excited about the new version, as it will make the MAC emulation 100% compatible.