Since 3.5 AmigaOS turns into a very fast rebootlloop (I think)

[spudje]

So I recently finally updated from a WinUAE 3.4 beta version to the stable 3.5 version.

Since then I have issues with many of my uae configs, which all worked fine before. The behaviour is, that after boot the screen turns black with a slight flicker. It looks like the emulation is in a very fast bootloop. Sometimes I get error messages that all of a sudden ROM files can't be found?????? Currently I'm working a lot with A4k WinUAE configs (incl CSPPC), so these at least are the ones causing issues. I tried with the latest 3.6 beta as well, same behaviour.

Video link that shows behaviour and error message attached. BTW disregard the 2 error messages popping up while booting AmigaOS.

[ Show youtube player ]

Hope anybody can help me fix this.

[Toni Wilen]

"Not enough information". Logs and config is always required. I hate videos.

[spudje]

OK, sorry, I'll try to provide them. Will have to wait till the weekend though. Do I have to turn on logging somewhere first?

[Toni Wilen]

winuaebootlog.txt is always created, winuaelog.txt is only created if misc panel log file option is ticked. (tick it before starting emulation)

Include also logs from working version.

[spudje]

Typical, it now gives same behaviour in (stable) 3.4 (don't remember which beta it was, I upgraded). It's probably some config setting?

Attached config & log files of the behaviour in WinUAE 3.5.

[Toni Wilen]

You have zero byte CSPPC ROM (="empty" uninitialized AF ROM image. Don't just copy those blindly from AF.). Old versions didn't accept it, now it is accepted as an empty flash that can be flashed with official flash updater.

[spudje]

Yes, I figured this out just now as well, pfff stupid me. I'm sorry bothering you with this, thanks a lot helping me! Copying the rom there and pointing to it made it work.

Mmm, still not fully flawless. WinUAE opens with message the PPC rom isn't there while it is. It's also not detected when scanning roms. However PPC configs work now when I point to the rom file. Sorry, again it's me. I had to rename the file.