WinUAE 3.2.0 beta series

[ziosante]

Originally Posted by Toni Wilen

I think you missed post #154

Yes, I missed.

Attached the dump.

Thanks

[AnnaWu]

Originally Posted by Toni Wilen

winuae.7z should fix it. I think all possible drive/disk combinations should now work correctly.

Excellent work, Toni.

[Toni Wilen]

http://www.winuae.net/files/b/winuae.7z update.

- x86 ide config save/load fixed
- fix crash when mouse driver option (or other similar options) enabled.

[AnnaWu]

Originally Posted by Toni Wilen

http://www.winuae.net/files/winuae.7z update.

- x86 ide config save/load fixed
- fix crash when mouse driver option (or other similar options) enabled.

Is the URL valid?

[Toni Wilen]

Originally Posted by AnnaWu

Is the URL valid?

It is now. It is usually quicker to check old posts for correct url

[AnnaWu]

Originally Posted by Toni Wilen

It is now. It is usually quicker to check old posts for correct url

Now it is ok, thanks a lot!

[Toni Wilen]

http://www.winuae.net/files/b/winuae_3200b9.7z

Beta 9:

- x86 floppy controller EOT parameter was read from wrong offset. Note that previously 1.4M floppy in 720K drive (configured in 2286+ BIOS) worked, not anymore.
- Added x86 bridgeboard 1.2M PC floppy image support.
- Added Advanced chipset option that emulates some 68040/060 board's (for example Blizzard 1240/1260) custom register byte write "bug" where byte write to custom register does not write same value to both upper and lower byte. Previously this was always enabled if CPU type was 68060. (Writing to even address: zero written to odd address, writing to odd address: works "correctly")
- Fixed emulation boot crash if mouse driver was enabled (b8)
- x86 IDE config didn't load correctly. (Reset and save needed to fix it). x86 VGA also needs config reset.

[Toni Wilen]

Bridgeboard-only posts moved to bridgeboard thread.

[ziosante]

Originally Posted by Toni Wilen

http://www.winuae.net/files/b/winuae_3200b9.7z

Beta 9:

- x86 floppy controller EOT parameter was read from wrong offset. Note that previously 1.4M floppy in 720K drive (configured in 2286+ BIOS) worked, not anymore.
- Added x86 bridgeboard 1.2M PC floppy image support.
- Added Advanced chipset option that emulates some 68040/060 board's (for example Blizzard 1240/1260) custom register byte write "bug" where byte write to custom register does not write same value to both upper and lower byte. Previously this was always enabled if CPU type was 68060. (Writing to even address: zero written to odd address, writing to odd address: works "correctly")
- Fixed emulation boot crash if mouse driver was enabled (b8)
- x86 IDE config didn't load correctly. (Reset and save needed to fix it). x86 VGA also needs config reset.

Tested, works fine for me. No more crashes at boot up.

Thanks.

[Arnie]

Forget it Toni.

[Toni Wilen]

http://www.winuae.net/files/b/winuae_3200b10.7z

Beta 10:

- IDE emulation internal operation change. Previously next block was read from hardfile after previous block was transferred. Now all blocks are buffered first before transferring (or if write: all data is received first and then all buffered data is written to HDF). Fixes A2286 BIOS built-in IDE driver which does not wait for interrupt or DRQ status bit between transferred blocks. (Which technically is a bug, driver is depending on some specific HD manufacturer/model internal implementation detail)
- Amiga to PC bridgeboard interrupt enable/disable state fixed. A2286 Janus hardfile access does not hang anymore.
- Added x86 CPU speed adjustment (CPU panel, full left = fastest possible mode). Note that some BIOS drivers use CPU delay loops, unexpected things can happen.. Fastest possible enables extra hack ("immediate" floppy to prevent floppy detection fail). Speed adjustment is only enabled after initial
BIOS diagnostics checks have been done because some timer tests fail if CPU is too fast..
- Added right control = right Windows key option. (Keyboards without right Windows key, quicker to use than creating custom mapping, note that it also disables keyboard layout B RCTRL=fire mapping)
- GUI window is now per-monitor high DPI aware.
- 3-State Apollo 500/2000 IDE/SCSI combo HD controller fully implemented. ROM added to ROM scanner. 3rd party replacement ROM available from Aminet. (http://aminet.net/package/disk/cdrom/AT_ApolloDev)
- CDFS automount without physical drives mounted 10 empty image drives (b1).

[Arnie]

Everything working with this beta for me.

One thing puzzles me though, the x86 CPU speed adjustment. If max speed is far left, shouldn't the incremental numbers decrease as you move it to the right?

[Toni Wilen]

Originally Posted by Arnie

One thing puzzles me though, the x86 CPU speed adjustment. If max speed is far left, shouldn't the incremental numbers decrease as you move it to the right?

No. It is similar to floppy speed.

There was no space for "fastest possible" checkbox and putting fastest in rightmost position would have made future scale adjustment more difficult.

Originally Posted by Arnie

Everything working with this beta for me.

The crashes under AmiKit 8.5.0 with FreeMem are back. They do not appear EVERY time you boot up AmiKit, but SOMETIMES.
Or is this a problem concerning FreeMem itself? I haven't follwed the Board on that issue, recently, sorry.

[Toni Wilen]

Originally Posted by wizzel

The crashes under AmiKit 8.5.0 with FreeMem are back. They do not appear EVERY time you boot up AmiKit, but SOMETIMES.
Or is this a problem concerning FreeMem itself? I haven't follwed the Board on that issue, recently, sorry.

Sounds like some timing sensitive bug in some system patch. Beta 10 does not have any Amiga/m68k emulation changes.

EDIT: I assume you meant emulated Amiga is crashing with some guru?

Originally Posted by Toni Wilen

I assume you meant emulated Amiga is crashing with some guru?

No, i mean it's a crash within FreeMem under AmiKit 8.5.0 (Software Error).
But i am by no means an Expert regarding these crashes. Maybe it's FreeMem related and not WinUAE.
The crash takes place every now and then on booting up AmiKit.

Please take a look at the screenshot.

[Toni Wilen]

Originally Posted by wizzel

No, i mean it's a crash within FreeMem under AmiKit 8.5.0 (Software Error).
But i am by no means an Expert regarding these crashes. Maybe it's FreeMem related and not WinUAE.
The crash takes place every now and then on booting up AmiKit.

Please take a look at the screenshot.

Usually this error is caused by buggy program that for example frees memory that it has not allocated or frees wrong amount of memory or has corrupted memory lists (due to some other bug)

It probably is bug in "ScreenText" program but it also can be caused by bug in some previously executed program that corrupted memory lists.

[Steve]

I got a crash while trying to save a game state using a Blizzard 1260 expansion board.

[Toni Wilen]

Originally Posted by Steve

I got a crash while trying to save a game state using a Blizzard 1260 expansion board.

I am quite sure this has nothing to do with 3.2 betas..

Anyway, state file is not supported by most expansion hardware (accelerator, rtg board etc). Don't do it is the only solution now

[Steve]

Originally Posted by Toni Wilen

I am quite sure this has nothing to do with 3.2 betas..

Anyway, state file is not supported by most expansion hardware (accelerator, rtg board etc). Don't do it is the only solution now

Ah ok then. Is there any difference in emulation speed between 1260 fastest possible and 020 fastest possible or is it just the instructions that are different? Shouldn't the 060 in CPU be automatically selected if an expansion like 1260 is chosen? I changed it manually (in CPU settings after choosing the 1260 expansion) but wasn't sure if changing it would make any difference.