|Re: [hatari-devel] Next Hatari version for OS X|
[ Thread Index |
| More lists.tuxfamily.org/hatari-devel Archives
This preference panel works much better. You already know about the TT RAM bug. I could only check so much since I could not compare it with the SDL menu in Falcon mode. I tried Miguel’s suggestion of removing everything from ~/Library/Application Support/Hatari, but that only allowed me to see the SDL menu before I selected anything. Once I selected the TOS 4.04 ROM and rebooted, the SDL menu went blank again. However, I did remember to try TOS 2.06. That ROM allowed me to select the 68040 and 68060 options and still allow me to see the SDL menu since it was not using the Falcon screen modes. I could see the proper preferences were being set in the SDL menu. I think this looks good once the TT RAM preference problem is solved.
Thank you for working on this.
> On Jun 15, 2015, at 3:19 PM, Jerome Vernet <vernet.jerome@xxxxxxxxxx> wrote:
> Le 15/06/2015 00:39, Bob Carpenter a écrit :
>> I tried your updated OS X preference screen with the Mercurial version of Hatari. I see that 68060 is greyed out even with the WinUAE CPU enabled.
>> Therefore, I set the value to 68040 and rebooted Hatari. After the reboot, Hatari showed a value of 68060 instead of 68040.
> You're right, it's a bug
> Find a new change here:
>> In addition, if I set the TT RAM value to 0 and re-enter the preference screen, the value has been set back to 4.
> It's also a bug and I can't figure why ! Relevant CNF_PARAMS of Hatari
> are well set. Need to investigate
>> One last thing, in the WinUAE core section, the English phrase “24 bits adressing” should be “24-bit addressing”.
> It's changed.
>> I wanted to compare the values to the SDL menu but the SDL menu does not work in OS X when you are in Falcon mode. This has been a problem for a while.
> I know. text do not show or same color as background in 32bpp. it's a
> SDl bug ???
> More over, you will find my oww instructions, based on Troed one's to
> make an working XCode project with Frameworks rather than MacPorts
> library here: