WinUAE 2.3.2 beta series

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