Watch out for this scam
Watch out for this scam


Watch out for this scam
Wait until they find out how much space is on their 2TB SSD...
That difference is because the drive manufacturer advertises capacity in Terabytes (or Gigabytes) and the operating system displays drive capacity in Tebibytes (or Gibibytes). The former unit is based on 1000 and the latter unit is based on 1024, which lets the drive manufacturer put a bigger number on the product info while technically telling the truth. The drive does have the full advertised capacity.
Hz are Hz though
Hz are Hz though
8 Hitz = 1 Hert
the drive manufacturer advertises capacity in Terabytes (or Gigabytes) and the operating system displays drive capacity in Tebibytes (or Gibibytes). The former unit is based on 1000 and the latter unit is based on 1024, which lets the drive manufacturer put a bigger number on the product info while technically telling the truth.
I understand why storage manufacturer do this and I think it makes sense. There is no natural law that dictates the physical medium to be in multiples of 2^10. In fact it is also the agreed upon way to tell clock speeds. Nobody complains that their 3 GHz processor only has 2.X GiHz. So why is it a problem with storage?
Btw, if you want to see a really stupid way to "use" these units, check the 3.5" floppy capacity:
The double-sided, high-density 1.44 MB (actually 1440 KiB = 1.41 MiB or 1.47 MB) disk drive
So they used 210 x 103 as the meaning of "M", mixing them within one number. And it's not like this was something off in a manual or something, this was the official capacity.
I believe OP was referring to the space lost after the drive is formatted. Maybe?
Bet even if you actually get the number of bytes from the raw block device, it won't match that advertised number.
Drive manufacturers aren't really at fault here. As long as you use the proper units everything is in order. There is no reason for drives to be an exact power of two, so TiB and 1024 don't really make sense here. The biggest offender and the only big player that still does it wrong is Microsoft by using non-standard units. The history behind the 1000/1024 confusion is IMHO really interesting: https://zeta.one/kilobyte-is-1000-bytes/
Does anyone ever actually use those prefixes? I've personally just couched the difference into bytes vs bits.
There is also reserve space for replacing bad sectors
oh no
Television is 29.97 fps.
NTSC is? I don't even remember this shit anymore lol
Original black and white NTSC television was 30fps interlaced. You got a half frame, every other scan line, every 60th of a second, so a full field was painted every 30th of a second. Why 30 instead of 24 like film? Because US electrical power is 60Hz. That could be used as a convenient timebase to sync signals with.
Adding color to that existing standard while still maintaining compatibility with existing black and white TVs was doable by very slightly decreasing the frame rate to 29.97, which was within the vertical sync tolerance of a television. worst case scenario you'd have to slightly turn the V Hold knob on the back of the TV set. The only 20th century analog video tech that was truly 60fps color video was VGA, a true RGB signal which AFAIK was never sent over the air.
Maybe your TV. Mines multilinghz
They terk our hertz.
Dey terk er hertz.
Trk r hrtz
I'd love to know the technical reasoning for this. It probably has to do with clock frequency multipliers like when doing serial comms your baud needs to be pretty close to the spec but it's pretty much never going to be exact.
I've only partially researched this, but I'm pretty sure it's actually an ancient carry over from when NTSC changed to colour. Wikipedia says it switched from 60hz to 59.94 "to eliminate stationary dot patterns in the difference frequency between the sound and color carriers". They just kind of kept doubling it and we ended up with these odd refresh rates, I'm guessing for NTSC TV compatibility.
Someone's never bought a 2x4
I hate that your right
My one frame every 50 sec is very important to me.
Blame NTSC
Good ol' Never Twice the Same Color
I wonder why they like never compute these things correctly, it's usually that you need to keep the reminder of last frames' "hz" and add it to the next frames computation.
Or just wing it and round it.
That's packed on backwards, before people even knew about KiB or it even existed(?) the drive companies pulled that scam that 1000B=1kB. So now it's no longer a scam per se, just IMO misleading.