I recently got a System 16 multi for my ESwat donor board. The board had a Hitachi FD1094 cpu which I replaced with a MC68000P12. No matter how many times I reburned the eproms, reseated them, reseated the multi, etc. I have constant static graphical corruption. The corruption does not change or move or wiggle, it is always exactly the same incorrect graphics in the same spots.

The only error I have seen in tests is J9. I tried replacing J9 but then both J9 and J10 were reporting bad. So then I replaced J10 too and they're still bad. It turns out I ordered the wrong chip. Original is UM6116K-2 and the replacements are UM6116K-2L which looks like it's a low power variant. I assume they're probably just being over volted now since I am actually seeing bad behavior from the color ram chips, but it is totally unrelated to the graphical corruption. Basically I'm getting color streaking on top of the incorrect graphics. No big deal except I haven't been able to find UM6116K-2 outside of kinds of sites you have to inquire first to order.
Any ideas before I just give up and get another mobo? Using the original CPU and ESwat board still works fine (aside from the color ram). Maybe it's the new 68k cpu that's the issue?

The only error I have seen in tests is J9. I tried replacing J9 but then both J9 and J10 were reporting bad. So then I replaced J10 too and they're still bad. It turns out I ordered the wrong chip. Original is UM6116K-2 and the replacements are UM6116K-2L which looks like it's a low power variant. I assume they're probably just being over volted now since I am actually seeing bad behavior from the color ram chips, but it is totally unrelated to the graphical corruption. Basically I'm getting color streaking on top of the incorrect graphics. No big deal except I haven't been able to find UM6116K-2 outside of kinds of sites you have to inquire first to order.
Any ideas before I just give up and get another mobo? Using the original CPU and ESwat board still works fine (aside from the color ram). Maybe it's the new 68k cpu that's the issue?