Extremely weird kickstart file issue
 

Hey guys

I have installed classicwb35, all fine except, when I try to load, for example, Banshee (AGA v), this requires the kick.40068.a1200 file, which I have, but it says it's invalid.... the weird thing is, if I boot from my CF card in UAE, Banshee works fine...

Would this suggest a memory issue on my Blizzard card?

Anyone else experienced anything like this?

I really can't get my head around how it doesn't work in the real Amiga, but it does in UAE :help

Chers for help

when you say you have kick.40068.a1200 file,do you mean you have the file in devs/kickstarts or you have kick 3.1 as roms.

sorry;

I have the kick.40068.a1200 file in Devs/Kickstarts and I have 3.1 roms.

This isn't my first setup, I did it exactly the same way as my last one, which was fine with every game i threw at it, I just decided to upgrade to os 3.5.

that is strange,i assume your using whdload to play the game.

yup!

Just had a thought, the time & date in my UAE is correct, but on my Amiga.the year is 1978 :).. would this cause any file issues?

nope,the time and date dont affect anything.

ile go and check that game on mine and see what happens.


EDIT:-just tried it on mine it works fine.


whats your setup?

Hey

Just been doing some testing myself, I have another CF card with os 3.0 classicwb full on it and it all works fine there....

Maybe I should try a format and start from scratch with os 3.5...

My Miggy is:

A1200, Blizzard mkIII @ 40mhz, 16M FRAM, no CDROM, 1gigCF card

EDIT

Found the issue!!!

When I partitioned my drive at the very beginning, I didnt name the first partition DH0...
I didn't know it was an issue as the classicwb os35 installation differs from 3.0/1 installs...
That also explains why it worked in UAE and not real Amiga, UAE named device as DH0...

Time to crack open the Cors Light! ;) - Thanks for help Roy

Thats very wierd, that should'nt effect it unless you have assigns to DH0:

Haven't checked... My Assign startup is standard, haven't touched it, but as soon as I booted to wb3.0, renamed the partition in HDToolBox and rebooted back to os35, it worked fine.