[–] 5 points 1 week ago

I remember building a computer in 2004 and finally making the decision to not include a floppy drive since I had just been booting from the CD drive for the past couple of issues anyways.

I was reminded of this several years later when I made the decision not to include a disk drive in my latest build.

  • source
  • parent
  • context
  • [–] 32 points 1 week ago (7 children)

    The manufacturer is labeling the drive correctly as 1TB (1000GB, 10^(12)B). It's Microsoft that incorrectly labels it as 931GB; it's actually 931GiB (931 * 2^(30)B). A Mac will correctly show 1000GB and a Linux machine will correctly show 931GiB.

  • source
  • parent
  • context
  • [–] 2 points 1 week ago

    Oh, it was absolutely meant unionically on my part. We had a conversation last week about how some people even take their notebook with them on vacation. Colleague said he'd kick me if I ever got that idea.
    Glad I'm at such a place.

    I'm a network admin though and don't have many special things going on most of the time. So any handovers are white short usually.

  • source
  • parent
  • context
  • [–] 2 points 1 week ago (2 children)

    I really love how this really applied to basically everything, the more you know about Linux for example – the most you are happy that something worked instead of asking HOW it works

    I'm talking to you, RAM memory!

  • source
  • [–] 58 points 1 week ago (17 children)

    The OS uses 1024 and the drive manufacturers are using 1000.

    Which is why a 1TB drive shows 931GiB of capacity. (1024 GiB =1 TiB, 1024MiB =1 GiB, 1024KiB =1MiB, 1024 Bytes =1KiB) but the drive manufacturers using SI prefixes doing 1000 Bytes =1 KB, 1000 KB = 1MB, 1000MB = 1GB, 1000GB = 1TB.

    Thus the discrepancy.

  • source
  • [–] 1 point 1 week ago

    I'm not fully sure, but it looks very much the type of image that would be AI generated. On the bottom right the people look like they have faces in the back.

    No signature (might have been cropped), but generally Artists sign their art. The poster has a slop profile picture, and this is a very low-effort post.

  • source
  • parent
  • context
  • [–] 1 point 1 week ago* (last edited 1 week ago)

    The upper letters have also lost their use with UNC paths. in the 2000's and 2010's, we had so many drive letters at my workplaces. I hardly used any of them, but they still mapped a bunch by default for departments that still relied on them. Now they're on NAS drives or SharePoint, which you can just access without mapping. I just pinned the ones I use in File Explorer so they're there but not "mapped".

    I still have an F: drive on my current company machine for some reason. It used to be a network home directory backup, but after OneDrive, I'm not sure where it points or why it still exists. Because I'm the sort of person who sees a YouTube video about what happened to Novell Netware and immediately click play, I recently learned that F: was the typical home drive letter for Novell Netware, with company/departmental share drives starting with G: or later. (https://support.novell.com/docs/Tids/Solutions/10027779.html) I remember in the early 2000's people still calling those drives and the login screen "Novell" even though it was Windows NT and NT shares by that point.

  • source
  • view more: ‹ prev next ›