English Amiga Board - View Single Post - Millennium 2.2 doesn't work correctly in WinUAE

Toni Wilen · 29 January 2011, 17:20

Problem found. Not a WinUAE problem. Guess why I usually always demand real A500 test, some ages old emulator does not really mean anything today..

It is buggy crack which only works with ECS Agnus.
If it is loaded on A500 with OCS Agnus, part of code gets overwritten with zeros. (0x70000 to 0x700b0)

Confirmed on my OCS and ECS A500s. ECS=works, OCS=borken.

All cracks except AGA fixed one seem to have same problem.. IPF works fine.

Technical details:

Game uses ETD_READ (Why? Stupid coder.) trackdisk.device command without initializing iotd_Seclabel ("random" data is 0xffff0000) which Agnus see as 0x70000 (OCS) or 0xf0000 (ECS, 0.5M chip = write goes nowhere, 1M chip overwrites unused part of chip ram).

KS1.x loader uses blitter to copy sector labels.

EDIT: Where is working OCS crack hiding? Game was released in 1989, before ECS..

29 January 2011, 17:20	#4
Toni Wilen WinUAE developer Join Date: Aug 2001 Location: Hämeenlinna/Finland Age: 49 Posts: 26,518	Problem found. Not a WinUAE problem. Guess why I usually always demand real A500 test, some ages old emulator does not really mean anything today.. It is buggy crack which only works with ECS Agnus. If it is loaded on A500 with OCS Agnus, part of code gets overwritten with zeros. (0x70000 to 0x700b0) Confirmed on my OCS and ECS A500s. ECS=works, OCS=borken. All cracks except AGA fixed one seem to have same problem.. IPF works fine. Technical details: Game uses ETD_READ (Why? Stupid coder.) trackdisk.device command without initializing iotd_Seclabel ("random" data is 0xffff0000) which Agnus see as 0x70000 (OCS) or 0xf0000 (ECS, 0.5M chip = write goes nowhere, 1M chip overwrites unused part of chip ram). KS1.x loader uses blitter to copy sector labels. EDIT: Where is working OCS crack hiding? Game was released in 1989, before ECS.. Last edited by Toni Wilen; 29 January 2011 at 17:57.