I tried to open a Disk Image file, and it wouldn't open. I tried all kinds of >apps (including Disk Utility and Disk Image Mounter, obviously) but nothing >would mount it. So I tried opening it on a machine running Mojave, and it >opened without any problem.
I tried to open a Disk Image file, and it wouldn't open. I tried all kinds of apps (including Disk Utility and Disk Image Mounter, obviously) but nothing would mount it. So I tried opening it on a machine running Mojave, and it opened without any problem.
I didn't know this was a thing. How to tell which disks won't mount under Monterey, so that I can convert them before the older system is gone for ever?
Martin S Taylor
On 7 Sep 2022 at 11:36:20 BST, "Martin S Taylor" <correspondence@mRaErMtOiVnEsTtHaIySlor.com> wrote:
I tried to open a Disk Image file, and it wouldn't open. I tried all kinds of
apps (including Disk Utility and Disk Image Mounter, obviously) but nothing >> would mount it. So I tried opening it on a machine running Mojave, and it
opened without any problem.
I didn't know this was a thing. How to tell which disks won't mount under
Monterey, so that I can convert them before the older system is gone for
ever?
Martin S Taylor
I'd expect that to mean it's damaged in a way that Monterey refuses to
touch for safety reasons,
What results do you get in Disk Utility if you go to Images/Verify and
scan the dmg?
I'd expect that to mean it's damaged in a way that Monterey refuses to
touch for safety reasons, rather than it being intentionally in a
changed format.
In article<0001HW.28C8ABA4002D403E70000BF3338F@news.eternal-september.org>, Martin S Taylor <correspondence@mRaErMtOiVnEsTtHaIySlor.com> wrote:
I tried to open a Disk Image file, and it wouldn't open. I tried all kinds of
apps (including Disk Utility and Disk Image Mounter, obviously) but nothing would mount it. So I tried opening it on a machine running Mojave, and it opened without any problem.
Odd. What does the "file" command say about it, e.g.
$ file rr2.dmg
rr2.dmg: DOS/MBR boot sector, code offset 0x34+2, OEM-ID "MSDOS3.3", sectors/cluster 2, root entries 112, sectors 1440 (volumes <=32 MB), Media descriptor 0xf9, sectors/FAT 3, sectors/track 9, dos < 4.0 BootSector (0), FAT (12 bit by descriptor), followed by FAT
-- Richard
/Users/mst/Desktop/Gardner.dmg: ISO 9660 CD-ROM filesystem data 'Gardner'
In article <0001HW.28C9D9A40058963870000771F38F@news.eternal-september.org>, Martin S Taylor <correspondence@mRaErMtOiVnEsTtHaIySlor.com> wrote:
/Users/mst/Desktop/Gardner.dmg: ISO 9660 CD-ROM filesystem data 'Gardner'
That looks vanilla enough. Jaimie, did the malformed dmg issue
you mentioned apply to ISO 9660?
In article <jnrq0gFoaf1U1@mid.individual.net>,
Jaimie Vandenbergh <jaimie@usually.sessile.org> wrote:
I'd expect that to mean it's damaged in a way that Monterey refuses to
touch for safety reasons, rather than it being intentionally in a
changed format.
Surely it would display an error message in that case?
/Users/mst/Desktop/Gardner.dmg: ISO 9660 CD-ROM filesystem data 'Gardner'
What happens if you rename it to .iso rather than .dmg?
What happens if you rename it to .iso rather than .dmg?
Same.
In article
<0001HW.28CA30E9006A3DCE70000ACD138F@news.eternal-september.org>,
Martin S Taylor <correspondence@mRaErMtOiVnEsTtHaIySlor.com> wrote:
What happens if you rename it to .iso rather than .dmg?
Same.
you said you can open it on mojave, so my suggestion is to do that and
use carbon copy cloner to copy everything to a new disk image.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 546 |
Nodes: | 16 (0 / 16) |
Uptime: | 165:06:06 |
Calls: | 10,385 |
Calls today: | 2 |
Files: | 14,057 |
Messages: | 6,416,521 |