마이크로 소프트의 Hardwaare white paper 에 보시면 모든 답이 있습니다.
FAT: General Overview of On-Disk Format
계산이 잘못되고 그런적은 없던거 같습니다.
계산을 잘못한적은 많은데...ㅋㅋㅋ
윈도에서 FAT16(?), 32(?) 로 포맷하시고...MBR(Master Boot Record)
확인하시고, 부트영역 가보시면 모든 정보 있습니다.
Hex Work**** 같은 프로그램으로 확인해 보시면 됩니다.
BPB_SecPerClus
------------------
Number of sectors per allocation unit. This value must be a power
of 2 that is greater than 0. The legal values are 1, 2, 4, 8, 16, 32, 64,
and 128. Note however, that a value should never be used that
results in a “bytes per cluster” value (BPB_BytsPerSec *
BPB_SecPerClus) greater than 32K (32 * 1024). There is a
misconception that values greater than this are OK. Values that
cause a cluster size greater than 32K bytes do not work properly; do
not try to define one. Some versions of some systems allow 64K
bytes per cluster value. Many application setup programs will not
work correctly on such a FAT volume.
FAT: General Overview of On-Disk Format
계산이 잘못되고 그런적은 없던거 같습니다.
계산을 잘못한적은 많은데...ㅋㅋㅋ
윈도에서 FAT16(?), 32(?) 로 포맷하시고...MBR(Master Boot Record)
확인하시고, 부트영역 가보시면 모든 정보 있습니다.
Hex Work**** 같은 프로그램으로 확인해 보시면 됩니다.
BPB_SecPerClus
------------------
Number of sectors per allocation unit. This value must be a power
of 2 that is greater than 0. The legal values are 1, 2, 4, 8, 16, 32, 64,
and 128. Note however, that a value should never be used that
results in a “bytes per cluster” value (BPB_BytsPerSec *
BPB_SecPerClus) greater than 32K (32 * 1024). There is a
misconception that values greater than this are OK. Values that
cause a cluster size greater than 32K bytes do not work properly; do
not try to define one. Some versions of some systems allow 64K
bytes per cluster value. Many application setup programs will not
work correctly on such a FAT volume.