Existing users, 
20/11/08 7:08:36 AM [0x0-0x12e12e].com.apple.archiveutility[9221] bunzip2: Compressed file ends unexpectedly;
20/11/08 7:08:36 AM [0x0-0x12e12e].com.apple.archiveutility[9221] perhaps it is corrupted? *Possible* reason follows.
20/11/08 7:08:36 AM [0x0-0x12e12e].com.apple.archiveutility[9221] bunzip2: Inappropriate ioctl for device
20/11/08 7:08:36 AM [0x0-0x12e12e].com.apple.archiveutility[9221] Input file = (stdin), output file = (stdout)
20/11/08 7:08:36 AM [0x0-0x12e12e].com.apple.archiveutility[9221] It is possible that the compressed file(s) have become corrupted.
20/11/08 7:08:36 AM [0x0-0x12e12e].com.apple.archiveutility[9221] You can use the -tvv option to test integrity of such files.
20/11/08 7:08:36 AM [0x0-0x12e12e].com.apple.archiveutility[9221] You can use the `bzip2recover' program to attempt to recover
20/11/08 7:08:36 AM [0x0-0x12e12e].com.apple.archiveutility[9221] data from undamaged sections of corrupted files.
NTI Dragon Burn
CD and DVD burning software.
Version: 4.5.0.15
My Console message - ttrtilley
bunzip2recover produced the same bad .dmg file as did both bunzip2 and Stuffit expander. Something strange at the end of the file. I vaguely recall having the same problem with the last version, but somehow got it mounted. Perhaps with Toast. Not this time :-($ bzip2recover NTIDragonBurn_v4505_OSX.dmg.bz2
bzip2recover 1.0.4: extracts blocks from damaged .bz2 files.
bzip2recover: searching for block boundaries ...
block 1 runs from 80 to 0
block 2 runs from 528 to 0
[snip]
block 237 runs from 166417064 to 0
block 238 runs from 166432072 to 0
block 476 runs from 166433128 to 0 (incomplete)
bzip2recover: splitting into blocks
writing block 1 to `rec00001NTIDragonBurn_v4505_OSX.dmg.bz2' ...
writing block 2 to `rec00002NTIDragonBurn_v4505_OSX.dmg.bz2' ...
[snip]
writing block 237 to `rec00237NTIDragonBurn_v4505_OSX.dmg.bz2' ...
writing block 238 to `rec00238NTIDragonBurn_v4505_OSX.dmg.bz2' ...
bzip2recover: finished
Reply to This
Monday, December 01 2008 @ 09:13 AM PST