Problem creating my first Whdload install: empty slave

[jotd]

Originally Posted by sir_leon

Just a few questions:
- GenericKick doesn't need to be builded again with every game right? Is it enough to set the CUSTOM parameter?

CUSTOM is just to set the executable. But if there are other things to patch you're stuck (unless you're using a .slave that reads startup sequence). For instance generic kick often applies to cracked DOS games without further protection, but it doesn't even handle assigns (that could be done, but right now you have to add those assigns, for instance check for a very simple slave: Andromeda Mission, that's just been released)

- what is the difference between GenericKick13 and GenericKick13HD? Does the ToolTypes have to be configured in the same way? (I can't get it to read s / startup-sequence)

I don't know those files. There's a _bootdos symbol that allows to NOT read startup sequence. Else everything is controlled by the startup sequence file, which allows assigns, intros... but it's not very "pro" to do that using startup sequence file.


Anyway, if you check any of the slaves released in whdload page, 99% of them have an extra specific fix to remove protection, fix a CPU dependent loop, etc... I'd say generic kick is good to check if the game is a good candidate for a real whdload specific slave... or run PD games without protection that are properly coded so they don't have access faults, CPU dependent loop, wrong blits without blitterwait, 020 incompatibilities, etc. etc.