WinUAE 3.0.0 beta series (was 2.8.2/2.9.0)

[antiriad76]

Is there any posibility of somebody developing uaegfx drivers for AmigaOS 4.X so that we can get "UAE 1920x1080 32bit BGRA" on the OS?

The Picasso IV card emulation is very limited when it comes to resolutions above 1024x768.

[B14ck W01f]

Originally Posted by antiriad76

Is there any posibility of somebody developing uaegfx drivers for AmigaOS 4.X so that we can get "UAE 1920x1080 32bit BGRA" on the OS?

The Picasso IV card emulation is very limited when it comes to resolutions above 1024x768.

I agree. It would be nice if I can get a 2048x1152 resolution.

I doubt that Toni could have the time to add more video cards even if he wanted to.

[Toni Wilen]

Originally Posted by B14ck W01f

I agree. It would be nice if I can get a 2048x1152 resolution.

I doubt that Toni could have the time to add more video cards even if he wanted to.

Only fully implemented (and license compatible) hardware SVGA chip emulation that exists is Cirrus Logic chip range and all CL compatible cards are already emulated, unfortunately Amiga Z2/Z3 CL based boards have max 4M hardware VRAM limit.

I don't write boring PC hardware emulations. Someone elses problem as usual. Perhaps QEMU or DosBox or something else does it someday.

I also don't write non-m68k drivers. Same "solution": Find someone who writes uaegfx wrapper for OS4.

[thellier]

Originally Posted by Toni Wilen

Find someone who writes uaegfx wrapper for OS4.

How ? I remember you wrote that "uae to native" interface (68k traps) is broken during ppc emulation (because that is the ppc that emulate the 68k)

Alain Thellier - Wazp3D

[Toni Wilen]

Originally Posted by thellier

How ? I remember you wrote that "uae to native" interface (68k traps) is broken during ppc emulation (because that is the ppc that emulate the 68k)

Yes but uaegfx can be easily modified to also support alternative "hardware API", because it is mostly hardware emulation only, just poke parameters to some reserved memory, write command id to some address, just like real blitter-like hardware works.

Filesystem and others can't support this method because they don't emulate hardware, they are practically the driver, they also need to see m68k state and control it (which allows them to run in another host thread).

[Toni Wilen]

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

Beta 22:

- CDTV-CR CD unit was initialized even when CDTV-CR emulation was not enabled. Broke CD access on configurations that used CD unit for other purposes.
- Changed directory filesystem max file size limit (when not using 64-bit dos packets) to 4G-1. Old 2G-1 was technically official max size but most native filesystems don't enforce it and support file sizes up to 4G-1 (at least as long as application uses unsigned integers)
- Standard CD image read sector function didn't handle (rarely used) 2336 byte CD sectors correctly.
- Some statefiles have corrupt "extra_cycle" value (probably saved by some buggy beta) that causes long delay when restored, added workaround.
- 68000 CE mode IPL line sampling timing update. Do it during any memory access, not just prefetches.

[Arnie]

Napalm Cue now mounting properly as image. Thanks

[thomas]

Is the PCMCIA IDE option on the harddrives page supposed to work? If yes, how?

I tried with a 2 GB VHD created by Windows Disk Management and formatted with FAT32. Made a boot disk with compactflash.device, fat95 and CF0, but it just hangs and after a long time says "no disk in drive". The same VHD works perfectly on uaehf.device (see CF1 on the supplied ADF).

[Toni Wilen]

Originally Posted by thomas

Is the PCMCIA IDE option on the harddrives page supposed to work? If yes, how?

Yes but more correct question is: does it (=not working) have anything to do with this beta series?

[BlackByte]

My A1200 does not boot config since version 2.9.0.
Ends with a software error.
Last working version 2.8.1

Greeting BlackByte

[Toni Wilen]

Originally Posted by BlackByte

My A1200 does not boot config since version 2.9.0.
Ends with a software error.
Last working version 2.8.1

Logs are missing. No logs = no help. Software failure message information is useless.

(Paths panel -> tick logging option, boot normally until software failure comes, press F12, click "Save all" button, attach file)

[BlackByte]

Sorry ;-)

here

[Toni Wilen]

Originally Posted by BlackByte

here

I can't duplicate it using your config. Log shows some 68030 MMU instructions (which are logged when MMU is not emulated), whatever does that most likely is needed to trigger the problem.

Tests to do:

Boot without startup-sequence. Run C:Setpatch manually. Did anything interesting happen?

Disable all Z3 fast RAM. Still not working?

Disable cycle-exact. Still not working?

(Do you mean 2.8.2b1 is not working or did you mean first 2.9.0 beta was the first one that does not work?)

[BlackByte]

Hi Toni, all version since 2.8.0 do not work.
Deactivated Z3 nearly RAM does not boot
Deactivated cycle-exact does not boot

Edit: sorry all beta version since v2.8.1

[thomas]

Originally Posted by Toni Wilen

Yes but more correct question is: does it (=not working) have anything to do with this beta series?

Yes, 2.8.1 didn't have this option.

[Toni Wilen]

Originally Posted by thomas

Yes, 2.8.1 didn't have this option.

It did, it was named "SC IDE" (due to space limits).

EDIT: I didn't notice your file attachment contains test data.

EDIT2: winuae.zip fixes it. (drive parameters had changed but PCMCIA IDE code was not updated to use new data)

[Toni Wilen]

Originally Posted by BlackByte

Hi Toni, all version since 2.8.0 do not work.
Deactivated Z3 nearly RAM does not boot
Deactivated cycle-exact does not boot

Edit: sorry all beta version since v2.8.1

Try also with standard 2M chip RAM size.

If nothing changes, I think only way to continue debugging is to boot without startup-sequence and run each command manually, one by one until it crashes.

I can't see any obvious changes in 282b1 that could cause this problem.

[lordofchaos]

Just noticed this nasty crash after running Ruff N Tumble (Paradox crack) trying latest Beta (22). It doesn't make it past the initial loading screen anymore.

I`m not sure how far back this error happens with previous versions of WinUAE but this version of the game had always worked on my real A500+.

Exact game version: Ruff 'n' Tumble (1994)(Renegade)(Disk 1 of 2)[cr PDX][t +17 ATX]

The Winuaelog it generated is around 8mb? Is that right? Had to compress due to size.

[Toni Wilen]

Originally Posted by lordofchaos

Just noticed this nasty crash after running Ruff N Tumble (Paradox crack) trying latest Beta (22). It doesn't make it past the initial loading screen anymore.

I`m not sure how far back this error happens with previous versions of WinUAE but this version of the game had always worked on my real A500+.

Exact game version: Ruff 'n' Tumble (1994)(Renegade)(Disk 1 of 2)[cr PDX][t +17 ATX]

The Winuaelog it generated is around 8mb? Is that right? Had to compress due to size.

Works for me. You have HD configured and it is HD controller type that does not exist in real world which invalidates your "works on real A500+" immediately

Log is big because it is filled with repeating messages, it can be manually truncated, only first 100 or so errors can be left.

[lordofchaos]

Originally Posted by Toni Wilen

Works for me. You have HD configured and it is HD controller type that does not exist in real world which invalidates your "works on real A500+" immediately

Log is big because it is filled with repeating messages, it can be manually truncated, only first 100 or so errors can be left.

I see. However, when removing the HD completely the game still fails to load Also tried downloading it again just in case the disk image was corrupt and still fails, yet the same version works just fine on real hardware.

Edit: Slaps forehead! I have the turbo function engaged with floppy speed. The game now loads normally. Sorry my bad