StoneCracker 3.11 (Tool/Exec/Data Cruncher) by Stoneware

StoneCracker v3.11b



Not enough memory for File Buffer!

File deleted.

Deleting File.

Deleting failed!

File succesfully saved.

Window opening failed!

File Buffer is now empty.

File Buffer is empty! Can't save!

File seems to be Relocatible.

File is a normal Data File.

File Buffer allocated.

Loading File into File Buffer.

User break.

Not a relocatible file. Auto break.

System Killer decruncher enabled!

Normal decruncher enabled.

Relocation succe

			WelCome to StoneCracker v3.11b


 ·The history of ultrafast StoneCracker series·
 v3.10 - first finished and released version. Worked ok and it didn't seem
 to have any bugs. Later I found that reading empty directories caused an
 error message.

 v3.11 - empty directory error fixed. No more error messages for nothing.
 Nobody informed me of bugs but more and more appeared in my own test. Some of
 them were really disturbing. The relocation routine sucked a lot. Task Held
 request was quite common when you tried to relocate program with inproper or
 not supported hunk structure. Automatic file deleting after failed saving
 didn't work. Also decruncher could have been optimized few clock cycles
 faster per bit shift.

 v3.11b - Relocation routine fixed. No more Task Helds. Also automatic remover
 for hunk_debug and hunk_symbol were removed. Now them both cause 'hunk type
 not supported' error message. Automatic file delete fixed and should work
 fine now. Decruncher optimized in both size and speed. 'Set task priority'
 disabled b'cos I thought it's just a joke. And finally few important notes
 considering this cruncher were included and colors changed.

 ·How to use this cruncher·
 Read the documentation file for StoneCracker v3.10.

 ·If you face unexpected effects or bugs?·
 Then please write me and tell what happened. If your program didn't work the
 problem is probably between your monitor and chair.

 ·Last words - last hope·
 A legal version which supports relocatible programs as OS wants them to be is
 on its way. It's just a matter of time when it's finished. Here are some
 details considering it: fast decruncher and relocator, length of code is as
 short as possible (used a lot of time for that) and the memory won't be
 freqmented after decrunching. Maybe multiple files select and command/data
 file switch.


				My address - for bug reports etc.

				Jouni Korhonen
				Hiihtomajantie
				11120 Riihimaki
				FINLAND





 MOVEQ	#0,d0		;succesful exit
 RTS