Path: utzoo!attcan!uunet!cbmvax!bagate!dsinc!unix.cis.pitt.edu!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!uwm.edu!rpi!julius.cs.uiuc.edu!psuvax1!psuvm!blekul11!ghgaeeh
From: GHGAEEH@cc1.kuleuven.ac.be
Newsgroups: comp.sys.amiga.programmer
Subject: Resident Tags again |
Message-ID: <91032.100737GHGAEEH@cc1.kuleuven.ac.be>
Date: 1 Feb 91 10:06:37 GMT
Organization: K.U.Leuven - Academic Computing Center
Lines: 21


     Dear readers,

     This time I did the way I was told to : I didn't put in a
(Kick)Memory-node, but instead I allocated the memory myself (in the
installation program with a normal AllocMem and in the reset-routine with an
AllocAbs).  The KickTag is put into Fast Memory with a pointer to a reset
routine, which is also located in fast.  Then I reset the Amiga and what do I
see ... Well, there is some improvement ... The version with the MemNode
didn't seem to get out of some loop, the new one only stays in for about half
a minute.  The what's wrong ?  Well, there's noone calling my reset-routine.
Exec seems to have forgotten all about my KickTag, although the KickTag
pointer and checksum are still valid after the reset.
     I also tried the other methode : CoolCapture ... but this one too |  Does
the Amiga have something against FastExpansion Memory or is there a simple
explanation for all of this ?  I hope you can tell me ...

                                             Thanks for your reading this,
                                             and for supplying the solution.

                                             Kurt Haenen