How can I delete a folder backed up via Time Machine to a .backupbundle disk image? When I try to delete the folder, I get the error message, "The operation can't be completed because backup items can't be modified." I found a similar question, "How can I delete a file marked as backup item?" The accepted answer says that this is a bug that will be fixed in a coming update. Unfortunately, this answer was written in 2011 –– 11 years ago. I tried to comment on the answer, but I did not have enough reputation. > A little more precision regarding what you tried would be helpful. > "when I Delete the folder". Which folder? Is that on the source disk, > or is it in the backup? And how did you try to delete? Also what > version of macOS and what format (HFS+ or APFS) is the backup disk > image? /Volumes/Time Machine Backups/Backups.backupdb/MacBook Pro (Retina)/2021-05-02-065359/Macintosh HD 1/Users/brianschack/Transmission Downloads On the backup. I tried dragging the folder to the Trash in the Dock. macOS Big Sur 11.2.3. Mac OS Extended (Case-sensitive, Journaled). > The accepted answer on your linked questin is basically wrong. The > highest voted answer is correct - you are trying to delete from a > protected area. You cannot just delete Time Machine files from Finder. @Ryccardo wrote the highest-voted answer to the question, "How can I delete a file marked as backup item?" He says, "[L]ocate the item in the 'in space' Time Machine view[.]" This is a backup of a computer that I traded in. When I go to the in-space Time Machine view on my current computer, it shows me the backup of my current computer –– not the computer that I traded in. He also writes, "There exists a helper program (command-line binary) [...] which allows you to supply a command and argument to completely bypass the access restrictions." When I navigate to /System/Library/Extensions, I do not see TMSafetyNet.kext. In a different answer, @Evan Kroske writes, "It seems like the bypass program doesn't exist on Big Sur." How can I delete a file marked as backup item?

I have a MacBook Air 2017. Out of the blue, I opened the MacBook and was confronted with the question mark. The Mac would only boot in recovery mode. In internet recovery mode, I copied the internal disk (dd conv=noerror,sync) to an external hard drive. Whilst I did create a 250GB disk image, I'm not sure of the quality of it, as I received many ‘disk not configured’ messages in the process. With that disk image from the external drive in another MacBook Air 2017, I used hdiutil imageinfo which said there were seven partitions on the disk image. I then used test disk/ file system utils which showed two partitions an EFI partition and an APFS. I created an image of the APFS partition which was 250GB but when I run **photorec** on that (writing to a second external hard drive) it hasn’t recovered any files. Any advice on next best steps or things that I need to do/ haven’t done. Would be hugely appreciated. Edit: A previous attempt at running photo rec on the full disk image yielded a 250GB plist file. Edit2: I can now use target disk mode to see the disk on another MacBook. However it fails to mount. DDRescue currently running and making slow progress.

I had a 12TB WD drive go wonky on me recently. It would show on Disk Utility but not mount. I tried some Terminal commands to force mount which failed. There are two partitions on my drive. One is about 12TB and the other is 150MB or so. I was able to mount the 150MB partition just fine using Terminal, but not the partition I need (with all my backup video projects). I had the bright idea of creating a disc image of the 12TB parition onto a RAID drive. It took about 26 hours but it made it successfully, but split the dmg files into parts. I tried to open the first dmg file and it didn't work, as I read should work. Great. So I read somewhere that I could try to piece the parts back together. I started to create a folder disk image of all the dmg parts. It was at about 90% done on the progress bar after a whole day so I left it clinking away overnight. I come back this morning and the progress bar is at maybe 5%. There is no cancel button and I'm afraid so screwing my new RAID drive up by force quitting Disk Utility. I don't mind if I screw up the image file I'm trying to create but I just got this RAID drive. Please help! Should I just wait to see if it finishes? Why did the progress bar go back down? Is the RAID drive I'm creating the disc image folder on in any danger of corruption if I force quit Disk Utility? Any insights would be greatly appreciated! Thank you * I checked Activity Monitor and it seems that Disk Utility is not doing much of anything. It did pop up to 0.1% CPU at one point. I also have something called com.apple.hiservices-xpcservice that's not responding. And the System percentage is red between 5-8%.

i'm stuck and urgently need assistance! I have rMBP 15"(MacBookPro **A1398**(**mid 2015**)), currently running **Big Sur**. The idea is simple, i just want to jump on Sequioa via OCLP(my rMBP is not supported anymore), since for development purpose it requires to have latest version of MacOS. The problem appears here, since i have a bunch of data / apps / settings and etc, which never was saved before and i would like to not lose it before upgrade process. I have an empty SATA3 SSD and SATA3 To USB adapter. Plus additional Backup drive (NTFS) where i store files from my personal Windows machine. What i'm trying to achieve : 1) Create **Image** disk with full clone of my current MacOS BigSur AS IS, which should contain all files / settings / apps and etc. After that i want to copy that **Image** on my NTFS backup drive and possible later i will move it to Cloud(e.g. OneDrive). 2) Create a full bootable clone on external SSD and keep it there temporarely while upgrading via OCLP. If it crashes(i hope its not), then i can erase\wipe my internal ssd and just clone again from external SSD freshly copied version and repeat process(or maybe full wipe and clean install, which I really don't want to do, its completely other story / question) Note #2 seems to be not a huge problem at all, since i could use at least basic Disk Utility for such job. Note #1 its more complicated, since i'm not "advanced" user of MacOS, to be honest i'm not even sure if that scenario possible / applicable, because i have no idea how in fact looks fully bootable **Image** of cloned MacOS system, i guess it should be the same how it works in Windows manner where you get **Image** as one file with format "**.iso**", but for Mac it will be one file as "**.dmg**". Also, i had in mind to use Time Machine, but this is much more complicated and not best solution for my case, since of you can't just copy/paste files from Time Machine, because under the hood it uses symlinks. Any advice appreciated. PS Could be possible through 3rd party apps like **CCC**, but unfortunately i didn't found anything similiar on my request...

This happened during my efforts of trying to fix my other computer. (See here for more). I was flashing a ISO image with balenaEtcher . Then I closed the lid of my laptop and left for 20 minutes. Strangely, after I come back, it was stuck, I couldn't cancel or anything. I quitted it and now I can't mount it anymore. When I try to restore it I got:

Restoring “disk3s2” from “Unnamed”

Validating target...
Validating source...
Repartitioning target device...
Could not change the partition type for /dev/disk3s2 - Operation not permitted
The operation couldn’t be completed. (OSStatus error 1.)

Operation failed…

When I try to erase it...

Erasing “disk3s2” and creating “UNTITLED”

Unmounting disk
Couldn’t modify partition map. : (-69874)

Operation failed…

And mounting it got me:

Could not mount “disk3s2”. (com.apple.DiskManagement.disenter error -119930868.)

What do I do?

I'm trying to disk imaging for my Macbook. I booted in Target Disk Mode and imaged the disk, but 'Macintosh hd - Data' is encrypted. I turned off FileVault encryption, diskutil still says 'Encrypted at rest'. How to turn off 'Encrypted at rest' on Macbook? My Macbook is using an Intel CPU and Monterey OS. Thank you!

I have a MB Pro 13" 2018 which has been running Mojave (10.14.6). I have been considering upgrading to the newest macOS. However, I want to have a way back in case that the new macOS is not performing as I would expect. What is the best way to ensure that I can come back? I have been considering options: 1. Create disk image in recovery mode and should the need arise, restore the whole disk image back. **EDIT** I tried booting into restore mode but image cannot be taken of the Mac HD, it is greyed out. I assume it is because of the encryption. Can this still be done? 2. There are notes to download Mojave from Apple store but I am not so clear on how to proceed from there. 3. There are suggestions to backup using time machine and then use that to restore but I am not sure if Time Machine would restore the whole system back to Mojave. Which is the best way to go? Along those lines, upgrading to Sonoma from Mojave, is it better to first clean the system and do it from a clean system or it does not really matter and I can do it from the existing system?

I created a sparse disk image of 400 GB with hdiutil command on an empty 500 GB external drive. After I have attached the disk image, I copy data to it. After about 17 GB of data I get an error stating: No space left on device Why is it that I cannot fully utilize the 400 GB and is it raising this error? hdiutil create -size 400g -type SPARSE -fs APFS -volname test /Volumes/data/test.dmg hdiutil attach /Volumes/data/test.dmg.sparseimage Any help much appreciated!

Good morning to you all - to save some sensitive business and private data on my internal SSD, I use Disk Utility to format an encrypted APFS sparseimage. When upgrading from Mojave to Sonoma, I copied all data to an external APFS drive, formated the internal drive and installed Sonoma (clean install) and copied all my stuff back to the home directory. After mounting the sparseimage I realized, that inside the mounted image about 3 of 7 files where corrupt - Any file formats on this image are more or less affected. I do have backups, which were done with CCC - Carbon Copy Cloner. But even those older APFS sparseimages already have some issues with data corruption. > Question 01 Question 02 < how can I than merge files and folders into a third destination folder from two different source images and repeat this merging process with as many of the backup images until I come close to the original state of the image? Or any other suggestions? Thank you all in advance and best greetings

I tried making a bootable macOS Sierra DVD and now I'm stuck with 2 disk images whenever I boot into Recovery Mode. The DVD is no longer inside the optical unit obviously. Ejecting doesn't work. Unmounting doesn't work. I tried resetting the PRAM with no result. I tried "diskutil unmountdisk force" with no result. These images weren't there prior to my failed attempt at installing from a DVD. There must be some sort of registry/cache somewhere.

I have a 2018 MacBook Pro I borrowed and need to return. I already have a cloud backup but wanted a full disk clone for extra safety. All my attempts are done in Recovery Mode. I first tried to clone the whole disk using hdiutil create -srcdevice /dev/disk0 -format UDZO -o /Volumes/ExternalDrive/disk0.dmg. I have an 80 GB file (the SSD was 1 TB and quite full of data), so I know something was wrong. When I attached it, I just got an empty image.

/dev/disk10 (disk image):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:     FDisk_partition_scheme                        +1.0 TB     disk10
   1:                       0xEE ⁨⁩                        125.1 GB   disk10s1
                    (free space)                         875.5 GB   -

I then tried to clone the APFS synthesized disk. It seemed to work, but the volumes are encrypted and I don't know how to decrypt them. On the 2018 MacBook, I have:

+-- Container disk3 AD3E4EE4-1440-468C-9CA5-677DE00BC5A8
|   ====================================================
|   APFS Container Reference:     disk3
|   Size (Capacity Ceiling):      1000240963584 B (1.0 TB)
|   Capacity In Use By Volumes:   733871874048 B (733.9 GB) (73.4% used)
|   Capacity Not Allocated:       266369089536 B (266.4 GB) (26.6% free)
|   |
|   +- Volume disk3s1 5220F233-F35B-4AAD-A056-41DA26FFB5EE
|   |   ---------------------------------------------------
|   |   APFS Volume Disk (Role):   disk3s1 (Data)
|   |   Name:                      Macintosh HD - 数据 (Case-insensitive)
|   |   Mount Point:               Not Mounted
|   |   Capacity Consumed:         721904885760 B (721.9 GB)
|   |   Sealed:                    No
|   |   FileVault:                 No (Encrypted at rest)
|   |
|   +-> Volume disk3s2 1578E60E-1F24-42F4-81D6-B14C53D1D51A
|   |   ---------------------------------------------------
|   |   APFS Volume Disk (Role):   disk3s2 (Preboot)
|   |   Name:                      Preboot (Case-insensitive)
|   |   Mount Point:               Not Mounted
|   |   Capacity Consumed:         1775439872 B (1.8 GB)
|   |   Sealed:                    No
|   |   FileVault:                 No
|   |
|   +-> Volume disk3s3 CB271A30-7E14-4CE5-9AF2-AEDE35166F74
|   |   ---------------------------------------------------
|   |   APFS Volume Disk (Role):   disk3s3 (Recovery)
|   |   Name:                      Recovery (Case-insensitive)
|   |   Mount Point:               Not Mounted
|   |   Capacity Consumed:         1116946432 B (1.1 GB)
|   |   Sealed:                    No
|   |   FileVault:                 No
|   |
|   +-> Volume disk3s4 4EE2238A-AD9A-4030-BFFB-42A03E737CD6
|   |   ---------------------------------------------------
|   |   APFS Volume Disk (Role):   disk3s4 (System)
|   |   Name:                      Macintosh HD (Case-insensitive)
|   |   Mount Point:               Not Mounted
|   |   Capacity Consumed:         8865898496 B (8.9 GB)
|   |   Sealed:                    Broken
|   |   FileVault:                 No (Encrypted at rest)
|   |
|   +-> Volume disk3s6 CDCF8CA7-0DAC-41A2-AB14-8D5458E159E4
|       ---------------------------------------------------
|       APFS Volume Disk (Role):   disk3s6 (VM)
|       Name:                      VM (Case-insensitive)
|       Mount Point:               Not Mounted
|       Capacity Consumed:         20480 B (20.5 KB)
|       Sealed:                    No
|       FileVault:                 No
|

but for the disk image:

/dev/disk11 (disk image):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                                                   +1.0 TB     disk11

/dev/disk12 (synthesized):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      APFS Container Scheme -                      +1.0 TB     disk12
                                 Physical Store disk11
   1:                APFS Volume ⁨Macintosh HD - 数据⁩     721.9 GB   disk12s1
   2:                APFS Volume ⁨Preboot⁩                 1.8 GB     disk12s2
   3:                APFS Volume ⁨Recovery⁩                1.1 GB     disk12s3
   4:                APFS Volume ⁨Macintosh HD⁩            8.9 GB     disk12s4
   5:                APFS Volume ⁨VM⁩                      20.5 KB    disk12s6

+-- Container disk12 AD3E4EE4-1440-468C-9CA5-677DE00BC5A8
    =====================================================
    APFS Container Reference:     disk12
    Size (Capacity Ceiling):      1000240963584 B (1.0 TB)
    Capacity In Use By Volumes:   733871874048 B (733.9 GB) (73.4% used)
    Capacity Not Allocated:       266369089536 B (266.4 GB) (26.6% free)
    |
    +- Volume disk12s1 5220F233-F35B-4AAD-A056-41DA26FFB5EE
    |   ----------------------------------------------------
    |   APFS Volume Disk (Role):   disk12s1 (Data)
    |   Name:                      Macintosh HD - 数据 (Case-insensitive)
    |   Mount Point:               Not Mounted
    |   Capacity Consumed:         721904885760 B (721.9 GB)
    |   Sealed:                    No
    |   FileVault:                 Yes (Locked)
    |
    +-> Volume disk12s2 1578E60E-1F24-42F4-81D6-B14C53D1D51A
    |   ----------------------------------------------------
    |   APFS Volume Disk (Role):   disk12s2 (Preboot)
    |   Name:                      Preboot (Case-insensitive)
    |   Mount Point:               Not Mounted
    |   Capacity Consumed:         1775439872 B (1.8 GB)
    |   Sealed:                    No
    |   FileVault:                 No
    |
    +-> Volume disk12s3 CB271A30-7E14-4CE5-9AF2-AEDE35166F74
    |   ----------------------------------------------------
    |   APFS Volume Disk (Role):   disk12s3 (Recovery)
    |   Name:                      Recovery (Case-insensitive)
    |   Mount Point:               Not Mounted
    |   Capacity Consumed:         1116946432 B (1.1 GB)
    |   Sealed:                    No
    |   FileVault:                 No
    |
    +-> Volume disk12s4 4EE2238A-AD9A-4030-BFFB-42A03E737CD6
    |   ----------------------------------------------------
    |   APFS Volume Disk (Role):   disk12s4 (System)
    |   Name:                      Macintosh HD (Case-insensitive)
    |   Mount Point:               Not Mounted
    |   Capacity Consumed:         8865898496 B (8.9 GB)
    |   Sealed:                    Broken
    |   FileVault:                 Yes (Locked)
    |   Encrypted:                 No
    |
    +-> Volume disk12s6 CDCF8CA7-0DAC-41A2-AB14-8D5458E159E4
        ----------------------------------------------------
        APFS Volume Disk (Role):   disk12s6 (VM)
        Name:                      VM (Case-insensitive)
        Mount Point:               Not Mounted
        Capacity Consumed:         20480 B (20.5 KB)
        Sealed:                    No
        FileVault:                 No

I tried various things on both the 2018 borrowed Mac and my new MacBook, but I couldn't figure out what the problem was:

jin@Joy-MBP ~ > diskutil apfs listcryptousers /dev/disk12s1
No cryptographic users for disk12s1

jin@Joy-MBP ~> diskutil apfs unlockVolume disk12s1 -user disk
Passphrase:
Unlocking the "disk" cryptographic user on APFS Volume disk11s1
User does not exist; try "diskutil apfs listCryptoUsers"

What should I try next?

I need to hide a particular folder on my Mac from other people who might want to view or copy them while I'm away from home. There are two ways I'm aware of. The first way is to hide the folder using Terminal.

chflags hidden your-folder

chflags nohidden your-folder

The second way is to move the files from the folder to a disk image, which is created using Disk Utility. And again, it seems there are two different ways, both are described here: [*Create a disk image using Disk Utility on Mac*](https://support.apple.com/guide/disk-utility/create-a-disk-image-dskutl11888/mac) , sections - *Create a disk image from a folder or connected device* > **Disk Utility** > **File** > **New Image** > **Image From Folder** > **Encryption** = **128-bit AES encryption** > **Passoword** = **...** > **Image Format** = **read/write** - and *Create a secure disk image* > **Disk Utility** > **File** > **New Image** > **Blank Image** > **Size** = **100 MB** (default) (as far as I understand, this value doesn't matter, because we will use **read/write** futher) > **Format** = **APFS** > **Encryption** = **128-bit AES encryption** > **Partitions** = **Single partition - GUID partition map** (default) (I don't know what does it mean) > **Image Format** = **read/write disk image** What I don't understand and what my question is about is whether any practical difference here between creating a disk image from folder and creating a blank disk image. And if it is, then what is this difference. Note that a disk image should not be limited to a particular size. I want to be able to add there as many files as I want. That is, its size should be adaptive.

I have a medical CD that needs to be duplicated (explanation below). While trying to create a disc image, Disk Utility encountered an "input/output error". The complete message was "Operation failed with status 5: input/output error". The disk itself is fine. System info: Mac OS Ventura, MacBook Pro M1 with an external drive. * Reasons I need to figure this out: The medical centers cannot accept files via Google Drive link, download attached files, or a thumb drive. Requesting a duplicate copy is taking way longer than expected and we don't know how many needed).

I have downloaded /Applications/Install macOS High Sierra.app I'd like to burn an .iso file I can install in VirtualBox on a newer mac that runs Catalina. Thanks

I'm writing a program which is meant to be loaded and run exclusively from a FAT32 SD card. I need to create an SD card image for distribution as well as for testing the storage and retrieval of files through this program (also exclusively on the SD card). I want to use a BASH script to automate the creation of this IMG file which contains the binaries of my program. What command line program can I use to achieve this and how do I use it?

I have a mounted HFS+ disk image that I'd like to be equally accessible to all the user accounts on that system, in that they can all read and write files on it, create and delete files, and copy files into it that will be readable and writable by all the other users. This is all within a single system, and not over a network or using file sharing. Normally I'd handle this using "ignore ownership on this volume". However, when I set it on a mounted disk image, it a) seems to have no effect, in that other user accounts still can't modify files, and b) it resets as soon as the disk image is reloaded. Is this a limitation of disk images? Is there any way to get this to work?

When using hdiutil to create a backup image from a terminal in recovery mode (Command-R) hdiutil create -srcdevice /dev/disk3 /Volumes/backups/ where disk3 is the "synthesized" drive (see diskutil output below), should /dev/disk0 (internal, physical) be sourced instead? The image (.dmg) would be used for a full restore, although individual file browsing/restoration would be nice too (which seems like sourcing disk3 should provide for)? ___ -bash-3.2# diskutil list /dev/disk0 (internal, physical): #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme *500.3 GB disk0 1: EFI EFI 314.6 MB disk0s1 2: Apple_APFS Container disk3 500.0 GB disk0s2 /dev/disk1 (disk image): #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme +1.2 GB disk1 1: Apple_APFS Container disk2 1.2 GB disk1s1 /dev/disk2 (synthesized): #: TYPE NAME SIZE IDENTIFIER 0: APFS Container Scheme - +1.2 GB disk2 Physical Store disk1s1 1: APFS Volume macOS Base System 942.9 MB disk2s1 2: APFS Volume Preboot 81.3 MB disk2s2 /dev/disk3 (synthesized): #: TYPE NAME SIZE IDENTIFIER 0: APFS Container Scheme - +500.0 GB disk3 Physical Store disk0s2 1: APFS Volume Macintosh HD 11.8 GB disk3s1 2: APFS Volume Macintosh HD - Data 91.9 GB disk3s2 3: APFS Volume Preboot 3.6 GB disk3s3 4: APFS Volume Recovery 1.1 GB disk3s4 5: APFS Volume VM 20.5 KB disk3s5 --- [**Note**:](https://support.apple.com/guide/disk-utility/create-a-disk-image-dskutl11888/mac) You can’t create images of individual APFS volumes. You can’t create images of APFS containers on Mac computers with Apple silicon or an Apple T2 Security Chip.

I am trying to port an operating system development project to macOS. The problem here is that the project uses a tool called parted which is only available on linux, not macOS. The parted tool allows you to create a partition table on a disk image (.dmg). Add/Remove partitions and format that partition to types such as Master Boot Record. My goal is to find a macOS tool that is able to do the following: 1. Create partition table on an image 2. Create a new partition 3. Format that partition to be a Master Boot Record

I have an archived read-only Time Machine drive sitting on a NAS. It is a straight dump (made with dd) of a CoreStorage encrypted HFS+ hard disk. It's taking up 10TB, and I expect that the much of the data is eminently compressible, but of course, being encrypted, things like gzip will not be able to meaningfully compress the file itself. I would normally just try things myself before asking a question, but given the need for between 20TB and 30TB of scratch space to attempt this, I want to have a very good sense beforehand of whether this will work. My requirements are: - It should be compressed substantially more than it is in its 'raw dump' state. - It must remain legible to Time Machine for restores and browsing. - It must remain encrypted in some form. Nice to have: - It would be nice to be able to do this in a way that is both in-place and safely resumable. - In-place because I would really like to reduce the necessary scratch space on the NAS. - Resumable because while I do have a 10GbE nic in the NAS and 2.5GbE on my mac, but even at wire-speed just reading the image is 10 hours, and in practice going through the SMB and Btrfs layers to the actual disk, it is likely to take more like 30-40 hours just for a straight read and then write; it would be nice to be able to reboot in the middle and not lose progress if we have a power cut or something. Non-requirements: - I don't want the resulting file to be read/write. In fact I plan to make the file itself read-only; this is historical data, not a live backup of a current computer. My guess would be to do something like this:

hdiutil convert input.dmg -o output.dmg \
    -format ULMO \
    -encryption AES-128

so the question is: should I expect that to work, and to result in a usable disk image at this scale of data?

I have an old hybrid CD-ROM made of two track : on Windows only the ISO9960 track is visible and mounted, and on macOS only the HFS track is visible and mounted. This is how the CD appears in the Terminal using df and diskutil:

iMac:VINTAGE ouafouaf$ df -k
Filesystem                        1024-blocks       Used Available Capacity  iused               ifree %iused  Mounted on
...
/dev/disk4s1s2                         330576     330576         0   100%       99          4294967180    0%   /Volumes/Dragor le dragon

iMac:VINTAGE ouafouaf$ diskutil list
...
/dev/disk4 (external, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:        CD_partition_scheme                        *778.1 MB   disk4

I want to make an ISO image that is usable under Windows (XP). I tried to with dd and different attempts:

dd if=/dev/disk4s1s2 of=Dragor1.iso bs=2k
dd if=/dev/disk4     of=Dragor2.iso bs=2k
dd if=/dev/disk4s1   of=Dragor3.iso bs=2k

- case 1: I obtain a file of about 330MB, which I can mount on macOS but not on Windows. It appears that this is only the HFS track. Note that the image I get with Disk Utility (.cdr file) is about the same size - case 2: I obtain a file of about 760Mo, which I can not mount at all - case 3: I obtain a file of about 660Mo, that I can mount on both macOS and Windows (so it contains both tracks) So far so good (even if I don't really understand the meaning of s1or s1s2)... But for the use under Windows I don't need the HFS track. I have many images to create for using them in a Windows XP virtual machine, and I don't want to allocate too much disk space: how can I make an ISO image of the ISO9660 track only ? I tried making the image directly under Windows, but the tools I have tried all make an image of the entire disk, HFS track included.