search

pombreda / theunarchiver-migrated

Mac, Linux and Windows universal unarchiver. CLI everywhere and MAC Gui. Objective-C, GPL-licensed. Originally from code.google.com/p/theunarchiver
Other
1 stars 0 forks source link

Cannot mount some Disk Images (DMG) unarchived from BZ2 (and even ZIP) #111

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Download the attached BZ2 file. 
2. Unarchive with The Unarchiver.
3. Try to mount the Disk Image.

What is the expected output? What do you see instead?
The outputted DMG is supposed to mount, but instead it says "The following disk 
images failed 
to mount" giving the reason "not recognized". I presume this is because the 
file has been 
unzipped improperly.

What version of the product are you using? On what operating system?
I'm using the newest version (1.6.1 on Leopard 10.5.2)

Please provide any additional information below.
I have tried this with many other BZ2 files (updates for the game Wolfenstein 
Enemy Territory) 
and even ZIP files (but these are 200MB, too large to attach - link: 
http://macinfront.macologist.org/mirror/macologist/details.php?file=321 (you 
have to follow a 
number of steps to download it: "Download xxx" (at the bottom) -> "I Agree" -> 
FileFront -> 
Download Now).

Note: The archived file is 1.4MB, but the disk image it yields is 8.2MB. 
Strange.

Original issue reported on code.google.com by rudi...@gmail.com on 18 May 2008 at 1:29

Attachments:

GoogleCodeExporter commented 9 years ago 
Strange, the file that I attatched (is the one I downloaded from the web) can 
be renamed to end with .dmg 
(taking off the bz2) and then it works!

It must be that something appends bz2 to files to be downloaded as DMGs. Could 
it be The Unarchiver or Safari?

I know there is a similar problem with Microsoft Office Word DOC files getting 
a DOT at the end of them (and 
PPTs getting POT).

Original comment by rudi...@gmail.com on 18 May 2008 at 1:31

GoogleCodeExporter commented 9 years ago 
It's a long-standing Safari bug. What causes it is a bit of a mystery.

Original comment by paracel...@gmail.com on 21 May 2008 at 11:22

GoogleCodeExporter commented 9 years ago

Original comment by paracel...@gmail.com on 21 May 2008 at 11:22

GoogleCodeExporter commented 9 years ago 
Status - invalid? lol

Original comment by rudi...@gmail.com on 22 May 2008 at 5:22