Heeeelp WHDLoad Problems.

[sir_bacharach]

Hi,
 
I have a 4GB CF card with a fresh new install of ClassicWB_ADV installed using my 3.1 WB disks.
 
When I use WINUAE with the same amount of RAM and the same ROMS as my actual Amiga 1200, it runs fine and all the games work.
 
When I put the CF card inside my real Amiga I get this error message when trying to run AGA Games, BASSCD32 and Roadkill are two I've tested.
 
error during 'resload_Loadkick'
invalid kickstart image 'devs:kickstarts/kick40068.a1200'
 
This is my Setup.. A1200 with 4GB CF, Blizzard 030 @50mhz with 128MB Ram, the jumpers are set to enable MAPROM and 60NS RAM.
 
These worked fine on a previous install which was exactly the same as this one a few month back.
 
Recently I've been installing OS3.9 with BoingBags, I said yes to install ROM Updates. I wonder, are the ROM updates just installed onto the CF and then mapped to memory or do they actually write over my physical Amiga ROM?? Could this be the problem??
 
The only other things I've done is set up networks between my Amiga and PC. But when I found out those games weren't working I reverted back to an absolutely clean install of ClassicWB with original 3.1 WB disks, but still I am having these problems.
 
I have made sure not to insert any form of PCMCIA card to eliminate any issues there.
 
But I feel absolutely stuck.
 
The regular non-AGA games seem to work fine, I've only tested a few, but I'm guessing they'll all be fine.
 
The 128MB Fast Ram from my Blizzard shows up in WB and all other functionality seems to be there, so I'm hoping my accelerator isn't broke.
 
I've tried taking the accelerator out, but if you do that there's not enough chip ram to run the version of ClassicWB I've installed.
 
Can anyone help shed any light on what's wrong here?
 
Thanks.
 
Rob.

[amiman99]

You are probably missing kickstart image @ devs:kickstarts/kick40068.a1200
See if is there, I think it should be 2 or 3 files, one of them is the ROM. The other 2 are .PAT, .RTB, so got to System:Devs/Kickstarts and do a view by name to see if all is there.

[sir_bacharach]

You are probably missing kickstart image @ devs:kickstarts/kick40068.a1200
See if is there, I think it should be 2 or 3 files, one of them is the ROM. The other 2 are .PAT, .RTB, so got to System:Devs/Kickstarts and do a view by name to see if all is there.

 
Yeah, they're all there mate, like I say, when I use the Drive in WINUAE the games all work. I'm fearing my Amiga is broke to be honest.

[Leffmann]

It's not a hardware error, it wouldn't manifest itself as a specific software-defined error-message like this.

I'm guessing you've either partitioned the drive wrong, f.ex forgot to set Max Transfer to 128 kB or less, or you've supplied the 3.1 Kickstart image for A4000 instead of A1200.

[amiman99]

You can use SnoopDOS to see what's going on.
Start SnoopDOS, Start your WHDload game, wait for it to give you error, and then check the LOG. It may give you clue in what's wrong.

[sir_bacharach]

You can use SnoopDOS to see what's going on.
Start SnoopDOS, Start your WHDload game, wait for it to give you error, and then check the LOG. It may give you clue in what's wrong.

I don't really know what snoopdos is but I'll look it up and give it a try. I have 3.1 rom on my actual amiga so I must be able to rip it to file and just use that one surely? Forgive my simpleton appearance. I'm still learning.

[sir_bacharach]

It's not a hardware error, it wouldn't manifest itself as a specific software-defined error-message like this.

I'm guessing you've either partitioned the drive wrong, f.ex forgot to set Max Transfer to 128 kB or less, or you've supplied the 3.1 Kickstart image for A4000 instead of A1200.

I think I'm gonna try the drive in my friends amiga. He has exactly same hardware setup as I do. If it doesn't work in his I'll try repartitioning the disk and reinstalling everything again. I'll try snoopdos first before any of this.

[matthey]

Recently I've been installing OS3.9 with BoingBags, I said yes to install ROM Updates. I wonder, are the ROM updates just installed onto the CF and then mapped to memory or do they actually write over my physical Amiga ROM?? Could this be the problem??

ROM (Read Only Memory) can *not* be written.

The AmigaOS 3.9 ROM update is installed to "DEVS:AmigaOS ROM Update". It will not be used if you rename or delete it. It's installed by a new for AmigaOS 3.9 C:SetPatch (version 44.38) which is executed at the beginning of S:Startup-Sequence. It can be skipped. My SetPatch line is "SetPatch NOROMUPDATE QUIET". I disable the MAPROM and use BlizKick to put a custom kickstart in MAPROM.

The only other things I've done is set up networks between my Amiga and PC. But when I found out those games weren't working I reverted back to an absolutely clean install of ClassicWB with original 3.1 WB disks, but still I am having these problems.

WHDLoad may not work with networking enabled (interrupts don't work right) but I don't think that is your problem judging by the error message.

[nicholas]

The AmigaOS 3.9 ROM update is installed to "DEVS:AmigaOS ROM Update". It will not be used if you rename or delete it. It's installed by a new for AmigaOS 3.9 C:SetPatch (version 44.38) which is executed at the beginning of S:Startup-Sequence. It can be skipped. My SetPatch line is "SetPatch NOROMUPDATE QUIET". I disable the MAPROM and use BlizKick to put a custom kickstart in MAPROM.

My next project is to build a custom kickstart containing all the patches I currently load from the startup-sequence into a ROM to flash into my Deneb.

Oh so many projects, so little time!

@Rob,

I've just sent a reply to your email you sent earlier today.

[sir_bacharach]

I think I know what's happened. I copied my original cf drive via winuae into a folder on my desktop. Whenever I copied the roms via winuae they probably worked. Then I deleted the folder on the desktop with my roms in by accident. Then when I restored the files to my desktoo I imagine I lost attributes of the file and the roms are probably now all corrupt. bummer. Maybe that explains why things work in WINUAE??

[sir_bacharach]

Arrrgh. I definately know the problem now. I had a clear out on my pc and thought I had duplicate rom folders so deleted one. I was left with my amiga forever kickstart roms. These are encrypted and will not work on whdload on a real amiga. They're meant for an emulated environment.

Game over...

[nicholas]

Ah that makes sense of what was happening.

You can get unencrypted ROMs from tpb easily enough if you've lost yours.

[sir_bacharach]

It's not a hardware error, it wouldn't manifest itself as a specific software-defined error-message like this.
 
I'm guessing you've either partitioned the drive wrong, f.ex forgot to set Max Transfer to 128 kB or less, or you've supplied the 3.1 Kickstart image for A4000 instead of A1200.

 
I tried everything because I was certain I'd set Max Transfer, but as it turns out, I hadn't pressed enter when I put the figure in so it didn't save the figure and the max transfer remained too high.
 
How did you know this would be the problem? Everything else seemed to be working perfectly. Seems odd. Has something similar happened to you before?
 
I love tinkering with Amigas, barely play any games. It's all trial and error.
 
Glad the accelerator isn't buggered, 200 quids worth, I swear I'd have just sold the rest of it. lol

[Matt_H]

Arrrgh. I definately know the problem now. I had a clear out on my pc and thought I had duplicate rom folders so deleted one. I was left with my amiga forever kickstart roms. These are encrypted and will not work on whdload on a real amiga. They're meant for an emulated environment.

Game over...

If you ever run into this problem, all you need to do is start up an emulated environment using the encrypted ROM and then use a Kickstart grabber from within the emulation. As long as the drawer where you save the grabbed ROM file is accessible by the host system, you'll have yourself an unencrypted ROM.

[sir_bacharach]

If you ever run into this problem, all you need to do is start up an emulated environment using the encrypted ROM and then use a Kickstart grabber from within the emulation. As long as the drawer where you save the grabbed ROM file is accessible by the host system, you'll have yourself an unencrypted ROM.

Yeah, I figured that out eventually, but my A1200 has 3.1 ROMS so I even tried ripping them. They wouldn't work in the real Amiga, only in the PC with WINUAE, but it's OK now, I just needed to partition the CF card again with the limited MAX TRANSFER setting. Copied all the OS and files and games back over again and it was fine.