IDE68k Problem?

[djos]

Hoping someone can help - I have an a500+ with Mika's IDE68k interface with a CF-Adapter & Kippers 8MB Fast Ram and I've been having major issues with WHDLoad games on it. Im pretty certain that it's a "disk" issue because running my CF cards under WinUAE everything is perfect.

So Background - I have 2x 4GB CF cards that I can replicate the issue with, one Kingston from AmigaKit running FFS and one SanDisk Ultra 4GB running PFS3. Both are partitioned using the "default" twin 1.9GB partitions HDToolBox gives you and I've tried both 0x1FE00 and 0xFE00 as the mask with no noticable difference.

Now for the problem - aprox 60% of WHDLoad games crash out fairly early or exhibit odd disk "issues" like save games vanishing etc. One easily replicable crash is with 1943 - it bails just after you hit F1 for a single player games with this error:



But if I run the CF Cards from WinUAE there's no issue at all and I can play the game. Im also fairly confident my HW is good as I've run detailed MemTest scans on my 500+ and all is well. I've also managed to play many of the games (haven't tried them all) that crash from Floppy Disk with no problems.

Any Idea's?

PS, I have now updated to WHDLoad 17.1 and the issue remains.

[djos]

Hmmm, I have a couple of things to try now, cheers.

[djos]

DOH! WHDLoad games still crash when run from ram disk.  

Looks like maybe it is a ram issue after all.

[djos]

Thanks Paul, I'll try your suggestions.

[djos]

Ok I tried v16.9 and the NOWRITECACHE option (on both 17.1 & 16.9) and got the same issues - v16.9 did give me a different error tho:



Swapping Kippers 8MB ram board out for Toms 8MB Board is next on my list of things to try.

[djos]

Arrrrgh, now Im really confused - I removed Kippers 8mb board and Installed Toms 8mb board and got exactly the same results.

So now im gonna make a vanilla CF Card with just WB3.1 (no ClassicWB) and WHDLoad and see what happens then.

[djos]

In your S:WHDLoad.prefs, I also recommend enabling the option NOAUTOVEC.
Without that option, some games won't even start. Give it a try.

That would make sense if say 1943 wouldnt start under any circumstances but when I put my CF card in my PC 1943 plays perfectly under WinUAE.

I even built a vanilla WB3.1 CF card with FFS tonight and 1943 produced the exact same crash as before.

[djos]

Cheers, i'll try those tomorrow - im off to bed (11pm here).

[djos]

Well, I've tried it and I get the exact same error! :laugh1:
 Seems as though this could well be a slave error.  The slave was written in August 2006, so it maybe works with a WHDLoad version from 2006.
I don't suppose this is a game that many people are interested in, and so this error has slipped through the net.
There's a lot of slaves for OCS/ECS games that are written to require a 68020 CPU & KS3 which is crazy, as all OCS/ECS games ever required was 68000.
One such example is Bubble & Squeak for the A500. I did my bit there and submitted a bug report last year via the Mantis Bug Tracker. It was one of my favourite games and I saw no valid reason why I shouldn't be able to play it on my A600. As of yet nothing has been done about it though, and I'm not holding my breath.
My advise... use an A1200 for WHDLoad, as that appears to be the target machine when it comes to slave testing and development.

Well that's a relief, I thought I was going stir crazy!!!

Thanks for your help Paul.