WinUAE 2.5.0 Beta series (Was 2.4.2)

[UncleSpam]

Toni,

Beta 17 looks good, with the exception of certain masks being applied in the Filter section.

For example "Art_Twisty.png" will cause the issue to appear, but less pronounced than before.

Without masks enabled, the issue is resolved.

-Bogdan

[Toni Wilen]

Originally Posted by UncleSpam

Toni,

Beta 17 looks good, with the exception of certain masks being applied in the Filter section.

For example "Art_Twisty.png" will cause the issue to appear, but less pronounced than before.

Without masks enabled, the issue is resolved.

Do you mean it is the mask only that has 1:1 pixel mapping problem? Amiga screen behind is always fine?

Has it always been like this on your system? What GPU?

EDIT: Attach also configuration.

[UncleSpam]

Yes, the Amiga screen, by itself, is fine.

The issue only appears with the certain masks enabled.

See attached file for my test config and another screen grab.

I'm using the Nvidia Quadro FX 770M graphics card on a Dell Precision M4400 with up-to-date certified drivers.

Regards.
-Bogdan

[Leandro Jardim]

The logs. The problem begins when I copy the contents of the new scalos beta onto the image (i do not execute it). I copy also "copymem.lha" (Aminet) and a backup of old ENVARC. Its also a 3.1 system, and I use NewIcons in Workbench, and he problem arrises when I view the drawer where I unpacked the Scalos archive or other drawers near it.

[Toni Wilen]

Originally Posted by Leandro Jardim

The logs. The problem begins when I copy the contents of the new scalos beta onto the image (i do not execute it). I copy also "copymem.lha" (Aminet) and a backup of old ENVARC. Its also a 3.1 system, and I use NewIcons in Workbench, and he problem arrises when I view the drawer where I unpacked the Scalos archive or other drawers near it.

What "problem"? Why do you think this has anything to do with emulation? Log only contains multiple sessions, nothing interesting there.

[Leandro Jardim]

Originally Posted by Toni Wilen

What "problem"? Why do you think this has anything to do with emulation? Log only contains multiple sessions, nothing interesting there.

The problems are from these three posts. Like I said, I would post the logs that would be possible to get with the problem that I have:

Originally Posted by Leandro Jardim

I tried my HD images in latest beta, and they dont work. I made some to work, but for some reason, AmigaOS lock-up during a directory read. They use RDBs and seems that WinUAE has corrupted the images that I tested because they doesnt work anymore in any version of WinUAE.

Originally Posted by Leandro Jardim

Latest beta (B16). I will supply the logs for you, I felt it could be important but that happens during some certain file management operations that I did in the last two tries, for the last two images that I worked into, and I need to track these operations and the logs.

The problem begins because for some reason, WinUAE doesnt loads the hardfile. Here are the first logs.

Originally Posted by Toni Wilen

I think I also managed to duplicate this. It is related to CDFS fix, not yet sure what goes wrong.

EDIT: This was brown paper bag bug. Any non-UAE controller hardfile/drive won't work in b16.. Unless it is the first one in list.

EDIT2: http://www.winuae.net/files/b/winuae.zip should fix it.

[Toni Wilen]

But that one was already fixed in b17. Are you really sure it is same "problem"?

Problem was non-UAE controller HDFs (For example IDE emulation) not getting mounted and your log shows HDFs are detected as expected.

"Problem" isn't very good description..

EDIT: Explain exactly what happens because I am sure your problem is totally different than I originally thought. (bug does not trigger if you only have one harddrive)

[Leandro Jardim]

I changed to B16 and installed Scalos Beta, but I dont liked it, so I deinstalled it. After this I got the problems. Always when I listed the hard file T drawer with the temporary unpacked archive of Scalos, the icons doesnt are shown as it should and Workbench locks up.

So after this, I deleted the hard file and got my backup copy. Copied my new s directory and env-archive that I got from the old hardfile to it. And copied Scalos again. Happened the same problem.

Not only the directory with the temporary archive of Scalos hangs up, but others as well, and my Windows directory mounted as a directory file system. I do not execute anything from it, only list its contents with Workbench. Its strange because the Windows directory is handled by WinUAE, not 68K, I guess.

So I executed PFSDoctor on all Amiga partitions but it doesnt shows anything wrong. I also always use a anti-virus on my Amiga partitions, doing a virus check on boot and a automatic scanning during a session. And the anti-virus doesnt shows nothing wrong, with zero suspicious vectors. I dont use too many patches, only NewIcons, DefIcons, BlazeWcp and CopyMem.

After this, I can even remove the directories with problems and recreate them, but the same problem arises. With the old backup that I have, that was not modified at all with B16/B17, this problem doesnt happens.

[Toni Wilen]

I still don't see anything related to emulation, just some AmigaOS-side software incompatibility or something. (Did you even test with older version?)

[Leandro Jardim]

Originally Posted by Toni Wilen

I still don't see anything related to emulation, just some AmigaOS-side software incompatibility or something. (Did you even test with older version?)

I discovered whats wrong with my "Amiga", its the ENVARC:deficons.prefs that was corrupted by some reason. Strange, that file is only read by DefIcons and the image is OK...

[mr.vince]

Toni, for the record: the same AmiKit folder (1.6, emulated as HDD) that works with 2.4.0 gurus with 2.5.0 latest beta. No UAE crashes, but guest OS trouble. If you want me to run some tests or send some logs... Let me know.

[Toni Wilen]

Originally Posted by mr.vince

Toni, for the record: the same AmiKit folder (1.6, emulated as HDD) that works with 2.4.0 gurus with 2.5.0 latest beta. No UAE crashes, but guest OS trouble. If you want me to run some tests or send some logs... Let me know.

You were supposed to test latest official version before posting here and 2.4.0 is not latest

At least include logs from non-working and working setup.

[mr.vince]

I tested the one that came with it. Guess that was for a reason.

I used the exact same config for both. Will prepare a package with logs, config (based on QuickStart with just HDD and RTG added).

[Toni Wilen]

Find also first beta that has the problem, if possible. Of course it can be simple Amiga software bug that didn't trigger until memory layout or something changed.

[Toni Wilen]

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

Beta 18:

- FPS and CPU% react quicker now. Can Show previously hidden CPU usage spikes. NOTE: CPU% now showing "myserious" usage spikes does not mean emulation has become slower!
- Automatically limit tablet mode X and Y coordinate range to prevent 16-bit signed overflows if tablet has large resolution. (not confirmed)
- Always generate full size mask texture, workaround for mask pixel mapping errors in some scaling modes.
- Only release pressed keys if window or screen gets reopened (prevents stuck keys), not when any graphics related config option changes.
- Do not allow GUI resize if GUI is larger than fullscreen resolution because Windows may automatically resize it to fit on screen, making GUI completely unusable.
- Always recalculate Display panel horiz/vert centering option internal values when configuration changes.
- 68030+ CPU and more compatible checkbox checked: enable very basic prefetch emulation, only 68000-68020 have more complex prefetch emulation.
- JIT + more compatible also enables basic prefetch. Only works if code is not yet translated. (Not much point but it was easy to do)
- Added route all MIDI In data to MIDI Out configuration option.
- Improved 68030 MMU instruction decoding. WHDLoad + MMU option enabled + 68030 CPU does not crash anymore. (No, there still is no 68030 MMU emulation, it is only emulating 68EC030 without MMU circuitry which probably does not exist in real world + hack for A3000 1.4 ROM)
- Few (rare) variants of MOVES didn't increase PC correctly.
- BSR.L was emulated as 68020+ instruction on 68000/010. (BCC.L was correct)
- For some reason 68000 BSR.B and BSR.W address exception stack frame PC field points to new odd PC, instead of address of BSR opcode.

[Neil79]

Nice no probs thus far in what i play anyway that's for classicwb and gamebase... Always keep a check on the latest builds, thanks

[Neil79]

Just played stunt car racer using gamebase and i'm getting mad flickering in the lower half of the screen when the car ends up on the track, main menu is fine... Using latest beta ^, it's set to full screen/SuperSai

[Toni Wilen]

Originally Posted by Neil79

Just played stunt car racer using gamebase and i'm getting mad flickering in the lower half of the screen when the car ends up on the track, main menu is fine... Using latest beta ^, it's set to full screen/SuperSai

Most likely it is game issue with too fast CPU option, last few official versions have increased CPU speed when chipset was in use. Probably also nothing to do with this beta series .

[Toni Wilen]

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

Beta 19:

- GamePorts panel Test function now shows all currently mapped input target(s). Can be used to test any kind of input event mapping.
- Do not map 3rd button to joystick/pad with more than 2 buttons if GamePorts panel gameport mode is joystick. Joystick is meant to be max 2-button, non-pullup resistor game controller.
- Directory filesystem ACTION_DISK_INFO InfoData->id_Inuse is now non-zero if any files or locks are open. (Was previously always zero)
- Use D3D (if available) to fetch GPU names listed in monitor selection GUI. Should now show correct GPU name when running on hybrid GPU systems.
- GUI CD audio volume control added.
- Standard PAL/NTSC mode horizontal position (without filters or centering enabled) is not slightly shifted anymore, not sure when this changed, probably in some update that improved programmed mode display positioning.

EDIT: Horizontal position change wasn't such a good idea after all..

[Toni Wilen]

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

Beta 20:

- Reduced Gayle based configuration CIA memory bank size to 4096 bytes, only accesses to bfdxxx and bfexxx goes to CIA chips if Gayle.
- Reverted b19 horizontal change, I forgot that it was made to fit max overscan modes better.. (Manually adding "gfx_horizontal_tweak=8" to config file can be used as a workaround, if needed for some reason)
- 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.
- added win32.gui_active_page=name, sets default GUI panel after emulation has been started (Old win32.gui_page = before emulation starts)
- In some situations adv. chipset may have used incompatible data stored in config file even if compatible settings was ticked.
- 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.
- On screen led HD/CD/NVRAM indicator is blank if device is not available (like floppies already did).

[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.

[wizzel]

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?