this post was submitted on 16 Jun 2023
11 points (100.0% liked)

Technology

37719 readers
104 users here now

A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.

Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.

Subcommunities on Beehaw:


This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.

founded 2 years ago
MODERATORS
 

I've been wondering this for years. I remember some years ago I was wondering why in the world an audio driver needs to be 500 MB big. Now we're almost at 1 GB.

What gives?

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 3 points 1 year ago

That is a PKzip-style self extracting archive, so running unzip on it works the way you'd expect. I ran the same string of commands on it that I did on the archive downloaded from Intel, and it looks like NNResources64.dll is the culprit, clocking in at 193 megabytes. The next biggest file in the archive is RTAIODAT.DAT, which weighs in at a comparatively svelte 55 megs.

I have no idea why they need to be that big. It makes no sense to me.