WinUAE 2.5.0 Beta series (Was 2.4.2)

[AmigaSurfer]

Originally Posted by Toni Wilen

Beta 20:
- RTC update in b11 was not compatible with KS 1.x.
- improved RF5C01A RTC emulation, previously KS2.0+ detected stopped clock and attempted to reset it (which is no-op because emulated clock's time is currently read-only) and after reset it finally read the time.
- RTC year value is saved differently depending on OS version, Pre-2.0: RTC year value = current year - 1900, 2.0+: year value = last 2 digits. Both methods supported when reading. WinUAE now uses pre-2.0 method if MSM clock chip (because this is the only type that KS1.x supports), 2.0+ if RF clock chip, previously always used -1900 method.
- RTC 12/24h bit emulated, this is not used by AOS.
- RTC time/date, alarm and memory data save/load to file supported (alarm time/date, note that alarm interrupt pin is not connected in Amigas, and 104 bits of memory, used mainly for A3000 SCSI settings, included with RF clock chip type). Date/time ignored when loading.
- Syncronize clock on the fly CIA TOD adjustment is now only active if heartbeat signal (b11) is detected.
- b11 heartbeat system was not fully disabled when UAE boot rom was unavailable.

Running timehack with filesize 6956 bytes leads to an guru 8000 0004.
Btw, is timehack still necessary?

[Toni Wilen]

Originally Posted by AmigaSurfer

Running timehack with filesize 6956 bytes leads to an guru 8000 0004.

00EF0000 64K/1 = 64K UAE Boot ROM

Nothing to do with above changes. You have A3000 configuration enabled (A3000 SCSI) = 0xf00000 is needed for A3000 1.4 MMU tricks = UAE boot rom is moved to 0xef0000 = timehack (and most other programs that use uae hook without extra tests) will crash.

Btw, is timehack still necessary?

Clock sync misc option should do the same.

[Toni Wilen]

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

Beta 21:

- Use software volume also in WASAPI non-exclusive because WASAPI main volume control also affects waveOut used by CD audio. (XP + DS also seems to affect waveout.. CDA really should use some more modern sound API, later...)
- Floppy sound sample mixing volume fix, volume level got lower if more than one drive had enabled sounds.
- Virtual mouse driver option IECLASS_POINTERPOS inputevent ie_Qualifier apparently needs to include mouse button state bits or Magellan II's (AmiKit) menus won't stay open, possibly affects other programs too. (This is not documented in HRMs, hmm...). "Start menu" still won't work but it is application bug because it also won't work if mouse is moved using Amiga + cursor keys.
- CDFS crash fix when unsupported media (not unreadable but for example UDF-only DVD) was accessed.
- Check and ignore possible duplicated CDFS CD insert or eject Windows message.
- Compile time directory filesystem logging is now runtime option (-filesyslog and -filesyslog2)
- Borderblank still didn't work correctly in all situations. (Aladdin AGA)
- Fullscreen DirectDraw mode IDirectDrawSurface7_Flip "Was still drawing" fix. (I still have no idea what was I thinking of..)
- Added "waiting blits" special case, when blitter is started and blit would use all available cycles: start waiting for the blit immediately.
- Changing hardfile path does not anymore clear device name and filesystem text boxes.
- Fixed crash when loading statefile with JIT enabled (b6 "ROM protection" should be disabled temporarily when loading UAE boot rom data..)
- zlib updated to 1.2.7
- Built-in AROS ROM updated.

[Mad-Matt]

I think the RTC updates have finaly fixed the various doom ports running with Jit+sync clock Enabled.

Game would always hang durring the screen wipe effect when starting game with Sync Clock +Jit enabled before, and seems fine now.

Have launched the game a few times now with various amiga configs(Aga/Rtg) and doom versions (Boom,Adoom,Doomattack) and game hasnt hung once.

[Toni Wilen]

Originally Posted by Mad-Matt

I think the RTC updates have finaly fixed the various doom ports running with Jit+sync clock Enabled.

Game would always hang durring the screen wipe effect when starting game with Sync Clock +Jit enabled before, and seems fine now.

Have launched the game a few times now with various amiga configs(Aga/Rtg) and doom versions (Boom,Adoom,Doomattack) and game hasnt hung once.

Not directly related to RTC stuff, fix was:

- Syncronize clock on the fly CIA TOD adjustment is now only active if heartbeat signal (b11) is detected.

When using the shutdown function in AmiKit 1.61 WinUAE brings up a hardware bus error combined with a software failure.

This worked in b20 (shuts down AmiKit).

Just wanted to let you know.

[mr.vince]

I can second this, but Toni will ask for a log file. I know it worked with an older Beta, but does not work with 20 here. I know Toni gave me a version to test graphics card detection issues, so could be that I have a not "official" beta 20.

[James]

Originally Posted by wizzel

When using the shutdown function in AmiKit 1.61 WinUAE brings up a hardware bus error combined with a software failure.

The actual failing program is uaequit:

http://thomas-rapp.homepage.t-online...ds/uaequit.lha

Failing in b20 and 21 here with an 80000004 as is MMKeyboard:

http://www.geit.de/stupid/mmkeyboard.lha

winuaelog.zip

[Toni Wilen]

Attach winuaelog.txt from last working beta version.

[James]

WinUAE_b19log.zip

[Toni Wilen]

Ah, another case of update that causes another, old bug to appear...

- In some situations adv. chipset may have used incompatible data stored in config file even if compatible settings was ticked.

This caused the problem but original bug is "Generic" Amiga model enabling A3000 DMAC emulation which causes relocation of UAE Boot ROM because it detected A3000 mode and A3000 1.4 "bonus" MMU relocation stuff uses 0xF00000 region which is normally reserved for UAE ROM.

Fixed version will be released soon.

I never noticed it because I always use "real" Amiga configurations. ("Generic" = fake IDE and other stuff so that mismatched ROMs won't hang at boot)

[Toni Wilen]

Does http://www.winuae.net/files/b/winuae.zip fix it?

UAE Boot ROM line in log should be back to F00000 from EF0000 when using "Generic" model configuration.

[James]

Originally Posted by Toni Wilen

Does http://www.winuae.net/files/b/winuae.zip fix it?

UAE Boot ROM line in log should be back to F00000 from EF0000 when using "Generic" model configuration.

Yes working now

[Toni Wilen]

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

Beta 22:

- "Generic" Amiga model incorrectly enabled A3000 DMAC emulation which caused most programs that require UAE Boot ROM in normal 0xF00000 area to crash. (Old bug, b20 adv.chipset caused it to appear much more commonly)
- Disable ROM protection when switching JIT off on the fly.
- Dragging standard HDF to Hardfiles panel sets correct default geometry.
- Added logical cylinder value to HDF config data, default is zero = calculate from size of the HDF (same as previously)
- Added "physical" CHS values to HDF config data, can be used to override autogenerared IDE emulation CHS values. (append ",logical cyls,C/H/S" to hardfile2 config entry. No GUI support.)
- GUI resize button was permanently disabled after it was unticked once.
- log_disabled=1 in registry (DWORD) or ini disables winuaebootlog.txt.
- Check DPI value when selecting default GUI size.
- CD32 audio emulation update, Guardian CD32 (and possible some others) had muted audio since b1. Immediate reply to CD play command should not have "play active" bit set. It should be only set in later status packets.

[emufan]

is there a problem with the "Power" button on the status line? since beta 20 it does not print "Power" on that area next to framerate in status bar of winuae.
i'm here in rtg mode, classicwb p96. window-mode, Display:Windowed "720" "568", within classicwb: screenmode: UAE 800x600 32 bit BGRA. the values dont match, however it works.
resizing the winuae window does not help. all other status-bar names/values are displayed.
just reporting, ignore if useless report.

[liveevil]

Just a question, please don't flame me, does WinUAE use multithreading ? I don't see any options for it. The reason I ask is that at the moment i'm going through my youth collection on a Dual Core Netbook 1.6 gig (I know it's technically underpowered). Nearly all A500 stuff works great (with slightly out-of-sync sound). A lot of AGA stuff makes the sound horrible but the video is about the correct speed. Can the video use 1 Core and the sound on another ?
Also, are the drive sounds on these betas alot louder than before or is it just me ?

[Toni Wilen]

Originally Posted by liveevil

Just a question, please don't flame me, does WinUAE use multithreading ? I don't see any options for it. The reason I ask is that at the moment i'm going through my youth collection on a Dual Core Netbook 1.6 gig (I know it's technically underpowered). Nearly all A500 stuff works great (with slightly out-of-sync sound). A lot of AGA stuff makes the sound horrible but the video is about the correct speed. Can the video use 1 Core and the sound on another ?

Problem is not sound taking too much, anything that takes too much time willl break sound.

Display update rate below normal frame time (1/50s PAL, 1/60s NTSC) = sound will break because new sound data was not generated fast enough.

Sound (and nearly everything else) is hardwired to display timing in Amiga hardware. It can't be emulated separately.

(and wrong topic for this discussion)

Also, are the drive sounds on these betas alot louder than before or is it just me ?

There was mixing bug, the more drives had drive sound enabled, the lower the volume.

[Toni Wilen]

Originally Posted by emufan

is there a problem with the "Power" button on the status line? since beta 20 it does not print "Power" on that area next to framerate in status bar of winuae.
i'm here in rtg mode, classicwb p96. window-mode, Display:Windowed "720" "568", within classicwb: screenmode: UAE 800x600 32 bit BGRA. the values dont match, however it works.
resizing the winuae window does not help. all other status-bar names/values are displayed.
just reporting, ignore if useless report.

I can't see any difference. Screenshot please.

[emufan]

booting.jpg shows window right after boot is started, "finished.jpg" when loading workbench is done, in rtg mode.
tested also with my amisys config. power is gone there too, and i'm pretty sure, it was there once

[Leandro Jardim]

Hi Toni, there is a bug I tracked only from beta 19 upwards when I use the mask Aperture2x4rb_Aaron in full-screen only. You can see what I am saying in the screenshot.

Better late than never, I use a Radeon HD4300 and Windows 7 Home Premium 32 bits and I have updated DirectX regularly.

Ah well, I used the same copper backdrop that you see in the picture on WinUAE and FS-UAE, both without the mask, and there the backdrop is softer, in terms of the color gradient, and much more realistic to 32 bit color, do you know what could cause this "degradation" of the color space, is this a bug or needs a fix someday, etc?