Home
| Calendar
| Mail Lists
| List Archives
| Desktop SIG
| Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings Linux Cafe | Meeting Notes | Linux Links | Bling | About BLU |
Most likely SOL. You could try gzip and see if it can do it. In your case it appears that the file is either truly corrupt or it may have been compressed on a different system. If the file was compressed on a Sparc, you might need to uncompress it on a Spark. If the data is really important, you can take the sources for uncompress and try to figure out how the file is corrupt and fix it by hand. That is a lot of pain. Ken Gosier wrote: > Hi, I have a compressed file I'm trying to uncompress. But > when I give the command, I get the error message: > > insize:1031 posbits:4844 inbuf:F0 CE F3 B7 0B (4) > uncompress: corrupt input > > I checked the man page for compress, and it tells me as a > diagnostic: > > uncompress: corrupt input > A SIGSEGV violation was detected which usually > means that the input file has been corrupted. > > which, as far as I can tell, means "tough shit." Anybody > have any experience saving corrupted files like this? > > Thanks very much for any help-- > > ===== > Ken Gosier > ken_gosier at yahoo.com > > __________________________________________________ > Do You Yahoo!? > Talk to your friends online with Yahoo! Messenger. > http://im.yahoo.com > - > Subcription/unsubscription/info requests: send e-mail with > "subscribe", "unsubscribe", or "info" on the first line of the > message body to discuss-request at blu.org (Subject line is ignored). > -- Jerry Feldman <gaf at blu.org> Boston Linux and Unix user group http://www.blu.org - Subcription/unsubscription/info requests: send e-mail with "subscribe", "unsubscribe", or "info" on the first line of the message body to discuss-request at blu.org (Subject line is ignored).
BLU is a member of BostonUserGroups | |
We also thank MIT for the use of their facilities. |