THE WIZARDS INC. present a magic tool called

                           Guru Information 2.0

                         written by THE DARK LORD

Oh boy, yet another lame guru number catcher ? No man, there's more to it than
meets the eye !!! Why bother reading this ? Well, all other guru information
tools (at least those I know) have three problems :

	a) you need to write down yourself which guru number occured
	b) you (almost) cannot get a register dump, which could be VERY
	   usefull if you are still in a testing phase
    and c) they don't feature kickstart 2.0 alerts..

	Well, this one handles it all !!! So, if you come across an
exception, simply invoke GInfo by its filename and read the information
provided. Besides only alert code/object information, you will also get a
register dump which represents the processor state at the task crash time.
However, this information will only be valid if you came across a DEAD_END
Alert, so just don't care about this if you've got a RECOVERY type..(maybe
I'll include a hide option for this registers at recovery alerts some day)

You can specify some options along :

	-v ....... This is rather neat, because you can include GInfo in
		   your startup.sequence with this option, and GInfo will
		   only pop up some message if some exception really
		   occured. 

	-c ....... will clear the LAST_GURU_NUMBER, so if you have
		   specified option valid, this will be the last time
		   for the information to show up.

	-a(cause)  specify a certain guru number to examine...
		   please note that following the 'a' you can enter any
		   valid hexnumber (up to 8 digits, no formating needs to
		   be done, even negative numbers are recognized...)

	-t ....... show task information. This one really will do any sense
	           if had a recoverable exception so that the task is still
	           somewhat valid in memory. There is no checking done if
	           the task information makes sense (who could one?!) so
	           this option won't be used by too many people very often.

Note: GInfo recognizes Kick2.0 alerts, too, but of course you can use both
Kickstart 1.3 and 2.0 (on A500,1000,2000,2500,3000) without problems. Ok,
so much for this, I think you should like using this, because it IS better
than the rest.

Assembly notes : 

If you've made changes to the sourcecode, assemble it using the provided
makefile, which reads somewhat like this :

macro68 ginfo.asm -E ginfo.error -O ginfo.o -C DTGL
blink from ginfo.o defaults.o to ginfo SMALLCODE SMALLDATA NODEBUG

If some lamer shitheads out there wonder why I use M68 instead of those nice
hacker absolute assemblers like 'MasterSeka' and 'AsmOne' : Macro68 is the 
f**king BEST Assembler on the Amiga, because 

	- it has 68000,68010,68020,68030 and even 68040 opcodes (!!!!!!!!!!!)
	- it has the new motorola syntax (see the source !!)
	- it is very fast (assembly time on A3000 : 2.2 seconds with images !!)
	- and you cannot code absolute shit wiv it !!!!!

OK, that's it for today...

*** Important Message : After a break of more than one year, THE DARK LORD
			will return in power next month, JUNE 1991 with the
			DARK SLIDESHOW Number 11 !!!!!!!!!!!!!!!!!!!!!!!!!!

			Watch out, because it's gonna be a real EYE-POPPER
			again, and it'll feature a real SUPERB animation!!!!!