http://blog.stealthpuppy.com/hall-of-shame/intel-graphics-and-the-dynamically-generated-dll IT infrastructure blog Wed, 07 Jan 2009 00:48:48 +0000 http://wordpress.org/?v=2.6.3 http://blog.stealthpuppy.com/hall-of-shame/intel-graphics-and-the-dynamically-generated-dll#comment-4320 chris lively Fri, 14 Sep 2007 20:13:02 +0000 http://blog.stealthpuppy.com/uncategorized/intel-graphics-and-the-dynamically-generated-dll#comment-4320 The thing is, Microsoft has standard directories for this garbage under AppData (vista) or Application Data (xp). Dynamically creating a new directory structure is about dumb. Further, the drivers could read this from the OS on the initial installation. It doesn't need to consume resources creating the same file every single time you log in. The thing is, Microsoft has standard directories for this garbage under AppData (vista) or Application Data (xp). Dynamically creating a new directory structure is about dumb. Further, the drivers could read this from the OS on the initial installation. It doesn’t need to consume resources creating the same file every single time you log in.

]]> http://blog.stealthpuppy.com/hall-of-shame/intel-graphics-and-the-dynamically-generated-dll#comment-3528 ladiko Sun, 02 Sep 2007 16:24:38 +0000 http://blog.stealthpuppy.com/uncategorized/intel-graphics-and-the-dynamically-generated-dll#comment-3528 thank you for the advice about moving it to the system32-folder. i also hate files laying somewhere they dont need to be. thank you for the advice about moving it to the system32-folder. i also hate files laying somewhere they dont need to be.

]]> http://blog.stealthpuppy.com/hall-of-shame/intel-graphics-and-the-dynamically-generated-dll#comment-274 singergr Thu, 28 Jun 2007 12:29:23 +0000 http://blog.stealthpuppy.com/uncategorized/intel-graphics-and-the-dynamically-generated-dll#comment-274 I ran into this the other day. If you look in system32, you'll see a whole bunch of files with names like igfxenu.lrc, igfxdeu.lrc, and so forth. What's actually happening is that the Intel driver is checking the user's language settings when they log on, then selecting the appropriate .lrc file and copying it to igfxres.dll. Also, at least with the latest Intel driver, it does make an effort to copy the file into system32. If the user doesn't have Administrator privileges, this won't work, so the driver creates that obnoxious directory tree as a fallback. If the root directory has more limited permissions than usual, this doesn't work either, leaving people with the ugly desktop context menu in your second screenshot. I ran into this the other day. If you look in system32, you’ll see a whole bunch of files with names like igfxenu.lrc, igfxdeu.lrc, and so forth. What’s actually happening is that the Intel driver is checking the user’s language settings when they log on, then selecting the appropriate .lrc file and copying it to igfxres.dll. Also, at least with the latest Intel driver, it does make an effort to copy the file into system32. If the user doesn’t have Administrator privileges, this won’t work, so the driver creates that obnoxious directory tree as a fallback. If the root directory has more limited permissions than usual, this doesn’t work either, leaving people with the ugly desktop context menu in your second screenshot.

]]>