WinUAE 4.2.0 beta series

[enigma776]

Originally Posted by Toni Wilen

Blizzard 1260 does not have built-in SCSI controller. You need to add SCSI Kit.
(and obviously this is not beta related and older versions have exact same behavior)

Huh, never had to before which is why it probably threw me. Sorry.

[Toni Wilen]

Originally Posted by enigma776

Huh, never had to before which is why it probably threw me. Sorry.

Blizzard 1260 has always required separate SCSI Kit (like in real world)
Perhaps you previously tried 2060 (has built-in SCSI), not 1260 (needs SCSI Kit)?

[enigma776]

Originally Posted by Toni Wilen

Blizzard 1260 has always required separate SCSI Kit (like in real world)
Perhaps you previously tried 2060 (has built-in SCSI), not 1260 (needs SCSI Kit)?

Oh! That might actually be it and not the first time my head got the 1260 and the 2060 confused. Once again I apologise.

[Toni Wilen]

http://www.winuae.net/files/b/winuae_4200b8.7z
http://www.winuae.net/files/b/winuae64_4200b8.7z

Beta 8: (Possibly final)

- Added A2090a ROM driver workaround, in one error condition situation it forgets to set correct DMAC mode before reading DMA status. So apparently DMA error bit can be also read when last mode was start DMA (or perhaps it is always valid). Fixes A2090a + tape drive hang.
- Not all autoconfig boards configured fully when used with A2620/A2630. (Which has differently behaving autoconfig driver compared to KS ROM in its boot rom)
- Sprite to bitplane and bitplane to bitplane collisions didn't work correctly if subpixel mode was enabled.

[James]

Originally Posted by Toni Wilen

(did it really work with correct size and colors?)

I think so, but a lot of scenes didn't display at all. Was not sure if that was due to slowness....

Originally Posted by Toni Wilen

Beta 7:

- ELF executable ROM loader crash fix.
- Borderblank + horizontally bitplane ending before display window end: part of right border was drawn using wrong color (borderblank color vs color 0).
- uaegfx and Picasso IV 8-bit palette overlay mode was not implemented. Fixes XIII/Oxyron PIP mode.
- Fixed uaegfx overlay corruption if allocated overlay bitmap width was not divisible by pixel byte size. (PiP_View + image with "unaligned" width)
- Disassemmbling 68020+ full format extension type (an,dn,xxxx.w/.l) didn't print an part.

Thanks!
XIII running really well now. Along with lots of rtgmaster PiP software (Genetic Species, Nightlong and many more), and several other demos.

[AMIGASYSTEM]

Originally Posted by James

XIII running really well now. Along with lots of rtgmaster PiP software (Genetic Species, Nightlong and many more), and several other demos.

Excuse me James om WinUAE how do you activate PiPs with Genetic Species in the window?

[James]

Originally Posted by AMIGASYSTEM

Excuse me James om WinUAE how do you activate PiPs with Genetic Species in the window?

Make sure you have rtgPIP.library in libs/rtg.
Delete GeneticS/GeneticSpecies/RtgScreenMode.prefs.
The screenmode selector that appears when you launch the game should offer you a range of PiP screenmodes - select 640x480 8bit or 320x256 8bit e.t.c. (24bit doesn't work correctly).

[Rotareneg]

In the Host/Miscellaneous menu, the State Files selector box accepts typed text, but strangely reverses everything typed so that typing "Shadow of the Beast" results in "tsaeB eht fo wodahS".

[meeku]

Hi,

Wanted to test the beta file, but my AV reports:
winuae64_4200b8.7z

Trojan:Script/Foretype.A!ml

[Toni Wilen]

Originally Posted by meeku

Hi,

Wanted to test the beta file, but my AV reports:
winuae64_4200b8.7z

Trojan:Script/Foretype.A!ml

False positive. Some AV always reports something weird at least once / beta series.