WinUAE 3.5.0 beta series (was 3.4.1)

[Toni Wilen]

Originally Posted by ross

Hi Toni, a replicable crash.

Fixed. That was nasty overflow due to really "wide" (and bad) display.

[Pyromania]

Thanx for the hard work Toni.

[ross]

Hi Toni, a not replicable crash (with same unresponsive requester like before).

Always the same configuration (AGA, blizzard 1230 MMU FPU, Cycle-exact 8x), WB 3.x, hires unlaced.
Some copper test, lowres, legal DDFxxx (even $048->$0d8 for overrun), shift , color and all: no problems.

If i change from Cycle-exact 8x to 4x then randomly crash (changes made not in custom screen mode but also in WB).
[EDIT: the change from 8x->4x with 'live' machine not a restart; from 4x->8x no problems]

Attached two example dump file.

Not a problem at all, was casual my change of emulation speed, but maybe help You to catch some hidden bug.


Thanks Toni!

[ross]

Originally Posted by Toni Wilen

I am quite sure it has nothing to do with MMU but you have some option(s) enabled that don't support weird custom chipset features.

No Toni, no oddities.
A simple standard Quickstart configuration (A1200, basic not-expanded configuration, host in windowed 752x572 display, CPU 030) highlights the bug.

Launch the attached .adf with and without MMU...

Surely as nothing to do with MMU but the change alters something somewhere.

[Toni Wilen]

Originally Posted by ross

No Toni, no oddities.
A simple standard Quickstart configuration (A1200, basic not-expanded configuration, host in windowed 752x572 display, CPU 030) highlights the bug.

Launch the attached .adf with and without MMU...

Surely as nothing to do with MMU but the change alters something somewhere.

I can't see any difference if compatibility mode stays the same. Note that it can only work if at least memory cycle exact is enabled, without it there can't be cycle conflicts by design!

[paraj]

Originally Posted by Toni Wilen

Yes but exact same thing has happened every time new MSVC has been released and I haven't seen any problems so far. Also usually optimizer gets more and more aggressive, easily breaking almost correct code that has previously worked fine.

And finally, I want to live dangerously, I want to use bleeding edge software, even including operating system

Of course, if it really breaks winuae, I'll use previous version because it won't just affect me only.

My experience from work is that the bugs are usually in advanced/niche/new stuff. With a (no offense meant) "C with classes" C++ codebase like winuae, I'd personally be pretty comfortable always using the latest MSVC version.

Bleeding edge C++ (for MSVC) on the other hand causes lots of tears. And if you're forced to support C++/CLI code I'll see you at the support group....

[ross]

Originally Posted by Toni Wilen

I can't see any difference if compatibility mode stays the same. Note that it can only work if at least memory cycle exact is enabled, without it there can't be cycle conflicts by design!

Toni, i do not know what to think, in my PC does not work.
In desperation i also installed in a clean virtual machine from scratch WinUAE 3.4.0 and overwritten with the beta3: does not work.
See attached images, i assure you that the options are based on A1200, cycle exact, only 030 w/MMU w/oMMU change.

What can I do?

Thanks,
ross

[Toni Wilen]

Include the config file. I repeat: ALWAYS include the config file.

[ross]

Originally Posted by Toni Wilen

Include the config file. I repeat: ALWAYS include the config file.

Toni, like i've said, a default A1200 basic +030/MMU.

I'm sorry, it seemed unnecessary.

Thanks,
ross

[Toni Wilen]

Fixed. I didn't know there was some lines that did work and some that didn't. Better description next time please

[Toni Wilen]

Originally Posted by ross

Hi Toni, a not replicable crash (with same unresponsive requester like before).

Always the same configuration (AGA, blizzard 1230 MMU FPU, Cycle-exact 8x), WB 3.x, hires unlaced.
Some copper test, lowres, legal DDFxxx (even $048->$0d8 for overrun), shift , color and all: no problems.

If i change from Cycle-exact 8x to 4x then randomly crash (changes made not in custom screen mode but also in WB).
[EDIT: the change from 8x->4x with 'live' machine not a restart; from 4x->8x no problems]

Attached two example dump file.

Not a problem at all, was casual my change of emulation speed, but maybe help You to catch some hidden bug.


Thanks Toni!

Need config + bootable disk that can be used to duplicate this (no HD, no WB). Dumps only point in buffer overflow because crash happens in code that makes no sense.

[ross]

Originally Posted by Toni Wilen

Fixed. I didn't know there was some lines that did work and some that didn't. Better description next time please

Toni, i apologize for haven't well described the problem.
I've difficulties with the English language..

Thanks!

[ross]

Originally Posted by Toni Wilen

Need config + bootable disk that can be used to duplicate this (no HD, no WB). Dumps only point in buffer overflow because crash happens in code that makes no sense.

Always the same configuration from:
http://eab.abime.net/showpost.php?p=...4&postcount=32
And the executable/bootable ADF from:
http://eab.abime.net/showpost.php?p=...7&postcount=44

Are totally random host crashes that occur changing CPU speed (cycle exact mode) from 8x to 4x (with live machine).
Better negate the possibility to change speed when amiga emulation is on?

But do not fiddle with it.
Probably it makes no sense that users change the parameter in that way..

Bye,
ross

[Toni Wilen]

Originally Posted by ross

Are totally random host crashes that occur changing CPU speed (cycle exact mode) from 8x to 4x (with live machine).
Better negate the possibility to change speed when amiga emulation is on?

I can't duplicate. It probably need just right timing.

Everything that is possible to change on the fly should be possible to change on the fly! It would be quite boring emulator if speed changes are not possible on the fly (and more).

[Toni Wilen]

http://www.winuae.net/files/b/winuae_3410b4.7z
http://www.winuae.net/files/b/winuae64_3410b4.7z

Beta 4:

- BPLCON4 bitplane XOR values didn't affect background color between end of bitplanes and end of horizontal diw.
- FPU packed decimal datatype conversions are now accurately emulated. (AG). Softfloat mode is now mostly complete.
- -serlog command line parameter without -log now only logs serial output (and reads serial input).
- Lightpen emulation absolute coordinate HID pointing device support. (For example Aimtrak Light Gun) No extra configuration needed, absolute coordinates are automatically used in lightpen mode.
- American Laser Games second player light gun support added. ALG #2 horizontal/vertical input event.
- Fixed buffer overflow when screen was extremely wide internally with bitplane dma overrun.
- Escape old style directory and hardfile paths if it contains "," (which is config file separator)
- Bitplane overrun didn't work in lines that didn't have any other chip bus accesses or when mode was non-CE.

[DamienD]

Originally Posted by Toni Wilen

- Escape old style directory and hardfile paths if it contains "," (which is config file separator)

Heya Toni,

Just tested this and it works

I did have to re-add the .HDF and then save the configuration. The new lines now look like this (added a gap between lines below for easy reading):

hardfile2=rw,DH0:".\\Games\\Simon the Sorcerer II - The Lion, the Wizard and the Wardrobe AmigaCD\\Simon the Sorcerer II - The Lion, the Wizard and the Wardrobe AmigaCD.hdf",32,1,2,512,0,,uae

uaehf0=hdf,rw,DH0:".\\Games\\Simon the Sorcerer II - The Lion, the Wizard and the Wardrobe AmigaCD\\Simon the Sorcerer II - The Lion, the Wizard and the Wardrobe AmigaCD.hdf",32,1,2,512,0,,uae

[ross]

Thanks Toni!

With this new beta I can't even replicate 8x-> 4x crash

[HanSolo]

I have something in my custom boot menu with current beta of winuae. With beta 3 I never seen that.

[waldiamiga]

Early Startup Control in Polish!

[Toni Wilen]

Originally Posted by HanSolo

I have something in my custom boot menu with current beta of winuae. With beta 3 I never seen that.

I think you'll notice that winuae version has nothing to do with that..