WinUAE v2.5.0 - possible bug with Hardware configs, ECS Agnus chipset setting

[SedrynTyros]

I don't think this is a big deal but I thought I'd point it out since it may confuse some people.

I noticed that when I loaded my Hardware configs that I'd previously saved to use the ECS Agnus chipset, it shows it as using the OCS chipset in the WinUAE v2.5.0 gui. Even if I change it to ECS Agnus then save the config, when I reload the config again it still defaults to OCS. This only seems to occur with Hardware configs, though. Full configurations will correctly save this chipset adjustment.

I decided to examine the config files in notepad and also looked back at some earlier releases of WinUAE. It looks like that starting with WinUAE v2.4.0, the ECS Agnus chipset became the default chipset (so-to-speak); when ECS Agnus is selected there's no longer a config line "chipset=ecs_agnus" in the config like there was in v2.3.3.

So, long story short, I found that when I manually changed the Hardware config files with notepad and added back the line "chipset=ecs_agnus" the chipset would show up correctly as ECS Agnus in the WinUAE v2.5.0 gui when the config was loaded.

I don't know if it's just a problem with the gui showing OCS in these Hardware configs and it's really using ECS Agnus or what, but I thought I'd bring this to your attention, Toni.

[Toni Wilen]

Hmm.. for some reason chipset config entry type was changed to "save only if value is not default" which isn't correct because chipset entry has existed since the beginning. Only new and rarely used entries should use this method, it keeps config file shorter and less messy.