Any idea what this SLZ algorithm is?

i beliefe unk files are FMV's, although they don't look like mpeg to me (probably somehow encrypted).

I guess so... I mean just by looking at their filesize... they have to contain videos...  .pk1 files, however, seem too small to be "interesting", even though they seem not compressed/encrypted.

I tried opening a Pcsx2 savestate taken during FMV playback to see if there was any hint as to which file contains video data being played by the emulator but again everything is so cryptic to me. I noticed however that there were a lot of references to "SLZ" in the savestate file "eeMemory.bin", which led me to believe that those SLZ files are a sort of a key to open other encrypted files (forgive my english I'm tired).

CUE, thank you very much for the source code, this will be really helpful for a lot of people all over the web I'm sure

I got a SLZ2 encoding code(with little bugs but i fixed them) on the web . According to this,i got the decoding tool(it is a right one),but the problem came!!!!
First,I decoding the raw file "a.slz2"(extracted from "vp2.iso") to a new file "a.slz2.bin",the new file turns to be a right-decoded file,thus,it is its self now,!
Second,I encoding(using the above encoding method) the file "a.slz2.bin" to a new file "a.slz2.bin.slz2";
Last,I find that the file "a.slz2.bin.slz2" has several bytes' difference from the raw file "a.slz2" !!! But they can be decoding to the same file.....what is going on?
Please help me!If you need the raw file ,I will mail it to you.Thanks!
image：
Email:luo7388458@gmail.com

Are you trying to say that if you decompress and recompress a file without making a change, you get 2 different files??
By the way, your link doesn't work.

Are you trying to say that if you decompress and recompress a file without making a change, you get 2 different files??
By the way, your link doesn't work.

Yes!
I think the slz2 compression(I got it from the net) has some little bug. So what I need is the right slz2 compression code,can you help me?

Is normal, you can use different offsets.

An example:

To encode "00-00-00", with previous data = "00-00-00-01-00-00-00-02-$" (the current position is '$'), you can use:
- get 3 bytes from $-8
- get 3 bytes from $-4

The 2-bytes chunk that indicate the compression of these data are different.

Is normal, you can use different offsets.

An example:

To encode "00-00-00", with previous data = "00-00-00-01-00-00-00-02-$" (the current position is '$'), you can use:
- get 3 bytes from $-8
- get 3 bytes from $-4

The 2-bytes chunk that indicate the compression of these data are different.

OK,Thank you very much!
I will not care this any more.
February 05, 2012, 12:22:30 AM - (Auto Merged - Double Posts are not allowed before 7 days.)-----"pk1" package format:
offset,size:data
000000,4:preserved bytes(00)
000004,4:number of the file record entries (name it with "n")
000008,4:the first file's offset(name it with "oft")
00000C,4:preserved bytes(00)
000010,16:first file entry（see about "pk1 file entry" below）
000020,16:second file entry
......
0000n0,16:the nth file entry
000oft:the start of file data
......

-----"pk1 file entry" format(16 bytes):
00-03,4:the type of the file?(I'm not sure)
04-07,4:may be one kind of parameter
08-0b,4:size of the file
0c-0f,4:offset of the file in the package file

Are you unpacking the PSX or PS2 games?

ps2 vp2
February 06, 2012, 12:23:12 AM - (Auto Merged - Double Posts are not allowed before 7 days.)CUE ,thank you for your source code!You are a great man!