Trolls AGA +3 UP crashing on real A1200 030

[BarryB]

Does this game only work on 020 CPU?

Everytime I click the mouse to continue from the trainer it crashes. It loads a bit of data first then decrunches but crashes, using an 030 with 32mb RAM.

[s2325]

Try different/without trainer.

[mai]

Originally Posted by BarryB

Does this game only work on 020 CPU?

Everytime I click the mouse to continue from the trainer it crashes. It loads a bit of data first then decrunches but crashes, using an 030 with 32mb RAM.

It seems, that cracktro is not 030 compatible, furthermore the known image is doscopied version, but could still run.

[BarryB]

Aye, just pulled out the 030 and now boots with 020, couldn't be arsed earlier as it was easier to post

So, is there a fixed trained version for 030+?

[mai]

Originally Posted by BarryB

Aye, just pulled out the 030 and now boots with 020, couldn't be arsed earlier as it was easier to post

So, is there a fixed trained version for 030+?

Try this:
Early Startup Control>Boot Options>Disable CPU Caches,
should work then.

Sorry, does not work.

just use the "Flashtro" release!

[BarryB]

Nope, tried that before posting, still crashes.

[BarryB]

Been playing on and off with various releases and found the following:

Trolls (1993)(Flair)(AGA)(Disk 1 of 2)[cr PDX][t +3 UP] - Not working on 030
Trolls (1993)(Flair)(AGA)(Disk 1 of 2)[cr PDX] - Not working on 030
Trolls (1993)(Flair)(AGA)(Disk 1 of 2)[cr PDX][f A4000 Caesar] - Working on 030 but found error on Medialand level, far left of level and up causes screen to slowdown and corrupt!
SPS 996 - Working on 030, Medialand level problem still present, even after using NO CACHE!

Used Disk2 from PDX release and SPS 996 and the error on Medialand is still present with 030, but NOT present with 020!!

So it looks like no version will work 100% on an 030 (and probably higher) CPU.

Anyone able to fix this for 030+?

Also, the slowdow/corruption appears to happen on any level if you get to a certain height up the screen when using an 030 CPU.

[TCD]

What about the WHDLoad version then?

[BarryB]

I don't have whdload, don't think i've ever used it!

[TCD]

Basically these kind of problems are one of the reason why WHDLoad exists I'd at least give it a try (and I'm pretty sure it'll work).

[Sandro]

Originally Posted by BarryB

Aye, just pulled out the 030 and now boots with 020, couldn't be arsed earlier as it was easier to post

So, is there a fixed trained version for 030+?

020 and 030 cpus are the same in fact there aren't programs or games that fail on one cpu but works on the other

in the case of trolls and other buggy prodigy cracks like Aladdin not works because the turboboard or fast ram add timing in chipset

try using degrader http://aminet.net/util/misc/Degrader.lha
try it with nofast ram option,ie you could try other options read docs

[Toni Wilen]

Wrong, this one crashes due to self-modifying code and differences between 020 and 030 (I think this is really rare condition)

68020 and 68030 instruction cache organization is very different:

68020 has 64 cache "slots", each slot is 4 bytes (1 long) = 256 bytes. Each slot can have instruction data stored from any available address.
68030 has 16 cache lines, each line is 16 bytes (4 longs) which is also 256 bytes. Single cacheline can only store 4 consecutive longs, aligned to 16 bytes addresses. (I think this change was made to support burst reads, burst fills complete cache line)

[BarryB]

Originally Posted by TCD

Basically these kind of problems are one of the reason why WHDLoad exists I'd at least give it a try (and I'm pretty sure it'll work).

But not in this case Tried WHDLoad 17.1 unregistrered and have exactly the same problem of slowdown/corruption when jumping to higher parts of a level?

[Sandro]

I was checking this deeply

1-the floppy crash is due 030 as Tony said..the bug can be reproduced on winuae changing CPU on the fly, using a 030 the prodigy cracktro crash but on a 020 it works

2- gfx bugs on medialand area (top left) are not related to 030...seems there is a bug in the original AGA game

3- the AGA version of this game is very buggy,the music plays unsynchronized in the intro and game, there are slow downs, there are gfx bugs on certain zones etc

in this case seems is recommended to play the ECS version instead, is more colorful and have no bugs
having cdrom in the Amiga is recommended to play the CD32 version using a CD32 emulator

[BarryB]

Originally Posted by Sandro

I was checking this deeply

1-the floppy crash is due 030 as Tony said..the bug can be reproduced on winuae changing CPU on the fly, using a 030 the prodigy cracktro crash but on a 020 it works

2- gfx bugs on medialand area (top left) are not related to 030...seems there is a bug in the original AGA game

3- the AGA version of this game is very buggy,the music plays unsynchronized in the intro and game, there are slow downs, there are gfx bugs on certain zones etc

in this case seems is recommended to play the ECS version instead, is more colorful and have no bugs
having cdrom in the Amiga is recommended to play the CD32 version using a CD32 emulator

Cheers, I'll try the ECS version. However, on the AGA version the graphic slowdown/corruption only happened with my 030 and not 020 on the levels I tried?

[StingRay]

Originally Posted by Toni Wilen

Wrong, this one crashes due to self-modifying code and differences between 020 and 030 (I think this is really rare condition)

Cause of the crash isn't self-modifying code, it is a buggy call to _LVOUserState(), intro gets VBR address in d0 -> trashes old StackPointer, calls _LVOUserState() with VBR instead of old stack -> bye bye.

[Toni Wilen]

Originally Posted by StingRay

Cause of the crash isn't self-modifying code, it is a buggy call to _LVOUserState(), intro gets VBR address in d0 -> trashes old StackPointer, calls _LVOUserState() with VBR instead of old stack -> bye bye.

This happens after the cache issue. (Perhaps there is emulation bug but 68030 cache emulation should be 100% exact. Did you test with real 68030 CPU?)

[StingRay]

No, as I don't have any 030 machine anymore. However, I do not see any SMC in the code and if it would be cache/SMC related it should work with disabled cache but it doesn't (see BarryB's post here in this thread). The only other reason for the crash could be the DEFJAM decruncher.

[BarryB]

Also, the FLT ECS version exhibits the same behavior with slowdown/corruption on 030 when jumping up to higher areas of the screen. This even happens, as Stingray suggests, with cache disabled. On the FLT version the play area goes black and the status panel area below just shows random garbage.

So it looks like neither ECS/AGA floppy version is 030 friendly, unless an original untouched ECS version exists to try?

[Retroplay]

Try the images I zoned a while ago, they're padded images from the OCS/ECS WHD version.
You need the manual available at HOL to pass protection screen.