exxos's Atari, Amiga & retro forum

Thanks @kohli79, that definitely motivates me to finish this for another release. :-P

(still no clue what could cause your sync issues but I'm glad that I'm on the good side of the barricade here :D)

@mikro Could I use one of these bioses on my ct60e? I'm still on 'e' version. Which would you recommend.

Steve wrote: 24 Sep 2026 08:11 @mikro Could I use one of these bioses on my ct60e? I'm still on 'e' version. Which would you recommend.

They don't bite. :-) There's nothing wrong with using 3.00 on your CT60e, without SuperVidel you will get basically what 1.03f offers. If you want latest stuff + insane's BIOS Setup, either take the alpha above or wait for 3.01 release.

mikro wrote: 24 Sep 2026 01:24 Thanks @kohli79, that definitely motivates me to finish this for another release. :-P

(still no clue what could cause your sync issues but I'm glad that I'm on the good side of the barricade here :D)

:bravo:

I flashed the official version 3.00 as a test. It has these synchronisation issues too. It’s a bit odd, really ... :?

kohli79 wrote: 24 Sep 2026 16:07 I flashed the official version 3.00 as a test. It has these synchronisation issues too. It’s a bit odd, really ... :?

I don't know man, I'm starting to think it is just a coincidence. From your previous posts:

- 1.05: no sync issues
- 1.03e: sync issues
- 1.03f: no sync issues
- 1.03f + insane's 1.05 changes: sync issues
- 1.03f + supervidel stuff you don't use + insane's 1.05 changes (3.01 alpha): no sync issues
- 1.03f + supervidel stuff you don't use (3.00): sync issues

It doesn't make sense. Either 1.05's changes influenced something or not, but it can't be both.

Only 1.03f has something which *theoretically* could fix something Videl-wise. If I were to guess, your monitor is too sensitive to fast changes on the Videl side: the boot sets 320x240x16bpp (even in 3.00 which doesn't have the 320x240x16bpp picture anymore; for timing purposes) and very quickly sets back to your boot resolution.

So you can try to experiment with that, a good test would be setting boot resolution to 320x240x16bpp and see whether your monitor isn't happier on the "broken" builds.

I’m using an OSSC V1.8. I mentioned that briefly earlier. Never mind … ;)

After I changed the boot resolution, these problems stopped occurring. Even now that I’ve switched back to 640x480. Nothing – no more sync issues. I also reflashed the versions where the problems occurred, and nothing’s wrong now. Crazy! :D
It’s likely that the set value wasn’t applied correctly, causing a conflict. It just needed to be changed and saved again. If this happens again, this simple fix should do the trick.