WinUAE 2.3.2 beta series

[thomas]

Originally Posted by Narf the Mouse

Fonts are mis-loaded arbitrarily, with, for example, "q" loaded in place of "r".

This happens since ages with Kick 1.3 / WB 1.3 if FF (Fast Font) is executed in Startup-Sequence, probably back to the 0.8 range of WinUAE versions. Does not happen in "modern" versions of WinUAE if Cycle Exact is enabled.

Originally Posted by Toni Wilen

- AROS ROM

AROS ROM does not work with HD floppies. Reports "trying to read a block outside the bounds" (don't remember exactly) in an Amiga requester.

[Narf the Mouse]

Originally Posted by Toni Wilen

Why do you think this is an emulation problem? or 2.3.2 specific?

Probably some blitter font acceleration patch that forgets to wait for the blitter etc..

It doesn't happen in Cycle-Exact. Other than that, nothing. I had noticed the bug before in a more generalized form when running in "Fastest Possible", but it seemed to be gone with "Maintain Chipset Timing".

Not sure where else to put it, but I first noticed this form of the bug in 2.3.1.

[Toni Wilen]

Originally Posted by Narf the Mouse

It doesn't happen in Cycle-Exact. Other than that, nothing. I had noticed the bug before in a more generalized form when running in "Fastest Possible", but it seemed to be gone with "Maintain Chipset Timing".

Not sure where else to put it, but I first noticed this form of the bug in 2.3.1.

It isn't an emulation bug, it is a software bug that depends on timing (missing blitter wait). Enable immediate blitter if you want to "fix" it.

[Narf the Mouse]

Originally Posted by Toni Wilen

It isn't an emulation bug, it is a software bug that depends on timing (missing blitter wait). Enable immediate blitter if you want to "fix" it.

Thanks.

[Toni Wilen]

Perhaps it is good idea to make blitter "auto-waiting" when using fastest possible cpu modes.

"Auto-wait" = CPU access to any blitter register while blitter is busy (and blitter dma is enabled) will stop the cpu until blitter has finished.

[Toni Wilen]

http://www.winuae.net/files/b/winuae_2320b4.zip

Beta 4

- added new autofire option. Button released = autofire. Button pressed = normal non-autofire firebutton.
- 231b13 reset fix fixed again (A1000 and Arcadia emulation crash)
- automatic resolution switch interlace detection was unreliable
- show a message and refuse real harddrive write attempts to block zero (=RDB write attempt) if drive has one or more mounted PC partitions. Partitioning is going to fail even if write appears to succeed.
- screen mode change (fullscreen<>windowed or windowed mode window size change) released all currently pressed keys, it should only happen when WinUAE loses focus, not when switching modes
- window title bar mouse text shortened, F12 note added
- stop the cpu and wait until blitter has finished if any blitter register is accessed while blitter is busy and cpu mode is fastest possible

[TCD]

Originally Posted by Toni Wilen

- window title bar mouse text shortened, F12 note added

[HOL2001]

Originally Posted by Toni Wilen

- 231b13 reset fix fixed again (A1000 and Arcadia emulation crash)

Works fine again!

[sink]

thk toni, excellent and interesting beta version!

[mr.vince]

Just pondering my head here... is Action Replay support broken again in latest beta?

[mr.vince]

Toni, not sure if you are referring to my post. Using 2.3.2 beta 4 I can't boot the virtual machine with an Action Replay ROM enabled. It keeps rebooting, I never see the Kickstart hand...

[Toni Wilen]

Originally Posted by mr.vince

Toni, not sure if you are referring to my post. Using 2.3.2 beta 4 I can't boot the virtual machine with an Action Replay ROM enabled. It keeps rebooting, I never see the Kickstart hand...

It was supposed to be reply to Megachur. (I usually only complain about reports that only say "it does not work" or similar, sorry)

Your post wasn't much better. "It does not work". Fortunately I found out what you meant before I started complaining (AR does not work in non-cycle exact modes)

[mr.vince]

It was just so obvious (rebooting loop) I did not post more info. But of course you're right... the report was shitty as hell.

[andreas]

Trying to flirt with Toni?!

[Toni Wilen]

http://www.winuae.net/files/b/winuae_2320b5.zip

Beta 5:

- floppy step signal's previous state was not restored properly from statefile (possible one skipped or one extra step when program steps for the first time after state was restored)
- tight DSKBYTR() read loop sometimes triggered second index sync pulse after few cycles. Broke some copy protections randomly. (for example original Double Dragon II)
- enable Gayle ID register in CD32 mode. CD32 boot menu checks for Gayle ID and immediately exists if Gayle is not detected. This must mean Akiko includes some (unused or never fully implemented?) parts of Gayle (at least ID register) because boot menu works on a real CD32.
- RESET instruction didn't work correctly in 68000 compatible non-ce (prefetch) mode (Arcadia/AR/A1000)
- only use triple buffer if triple buffer selected and vsync enabled. Seems to fix (at least partially) random Direct3D blank screen issue (also triple buffer in non-vsync modes is quite pointless)
- configuration file chipset_refreshrate accepts now floating point values

[Dr.Venom]

Originally Posted by Toni_Wilen

- configuration file chipset_refreshrate accepts now floating point values

Toni, as posted in the other thread (http://eab.abime.net/showthread.php?t=58495), many thanks for adding this option.

There are some small issues where the custom floating point refresh rate gets overwritten/reset to the default value 50.00hz.

To be precise, when a custom refresh rate has been set (eg. 49.92) all is well until:

F12 --> click 'display' panel --> click OK. --> custom refresh rate is automagically reset to 50.00
F12 --> click 'display' panel --> click on pull down menu to select 'double buffer' --> custom refresh rate is reset top default 50.00
When a game or demo switches from a non-laced screen to an interlaced screen (eg demo 'Tint' or game 'Slamtilt'), then winuae resets the custom refresh rate back to the default value of 50.00.

Hopefully you can iron these little 'bugs' out. Thx & WinUAE 4ever

[Mad-Matt]

This will perhaps need confirming by others, but using beta 5 - the avi recorder is recording at 49 fps instead of 50 fps for video and is going out of sync with audio quite quickly.

Audio is commig in at 49.919 on both, ill have to check back a few version to see if this is normal or not.

[Toni Wilen]

Originally Posted by Mad-Matt

This will perhaps need confirming by others, but using beta 5 - the avi recorder is recording at 49 fps instead of 50 fps for video and is going out of sync with audio quite quickly.

Audio is commig in at 49.919 on both, ill have to check back a few version to see if this is normal or not.

Probably side effect of floating point frequency support in previous beta.
Actual exact refresh rate is 49.92 (313 lines) or 50.08 (312) . Previously it was always rounded to 50.00.

I guess vsync and avi recording should always use integer refresh rates.

[Toni Wilen]

http://www.winuae.net/files/b/winuae_2320b6.zip

Beta 6:

- Display panel overwrites chipset_refreshrate decimal part only when slider is adjusted
- Display panel directly accepts non-integer refresh rates
- last serial port device was not listed (b1)
- added serial_stopbits configuration parameter, sets Paula serial port emulation stop bit length. (0 = 1bit, 1 = 1.5bits, 2 = 2bits) Technically it should always work but at least some USB adapters don't seem to reliably read Amiga serial data at 19200 without setting it to 1 or 2. (interestingly for example 115200 works fine, this is quite confusing)
- Gameports panel remapping fixed (b4)
- avioutput refresh rate was not rounded to nearest integer (b5)
- fixed crash when switching from RTG mode to native mode (old bug, only in specific combination of filter and display settings)

[Toni Wilen]

http://www.winuae.net/files/b/winuae_2320b7.zip

Beta 7: (1-2 weeks to go)

- borderblank only worked in AGA mode, BPLCON0 bit 0 was ignored in ECS Denise mode
- config_window_title configuration entry added, text shown on GUI and main window title bar if set
- delay allocation of filter buffers if current mode is RTG
- fixed uninitialized buffer when writing joystick input settings to config file, possible worst case issue was corrupt input configuration data in config file
- AROS ROM updated