English Amiga Board - View Single Post

Toni Wilen · 31 March 2022, 09:42

Possibly $f00000 UAE boot ROM causing those hits (if $f0 ROM is not marked as mapped in MMU config). Try changing ROM panel board type to 128k model (which disables old-style $f0000 ROM and replaces it with single 128k autoconfig board)

EDIT: and don't enable any compatibility features, some of them are not fully MMU emulation compatible. ("more compatible", cycle-exact etc)

31 March 2022, 09:42	#2
Toni Wilen WinUAE developer Join Date: Aug 2001 Location: Hämeenlinna/Finland Age: 47 Posts: 25,382	Possibly $f00000 UAE boot ROM causing those hits (if $f0 ROM is not marked as mapped in MMU config). Try changing ROM panel board type to 128k model (which disables old-style $f0000 ROM and replaces it with single 128k autoconfig board) EDIT: and don't enable any compatibility features, some of them are not fully MMU emulation compatible. ("more compatible", cycle-exact etc) Last edited by Toni Wilen; 31 March 2022 at 09:52.