Bug I think...

[NLS]

Not really serious.
Here is how I did it.

Winuae64, latest release, Win10x64.

I used quickstart. Selected A500 and "most common" configuration.
All fine. I run some apps, ok.
Then I wanted to boot something like a brand new original A500, so in quickstart I selected configuration with 1.2 ROM, OCS Agnus and +512k slow.
Then I clicked "restart". It "closed" all winuae windows, waited for a while then it went back to config with the choices I made in quickstart.

So I started the machine AND... CLI reported I was booting workbench 1.2 (which is what I chose) on a *1.3* kickstart machine!
I pressed F12 and it did have "1.2 ROM... etc." in quickstart configuration.


I quit WinUAE and restarted it. It remembered my last choices, so I started and this time it booted propertly workbench 1.2 ON kickstart 1.2.

Don't know if someone can replicate this.

[Schlachtwerk]

When you the Rom not have, Winuae use the internal AROS Kickstart replacement rom

[emufan]

are you using the portable mode (F12 -> Path -> portable)?
if so, disable it, next enable it again. it did reset the quickstart settings here on my box.
Quickstart configs work again, after the bug annoyed me for a year.

[NLS]

Schlachtwerk, I have all the needed roms (and surely the most important ones), else I wouldn't ask.

I have "portable" selected (which I assume just means were .ini is saved/read), I don't want to reset my .ini file. It doesn't look like a file access issue, as quickstart settings show properly as I set them.
The problem is what I describe in bold above (discrepancy between selected configuration and active configuration, although I pressed "Restart" on WinUAE - only real restart of the program "fixed" it).

[NLS]

Well definitely something is acting weird...

[Toni Wilen]

Not enough information in that screenshot (Important part is missing). It can be perfectly normal if quickstart configuration is not activated. (with button or checkbox)

[NLS]

Thanks Toni, I will do more tests when I can.
What part of the screen you are missing?

How is quickstart configuration activated? Which button or checkbox?

I select quickstart configuration (while another runs), click "restart" and expect that after restart (and not plain reset of the emulated machine of course), it will be "active". It definitely shows as selected though.

[Toni Wilen]

I am not sure if I understood..

Quickstart is "one way". When Quickstart panel "start in quickstart mode" is ticked or "set configuration" is pressed, current Quickstart settings become current configuration. After that configuration can be manually changed and quickstart panel has no effect anymore (unless button is pressed again)

[NLS]

Well exactly.
I start in quickstart mode (and that is clicked).
I select a mode, it works.
I click another mode (for example I was A500 KS1.3 512+512 and select A500 KS1.2 512).
I press "restart" (because I assume "reset" is not the proper button to press).
It "starts" again, shows the new mode (1.2) I selected before restart.
I start the emulation...
...and I am still in the previous mode.
I quit WinUAE, start it again, it shows the new mode (1.2 - correct again) but now if I start the emulation it starts properly in that mode.

I am not sure if this has anything to do with that WinUAE is on a mapped drive (from another computer). Access is proper full control (I use the same domain user on both machines).

(I used to use UNC paths, but since you verified already a bug with long paths on latest version when looking for ROMs, I switched to mapped drives)