" /> ContentsIndex< BrowseBrowse >


    Frequently asked questions


    ACE supports up to 256 ROMs... but I only see 16 ROM parameters?!

    Arguments actually only exist for the first 16 extension ROMs. If you really
    need to configure ROMs up to 256, you can perform the operation by using the
    "FLASHROM" command from the AREXX port. But keep in mind that the firmware
    only initialize the first 16 foreground ROMs.

    16 ROMs is enough in most cases.

    Why do ACE only manage 512KB of expansion memory?

    This is the standard limit envisaged by Amstrad at the moment of the CPC
    conception. The only way to manage more memory is to use some specific
    extensions (like the 2MB Memcard from RAM7).

    Considering the poor support for this kind of interface, I don't think that
    adding a related emulation would be of any real use.

    What about the quality of the various CRTC types regarding demos?

    To tell you the truth, only the CRTC 1 emulation is fully accurate. others
    support needs to be improved. Please, always prefer CRTC 1 and choose other
    CRTC only for demo specifically requiring it. Next versions of ACE will
    focus on improving CRTC 0 in order to have the same quality than the CRTC
    1. CRTC 2 is not that important and will be done later.

    Of course, the CRTC 3 is mandatory to use the Amstrad Plus emulation and
    works properly.

    I often have warning messages when opening DSK files!

    The DSK format is really awful and the tools used to generate them from the
    real physical discs are often bugged. Practically, the informations
    contained into the DSK files are not sufficient (when they are not simply
    wrong) to permit a really accurate FDC and floppy disc drive emulation.

    A complex on-the-fly fixing mechanism is built into ACE in order to try to
    rebuild the missing or altered informations; the warning messages are
    related to this behavior. You can disable them with the option "NOWARNINGS"
    or by using the "Preferences" menu (fixes are always applied but you will no
    longer be informed about them).

    In a next version of ACE, a brand new disc image format will be introduced
    to avoid all the FDC emulation problems related to the DSK format. Import
    or export to DSK will remain possible when applicable.

    Why an inserted DSK is not modified when I write into it from ACE?

    It is, but not in real time.

    ACE does not manage directly the DSK files. Instead they are loaded and
    converted into an internal structure. When you update the content of
    an image disc from ACE, only this internal structure is modified. The DSK
    file will be modified from this internal structure when it is ejected from
    ACE or if you quit ACE.

    Moreover, ACE will try to keep the original format when it updates the DSK
    file. Standard DSK remain standard and Extended DSK remain extended. If a
    Standard DSK was altered in a way in cannot be saved in this format anymore,
    ACE will ask you to confirm that you want to convert it to Extended DSK.

    What is the difference between "Reset" and "Cold reset"?

    A reset simply emulates a CPC hard reset. It means that all the chipsets and
    the microprocessor are initialized but not the memory. It is just the very
    same behavior you would have on a real CPC with a hard reset button (like
    the one on the Multiface Two or the Hacker).

    A cold reset is like if the CPC was just on-powered, everything including
    the memory is reset.

    By default ACE emulates a CPC6128, how to configure it for another CPC model?

    The main difference between the CPC models is related to the version of the
    firmware and BASIC ROMs installed. The CPC6128 uses version 3 of the
    firmware while the CPC664 uses a version 2 and CPC464 a version 1. The CPC+
    range uses a firmware version 4 with a BASIC 1.40.

    You should take care of the BASIC ROM installed:

    - BASIC 1.00 is only compatible with firmware ROM version 1,
    - BASIC 1.10 is only compatible with firmware ROM version 2,
    - BASIC 1.2x and 1.40 are only compatible with firmware ROM version 3 or 4.

    Is case you really don't want to emulate a CPC6128 but an older CPC model
    you can use the 64KEXPMEMSCHEME tooltype to fit the way 64Kio based models
    are handling expansion RAM. You can also make use of DKTRONICSBUGS tooltype
    to simlate a DK'Tronics expansion RAM (which have some flaws regarding
    internal expansion RAM of the 128Kio base models).

    Eventually, you can configure any amount of memory but no cassette emulation
    is available yet even if you configure ACE to emulate a CPC464.

    How to have a smooth 50Hz display like on CPC?

    CPC games and demos are running at 50Hz. To have a perfectly smooth display
    like on a real CPC, you must then have the very same frame rate frequency
    (or a multiple of it) on your system.

    Generally, you will not have a 50Hz graphic mode available by default.
    However it is really easy to create one from MorphOS monitor preferences
    (just be sure that you create a 16, 24 or 32 bits color depth screen).

    If your screen monitor supports 50Hz frame rate (you may need to alter its
    default auto-detected capabilities), just create a new screen mode at
    exactly 50.0801Hz. Then, get the mode ID, and put it into the tool type
    SCREENMODE of ACE (eg. SCREENMODE=0x40920058).

    Till now, each time ACE uses the full screen mode, it will be at 50Hz and
    everything is smooth like on a real CPC!

    Unfortunately, a lot of games and demos do not match the default 50Hz
    frequency... and they will not be smooth again... There is no real
    solution (because the screen frequency can change at any time). Anyway, you
    can get the program's frame rate from the video information window and then
    create a new screen mode at this frequency.