Articles from o1i's blog
Some many hours of debugging more, I managed to get the first Picasso96 / uaegfx screen to work:
After a long break (and a long silence here), I returned to my WinUAE port. It still had no Picasso96 support, something which annoyed me a long time now. Problem was, that even everything looked ok (to me), as soon as the uaegfx monitor was added, it crashed. As both uaegfx and rtg.library are closed source, debugging it was a nice lesson, but lead to no results.
So I compared all uae generated 68k library and modeinfo structs with the fs-uae structs and (for me) everything looked ok.
The problem with bugfixes, that try to fix randomly appearing bugs, is, that you can never be sure to have it really fixed. So one day after the last post the bug appeared again, just under a little bit different circumstances.
So back to bug-hunting again, but I was sure now, that the problem is in the Zune Listclass, not in my code. So after some time I discovered, that the Listclass stores the sizes of the columns of each line in an array, which gets allocated at object creation time.
Not much progress on WinUAE on AROS the last months.. why?
I never got the harddrive tab working reliable. Adding a new harddrive with the gui always resulted in a TLSF memory allocation error and I had no idea, why. The pool was damaged somewhere..
So I searched and debugged for .. many hours. Too many, so I always stopped hunting for the bug after maybe 5 hours and gave up. And restarted weeks later. And restarted.. and the last start was finally successful :-).
I did some smaller things in WinUAE, but I was quite lacking motivation and time the last few months..
So today I decided to do something just for fun:
So does Santa have a final WinUAE release for AROS?
Well, I don't know of course, but I don't have one, sorry.
The (quite painful) merge to 3.2.0 is now completed, I started picasso96 support (half-done) and just wanted to give you an update on the current state.
With just a few adjustments to the SDL code I got an output window, which also contained the status line and looked quite ok.
But nothing happened. The CPU emulation code was called and then .. nothing!?
In my old 2.8.1 version I added some assembler operations to get a better timing for the processor speed, as AROS seems not to be able to provide something like that.
And I enclosed the assembler part with