IDE68k Problem?

[paul1981]

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).

[paul1981]

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.

[paul1981]

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.

[paul1981]

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.

[paul1981]

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.

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.