I don't. I won't touch PC hardware (chips) unless there is ready made emulation. Cirrus Logic emulation is the only one full VGA emulation that exists, at least in QEMU.

Quote:

Something seems to be wrong with Cycle exact mode in the newest Beta 6. Using Quickstart Config mode A4000 with 68030 CPU and cycle exact. Tested with the TBL demo Glow - Sound is distorted, with the same settings under Beta 5 it works as it should.

But is the sound problem due to CPU% going over 100% now? Always required information when sound gets bad.

Sorry for the missing information. Yes it is going far over 100% <---- 190-200% instead

Only in that demo? Does early boot menu or WB also show much higher CPU% compared to previous version? Does it also happen if you select A1200 quickstart config (with cycle-exact)? If you use previous config but change CPU to 68030?

EDIT: one more test, delete or move default.uae out of configurations directory, then try again.

A1200 quickstart works fine, no higher cpu usage - And i did what you suggested, i choose temporalrily an empty folder without configurations inside - makes also no difference.

But what's making a difference in Beta 6 is in Cycle Exact mode with Quickstart A4000 030 if i change the switch from fastest possible towards approximate A500/A1200 - but it should make no difference in that case since after all it is cycle exact mode?

Edit the last hopefully!

Gone back now to 2.8.1 which is used in Amiga Forever, tried to load also that similar config there - in direct comparison i found the following out: in 2.8.1 iN Cycle exact mode, no matter if A1200 or A4000 the additional checkboxes for fastest possible and approximate A500/A1200 mode under CPU and FPU are greyed out and can not be changed, while in 2.8.2 Beta 6 and 5 they are not greyed out and can be changed under Cycle exact mode. This is the first thing which seems to be wrong?

In 2.8.1 which is used right now in Amiga Forever i can run demos like TBL Glow and Goa in Cycle exact A4000 030 mode with a custom CPU frequency of 40 MHZ without distorting sound while under 2.8.2 Beta 6 with that same value i have distorted sound.

A1200 quickstart works fine, no higher cpu usage - And i did what you suggested, i choose temporalrily an empty folder without configurations inside - makes also no difference.

But what's making a difference in Beta 6 is in Cycle Exact mode with Quickstart A4000 030 if i change the switch from fastest possible towards approximate A500/A1200 - but it should make no difference in that case since after all it is cycle exact mode?

Cycle exact always required "approximate" setting previously. It still does but now "fastest possible" is also available (as explained in changelog).

Previously it was always forced back to "approximate" if CE was selected. (It means "a500/a1200 approximate" or "cycle-exact" as in any cycle-exact mode, not just a500/a1200)

Used that test config. CPU usage was under 2.8.1 around 40-60% and under 2.8.2 B6 close to 190-200% - Testing now also with Beta 5 - Even there is a small regression with that config and same demos - i did not notice that sadly before, in Beta 5 it is around 140-150%

Edit again: Ok, seems stable under Approximate settings in latest betas, but gets more and more cpu power demanding in fastest possible. Thanks anyway, so fastest possible should be avoided in that case, good to know

Used that test config. CPU usage was under 2.8.1 around 40-60% and under 2.8.2 B6 close to 190-200% - Testing now also with Beta 5 - Even there is a small regression with that config and same demos - i did not notice that sadly before, in Beta 5 it is around 140-150%

Yes but you'll notice that if you load it to older version, approximate is selected and you can't even change it. You need to put it to approximate manually to match old config!

Your config is technically invalid because it has CE and fastest possible enabled, for some reason.

hmm, there is still a problem with BPPC boot menu changing noMapROM/MapROM, use, saving ... after that is impossible to enter into boot menu, also strange screen is shown in SysInfo (see pic.1 below) with 68000 library on $08xxxxxx address (should be at $68xxxxxx) and with "NO AUTOCONFIG FOUND" ?!

p.s. But on CSMK3/CSPPC both boot menu saving and FlashUpdates seems work fine (see on pic.2 & 3).

p.s.2. Seems also on BPPC FlashUpdate tool works if applied on new renamed flash file (see on pic.4 & 5), and it change it from 256k to 512k. Nice.
So, only saving from boot menu seems still problematic on BPCC.

Seems in beta7 the Blizzard 2060 map rom works if "MapROM" is checked in WinUAE rom option !
On below link is said: "maprom selectable by jumper", so it is similar to B1260 then.http://amiga.resource.cx/exp/blizzard2060

JSeems in beta7 the Blizzard 2060 map rom works if "MapROM" is checked in WinUAE rom option !

It does not! There is reason why it is mentioned in changelogs. It may appear to work but map rom memory is still in system free list and sooner or later whole system crashes.. B2060 memory mapping is complex and I am not sure how it works.

Quote:

In this file you can find configurations for Basic Amiga (500/500+/1200 etc...).

Note that only quickstart configurations are accepted if you want to report anything related to A500/A1200 compatibility. Anything else: not my problem. (and I don't see what does these have to do with 2.8.2 betas, this is beta only thread)