LZSS v0.01 is here!

[Cyan]

an "optimized hash function" ?

Last time i tried to test hash functions, i found little differences between most formulaes,
with the notable exception of byte-aligned operations, which should be avoided.
(For example, for a 4 bytes to 16 bits hash, one should avoid :
hash = input ^ input>>16;
)

That situation aside, any odd number seemed to produce mostly equivalent results;

Anyway, i'm very interested in what you could find...

[spark]

The name of a program shouldn't be "LZSS". LZSS is about bit flags to determine match or a literal. And here we have no bit flags. Just can't figure out how to call it. It should contain an "LZ" - *SOMETHING*LZ or LZ*SOMETHING*.

Maybe LzSpeedy or SpeedyLz.

As a bonus, neither term seems to be in use, yet. (no google hits)

--
Wiktionary entry for speedy::

Speedy (adjective)
1. Characterized by a rapid or swift motion.

synonyms: fast, swift, quick

[m^2]

Encode, your LZSS sources disappeared from here. Could you repost them?

[m^2]

Encode, no comments?
Anybody?

[encode]

Wow, I'm here!
The source is attached, but take into account - it is an extremely old code... Many things changed from that time... Anyway, I have an idea about the new super fast and open source encoder a la CRUSH (LZ77 + bit codes) but with simpler (faster) bit codes or byte aligned codes...

[m^2]

Thank you.

[Menno de Ruiter]

Hi hi,

Is the lzss001.zip compatible/same as the ntfs microsoft variant? I remember a while ago I asked you this, and something was not exact the same, but I can't remember clearly anymore. I want to write some tools for converting an uncompressed disk to a compressed disk, but not with using the dll's from ms... dont know if I will succeed

[encode]

It's not compatible. However, it's pretty similar, and changing window size and fixing match length/offset coding you can make it compatible! Match flag coding and literal coding scheme are the same!