94 (count 'em) caves from moi on the way
Moderator: Admin
- LogicDeLuxe
- Member
- Posts: 637
- Joined: Sun Jul 15, 2007 12:52 pm
- Contact:
Algorithm 2 is buggy, use only 1 and 3 (simultanously) instead. While both also work alone, the compression is weaker than, ie. resulting in a bigger file size.
If you still get a crash, you probably got the startadress wrong.
Drive emulation shouldn't matter, as all it does is simply reading and writing the files sequentially. (Also works with old PC64)
The Fast Crueler is a more advanced crunsher than the Final Super Compressor. In rare cases (1 out of 100 maybe), it fails, though, thus I still included the Final Super Compressor just in case on CLCK disk as well. It takes roughly 10 minutes for a Boulder Dash, which is quite fast for such a strong cruncher on a c64 while similar crunchers take hours for the same result. In an emulator, this can be sped up, of course.
If you're working an a PC (or any other advanced computer), you also could give Pucrunch a try. It's stronger than anything on a plain C64 and fast like hell with the horsepower of today's systems. It requires a raw file though, as it doesn't work on disk images.
If you still get a crash, you probably got the startadress wrong.
Drive emulation shouldn't matter, as all it does is simply reading and writing the files sequentially. (Also works with old PC64)
The Fast Crueler is a more advanced crunsher than the Final Super Compressor. In rare cases (1 out of 100 maybe), it fails, though, thus I still included the Final Super Compressor just in case on CLCK disk as well. It takes roughly 10 minutes for a Boulder Dash, which is quite fast for such a strong cruncher on a c64 while similar crunchers take hours for the same result. In an emulator, this can be sped up, of course.
If you're working an a PC (or any other advanced computer), you also could give Pucrunch a try. It's stronger than anything on a plain C64 and fast like hell with the horsepower of today's systems. It requires a raw file though, as it doesn't work on disk images.
Thanks for the advice! That'll make next time much easier.
LogicDeLuxe wrote:Algorithm 2 is buggy, use only 1 and 3 (simultanously) instead. While both also work alone, the compression is weaker than, ie. resulting in a bigger file size.
If you still get a crash, you probably got the startadress wrong.
Drive emulation shouldn't matter, as all it does is simply reading and writing the files sequentially. (Also works with old PC64)
The Fast Crueler is a more advanced crunsher than the Final Super Compressor. In rare cases (1 out of 100 maybe), it fails, though, thus I still included the Final Super Compressor just in case on CLCK disk as well. It takes roughly 10 minutes for a Boulder Dash, which is quite fast for such a strong cruncher on a c64 while similar crunchers take hours for the same result. In an emulator, this can be sped up, of course.
If you're working an a PC (or any other advanced computer), you also could give Pucrunch a try. It's stronger than anything on a plain C64 and fast like hell with the horsepower of today's systems. It requires a raw file though, as it doesn't work on disk images.
Watcher Kitty is always watching...