Posts by Timm

It's a bog-standard config, I can use it without issues. Could you tell us the name of the game that causes problems, or some demo perhaps?

Quote from lokz

Dear Timm, then it is time to update your Acatool wiki with this information.

I suspected that PCMCIA booting issues are caused with "slowmem" region (since it boots fine with plain expansion), but no way to do it right now.

Can support for this type of management be expected in some ACA firmware updates for this card?

Done, updated in the WIKI. At your service.

No, to my knowledge the ACA1221lc hardware doesn't support switching the CPU.

Quote from lokz

Dear Timm, basically you say I cannot select memory modes with ACA1221lc?

Exactly. You can change the CPU clock, and with the 14MHz clock you get synchronous operation, but the CPUPON, CPUOFF, and MEMMODE options are not for the ACA1221lc card. The memory in the "slow mem region" is not really slow on the ACA1221lc, it's fastmem that just happens to be in that region.

Quote from lokz

Please write me correct line of code, how do I select this "1 fastmem but no $C0 memory" and save to flash.

This is not getting written to flash. The documentation may be scarce here, but at least it says: "when switching CPUs" and "This option is useful in combination with the CPUOFF and CPUON options". The ACA1221LC does not support switching the CPU.

If you don't switch the CPU, it's not being considered, and the tool behaves as if no command was given, so it brings up the GUI.

So, for example, this would work, if you had a ACA1233n:

# acatool cpuoff mm=1

Admittedly, some feedback from the tool would be nice in that case.

Quote from Warty

Anyway... does anyone have a ScreenMode/Overscan/Indivision config combination that would do what I want, which is 1280x1024 integer scaled workbench?

In theory the very first Indivision mode from the preset list, "Pre 640x512 PAL" should do just that, as it uses the VGA mode "Pre 1280x1024 VESA". But by default it's deactivated and wouldn't be selected. A double-click on the mode or unchecking the "Disabled" checkmark, and it should do. Please test the mode before using "Test/Adjust".

Sorry Jens, on ECSv2 we're counting differently than on AGAmk3.

On ECSv2 it's usually Min. Lines 286, Max. Lines 287 that selects a mode for a PAL screen.

If you want to give it a try, here's a release candidate of version 2.4 of the ECSv2 config tool:

http://wiki.icomp.de/w/images/…divisionECSv2-2.4-rc1.lha

There are no FPGA changes yet, but chances are that this and some other issues may go away with this update.

Quote from Jens

I'll keep silent for now - Timm will find a solution

Oh really?

As for the rescue disk, the beginning of the file 'flashtool' is overwritten with garbage. That's why it isn't recognized as an executable.

Regarding the requester, I'd suggest to take out the cosmos patch. But when the problem still persists when booting without startup-sequence, I'm out of ideas for the time being.

As you said, config tool 1.6 didn't give you these problems. As a workaround you can use config tool 1.6 and flash the firmware from 1.7.1.

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).

Thanks, but I'd need a listing using the 'list' command to see the protection bits, too.

Quote from BlackTiger78

i also have bug with saving configuration to device on 171 each startup got info

"The configuration is not saved to the device" i must do flashtool saveconfig config

Thanks. Please also post your configuration file for investigation.

Quote from BlackTiger78

worst:

- 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.

IndivisionAGAmk3-1.6.1.lha

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:

You can find TestRMB in http://aminet.net/util/misc/MouseTest.lha.

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?

Quote from doggggg

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.

Quote from Jens

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.

Quote from mbruines197703

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.)