BARF wrote:The BARF compressor will compress any nonempty file by at least one byte. Thus, by compressing already compressed files over and over again, it is possible to eventually reduce any file to 0 bytes.
How is that possible? I don't understand how it could, unless there is some dictionary or something that they are not including. Otherwise, you could compress the LOTR DVDs until the point that you could memorize it, and just watch in on any computer...
Hey! You could compress everything on your computer and just run it from RAM!
kevman wrote:How is that possible? I don't understand how it could, unless there is some dictionary or something that they are not including. Otherwise, you could compress the LOTR DVDs until the point that you could memorize it, and just watch in on any computer...
Hey! You could compress everything on your computer and just run it from RAM!
It's a joke format. It compresses files by removing one byte and encoding it in the filename. If you rename the file, you can't 'decompress' it.
D:\Incoming>barf c readme.txt
readme.txt (861 bytes) -> readme.txt.x (659 bytes)
D:\Incoming>barf c readme.txt.x
readme.txt.x (659 bytes) -> readme.txt.x.x (638 bytes)
D:\Incoming>barf c readme.txt.x.x
readme.txt.x.x (638 bytes) -> readme.txt.x.x.x9v (637 bytes)
D:\Incoming>barf c readme.txt.x.x.x9v
readme.txt.x.x.x9v (637 bytes) -> readme.txt.x.x.x9v.x0h (636 bytes)
D:\Incoming>barf c readme.txt.x.x.x9v.x0h
readme.txt.x.x.x9v.x0h (636 bytes) -> readme.txt.x.x.x9v.x0h.x9v (635 bytes)
D:\Incoming>barf c readme.txt.x.x.x9v.x0h.x9v
readme.txt.x.x.x9v.x0h.x9v (635 bytes) -> readme.txt.x.x.x9v.x0h.x9v.x0d (634 by
tes)
D:\Incoming>barf c readme.txt.x.x.x9v.x0h.x9v.x0d
readme.txt.x.x.x9v.x0h.x9v.x0d (634 bytes) -> readme.txt.x.x.x9v.x0h.x9v.x0d.x0j
(633 bytes)
D:\Incoming>barf c readme.txt.x.x.x9v.x0h.x9v.x0d.x0j
readme.txt.x.x.x9v.x0h.x9v.x0d.x0j (633 bytes) -> readme.txt.x.x.x9v.x0h.x9v.x0d
.x0j.x1t (632 bytes)
D:\Incoming>barf c readme.txt.x.x.x9v.x0h.x9v.x0d.x0j.x1t
readme.txt.x.x.x9v.x0h.x9v.x0d.x0j.x1t (632 bytes) -> readme.txt.x.x.x9v.x0h.x9v
.x0d.x0j.x1t.x1t (631 bytes)
D:\Incoming>barf c readme.txt.x.x.x9v.x0h.x9v.x0d.x0j.x1t.x1t
readme.txt.x.x.x9v.x0h.x9v.x0d.x0j.x1t.x1t (631 bytes) -> readme.txt.x.x.x9v.x0h
.x9v.x0d.x0j.x1t.x1t.x1i (630 bytes)
D:\Incoming>barf c readme.txt.x.x.x9v.x0h.x9v.x0d.x0j.x1t.x1t.x1i
readme.txt.x.x.x9v.x0h.x9v.x0d.x0j.x1t.x1t.x1i (630 bytes) -> readme.txt.x.x.x9v
.x0h.x9v.x0d.x0j.x1t.x1t.x1i.x1i (629 bytes)
The point being, even if you could compress the file to 1 byte, it would take WAY too long, not to mention the size of the filename...
I don't know of a file system that allows more than a 255 characters in the filename. I'm sure that there are a few, but I doubt there would be any that allows more than a thousand characters.
D:\Incoming>barf c readme.txt
readme.txt (861 bytes) -> readme.txt.x (659 bytes)
D:\Incoming>barf c readme.txt.x
readme.txt.x (659 bytes) -> readme.txt.x.x (638 bytes)
D:\Incoming>barf c readme.txt.x.x
readme.txt.x.x (638 bytes) -> readme.txt.x.x.x9v (637 bytes)
D:\Incoming>barf c readme.txt.x.x.x9v
readme.txt.x.x.x9v (637 bytes) -> readme.txt.x.x.x9v.x0h (636 bytes)
D:\Incoming>barf c readme.txt.x.x.x9v.x0h
readme.txt.x.x.x9v.x0h (636 bytes) -> readme.txt.x.x.x9v.x0h.x9v (635 bytes)
D:\Incoming>barf c readme.txt.x.x.x9v.x0h.x9v
readme.txt.x.x.x9v.x0h.x9v (635 bytes) -> readme.txt.x.x.x9v.x0h.x9v.x0d (634 by
tes)
D:\Incoming>barf c readme.txt.x.x.x9v.x0h.x9v.x0d
readme.txt.x.x.x9v.x0h.x9v.x0d (634 bytes) -> readme.txt.x.x.x9v.x0h.x9v.x0d.x0j
(633 bytes)
D:\Incoming>barf c readme.txt.x.x.x9v.x0h.x9v.x0d.x0j
readme.txt.x.x.x9v.x0h.x9v.x0d.x0j (633 bytes) -> readme.txt.x.x.x9v.x0h.x9v.x0d
.x0j.x1t (632 bytes)
D:\Incoming>barf c readme.txt.x.x.x9v.x0h.x9v.x0d.x0j.x1t
readme.txt.x.x.x9v.x0h.x9v.x0d.x0j.x1t (632 bytes) -> readme.txt.x.x.x9v.x0h.x9v
.x0d.x0j.x1t.x1t (631 bytes)
D:\Incoming>barf c readme.txt.x.x.x9v.x0h.x9v.x0d.x0j.x1t.x1t
readme.txt.x.x.x9v.x0h.x9v.x0d.x0j.x1t.x1t (631 bytes) -> readme.txt.x.x.x9v.x0h
.x9v.x0d.x0j.x1t.x1t.x1i (630 bytes)
D:\Incoming>barf c readme.txt.x.x.x9v.x0h.x9v.x0d.x0j.x1t.x1t.x1i
readme.txt.x.x.x9v.x0h.x9v.x0d.x0j.x1t.x1t.x1i (630 bytes) -> readme.txt.x.x.x9v
.x0h.x9v.x0d.x0j.x1t.x1t.x1i.x1i (629 bytes)
The point being, even if you could compress the file to 1 byte, it would take WAY too long, not to mention the size of the filename...
I don't know of a file system that allows more than a 255 characters in the filename. I'm sure that there are a few, but I doubt there would be any that allows more than a thousand characters.
My point exactly - I was implying that the filename might be too big.
No, JMA doesn't support multiple files in one archive, at the moment anyway IIRC.
whicker: franpa is grammatically correct, and he still gets ripped on? sweener2001: Grammatically correct this one time? sure. every other time? no. does that give him a right? not really.
whicker: franpa is grammatically correct, and he still gets ripped on? sweener2001: Grammatically correct this one time? sure. every other time? no. does that give him a right? not really.
