AR mk3 read error when writing on floppy (WinUAE 5.0.0)

[kremiso]

seems its not possible to write anything on disk when using an Action Replay rom (3.09)

i always have a read error here, using the official 5.0.0 release

it worked fine with the 4.x releases

[Rock'n Roll]

no problems here. (create standard disk)
wt 0 2 $20000
Disk ok

more info needed

[kremiso]

i'm not sure, but i think i get the triggering factor

setting 1 MB of CHIP RAM, and trying to write a freeze state to disk will always lead to a read error

i'm adding a screenshot
note that the 'dir' command does work, as the SLOADER;
the SA test does not instead

[Toni Wilen]

Worked for me. Selected cycle-exact A500 ECS 1M quickstart, selected AR3 ROM, booted to cli, freeze button, typed "sa 1", compression and save was succesfull.

sa 1
Disk ok

dir
Directory of (empty)
153270 1
1438 blocks free, 18.2 % of disk used

"sloader" also worked.

[kremiso]

something just on my side then

Toni, i'm trying to made tests also with the latest 5.1.x betas, but it's even worse here, the freeze button (page up) make freeze the entire WinUAE

[Toni Wilen]

Originally Posted by kremiso

something just on my side then

Toni, i'm trying to made tests also with the latest 5.1.x betas, but it's even worse here, the freeze button (page up) make freeze the entire WinUAE

Still works for me. Config file required.

[kremiso]

ok
if can help im using the 32bit versions on a win7 pc atm;
i see a checksum ar3 error in the winlog file, maybe its due to the patched for kick 2.x , but i dunno if is related to the issue

note that with the 4.x releases all worked fine, and with the 5.0.0 the freeze works fine

this is what happens when pressing page up on the kick boot screen :

[Toni Wilen]

Ah, it is AR3 doing stupid things with VPOSW which is not going to work very well if CPU is not slow enough (not cycle-accurate). Previously this was not allowed but recent versions improved emulation of these hacks.

Next beta will again only allow VPOSW writes that are used to for "fake 60Hz" if CPU is not cycle-accurate.

[kremiso]

glad to know you catched it, i'll update in future then

[kremiso]

hi Toni
just to report testing with your latest beta7 here

- Ignore backwards or same line vertical VPOSW writes if it was CPU write and CPU emulation is not in accurate mode. This basically reverts VPOSW updates to pre-5.0 behavior when CPU is not at least in memory cycle exact mode, supporting only usual "fake NTSC" modes. At least AR3 does stupid things with VPOSW that can't work if CPU is not slow enough.

sadly no luck on my side, the emulator is still freezing when pressing page up key;
i need to close the WinUAE process into the task manager

tested with default A500 configuration and both 3.09 MKIII roms (standard and hacked for k2.x);
cycle exact and best compatibility both ticked

[jotd]

I must say that it's a crime to use AR3 on WinUAE when you have WinUAE monitor

Except if it's to create save files to reload on a real machine

[kremiso]

Noah's Ark syndrome