@robotspacer - for BlueSCSI, a .DSK is fine. BlueSCSI handles many types. And Disk Copy images (both 4.2 and 6.x types) do not strictly require any resource fork data to be mounted, so even if it's lost in translation, the disk should work anyway—on a BlueSCSI, at least. On a Mac, you'd have to change the creator and file type for the file to be recognized. Disk Copy 6.x would complain that the checksum is missing from the absent resource fork, but it could still be mounted.