Cycles auto and max bugged because of default limits

[andres-asm]

The beauty (and the purpose) of cycles auto and max is that you wouldn't need to tweak so much to get decent game performance

Setting cycles to max results in the following:

This would be fine for low end games but not for something like quake... I benchmarked with this: quake +timedemo demo1

I didn't have enough patience to wait for the timedemo to finish

If I do the same but beforehand I run: config -set cpu cycles max

auto is also unusable for quake too even if I set it from the commandline, not sure why, but it's worse when using the core options because the result is:

[andres-asm]

Weirdly enough auto in DOSBox-SVN is perfect in my device:

[realnc]

If you don't want a max cycles limit, set them to 0.

[andres-asm]

for whatever reason it all just worked even in auto now...