redwolfe_98
join:2001-06-11 | reply to SUMware
Re: .NET Framework Rootkits
i agree with you, netfixer.. i hate having "NETFramework" installed, but my ati (video card) driver-package requires it..
as far as i know, hewlett-packard "printer" driver-packages also require "NETFramework".. |
|
OZO
Premium
join:2003-01-17
1 edit | What if you will install driver only - does it require .NET too? |
|
redwolfe_98
join:2001-06-11
 ·RoadRunner Cable
1 edit | said by OZO  :What if you will install driver only - does it require .NET too? the ati driver, alone, does not require NETFramework, but the "catalyst control center" does require it..
i am not that familiar with working with "hewlett-packard" drivers, so i don't know if you can work around not having "NETFramework", with them, or not.. in my experience with installing the regular HP driver-packages, which is the only ones that i have used, NETFramework is installed as part of the installation-process, when the drivers are being installed.. |
|
NetFixer
Freedom is NOT Free
Premium
join:2004-06-24
Murfreesboro, TN
 ·Vonage
 ·Cingular Wireless
·AT&T CallVantage
 ·AT&T Southeast
1 edit | reply to redwolfe_98
said by redwolfe_98 :i agree with you, netfixer.. i hate having "NETFramework" installed, but my ati (video card) driver-package requires it.. as far as i know, hewlett-packard "printer" driver-packages also require "NETFramework".. That sux for you. 
Fortunately for me, the ATI video cards and HP printers in use on my Windows 2k & XP systems work just fine using the builtin O/S drivers (the same applies for my Linux systems), so no .NET crap was required on my Windows systems. I did try the ATI supplied RADEON package on one PC, but the overhead and security risks of the .NET crap made me remove it after a brief test. I saw no benefit to me for using the bloated ATI package.
--
A well-regulated militia, being necessary to the security of a free State, the right of the people to keep and bear arms shall not be infringed.
»portscan.dcs-net.net
»nature-pics.com |
|
OZO
Premium
join:2003-01-17
| reply to redwolfe_98
If in the printer package you have a folder with *.INI file along with set of other files (usually with *.dl_ extensions) you may install the driver directly. In this case you do not have to run any "setup" program from the package (and it will not install any .NET). That's the way I install my drivers. |
|
salzan
Experienced Optimist
Premium
join:2004-01-08
WA State
| reply to redwolfe_98
said by redwolfe_98 :the ati driver, alone, does not require NETFramework, but the "catalyst control center" does require it.. You can use ATI Tray Tools instead of the Catalyst Control Center. No need of .NET for ATI cards.
I have avoided .NET completely. |
|
AB
Premium
join:2006-04-04
Leesburg, VA
| reply to redwolfe_98
said by redwolfe_98 :. . i am not that familiar with working with "hewlett-packard" drivers, so i don't know if you can work around not having "NETFramework", with them, or not.. in my experience with installing the regular HP driver-packages, which is the only ones that i have used, NETFramework is installed as part of the installation-process, when the drivers are being installed.. The HP AIO printer I use (1200 series, which is an older one) has no reliance upon .NET Framework. |
|
