ACA1233n MapROM and Elbox Mediator

Caution: Non registered users only see threads and messages in the currently selected language, which is determined by their browser. Please create an account and log in to see all content by default. This is a limitation of the forum software.


Also users that are not logged in can not create new threads. This is a, unfortunately needed, counter measure against spam. Please create an account and log in to start new threads.

Don't Panic. Please wash hands.
  • I've been having a slight problem with my ACA1233n MapROM working with Elbox Mediator 1200TX Black series.

    My setup is as follows:

    Amiga 1200 Rev 2B board

    ACA1233n 40Mhz version with RTC addon

    Voodoo3 16Mb video card

    Adaptec SCSI 2940UW connected to a SCSI hard drive and CD-ROM

    Creative SoundBlaster 1238 CT4750

    Realtek RTL8139 10/100 network card


    I have ACAMapROM /I q as the first line in my startup-sequence but when Wwhen running ACAInfo from shell once Workbench is loaded it always shows the MapROM status as disabled.


    If I boot with no startup-sequence and run the maprom program manually, it works properly, on the soft reboot it shows the MapROM status as enabled. It's only when booting to Workbench it shows as disabled.


    I'm wondering if, because the Mediator uses the RAM on the video card for DMA access, is it mapping the video RAM to the memory area where the MapROM utility expects to find the ROM loaded?

  • This may be a display error, and MapROM is actually on. Please double-check with the tool "bustest" and compare the "fast" speed versus the "rom" speed. This will give a clear indication if MapROM is on or not.

  • Hi Jens, thanks for the prompt reply. Looking at the results of the bustest it appears to be working properly. Here are the results:


    BusSpeedTest 0.19 (mlelstv) Buffer: 262144 Bytes, Alignment: 32768

    ========================================================================


    memtype addr op cycle calib bandwidth


    fast $40890000 readw 130.0 ns normal 15.4 * 10^6 byte/s


    fast $40890000 readl 155.2 ns normal 25.8 * 10^6 byte/s


    fast $40890000 readm 144.3 ns normal 27.7 * 10^6 byte/s


    fast $40890000 writew 78.6 ns normal 25.4 * 10^6 byte/s


    fast $40890000 writel 79.5 ns normal 50.3 * 10^6 byte/s


    fast $40890000 writem 74.2 ns normal 53.9 * 10^6 byte/s


    chip $00018000 readw 575.8 ns normal 3.5 * 10^6 byte/s


    chip $00018000 readl 577.9 ns normal 6.9 * 10^6 byte/s


    chip $00018000 readm 617.8 ns normal 6.5 * 10^6 byte/s


    chip $00018000 writew 576.0 ns normal 3.5 * 10^6 byte/s


    chip $00018000 writel 578.8 ns normal 6.9 * 10^6 byte/s


    chip $00018000 writem 579.0 ns normal 6.9 * 10^6 byte/s


    rom $00F80000 readw 129.6 ns normal 15.4 * 10^6 byte/s


    rom $00F80000 readl 155.2 ns normal 25.8 * 10^6 byte/s


    rom $00F80000 readm 144.5 ns normal 27.7 * 10^6 byte/s

  • Right - so not a "showstopper", it's working, but not properly displayed. I'll put it on the list of things to be checked, but please understand that in these busy times, this cannot have high priority.

  • Right - so not a "showstopper", it's working, but not properly displayed. I'll put it on the list of things to be checked, but please understand that in these busy times, this cannot have high priority.

    HI ,

    no problem, it's just a cosmetic issue,as long as it is actually working then I have no problems. I understand you are very busy with other projects and this hardly warrants immediate attention. I am very happy with this card so far and it was just a niggling little thing anyway.

  • The last reply was more than 365 days ago, this thread is most likely obsolete. It is recommended to create a new thread instead.