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.

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

WHDLoad 17/17.1 seemed to make a bunch of my games fail, so it's worth keeping the 16.9 version in your C: so that you can alternate between the two versions to see if it fixes some of your problems.

Regarding the saving issue, do you have NOWRITECACHE enabled in your S:WHDLoad.prefs?
Basically, unless you have a 68010 or above CPU then you can't quit the majority of games, and therefore your saved games will not save correctly, as WHDLoad will not get the chance to write the remaining data in the write cache to the save file(s) which happens when you press the Quit key (usually F10, Del, or PrtSc). Enabling NOWRITECACHE will fix this, it will save your game there and then in totality (screen will flicker to black a few times whilst it saves, and the saves take a little longer).

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.

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.

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.

Everyone should have the NOAUTOVEC option enabled. I don't think an error related to that would show under WinUAE.

Also, if you're still stuck, try the NOMEMREVERSE option. I need this option on my A600 with 2MB PCMCIA fast memory. This option is (rarely) needed by some Fast Ram expansions... it doesn't hurt enabling it anyway.

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

You're welcome. I'll try the game 1943 on my A600 later on and I'll let you know if I have any problems with it.

It is unfortunate, but many of the WHDLoad games were worked out and tested on machines that were not like the ones they are being run on (yours, mine and others).  If you really want it to work, you may have to code the game yourself on your setup.