Old crunchers

absence · 25 June 2012, 16:57

Is it possible to tell which old exotic cruncher has been used for a data file? XFD recognises "Bytekiller data", but does it support all of those old crunchers (TryIt Cruncher, Flash Packer, TetraPack, etc.)? I have a file that i suspect is crunched with one of those, but xfdlist doesn't recognise it.

StingRay · 25 June 2012, 17:03

XFD supports a lot of crunchers. However, it sounds like your file has been "protected", i.e. some slight modifications to the header/decruncher code. Attach the file here and we can have a look.

absence · 25 June 2012, 18:40

It turned out that it WAS Bytekiller data, but the compressed size was bigger than the original (!), so XFD didn't understand it for some reason (bug?).

StingRay · 25 June 2012, 18:47

If it was a standard bytekiller crunched data(!) file, there is no guarantee that it will be recognised since these files normally do not have an ID.

25 June 2012, 16:57	#1
absence Registered User Join Date: Mar 2009 Location: moon Posts: 373	Old crunchers Is it possible to tell which old exotic cruncher has been used for a data file? XFD recognises "Bytekiller data", but does it support all of those old crunchers (TryIt Cruncher, Flash Packer, TetraPack, etc.)? I have a file that i suspect is crunched with one of those, but xfdlist doesn't recognise it.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
crunchers with c and asm sources	xxxxx	Coders. General	46	22 August 2019 08:20
Crunchers that support overlays?	BarryB	support.Apps	9	07 March 2017 11:58
What Crunchers do you guys prefer?	Plagueis/KRX	Coders. General	67	30 July 2014 23:20
Old crunchers for A500/WB1.3?	Photon	Coders. General	21	03 December 2004 02:14

25 June 2012, 17:03	#2
StingRay move.l #$c0ff33,throat Join Date: Dec 2005 Location: Berlin/Joymoney Posts: 6,863	XFD supports a lot of crunchers. However, it sounds like your file has been "protected", i.e. some slight modifications to the header/decruncher code. Attach the file here and we can have a look.

25 June 2012, 18:40	#3
absence Registered User Join Date: Mar 2009 Location: moon Posts: 373	It turned out that it WAS Bytekiller data, but the compressed size was bigger than the original (!), so XFD didn't understand it for some reason (bug?).

25 June 2012, 18:47	#4
StingRay move.l #$c0ff33,throat Join Date: Dec 2005 Location: Berlin/Joymoney Posts: 6,863	If it was a standard bytekiller crunched data(!) file, there is no guarantee that it will be recognised since these files normally do not have an ID.

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)