exxos's Atari, Amiga & retro forum

Thanks for the explanation. :thumbup: Yes, the BIOS is gone, but personally, I don't think it's a big deal. Whenever I made a change, it was never saved. I have no idea why. If I had the choice, though, I'd want it back. ;) I did all of this using CPX, with no problems. There are also matching CPX versions available for the current new versions.

kohli79 wrote: 22 Sep 2026 12:55 Thanks for the explanation. :thumbup: Yes, the BIOS is gone, but personally, I don't think it's a big deal. Whenever I made a change, it was never saved. I have no idea why. If I had the choice, though, I'd want it back. ;) I did all of this using CPX, with no problems. There are also matching CPX versions available for the current new versions.

I am confused again, so why did you choose the no-bios version? If you wanted bios?

Steve wrote: 22 Sep 2026 14:23

kohli79 wrote: 22 Sep 2026 12:55 Thanks for the explanation. :thumbup: Yes, the BIOS is gone, but personally, I don't think it's a big deal. Whenever I made a change, it was never saved. I have no idea why. If I had the choice, though, I'd want it back. ;) I did all of this using CPX, with no problems. There are also matching CPX versions available for the current new versions.

I am confused again, so why did you choose the no-bios version? If you wanted bios?

Because of the bug fixes. As I said, the problem with the image has gone with the new version. It’s not a big deal that the BIOS is gone now. But if I had to choose between having it or not in future, I’d go for the BIOS. ;)
It’s likely to be added back in future anyway. :)

Now I understand... I missed that mikro made a minor version bump to 'f' since 'e' was released. But I will probably wait for a version that incorporates the bios.

Steve wrote: 22 Sep 2026 15:10 Now I understand... I missed that mikro made a minor version bump to 'f' since 'e' was released. But I will probably wait for a version that incorporates the bios.

:thumbup:

kohli79 wrote: 22 Sep 2026 12:55 Whenever I made a change, it was never saved. I have no idea why.

Most likely because you have got the CT63 from Centuriontech with the "wrong" flash? Could you save anything in the CPX (like changed MHz, ROM/RAM setting, ...) in 1.05 / 1.03e? Because 1.03f should fix this (which is no help to you since it doesn't contain the bios unless... hang on...)

... typing typing typing...

Can you try the attached image? It's imperative that you use Flash060.prg from 1.03f but apart from that, your BIOS + saving parameters to flash should work now.

Thanks, Mikro. :) Yes, I can make changes via the CPX. That worked fine before as well. (1.05/1.03e)

I’ve flashed your version and it’s now working with the BIOS. Changes are being saved. :dualthumbup:

But I’m now having these screen synchronisation issues again. This happens occasionally after a reset or when the Falcon starts up. The screen only appears once the desktop has finished loading. You can see this very clearly on the OSSC display: it isn’t picking up a signal and the display is going haywire. This problem first occurred in version 1.03e. With V1.03f, this problem had been resolved. :?

Interesting. What I did was basically taking 1.03f and put insane's 1.05 on top of it. Do you see those synchronisation issues also on your previous 1.05?

If you like, you can try this alpha version of 3.01 -- it is basically my 1.03f + SuperVidel detection + insane's changes (but not to the boot process). You can give it a try although I'm still not sure what could causing your issues.

Okay, thanks. I'll test it with the alpha version.

I'd never had these problems before; they only started after I installed version 1.03e.
With v1.03f, everything was fine again.

There don’t seem to be any issues with the display on the Alpha. :)
Changes made in the BIOS can also be saved.