🚀 go-pugleaf

In article <1993Jan11.104407.29772@email.tuwien.ac.at> nino@vmars.tuwien.ac.at (Marinos Yannikos) writes:
>Then again, most games don't use self-modifying code (ok, perhaps some of
>the games from former demo-coders),

Copy protection is the big sinner here.

> the stack frame isn't particularly
>interesting for games either (Can't think of any serious reason, this
>should only give vector-bending software a hard time),

If you change return address in an interrupt you get problems (basically
doing a sort of multitasking; switching from one part of the code to
another. I think I have heard SWIV being an example of this).

> and the timing
>won't be so much of a problem either, because 1. most games run in the
>VBL (so the speed depends on the display frequency), 2. those which don't
>won't run THAT much faster, since the Falcon is only 4-5 times faster
>than the ST in the ST modes... :)

Here I was talking about custom loaders that do something like:
	move.w	#3000,d0
wait	dbra	d0,wait

when they wait for the floppy to go from track to track or something else
that needs a delay.

>Well... Actually I don't think the old games are so important - except
>a few good ones (Dungeon Master ...) there isn't anything that will
>look or feel particularly good after you've seen some real Falcon games...

If we can throw away the oldest games then the compatability percent jumps up.
-- 
|/// borgen@stud.cs.uit.no (Boerge Noest) | Amiga B2000			 \\\|
|//  Box 218, 9001 Tromsoe, Norway	  | Remember to :-) when needed	  \\|
|/   The worlds northernmost university	  | Life is worth living.	   \|
#Disclaimer: This university and me does not agree.