E-Maculation

Sharing window in Fusion for dos is a pc transfer to Fusion ? If yes, i don't know how to start it.

Do you have the file sharing extension in your extensions folder? That dialog suggests you may not.

Which OS are you running in Fusion?

7.1.1

To share via BII, you'll need this then: http://macintoshgarden.org/apps/file-system-manager-12

For Fusion, you'll likely need to mount the disk image in BII and transfer things in/out that way, unless you've got a SCSI bridge and drive handy.

Fusion uses .HFx, where x can be 2 or 3 or 4 etc.
It can make other .HFx. My .HFx came from the below link :

Bootable OS7.1 System on a 240MB disk image. Fusion has to set to Mac_IIcx or another 7.1 compatible Mac.

http://macintoshgarden.org/apps/fusion-pc
I don't know if it can read .dsk files.

.HFx files are just raw HFS images, and use those file extensions so Fusion knows which SCSI ID to use for the drive image (0 to 7).

BII can read raw HFS images, including those labeled HFx. Both Disk Utility on OS X and qemu-img on all platforms can read raw HFS images and convert them to other formats.

qemu-img supports the following container formats: blkdebug blklogwrites blkreplay blkverify bochs cloop copy-on-read dmg file ftp ftps host_device http https luks nbd null-aio null-co parallels qcow qcow2 qed quorum raw replication sheepdog throttle vdi vhdx vmdk vpc vvfat

'raw' is the container format (essentially no container) your HFx images are in. Default for OS X is DMG, default for QEMU is QCOW, default for Parallels Desktop is parallels, default for VMWare is VMDK, default for BOCHS is bochs, default for VirtualBox is VDI, default for Virtual PC is VPC, etc.

.dsk is usually just a HFS raw image with the extension .dsk instead of .hfx, although sometimes it's got a Disk Copy header in front of the HFS file.

adespoton wrote:.HFx files are just raw HFS images, and use those file extensions so Fusion knows which SCSI ID to use for the drive image (0 to 7).

BII can read raw HFS images, including those labeled HFx. Both Disk Utility on OS X and qemu-img on all platforms can read raw HFS images and convert them to other formats.

qemu-img supports the following container formats: blkdebug blklogwrites blkreplay blkverify bochs cloop copy-on-read dmg file ftp ftps host_device http https luks nbd null-aio null-co parallels qcow qcow2 qed quorum raw replication sheepdog throttle vdi vhdx vmdk vpc vvfat

'raw' is the container format (essentially no container) your HFx images are in. Default for OS X is DMG, default for QEMU is QCOW, default for Parallels Desktop is parallels, default for VMWare is VMDK, default for BOCHS is bochs, default for VirtualBox is VDI, default for Virtual PC is VPC, etc.

.dsk is usually just a HFS raw image with the extension .dsk instead of .hfx, although sometimes it's got a Disk Copy header in front of the HFS file.

Ok

.sea files can be put inside with HFVexplorer. I will check other file types.

Just a note: .sea is a format that contains a resource fork. If you copy these to a non-HFS volume, that fork will be lost.

Of course, most decompression software will still extract the archive from the data fork if it's a known archive type, but the guest OS will consider them damaged if you attempt to double click them.

.sea stands for Self Extracting Archive, and is usually a stuffit archive with an extractor in the resource fork. But it could also be a Disk Copy self extracting archive, and these can be trickier to extract if you lose the resource fork.