Quote:
Originally Posted by StingRay
Sounds like the slave author was very lazy if he uses different slaves for different memory configurations.  |
It's a limitation of WHDLoad, not the slave author. The problem is that the memory requirements are hardcoded into the slave header.
WHDLoad will abort if it can't allocate the memory requested in the slave header, so, for example, if the game is playable on 0.5Mb chip but has extra features for 1Mb chip you need two slaves with these memory configurations coded into their headers. If you do just the 0.5Mb chip slave, 1Mb owners miss out on the extra features. If you do just the 1Mb chip slave, 0.5Mb owners can't run the game.
I had words with Wepl about this many years ago
