New AmigaOS 3.2 install - display problems

[n9yty]

I thought I'd experiment with a totally clean start.

* A1200
* New Kickstart 3.2 ROMS
* New 32GB CF Card

Using ADF images and a GOTEK3 internal and external, I thought I could manage all the floppy disk shuffles and it worked. I was able to boot from Install, partition the CF card, install PFS3, and format it. I then installed AmigaOS 3.2 using the floppies.

I have the Amiga connected to my LCD display using an Amiga to SCART cable and a SCART to HDMI converter box. This has been working very well for me on the ClassicWB 28 install.

What is quirky, though, is that now the display sometimes comes up with two copies, one on each side of the display, or just black, or other odd stuff. Even when it is "stable", I started installing some odd software for fun and when they change display modes the screen most often goes black and I have to reboot.

Trying those same programs under my ClassicWB 28 install works perfectly, so I am puzzled as to what is going on. I had copied the files from Storage/Monitors to Devs/Monitors, but trying various NTSC and PAL modes seem to all act strangely.

Booting back into the ClassicWB 28 with the 3.2 ROMS (and copied over icon.library and workbench.library) works fine still, so it doesn't seem to be hardware. To test that, I pulled down my second Amiga 1200 and it behaves the same way.

What could it be on the ClassicWB install that works better with my monitor setup than the base AmigaOS 3.2 install?

[n9yty]

Looks like this should have been in APPS, not OTHER, sorry about that. . I can't move it I don't think.

Anyway, I copied the PAL and NTSC Monitor definitions from my old install over to the new one and the problems seem be fixed.

How can I figure out why that is the case (they are different file sizes), and where the other ones came from?

[Samurai_Crow]

Do you think the old screenmodes came from another version of Workbench?

[n9yty]

Possiby, it was a ClassicWB 28 install from probably Workbench 3.1.

PAL is 6,156 bytes and NTSC is 6,168 bytes.

I don't know enough about how they work to find more than that, but I am intrigued by the very different behavior in this setup.

UPD: I found a Workbench 3.0 Storage disk ADF file and the PAL is 6,156 and NTSC is 6,168, so they line up. That is where they came from.

Now the question is, why do they work so well and the new ones don't?

[thomas]

I remember when upgrading my A4000 from 3.0 to 3.1 back in the 1990's, the new drivers had the border blank feature enabled by default. Maybe it's the same here and the black border confuses the monitor.