Rainbow Islands WHDLoad on plain 68000

[Gaula92]

Hello there

Is there a version of this Whdload game that works on a plain 68000 amiga?
It's supposed to work, but I get an error instead:

Address Error ($F00C)
PC = $3EEF2E Resload ($4EE)
Read from $D200444F

Thanks!

[Gaula92]

After more than a year, I'd like to know if there's a Rainbow Islands fixed Whdload install for plain 68000 amigas, since it's not mentioned in the Readme that it should need a 68020.

thanks!

[fitzsteve]

Have you tried tooltypes like 'NOVBRMOVE' ?

[Gaula92]

The VBR moving feature requires at least a 68010 to work. On a 68000 this option has no effect, because the VBR is always at $0 and cannot be moved. (from Whdload docs)

But I tried EVERY tooltype (option) available, even if it had no sense on a plain 68000.

[Predseda]

Which Kickstart?

[Codetapper]

Have you submitted a bug report to Keith on the WHDLoad site?

[Gaula92]

@Predseda: kickstarts 3.1 and 2.05 from Amiga 2000, 500+, etc... I tried a lot of them. The same error is present.

@Codetapper: It was reported years ago, it seems:
http://mantis.whdload.de/view.php?id...9e12ca480e91ca

It's plain 68000 wich causes the problem. Runs fine on my real Amiga 1200 or with anything more than a plain 68000 on FS-UAE.

[Abaddon]

Originally Posted by Codetapper

Have you submitted a bug report to Keith on the WHDLoad site?

I did the JST version years ago, but Mr Larmer and JOTD worked on the WHDLoad version. I suppose I can have a look after I finish the Pegasus update.

[Gaula92]

@Abaddon: I have your JST version here, too. It's great on my Amiga 1200, but it behaves VERY strangely on the Amiga 600 and Minimig:
-Runs perfect without any slowmem
-It hangs on a red screen with slowmem enabled.
-Using nofastmem (and hence disabling slowmem, according to avail) has no effect: same red screen.

So it only runs when slowmem is disabled before I boot
I wouldn't mind using your JST version: I love Whdload (almost best money ever spent on an Amiga program) but I can take some variety. Maybe it's easier to fix your JST version first?

[amigoun]

Similar problem with the Nicky Boom (WHD / JST) on plain 68000..

[Gaula92]

Yes, exactly the same problem

[Wepl]

I need a register dump to check that. Please attach one.

[Gaula92]

I've been trying to generate coredumps for both games, but the COREDUMP parameter doesn't make it work: the games just reset the Amiga anyway (Nicky Boom) or show a dialog on wich I can click a lot of times without any result (Rainbow Islands): the dialog for Rainbow Islands says

Address Error ($F00C)
PC = $3EEF2E Resload ($4EE)
Read from $D200444F

I also tried the SNOOP parameter, but I get a "sorry, snooping requires a 68030 cpu" message, and both games work fine on a 68030.

If you tell me how can I generate core dumps in other way, I will do it.

[BippyM]

Look in C: there are a few files .whdl_dump .whdl_memory and .whdl_register

[Gaula92]

Thanks, Bippym!

Here they are, after running Rainbow Islands.

[Wepl]

probably an interrupt is corrupting the stack
try latest whdload and set option NoResInt

[Gaula92]

I'm getting the same errors with the Whdload version you posted and the NoResInt parameter.

[dJOS]

I found the same issue with 1943 and I have tried a 68010 and plain 68k with no luck (oddly it works fine in WinUAE):

16.9:


17.0:


After discussing it with a few others it was determined that the a1200 was the target machine for many WHDLoad mods.

http://www.amibay.com/showthread.php?t=40024
http://www.amiga.org/forums/showthread.php?t=63951
http://eab.abime.net/showthread.php?t=67542

[Abaddon]

I finished Pegasus, so I will start working on updating the WHDLoad version of Rainbow Islands tomorrow.

@dJOS
I was certainly one of those that didn't test on the 68000 as I didn't have one available especially while working on JST installs. Now I try to test them on WinUAE with a with 68000. That's also the main reason I add the ability to disable the patching of the blitter waits to all my installs as the games usually run too slow on the 68000.

[dJOS]

Hi Abaddon, the weird thing is that 1943 in WinUAE, using the same HW profile as what I have in my 500+, works fine.