|
Cranker by The Electronic Knights
[nfo]
|
||||||||
|---|---|---|---|---|---|---|---|---|
|
|
|||||||
|
popularity : 63% |
|||||||
alltime top: #4241 |
|
|||||||
|
||||||||
added on the 2016-08-30 13:32:32 by elkmoose  |
||||||||
popularity helper
comments
Titanics replacement is a nice idea but it should give at least a warning when then crunched binary is larger than the original uncrunched one as it just happened when I did a quick test. More than 1k for the decruncher is also quite a lot.
Another problem: if output file is the same as the input file nothing will be saved and there is no error message either. Output looks like everything was done fine while in fact no crunched file was saved at all.
just what i always wanted!! if it works as expected, you save me a ton of time, as i was planning something like that for a while (titanics is really obsolete and slow even on A4000).
anyway, how about exe for mac os? there are quite a few of us developing using that devil's os. ;)
i can help with the compile if needed.
anyway, how about exe for mac os? there are quite a few of us developing using that devil's os. ;)
i can help with the compile if needed.
I too always wished someone would do one like this. Need to give it a try soon.
Great initiative to make a fast and better packing Titanics cruncher replacement! :-D
As for the comparison in the README, it seems you are a bit out of touch concerning memory overhead. Shrinkler has had a low-overhead feature (the overlap option) for more than one and a half years by now. Using that, the memory overhead of Retro Dentro is 528 bytes - less than half that of Cranker. And it runs fine on 512+512. Shrinkler doesn't deallocate that memory, though, so if the demo needs to allocate absolutely all of the rest of memory after loading, Cranker wins.
Shrinkler-compressed executables also works fine with LoadSeg, provided A3 is set up to point to the loaded segment list, as all OS execution functions do. OK, I admit this is sort of obscure, and you have to read the official Shrinkler forum (or the code) to figure it out. Better documentation is needed on my part. In the end, those 4 bytes saved were probably not worth the hassle. :)
Finally, no Titanics cruncher replacement can be complete without the ability to print a "Decrunching while loading" text, but since this is version 0.1, I'll let you pass on that one for now. ;)
As for the comparison in the README, it seems you are a bit out of touch concerning memory overhead. Shrinkler has had a low-overhead feature (the overlap option) for more than one and a half years by now. Using that, the memory overhead of Retro Dentro is 528 bytes - less than half that of Cranker. And it runs fine on 512+512. Shrinkler doesn't deallocate that memory, though, so if the demo needs to allocate absolutely all of the rest of memory after loading, Cranker wins.
Shrinkler-compressed executables also works fine with LoadSeg, provided A3 is set up to point to the loaded segment list, as all OS execution functions do. OK, I admit this is sort of obscure, and you have to read the official Shrinkler forum (or the code) to figure it out. Better documentation is needed on my part. In the end, those 4 bytes saved were probably not worth the hassle. :)
Finally, no Titanics cruncher replacement can be complete without the ability to print a "Decrunching while loading" text, but since this is version 0.1, I'll let you pass on that one for now. ;)
Amazing tool! Please, add the (configurable) loading-and-decrunching text and the warnings that Stingray pointed and this will be perfect!
This is great tool for classic OCS stuff!
This is great tool for classic OCS stuff!
@Blueberry: Sorry for putting down and kudos for Shrinkler. I will correct the docs. I didn't read yours as it seems. One reason for Cranker was that a particular Zymosis prod didn't work here: http://www.pouet.net/prod.php?which=67945
I think there's a chance now this can be corrected by supplying a3 in the launcher and enabling the LoadSeg() option in the packmenu config.
@bonefish: OS X version: No problem, it's all ANSI C. Will get back to you, or contact me directly.
@StingRay: Thanks, will be corrected.
Timeframe for fixes and suggestions is next week at the earliest.
I think there's a chance now this can be corrected by supplying a3 in the launcher and enabling the LoadSeg() option in the packmenu config.
@bonefish: OS X version: No problem, it's all ANSI C. Will get back to you, or contact me directly.
@StingRay: Thanks, will be corrected.
Timeframe for fixes and suggestions is next week at the earliest.
tool thumbs
another tool thumb!
noble quest
Quote:
@Blueberry: Sorry for putting down
Not at all. You saw a problem and you did something about it. That's cool.
Haven't tried it yet, but more options for crunching A500-releases are always welcome :)
The new OCS dedicated tool, long awaited Titanics replacement? Is he The One? Or a fair competition for the mighty Shrinkler? All sounds Gr8! Thanks for releasing it, already looking forward to all the updates of it! OCS stuff r0x!!!
No message displaying while loading and decrunching? No thumb until then ;)
Most issues have been worked on, and the scope has been extended.
http://neoscientists.org/~bifat/binarydistillery/cranker-0.2.lha
Changes:
Added options for displaying text and to avoid poking to the bgcolor register. Incompressible hunks are being stored now. The source of the
decrunch header is now included and a custom header can be specified in the command line. This way you can use Cranker as a loader system, disable crunching in the commandline and just exploit async I/O to e.g. show an effect while loading.
Ofcoz, none of these nightshift results have been tested yet. :-)
http://neoscientists.org/~bifat/binarydistillery/cranker-0.2.lha
Changes:
Added options for displaying text and to avoid poking to the bgcolor register. Incompressible hunks are being stored now. The source of the
decrunch header is now included and a custom header can be specified in the command line. This way you can use Cranker as a loader system, disable crunching in the commandline and just exploit async I/O to e.g. show an effect while loading.
Ofcoz, none of these nightshift results have been tested yet. :-)
Nice update! :) Except for the warning when the crunched file is larger than the original file all the issues I found are fixed. Also, hooray for the TEXT option, excellent! :)
Complains about no FPU with FS-UAE emulating an 040 and no macOS binary. I'll thumb up when I manage to run it :)
yeeeeees, we want/need macOS binary!!!! :))
compile offer still stands.
compile offer still stands.
@Bonefish: Ok, here you go
Code:
$ hg clone http://home.sm41.de/.cranker-dev@bitfat: amazing! just seen it, otherwise it would be sooner. let me know if you have a mac and need a makefile_osx.
@others, here you go:
https://dl.dropboxusercontent.com/u/21386780/cranker/cranker_osx_v0.2.zip
(32 + 64 bit exe, OS X 10.5 or later)
i've quickly tried it and it works, but feel free to let me know if there is any problems with OSX version.
@others, here you go:
https://dl.dropboxusercontent.com/u/21386780/cranker/cranker_osx_v0.2.zip
(32 + 64 bit exe, OS X 10.5 or later)
i've quickly tried it and it works, but feel free to let me know if there is any problems with OSX version.
It would be wise to rename the prod in this page to simply "Cranker" (without version number) and update the download link to some URL that always contains the last version.
what ham said!
I have renamed the prod, as for the the download links, that's up to Bifat. :)
Ok, the download link now points to the current version 0.3.
Changes: Raw data decruncher included, one of the fastest decrunchers for 68000. Minor bugfix in decrunch header. Added Amiga-style commandline parsing, new options CDATA, DDATA, MAXOVH, MERGE. Removed former hardcoded limit of 64 bytes maximum overhead. Full sourcecode release. I guess a Mac OS X version is underway, too, I didn't hear back from Bonefish yet.
Changes: Raw data decruncher included, one of the fastest decrunchers for 68000. Minor bugfix in decrunch header. Added Amiga-style commandline parsing, new options CDATA, DDATA, MAXOVH, MERGE. Removed former hardcoded limit of 64 bytes maximum overhead. Full sourcecode release. I guess a Mac OS X version is underway, too, I didn't hear back from Bonefish yet.
i believe that bifat updated the download, so now it also have osx binary and makefile.
Now on Aminet too:
http://aminet.net/package/util/pack/cranker.lha
There seems to be a cruncher week at aminet: DefPack, MaxPak, OmegaPacker, Cranker... hot, hot, hot!
http://aminet.net/package/util/pack/cranker.lha
There seems to be a cruncher week at aminet: DefPack, MaxPak, OmegaPacker, Cranker... hot, hot, hot!
Update to 0.40 available here and on Aminet: Disk motor is now turned off before the executable is started, in an OS-legal way, no poking to hardware registers.
Excellent.
Cranker 0.42 now available under the download link and expected to show up on Aminet soon.
The Amiga version now works on Kickstart 1.x and on 68000 CPUs, a FPU is no longer required. It's even fast enough to realistically crunch a demo on an Amiga 500. :-) This was a reasonable request by Sachy. Crunching fastmem hunks is now supported. Added an example decrunch header (including source) showing the load/decrunch progress.
The Amiga version now works on Kickstart 1.x and on 68000 CPUs, a FPU is no longer required. It's even fast enough to realistically crunch a demo on an Amiga 500. :-) This was a reasonable request by Sachy. Crunching fastmem hunks is now supported. Added an example decrunch header (including source) showing the load/decrunch progress.
Haven´t made use of it yet, so can´t put any real feedback, sorry! maybe later then! ;)
But reading "Titanics replacement" makes me insta-happy, have a thumb up already for the effort, i will use it for sure in the future! :)
But reading "Titanics replacement" makes me insta-happy, have a thumb up already for the effort, i will use it for sure in the future! :)
Yet another update - version 0.51 fixes some bugs with partly uninitialized hunks (produced by some compilers), hunk merging, and it strips debug/symbol hunks.
New version 0.64 under the download link: New read-ahead logic for faster loading, faster decruncher, can show textfiles (e.g. for ANSI logos), added decrankers 'picture' for showing a picture while loading, 'black' for a black screen while loading, userdata append option, some bug fixes, major source code and build cleanup and improved documentation
Looks like it's working now for me. Sometime before when I tried using it the executable crashed on start. Seems to have been fixed. Great stuff. Will definitely try to use it for when Shrinkler is too slow.
First up, I thougt: "Okay, another cruncher.. what for?" As I came in the situation I finally needed some cruncher to handle a large file, I tried Cranker and I must say I'm really impressed:
-very fast decrunching with fine size
-nice options for during decrunching
-continuously updates
-great replacement of the legendary Titanics Cruncher
A big thanks to Bifat! :)
-very fast decrunching with fine size
-nice options for during decrunching
-continuously updates
-great replacement of the legendary Titanics Cruncher
A big thanks to Bifat! :)
Super late thumb, great that you're adding features! Downloaded it again to see. About time for a replacement for Titanics-Cruncher for sure :)
Thanks for making this - works great.
Great tool which really loads and decrunches at the same time! And the -tf option is just too cool.
Takes 5 min to compile an executable for Windows, just requires a MinGW installation.
Used it to compress Five, worked well even if I could not get a huge compression ratio as most of the file data are samples for the 250kb music.
Thanks Bifat!
Used it to compress Five, worked well even if I could not get a huge compression ratio as most of the file data are samples for the 250kb music.
Thanks Bifat!
Awesome stuff. Dare I to ask for a 64bit version so I can compile and use this under latest OSX :) ?
difficult bug report to where?
ok nevermind, i RTFM. sry.
Cranker is now available in version 0.66 on Aminet, under the download link, and here:
http://neoscientists.org/~bifat/binarydistillery/cranker/. Precompiled binaries for Linux, MacOSX and Windows have been updated too. See src/INSTALL for instructions on how to compile it yourself for your funny computer.
Changes: Some flickers and glitches removed from the decrankers black, picture, and cinema. The picture option was pointless when starting an executable with a fast CPU from harddisk. Added SHOWTIME argument, the minimum number of seconds to display the picture. Default: 5.
This is a reminder to consider using Cranker for crunching your big Amiga OCS onefilers especially in the '-d cinema' or '-d picture' modes for a maxmium pleasant UX. Stay tuned for our next release where we will showcase again why using Cranker is a good idea for bigger filedemos.
http://neoscientists.org/~bifat/binarydistillery/cranker/. Precompiled binaries for Linux, MacOSX and Windows have been updated too. See src/INSTALL for instructions on how to compile it yourself for your funny computer.
Changes: Some flickers and glitches removed from the decrankers black, picture, and cinema. The picture option was pointless when starting an executable with a fast CPU from harddisk. Added SHOWTIME argument, the minimum number of seconds to display the picture. Default: 5.
This is a reminder to consider using Cranker for crunching your big Amiga OCS onefilers especially in the '-d cinema' or '-d picture' modes for a maxmium pleasant UX. Stay tuned for our next release where we will showcase again why using Cranker is a good idea for bigger filedemos.
Woohoooo!
Nice
Tools for the masses
Excellent!
...tested it, and it will certainly be used in future shenanigans
Hi! Awesome tool. Is there btw some known issue when compiled to 64bit binary? I see the makefile has -m32 for GCC, but the thing seems to work fine (atleast in this one test :)) without it on 64bit Linux.
I don't remember if there were issues with 64bit. I think we had at some point a 64bit version for MacOSX. So the answer is "no known issues, maybe due to forgetfulness". The main reason is that the main target Amiga is 32bit, and 32bit executables can usually be executed on both 32 and 64bit architectures, which makes is easier to maintain precompiled binaries for Lindows.
Been using it for a while now!
(And I'm using the Amiga version natively. Works great!)
used it!
Using it in a production that you will see very soon as in-demo (de)cruncher. Thanks Bifat!
submit changes
if this prod is a fake, some info is false or the download link is broken,
do not post about it in the comments, it will get lost.
instead, click here !
It decrunches while loading and decrunching requires no additional
memory. Cranker is by far the fastest way to run large executables
from disk on old, unexpanded Amigas like Amiga 500, 600, and 2000.
please check the README (click the NFO link!)