Jump to content

Recommended Posts

Posted

ok this is bul***** !

the folder under C:\Windows\System32 is EMPTY

yet all files seem to be dumped into

 

C:\Windows\assembly

and

C:\Windows\Microsoft.NET\DirectX for Managed Code

 

is this meaning that DX is no more native but shitty .net library set ?

 

what if I want to yank out .net 2 out of win7 completely (and I will try)

- yes I will break DWM, but I expect OS to revert to ordinary UXTHEME (XP) then

- explorer should live without it as its not written in managed code (aka .net)

 

but what about DirectX ?


Posted

C:\Windows\System32\directx is empty

 

 

Also I don't understand the anger about where DirectX files are located...

 

If i want yank out .net completely then DX will be issue as it is linked to freaking .net

Posted

It's been awhile sine I've looked much at DirectX, but IIRC Windows 7 has never had a C:\Windows\System32\directx folder. Never. I believe that the DirectX DLL's are in C:\Windows\System32, and also in C:\Windows\SysWOW64 for Windows 7 x64.  I believe that the only connection between DirectX and .NET is the optional DirectX for Managed Code, at least that's the way it used to be, and you very rarely hear much about that any more.  Why are you convinced of the connection between DirectX and .NET?
 
And like Trip, I don't understand your current anger about DirectX.  The way DirectX works in Windows 7 hasn't changed since Windows 7 first came out, so why get mad now, 6 years later?  I mean, I know you like to play the role of a bitter, angry old (young?) man, but still...

 

Cheers and Regards

Posted

its not anger towards dx ... but toward .net

do you guys even read what was written above ? (2 times)

 

but now that I see all relevant dx files are in sys32 then this topic is concluded :P

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...