By using this site, you agree to our Privacy Policy and our Terms of Use. Close
SvennoJ on 26 February 2019
Edit Thread
Bofferbrauer2 said:
SvennoJ said:

I guess, it says dedicated video memory 6144 MB GDDR5, total available 14257 MB (shared system memory 8113 MB)

Who knows, the 32 GB flash card is actually 28.8 GB
The 256 GB SSD is actually 237 GB
The 1TB HDD is actually 931 GB

Cutting corners everywhere!

Who knows, the 32 GB flash card is actually 28.8 GiB
The 256 GB SSD is actually 237 GiB
The 1TB HDD is actually 931 GiB

For those who don't know, GB and GiB are 2 different things and also pronounced differently. GB would be Gigabyte, while GiB would be Gibibyte. 32 GB would be 32*10^9 bytes while 32 Gibibytes would amount to 2^35 bytes. This is also the reason why a 1TB HDD for instance only shows up as 932 GiB. That's nit just due to formatting the HDD, but due to conversion, as 1KiB is 1024 bytes but 1 KB is just 1000 bytes

I know about the trickery of marketing, still doesn't add up though

32*1000*1000 / 1024*1024 = 30.5 GB
256 -> 244.1 GB
1 TB -> 953.6 GB

Ah it fits if you convert to terabyte, dividing it by (1024*1024*1024)

32 -> 0.0298 TB
256 -> 0.238 TB
1TB -> 0.931 TB
Sneaky!

Still not correct for the USB stick, however that might explain why the creation of a recovery drive failed. Perhaps it has some bad sectors that automatically got fix in the scan and verify process that kept popping up after the recovery drive creation failed. The makes the drive useful by I guess flagging the bad sectors, reducing the total capacity. However when creating a recovery drive it does a quick format first without checking, then gets write errors when it gets to the bad sectors.