You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Say you have a SD card split 7 ways, 2GB each, each formatted by a Kurzweil K2000. The K2000 uses a FAT16 file system that both Windows and Mac can mount, although it doesn't use a partition map on Sector 0 as is common elsewhere. (Not having a partition map is a legal thing.)
Taking that SD card and putting it in a standard card reader, hooked to a Mac or Windows, each mount the first drive (starting at Sector 0) successfully (Mac gives it a Volume name 'Untitled', Windows gives it a drive letter), and operates on it fine.
If you put that SD card in a ZuluSCSI v6.4 (or SCSI2SD v6.0), and hook it up to a Mac, it mounts all 7 drives, as it's supposed to.
However, doing the same with Windows, the drives are detected but Windows does not 'mount' them; that is, does not give them a drive letter, and when looking at them in Disk Management, it first gives a dialog saying "drives must be initialized", then when cancelled, all 7 drives show as Unallocated.
Maybe this is a Windows problem, but why would Windows behave "properly" using a regular card reader but not react properly using ZuluSCSI v6.4 (or SCSI2SD v6.0) as a card reader? It seems perhaps something could be done in ZuluSCSI v6.4 firmware that could correct this.
The text was updated successfully, but these errors were encountered:
Say you have a SD card split 7 ways, 2GB each, each formatted by a Kurzweil K2000. The K2000 uses a FAT16 file system that both Windows and Mac can mount, although it doesn't use a partition map on Sector 0 as is common elsewhere. (Not having a partition map is a legal thing.)
Taking that SD card and putting it in a standard card reader, hooked to a Mac or Windows, each mount the first drive (starting at Sector 0) successfully (Mac gives it a Volume name 'Untitled', Windows gives it a drive letter), and operates on it fine.
If you put that SD card in a ZuluSCSI v6.4 (or SCSI2SD v6.0), and hook it up to a Mac, it mounts all 7 drives, as it's supposed to.
However, doing the same with Windows, the drives are detected but Windows does not 'mount' them; that is, does not give them a drive letter, and when looking at them in Disk Management, it first gives a dialog saying "drives must be initialized", then when cancelled, all 7 drives show as Unallocated.
Maybe this is a Windows problem, but why would Windows behave "properly" using a regular card reader but not react properly using ZuluSCSI v6.4 (or SCSI2SD v6.0) as a card reader? It seems perhaps something could be done in ZuluSCSI v6.4 firmware that could correct this.
The text was updated successfully, but these errors were encountered: