Your game may be able to work with some degraders like jst but it's not granted (jst execute command with nocaches option for instance) There are also launch scripts (like slamtilt) that mount a virtual drive in memory and boot from it but the limitation of this is that your virtual drive must include, as the boot volume, all the system files needed by the game (c commands, libs, devices.) and in most cases it may consume way too much memory for your game to run.¸ (some assigns may be needed for your game and then the exec command.) Your startup-cruise would be something like that You can find tude on aminet and it's the only really reliable reset tool i found (though i also use it as a degrader). The way i go around it is that i design a script for this kind of games which renames startup-sequence as startup-temp and renames a pre-defined startup-cruise for instance, as startup-sequence.then wait 2 to 3 seconds to clear disk caches.and then reboot.typically : It's due to the first line of your workbench S:startup-sequence, ie "setpatch quiet" which enables AGA modes. My intention is to be able to install these games in ClassicWB. My question is.is there any way or program to avoid this incompatibility?
I have some adf games that work in A1200 like Cruise for a Corpse or Mig-29M SuperFulcrum but they doesn't work loading from WB3.0 or ClassicWB!,as they don't work in adf from WB either they work installed from WB.
0 kommentar(er)
