WinUAE 2.3.2 beta series

[Toni Wilen]

2.3.2 beta series.

This time shorter beta series.

Quick rules:

Allowed posts in this thread:

- bug reports but make sure bug is NOT in previous offical version. (Old bug -> separate thread)
- comments and suggestion about new features in betas or changed feature in beta. (missing feature or old feature which has not been changed in latest beta series -> separate thread)

Everything else will be deleted, no questions asked. (includes offtopic posts, discussion about pros and cons of public beta testing etc..)

Misc notes:

- "not working" is not a bug report -> instadelete
- always include name of the program. "Everything" or "most games" fail is not a bug report!
- always use quickstart settings. Non-QS setting reports will be ignored unless there is reason why quickstart isn't good idea but still test using quickstart just to confirm! (unless it needs some HD highend config)
- always check logs (both winuaebootlog.txt and winuaelog.txt, don't forget to enable logging in misc-panel) for possible error or warning messages.
- remember to include PC specs + Windows version (if asked)
- graphics error -> include screenshot.
- disk based program -> include CRC32 (mouse over disk history arrow down button will show CRC32) of the image(s) (or SPS ID or full tosec name if from latest set). Plain name of the game is NOT generally enough! (usually there are different cracks, trainers etc..)

As usual, betas may destroy your PC and your sanity

This thread is for general discussion (bad/good/stupid idea/whatever, no trolling or flaming) about public beta testing.

Beta test related PMs or emails will be generally ignored.

[Toni Wilen]

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

(shorter beta, small fixes and updates mainly)

Beta 1:

- added built-in AROS KS ROM (alpha development build), used by default if no ROM files available, not very useful at this point but more compatible than very basic UAE KS replacement
- serial port telnet server (win32.serial_port=tcp://host/port, add /wait to delay startup until client connects)
- DSKLEN=0x8000 emulation timing improved (Codertrash / Mexx crash after fractal part)
- improved disk wordsync bit timing (El Egg Tronic Quarts / Quadlite)
- improved CIA emulation accuracy in cycle-exact modes (Risky Woods sound glitches)
- fixed random sample ripper crash (ancient bug)
- CDA sound volume configuration entry (sound_volume_cd), default = same as sound_volume value, no GUI yet
- on screen led bar position configuration. config file only, "osd_position=x:y" 0:0 = default, negative value = offset from top of screen, add % to make it percentage of display height (osd_position=0:95.0%), x-coordinate positioning not fully supported yet)
- restoring statefile with memwatch point didn't automatically enable debugger memwatch subsystem

[Zosite]

Splendid! Risky Woods is now indeed fixed, and not only under Cycle-exact but also without it and even using Immediate Blitter.

Actually, the Cycle-exact mode puts there some subtle slowdown you may don't like, though chances are that it was also there on the original A500.

And if you don't use CE nor Immediate Blitter it seems there's some obscure graphic glitch which flashes from time to time in the background, but it's something sooooooo hard to appreciate, let alone to replicate, that I prefer to avoid calling it a bug unless someone else notices (and minds) about it.

Anyways... thanks again, Toni! As soon as you add a GUI for CDA volume I'll change the 2.3.1 for that new one. T-Zer0, you know... which also works quite well since 2.3.1 beta 8, by the way (now if only those SaveStates could also include CDA playing status).

[gimbal]

Originally Posted by Toni Wilen

- fixed random sample ripper crash (ancient bug)

Confirmed fixed!

[gilgamesh]

Wow, Turrican2 runs with AROS ROM. Great!

(There was some fllickering, but I suppose this is because WinUAE complained about wrong DirectX Version. I'm running it on Wine.)

[Mclane]

Originally Posted by gilgamesh

Wow, Turrican2 runs with AROS ROM. Great!

(There was some fllickering, but I suppose this is because WinUAE complained about wrong DirectX Version. I'm running it on Wine.)

Excuse my ignorance, what's this aros rom you talk of, I've heard of AROS but never saw a rom and its uses?

[gimbal]

Originally Posted by gilgamesh

(There was some fllickering, but I suppose this is because WinUAE complained about wrong DirectX Version. I'm running it on Wine.)

Lol? You are running an Amiga game in an emulator for Windows under something that is "not an emulator" bit secretly still is

Run all that in VirtualBox and you'll have inception.

[lilalurl]

Originally Posted by Mclane

Excuse my ignorance, what's this aros rom you talk of, I've heard of AROS but never saw a rom and its uses?

http://eab.abime.net/showthread.php?t=56211

[gilgamesh]

@Mclane: Free (as in speech) Kickstart Replacement, now included in WinUAE (#2)

Originally Posted by gimbal

Run all that in VirtualBox and you'll have inception.

Last time I checked WinUAE worked flawlessly (albeit slower) in Wine. I checked KS 1.3 and the flickering is still there, so it isn't AROS, and that is my point atm.

[Mclane]

Thanks peeps...Had to ask as I'm very nosey

[Toni Wilen]

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

Beta 2:

- 68000 exception 3 emulation changes (again), many very old copy protections didn't work since last large CPU emulation update (for example original Soldier of Light and Zoom!)
- win32.floppy_path and win32.hardfile_path finally really do what they are supposed to do (multiple paths supported, use paths if file not found using original path)
- include non-CDTV/CD32 CD audio state in statefile. Currently ignored during restore
- fixed color change table overflow crash that can happen when running amiga program crashes really badly
- AROS ROM updated, now includes WB replacement

[gilgamesh]

Originally Posted by Toni Wilen

- AROS ROM updated, now includes WB replacement

You mean one can boot into wanderer? If yes, how?

[Toni Wilen]

Originally Posted by gilgamesh

You mean one can boot into wanderer? If yes, how?

Wanderer won't ever be in ROM (it is too big). Wanderer boots simple by getting AROS full m68k-amiga setup which includes Wanderer and everything.

ROM WB is Jason's minimal Workbench replacement called Workbook which starts by using any WB disk C:LoadWB.

[gilgamesh]

So I've made an ADF, formatted it , installed, made a dir called 'c', copied LoadWB from WB1.3, booted to AROS CLI and typed in 'c:LoadWB'. Nothing happened.

What did I do wrong?

[Toni Wilen]

Originally Posted by gilgamesh

So I've made an ADF, formatted it , installed, made a dir called 'c', copied LoadWB from WB1.3, booted to AROS CLI and typed in 'c:LoadWB'. Nothing happened.

What did I do wrong?

Works for me but there can be any kinds of bugs here and there. Does unmodified WB1.3 disk boot to WB? (or 2.0+ without setpatch and iprefs, these can cause problems)

[gilgamesh]

WB1.3 sort of works. It boots ok, then I enlarged the folder. It got stuck in the state shown in the screenshot.

I only have 1.3 so somebody else might give 2.0 a try.

[hexaae]

Problems with keyboard!
Using WUAE 2.3.1 (public download) all WHDLoad in-game keys always work. Starting with beta 2.3.2b1 and b2 some games refuse to accept keys input.
E.g. IK+ when you start playing F8-F10 to change speed won't work and also quit key won't do anything. This happens for a lot of WHD games (IK+, Gods, Disposable Hero etc.). They perfectly work with WUAE 2.3.1 instead and keyboard input was always accepted....

[Mclane]

Could be a silly question but why does point / bilinear no longer work in the null filter, you can enable it but it does not work, I can get it to come one by setting full screen TV and settings like that but default has no effect.

Is this meant?

[Toni Wilen]

Keyboard problem is related to CIA changes, sometimes interrupts are lost, fixed soon..

Bilinear works still the same, it does not do much if pixels are doubled and 1:1 mapped.

[Mclane]

Originally Posted by Toni Wilen

Bilinear works still the same, it does not do much if pixels are doubled and 1:1 mapped.

Correct as always, I swear I've had double ticked before...

But yes, in normal its all good..Thanks Toni..

[Toni Wilen]

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

Beta 3:

- TD_WRITE64, TD_FORMAT64, NSCMD_TD_WRITE64 and NSCMD_TD_FORMAT64 io_Actual was always zero
- b1 CIA update broke CIA interrupts partially (keyboard problems etc..)
- MIDI input buffer length command line parameter, -midiinbuffer 12345
- AROS ROM updated, should work better again, previous one was quite broken

[gilgamesh]

Now I get error message like

Recoverable Alert!
Program Failed
Task: 0x00CAF600 - Workbench
Error: 0x0100000F - Memory header not located
PC: 0x00F879C8
Wait for disk activity to finish.

and

Recoverable Alert!
Program Failed
Task: 0x002AA5F0 - Workbench
Error: 0x01000009 - Memory freed twice
PC: 0x00F8739A
Wait for disk activity to finish.

when trying LoadWB on Aros. Which memory configuration do you recommend?

[Toni Wilen]

"Not working" "report" = I have no idea. Include at least logs.

[gilgamesh]

Problem solved. I simply didn't know that LoadWB must be followed by EndCLI (stupid me). Thanks to andreas for the tip.

Workbench works much better now with Aros ROM.

[Toni Wilen]

Originally Posted by gilgamesh

Problem solved. I simply didn't know that LoadWB must be followed by EndCLI (stupid me). Thanks to andreas for the tip.

Workbench works much better now with Aros ROM.

Works fine here without endcli, but Workbook is still work in progress, it can have memory leaks etc..

[andreas]

Toni, that must be a specialty of your AROS ROM then.

I'm 100% sure that LoadWB from WB 1.3 under *genuine* C= KS 1.3 will just "silently" execute the command but show absolutely no change on the screen. (well except for redisplaying the 1> prompt )
Not until you end the CLI with endcli, you actually see what got loaded behind the curtain.

Or we're not talking about the same thing...

[gilgamesh]

Yes, I see. It does work in the background.

Problem was this: I had LoadWB in Startup-Sequence, and I thought LoadWB would automatically close CLI. So I didn't notice Workbook in the background and called LoadWB from CLI a second time.
Second call to LoadWB always crashes with memory related errors. Probably it is not worth the trouble yet. (I can still post logs if you disagree.)

I don't see icons yet, though andreas already told me to include icon.library. (Insert volume "ENV". Huh?) Maybe somebody could make a complete workbook disk with Aros libs and Aros LoadWB. (That would rule out stupid user errors.)

[Toni Wilen]

I assumed that everyone knows LoadWB opens the workbench behind boot shell window and endcli only closes the shell window. That should be basic Amiga knowledge..

Loadwb crashing is a bug, aros workbench.library should detect that WB is already running and not attempt to run it again.

icon.library is in aros rom, something inside aros may require ENV: (which is 2.0+ feature) when it shouldn't. AROS was designed for 3.1 compatibility after all, non-m68k developers didn't need to care about that.

[msayed1977]

Only with WinUAE 2.3.2 Beta 3:
I only tried "Kick Off 2" and "Battle Chess". Both of them do NOT work at all.
They give a black screen.
You can try my attached configuration files.

I use WinXP Professional SP3.
My card is GeForce 8500GT.

Here is my log file.

[Toni Wilen]

Sure it isn't unexplained direct3d black screen issue which seems to be most common on Windows XP?

[msayed1977]

Originally Posted by Toni Wilen

Sure it isn't unexplained direct3d black screen issue which seems to be most common on Windows XP?

I do NOT know.

[Maren]

I get a "D3D: initialization failed" error as WinUAE attempts to switch to the standard PAL 720x576@50Hz mode as long as "(50Hz) PAL" is selected from the Display panel. If "Default refresh rate" is used instead, I don't get the error and WinUAE seems to be able to initialize properly. Interestingly enough, this also happens even when the desktop is already working under the screen mode WinUAE is supposed to use.

Regards.

[Toni Wilen]

Originally Posted by msayed1977

I do NOT know.

Switch to directdraw in misc panel and you know. In my randomly chosen version of Kick Off 2 (ALWAYS include CRC32!) I never saw completely black screen during booting.
Also quickstart configuration test is a must, I won't touch any custom configurations until it is confirmed working with Quickstart.

Do you even get WB hand screen?

Originally Posted by Maren

I get a "D3D: initialization failed" error as WinUAE attempts to switch to the standard PAL 720x576@50Hz mode as long as "(50Hz) PAL" is selected from the Display panel. If "Default refresh rate" is used instead, I don't get the error and WinUAE seems to be able to initialize properly. Interestingly enough, this also happens even when the desktop is already working under the screen mode WinUAE is supposed to use.

Only in 2.3.2b3? Surely not?

[dlfrsilver]

i tried Kick off 2 with A500 quickstart configuration and it works.

[msayed1977]

All games did NOT work with beta 3.
Now I have tried QuickStart. It gave the same result.
When I switched back to my custom configuration, the games worked fine as with beta 2.

Note:
After using QuickStart, the emulator said that I should use Kickstart 1.3. I already use it.

[Retro-Nerd]

Just tried a Kick Off 2 IPF image and the Genesis & Angels crack. Both works fine with Beta 3+Quickstart.

[Maren]

Originally Posted by Toni Wilen

Only in 2.3.2b3? Surely not?

Well spotted , sorry about that. This is indeed something inherited from the latest official release, which I completely overlooked as I normally just jump into the latest beta wagon and forget abut everything else.

I, whoever, don't recall this happening in at least some of the 2.3.1 betas that I got to test some time ago.

[Toni Wilen]

Originally Posted by msayed1977

All games did NOT work with beta 3.
Now I have tried QuickStart. It gave the same result.
When I switched back to my custom configuration, the games worked fine as with beta 2.

I used your config and Kick Off 2 still works fine (btw, your config is quite strange, 68000 + 1.3 + AGA and some harddrive also included)

This is not going anywhere without checksums (or email or upload it to the zone or something)

Note:
After using QuickStart, the emulator said that I should use Kickstart 1.3. I already use it.

1) ROM path is incorrect, check Paths panel and then press rescan roms.
or
2) You have bad (patched, hacked, unofficial, whatever) 1.3 rom image.

[Narf the Mouse]

Configuration: A500, 512k Chip RAM, 512k Slow RAM, Workbench copied to and loading off a HDD Directory. FA-18 Interceptor in DF2:, DF1: empty. Cycle-Exact off; CPU set to "Fastest possible, but maintain chipset timing".

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

Does not happen without FA-18 Interceptor in DF2: (also happens with Battletech: The Crescent Hawk's Inception in DF2: ). Problem appears to reduce over repeated resets.

[Toni Wilen]

Originally Posted by Narf the Mouse

Configuration: A500, 512k Chip RAM, 512k Slow RAM, Workbench copied to and loading off a HDD Directory. FA-18 Interceptor in DF2:, DF1: empty. Cycle-Exact off; CPU set to "Fastest possible, but maintain chipset timing".

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

Does not happen without FA-18 Interceptor in DF2: (also happens with Battletech: The Crescent Hawk's Inception in DF2: ). Problem appears to reduce over repeated resets.

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