blubaugh@ucqais.uc.edu (Dwight Blubaugh) (08/25/89)
I couldn't get the recent posting of Noclick3.3 or 3.4 to work on my Hurricane
68020 machines. By using Metascope on my 2500 I could look at the stack
information that Noclick modifies within the trackdisk.device. When running
in 68000 mode Noclick would change a location with the value 0x00feaaf6. On
a 68020 machine this value is located 4 bytes further on the stack. I have
FileZapped all references of 0x46 to 0x4a and Noclick now works great on my
68020 machines. What I really wanted, and would have helped a lot, was some
reference to the 68020 vs 68000 stack. My Motorola books tell me all sorts of
things about Stack frames but I needed to know what Exec does in a case of
task switches. Has anybody worked this out in a clean readable example? The
Exec dissassembler from Markus Wandel helps some but leaves the 68020 stuff
uncommented. What I suspect is that the extra 4 bytes offset is from the
68020 saving the Vector offset on the stack which the 68000 doesn't.
Does anybody have information on this?
--
technical advisor of Ohio Valley Amiga Users Group
(Cincinnati Ohio P.O. Box 428539)
UUCP: {decuac,mit-eddie,phri,pyramid}!uccba!ucqais!blubaugh
USMAIL: Dept of Chemistry ML172, University of Cincinnati, Cincinnati OH 45221