STONE CRACKER v2.99d - We Fixed It


 Thank you for your interest to Stone Cracker crunchers. Firts of all I hope
 you remembered to copy the cruncher itself and the docfile. Please try to
 spread them together.

 Stone Cracker is a Public Domain program mainly for demomaker etc. users
 purposes. It is quite common within these users to program into absolute
 memory locations which surely has some advantages. Because I'm a part of
 that user group I developed an 'absolute address - non system - demo cruncher'.

 Because there are several different Stone Cracker versions around I think it's
 better make a list of them (all versions aren't listed) and explain each one a
 bit.

	·v2.69 - Somebody got this one?
	·v2.70 - The first real Stone Cracker version. It had all the needed
		 features and worked just fine.
	·v2.71 - Some little improvement.
	·v2.80 - Similar to v2.71. Only few improvements. Never spread!
	·v2.81 - Quite similar to v2.71 & v2.80. Few improvement done to
		 user interface and especially to decruncher. Not spread
		 that much.
	·v2.90 - A test version and never released.
	·v2.91 - A test version too and never released.
	·v2.92 - Totally different when compared to earlier versions. Even
		 the crunching algorithm was changed. Because of reprogramming
		 the whole cruncher it had several bugs and couldn't handle all
		 kinds of data (areas longer that 64Kb of crunchable data
		 bugged).
	·v2.99 - Better version of v2.92. New features were added like hunk
		 relocator and no any limits to the data to be crunched. But
		 anyway there were few very odd(??) bugs around. Never spread!
	·v2.99b- The official v2.99 release. Worked just fine and some little
		 improvements. But I wasn't satisfied with it because after
		 a while I noticed that not everybody codes like I do. Others
		 could face some unexplained things like the cruncher freezed
		 itself at the end of crunching process for a couple of minutes
		 but then continued like nothing had happened.
	·v2.99c- A better version of v2.99b. Those nasty little thing were
		 removed and few bigger improvements were done. The megacrunch -
		 option was removed and low memory address - option was added
		 to quarantee 100% workablity for the programs. Not spreaded
		 very much.
	·v2.99d- Some minor improvements. Speedup buffer (???) removed and code
		 optimized a bit. New default value for Max equal lenght.
  ** ELF-CO edited the following **
 ·v3.00- More of a gfx fix really.  Some more minor improvements, like
   the on-line docs (help files, activated with *h at anytime)
   I am not too sure about all the improvements Jouni put in, as he
   hasn't sent me the updated docs for it.  I can tell you that I spent
   four hours with it on my system (9 megs ram/14mhz) and it worked just
   fine on every file.  When I get more info, I shall post it for you.

 When you run this cruncher it doesn't matter whether you run it from Cli or
 WorkBench. A window will appear into the screen and some credits are shown.
 Note that you can exit the cruncher any time by typing '*' into any question.
 Both mousebuttons will abort crunching.

	·Buffer size: #		- Work area for the cruncher. You program
				  should fit into this memory area. Note! You
				  give the size in kilobytes (decimal).

	·File to load:		- Nothing to explain...

 If your program looks like a relocatible program (cruncher finds the hunk area)
 next question will appear.

	·Fix address: $		- Now you can fix your relocatible program into
				  any address you want. If there are such hunks
				  that this relocator can't handle an error will
				  occur. Note! You can skip the relocation by
				  pressing the enter.

 If your program looks like a raw data next question is this.

	·Efficiency (0-5)	- This is the lenght of the area where the
				  cruncher searches for equalities. The longer
				  the area is the better the result is but at
				  the same time the crunching time gets longer.

	·Max equal lenght: #	- This option is just for shorting the crunching
				  time. If you define Max equal lenght to #2000
				  bytes always when the cruncher finds a crunch-
				  able area that is #2000 bytes or more it will
				  crunch it immediately and DON'T start
				  searching for a better case. This is very use-
				  ful if your program includes long empty areas!

	·crunch crunch... zz zz  zzzz z     z   zzz

	·Save exec. or data:	- You can save the crunched data whether with
				  the decruncher header or not. If you choose
				  data next question will be: File to save.

	·Decruncher type:	- There are two different decruncher for the
				  program: normal and system killer. If you
				  choose normal next question will be:
				  Decruncher location.

 These questions are for the system killer only!

	·Supervisor Stack (SSP)	- You must relocate the stacks. Note!! NEVER
				  put it inside your programs area!!

	·User Stack (USP)	- You must relocate this stack too. Note!! NEVER
				  put it inside your programs area!!

	·Status Register (SR)	- You can define the whole Status Register like
				  supervisor bit, interrupt priorities & flags.

	·Int Ena ($dff09a): $	- You can define which interrupt is on etc.

	·Dma Con ($dff096): $	- Same as below but for Dma channels.

	·Adk Con ($dff09e): $	- Again the same...

 H