Posts by Timm

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 can't reproduce the issue that you are reporting. I can load your config and 'Save&Apply' it. Coincidentally it works with the TV/monitor I'm using, too. Repeatedly starting the config tool doesn't bring up a requester.

    Then I noticed that in your video you were using version 1.6 of the config tool. So I tried with version 1.6, too. But that wasn't a problem either, 1.6 and 1.7 handle the configuration equally (as it was supposed to).

    Currently my best idea is that you try booting without startup-sequence from the boot menu, then start the config tool by entering sys:prefs/indivisionagamk3 (or where it is located), and report back if that gives a requester too.

    Thank you.

    This is very strange, everything on the disk looks correct, except for that it isn't. Maybe you can take a snapshot of the disk, as an Lha or disk image.

    Meanwhile I'll investigate EDID and configuration.

    For the time being, your EDID information looks correct here. When selecting 'Settings/Restore to Defaults' and then 'Settings/Re-Read Monitor Display Data...", two modes are reported, and they appear very reasonable (1080p@60 and 1280x720@50).


    - i thing there is a "copy error" with creating rescue disk in 1.7.1

    tested 3 times good diskietes and after boot got this error flashtool - file is not executable

    after manual copy files from IndiMk3 dir all works fine.

    - another problem 171 dont always save a configuration to device (scalines for examples) - 16 all ok

    I cannot reproduce issues with creation of a rescue disk. I tested it several times.

    I can however confirm a bug with saving the scanline setting. The scanline setting is canceled out from the configuration on the device.

    Regarding your monitor, if possible, please read and save the monitor EDID using the command line:

    # IndivisionAGAmk3 SAVEEDID myedid

    and post the file myedid here.

    Please show a listing of the rescue disk with the 'list' command.

    Thank you. :-)

    I don't get it, this EDID produces two modes for me.

    Please test with the attached version 1.6.1 of the config tool. After selecting 'Settings/Restore to Defaults' and 'Settings/Re-Read Monitor Display Data...', how many new modes are reported?

    This version of the config tool is not for general use; it produces a lot of debug output. The output can be recorded on a serial interface or using a tool like Sashimi. If you still get an error, perhaps you can try to record the debug output and post it here.


    I find it important to warn the user because you could accidentally press the right mouse button. The 10 seconds delay gives you the opportunity to issue a reset. Ok, taking note of adding a sequence like this as an installation option. I'll think about it. I find this a bit too complicated to explain. Inserting a disk when the display has gone black seems more straightforward to communicate. Also a rescue disk survives "experiments" on the OS installation.

    If you can connect a monitor to the native display without hassle, then you do not even need the rescue disk for the IndivisionAGAmk3. For regular use, the config tool should be absolutely enough. If you think it's worth the effort, you can add the following lines to your S:user-startup:

    1. c:TestRMB
    2. if warn
    3. echo "About to flash IndivisionAGAmk3 firmware in 10 seconds..."
    4. ; c:beep
    5. wait 10 sec
    6. ; c:beep
    7. c:indivisionagamk3-flashtool flash devs:indivisionagamk3-firmware
    8. endif

    You can find TestRMB in

    From the IndivisionAGAmk3 archive, copy flashtool to c:indivisionagamk3-flashtool and firmware to devs:indivisionagamk3-firmware. To be a bit more on the safe side, find some tool to produce an audible beep, and comment in the appropriate lines.

    This is difficult to explain.

    How many modes did the tool report to have added with version 1.5?

    Could you invoke the config tool from the command line like this:

    # IndivisionAGAmk3 saveedid myedid

    and post the file myedid here?

    Timm, if you read this, please know that "Is live, but wouldn't be applied" is an insane status message. The config program should never just shrug it's shoulders to the user and say "according to the configuration, this mode should not be the one active right now, but it is anyway". Why is that even a possible situation that can occur?

    The old MK2 has a reputation for having a high learning curve. But this situation of being stuck in the wrong mode, never happened.

    What is also insane is it's possible sometimes to click "Find live mode" and get a dialog box telling you that there is no config matching the live mode. How is that happening? How does the indivision find itself outputting video but not in any of it's configured video modes?

    While you edit the configuration, the settings are not automatically synchronized with the configuration on the device and in live registers. "Is live, but wouldn't be applied" just means that you have changed the configuration in a way that the current mode wouldn't be selected again when you'd save the configuration to the device and/or apply the configuration now. If you click "Apply" in this situation, a different mode will be used, and the message goes away. Select "Last Saved", and it should go away too. Both actions synchronize the configuration being edited with the configuration on the device and in live registers. Same with "Find live mode": It is possible that you change the configuration so that no mode currently matches the mode selection criteria. The most obvious reason for this to occur are changes in modes being enabled/disabled.

    I have settled for this philosophy, and I have no plans to change it at this point.

    Timm, it appears to be board- and accelerator specific. mbruines reported that the old ACA1233 works fine, while the ACA1233n doesn't, and it's worse on one main board than on another. If you want to replicate the problem, you should use the ACA1233n-55. IHave sent one of these accelerators to Peter as well, hoping that the problem shows on his machine.

    I can confirm that this demo does have problems with an ACA1233n-55 here, and I saw black screens and the OSD several times. Also there were interruptions in the sound. Just for the record, when watching this demo on an ACA1233n-55 with native video/audio, it's not free of a plethora of other problems, and it crashes early.

    On the rev 1d1 i had the folowing issues:

    The demo JezesOnEs from LSD is guaranteed to give a lot of black screens, so very easy to reproduce!

    The demo Hardwired gave an interlaced effect on the first part displaying the white big text and some blackouts.

    I may be missing something from earlier posts in this thread, but I tested on an HDM! TV, an unexpanded A1200, firmware 20200824. I selected 'original chipset' and 'disable CPU caches' in the boot menu. The VGA mode selected was 'EDID 1280x720@50', audio mode 96kHz.

    I sat about 15 minutes into the Jesus on E's (before it crashed). As far as I can tell, the show was totally flawless visually and sound-wise. I didn't get black screens and I didn't see the OSD.

    How did you get Hardwired to work on an A1200? It says 'this demo don't like axel' on CPUs > 68000. (I expected this, it is what I remember.)

    Additionally, I've noticed that when I cycle through the audio/DVI modes on the Advanced options modal window in quick succession, the Indivision Tool sometimes seems to get itself into a state where it thinks it has already saved/synced changes I’ve made, when it has not. I have to quit out of it and redo them when this happens.

    Bugs in this regard are certainly possible, but I cannot reproduce it.

    In any case, it would be hard to imagine that something like this would have something to do with multitasking and CPU speed.

    This blank space can be filled by changing the scaling values. However, the "PRE" modes are protected from being changed - all the fields become really adjustable after you've made a copy of the mode and applied that to the "current" screen mode.

    You are right that "dangerous" settings are protected in the 'Preset' modes, but position and scaling are always adjustable.

    In regards to it not sensing resolution, I am still confused in one regard.

    Upon first installing, default settings, I had no idea what profile was being used for games. As I mentioned, I found out it was using the 800x600 profile as default for games (by looking at the OSD). This part I do not understand, could you elaborate? How did it choose 800x600 profile, why was this the chosen profile. Understanding this fact will help me understand the entire system and how it works (I have read the docs)

    The point that is needed for understanding: On a mode switch, the mode list is evaluated from top to bottom. The first mode that matches the criteria will be used. The criteria are (mainly) the number of lines on the screen, and secondarily the 'Select on' criterion. The reason why 'Pre 800x600 PAL' is selected in the defaults is simply that there are no other modes enabled in the list above that match its line number and 'Select on' criterion. As you can see, PAL has 313 lines on the screen. So the mode matcher falls through the whole list until it reaches the last entry.

    Our idea was that there should be robust catch-all PAL and NTSC modes, as they are supposedly needed most often. We further assumed that people would like to overlay the robust defaults (mainly for PAL) with more specialized modes that we cannot guarantee to function on the wide variety of monitors. So we sorted some mode presets ('Pre 640x512 PAL', 'Pre 720x548 PAL', 'Pre PAL Auto+VSync', 'Pre 736x548 PAL VSync') to the top of the list, but disabled them. So the user can rely on the default, but additionally select and try these modes using 'Test/Adjust' in order to see if they work for them, and then enable more specialized modes that are to their liking - because when enabled, they match earlier in the list.

    Thank you for your suggestions, they are duly noted.

    Please prefer the GUI, not the shell method, it's so much easier and less error-prone to flash the Firmware from the Pull-Down menu. Also when you click the "Flash" button in the GUI dialogue, the current configuration is automatically written back after flashing the firmware. When flashing using the commandline tool, a power cycle is likely needed and the configuration still needs to get written back.

    You can already save a configuration using the menu item 'Project/Save As...' and load it later using 'Project/Open...'.

    You can see the FPGA version in the OSD. For example, select a different Indivision mode and click 'Test/Adjust' to see it.

    (Ok, it might be a good idea to produce the OSD always on entering the Test/Adjust screen.)

    Here are my test results from a BenQ BL702a.

    Default settings work with both PAL and HiGfx (1024x768). On HiGfx the screen was off by one pixel to the right. Pressed the Auto Adjust button on the monitor. Then I corrected it by pressing the cursor left key once on the Test/Adjust screen. Then I invoked 'Pick VGA Mode from Display Data', which gave me 'EDID 1280x1024@60', which tested Ok. Then I applied this VGA mode to all Indivision modes.

    Finally I tried Test/Adjust on '(Pre PAL Auto+VSync)', which gave "Out of Range" on the monitor. Then I tried Test/Adjust on '(Pre PAL 736x548 PAL VSync)', which tested Ok, so I enabled this mode. For HiGfx (1024x768) I later picked the VGA mode 'Pre 1024x768 60Hz XGA', because it looked better. The highest resolution and an ultra-crisp display in 1:1 pixel resolution I get on PAL SHires Interlaced. But PAL SHires Interlaced has some glitches on my A1200, therefore I selected the 'CCKLine Pull-Up" option in the Advanced Options window, which stops the glitches immediately on this machine. Then I saved the configuration.

    So, with a BenQ 702a, I get both: Crisp high resolution Workbench and VSync/50Hz for games and demos.

    It's more complicated than that.

    The flashtool reports its own version, which is not necessarily in sync with the config tool's version.

    Also it reports the flash chip's Id and version, this version is currently 1.0. So we have four versions:

    - 'IndivisionAGAmk3' config tool: version is currently 1.x

    - flashtool: version is also 1.x, similar, but not necessarily the same as the config tool :-)

    - FPGA firmware: version is in ISO-date format, e.g. 20200812

    - flash: this version is currently always 1.0.