DCE Mini-Megi Chip installation

[x56h34]

I recently bought this chip from Vesalia. It's a revision 2.1 Mini-Megi Chip with an NTSC 2MB Agnus soldered onto it. I've installed it in my revision 6.2 NTSC A2000.
The instructions were in German, however I think I figured out how to install it, but...

Although the A2000 now reports 2MB of chip ram, I notice that all of a sudden, there are some graphics glitches when I navigate through OS3.1 or OS3.9. Menus would look corrupted, as well as icons. There are no crashes whatsoever, but graphics seem slightly trashed.

This doesn't happen with the original, 1MB Chip RAM setup, so I'm sure my A2000 itself is OK.
It does however happen regardless of whether I strip the A2000 down to just basic 2MB Chip ram, 68000 CPU, no hard drive, no SCSI, or leave all the expanded stuff in.

I was wondering if there is some extra configuration that I may be missing, like a jumper which needs to be switched, or similar?

Thanks for any help in advance.

[x56h34]

Ed, I appreciate your continuous effort in helping out with my problems.
It's good to know that Mini-Megi chip by design will give those glitches, with 3.1 rom. I don't really want to switch to 2.x rom from 3.1, so I guess I'll have to take it as it is. :-)

As for the WHDload issue, I haven't yet tried to fiddle around with it. I may leave it as it is, and strictly use my A1200 for WHDLoad gaming, and leave the A4000 highly expanded. :-) The Catweasel/Buddha S-class card is just too cool. ;-)

Thanks again.

[x56h34]

Ed, your chip is a DKB product, right? Could it be that both DCE and DKB couldn't figure out a way around the 3.1 rom glitches? :-? Or was it that the boards were designed before 3.1 rom was released?

[x56h34]

@EzdineG:

Yeah, these glitches happen no matter what, even when my A2000 is with only these specs:
68000CPU, 3.1Rom, 2MB chip ram, and nothing else.
I would insert the WB3.1 floppy, let it load up, start opening windows, moving them, resizing, opening menus, and the glitches would still be there.

Keep in mind that you most likely have a different product (DKB MegaChip) and I have a DCE MiniMegi Chip. They sound similar, however they are a totally different design by 2 different companies.

Interestingly enough, the Picasso96 libs glitches when no driver loaded look about exactly the same as this problem of mine. I know, as I've used P96 with other Amigas, and before I would activate the actual monitor driver, the regular native screen within the OS would always be glitchy.

[x56h34]

Thanks Lemonty.
I'll look into it this weekend. I think that this concerns only the old A2000 models with the 512KB Agnus chips. The ECS A2000 units (like mine) should already have this set by default, however it doesn't hurt to check.