When fixing a non-hyper-allocated message base, the newly created .sha
(header allocation) file would contain one extra zero-record because I
wasn't accounting for the SMB/status header (32 bytes) in the .shd file
when I was initialing the new .sha file. This explains chksmb warning
	!Size of SHA file (x) does not match SHD file (y)
after running fixsmb on a message base.