View Single Post
Old 28 December 2013, 09:12   #18
Toni Wilen
WinUAE developer
 
Join Date: Aug 2001
Location: Hämeenlinna/Finland
Age: 42
Posts: 19,513
Something causes quite bad memory corruption because "DMA conflict" messages are only logged when DMA debugger is active and it can be only activated by using debugger commands.

You probably need to narrow it down to some command in your startup-sequence or wbstartup.
Toni Wilen is offline  
 
Page generated in 0.04587 seconds with 9 queries