GHGAEEH@cc1.kuleuven.ac.be (02/01/91)
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 HaenenDXB132@psuvm.psu.edu (02/02/91)
In article <91032.100737GHGAEEH@cc1.kuleuven.ac.be>, <GHGAEEH@cc1.kuleuven.ac.be> says: >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. Exec will not use KickTagPtr if ANY of the AllocAbs's made using KickMemPtr failed. This might be the problem... > 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 ... Again, CoolCapture is called before the very important InitCode call that gets things running, including (in expansion library) configuring plug-in boards and AddMemLIst-ing their memory. If you want to use this approach, try using WarmCapture. Take a look at Markus Wandel's Exec disassembly for more detail. -- Dan Babcock