Quote:
Originally Posted by jotd
It was possible with Action Replay save state but with whdload / modern amigas it's not.
One of the reasons: no way to save the state of write-only chips without dedicated hardware.
whdload can record them if you have a MMU but that slows down the running game and was never exploited for a savestate.
Plus the fact that expansion/whdload memory would have to be the same at each run (using AllocAbs)
Some attempt was made with JST (and some slaves) but never was generalized. slaves had to be reworked to provide more info (basically info on write-only registers)
|
It makes perfect sense, thanks for chiming in. In fact, my hopes were slim. In some games, because of cheats and startup codes, I am managing to do this (e.g. Flashback) and all is good.
Stuff like Dune II is no problem as it's got a built-in save system and WHDLoad works with it... Lots II has codes so it's OK, once I get one I save it and recall it the next time.. but stuff like Desert Strike or D/Generation are hardcore
