Re: Want to go from a nvidia card to ati card, what problems can i expect?
On Sat, 10 Nov 2007 18:04:17 +0000, ATIuser
<atiuser@privacy.invalid.com> wrote:
>
>On Sat, 10 Nov 2007 15:36:14 +0000 'Steve Evans'
>wrote this on alt.comp.periphs.videocards.ati:
>
>>On Sat, 10 Nov 2007 12:49:20 +0000, ATIuser
>><atiuser@privacy.invalid.com> wrote:
>>>If you uninstalled .NET, were you still able to install ATI drivers?
>
>
>>No, he probably just went for a driver only install.
>>I always do a system image before anything major, like installing .net
>>for example, but to be honest, I don't know what all the fuss is
>>about. With a bit of registry and services tweaking after installing
>>the .net and ati drivers, I was able to get rid of most of the
>>memory-hogging crap, and as stated before, get my memory usage pretty
>>much as it was before the installation.
>>
>>It's only a problem for those that don't know how to tweak yet still
>>look at their system resource usage......
>
>IIUC, it's possible to install ATI drivers only without .NET and
>not to bother with CCP ...probably using ATI Tray Tools instead?
>
Yes, I'm pretty certain you don't need .net for drivers only, and tray
tools will allow control over the driver settings.
>It would be helpful if you posted a list of the changes you made
>to registry/services after installing, and I assume that still left
>.NET installed?
Run regedit and look in these locations pre and post drivers install.
HKEY_CURRENT_USER\Software\Microsoft\Windows\Curre ntVersion\Run
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\Run
Run services.msc and do the same, making a note of what is there pre
and post install.
Most of the stuff that get's added to those locations *should* be ok
to delete/disable.
Re: Want to go from a nvidia card to ati card, what problems can i expect?
On Nov 10, 4:49 am, ATIuser <atiu...@privacy.invalid.com> wrote:
> On Fri, 09 Nov 2007 23:55:44 -0800 'Red Cloud'
> wrote this on alt.comp.periphs.videocards.ati:
>
>
>
>
>
> >On Nov 6, 7:23 am, ATIuser <atiu...@privacy.invalid.com> wrote:
> >> On Tue, 06 Nov 2007 09:21:41 -0500 'Mike Ray'
> >> wrote this on alt.comp.periphs.videocards.ati:
>
> >> >ATIuser wrote:
> >> >> On Mon, 05 Nov 2007 01:32:39 +0000 'Steve Evans'
> >> >> wrote this on alt.comp.periphs.videocards.ati:
>
> >> >>> I've gone from 9800 to x850xt to x1950pro, and all cards have
> >> >>> performed well for me. I like to run a very quiet system, so it is an
> >> >>> added bonus that the last 2 cards on the list have been 'silenced',
> >> >>> using the fan tweak feature, on the excellent ati tray tools.
> >> >>> Don't worry about having to install .net 2, or the ati control centre,
> >> >>> as these memory hogs can be brought under control with a bit of
> >> >>> registry/service editing!
>
> >> >> Are you saying that it's possible to install an ATI X1950 card and
> >> >> drivers *without* installing .NET? That would interest me since my
> >> >> current ATI card (9800Pro) doesn't need .NET but afaik the later
> >> >> ones do and I don't have it installed.
> >> >Somewhat OT but what is the problem with .NET? (I ask because I just
> >> >installed it for PAINT.NET) Are you just trying to run a very 'lean'
> >> >system without extra junk or are there issues with .NET?
>
> >> Yes, I do like to run a lean machine and have ripped out large
> >> unneeded parts of my XP-Pro-SP2 system. But also.....
>
> >> There are no (tech) issues with .NET that I know of except that it
> >> is *yet another fat layer* of MS bloat and seemingly it's primarily
> >> beneficial to s/w developers, not end users.
> >> Some folks think it's the thin end of the wedge from MS to
> >> discreetly push another corporate goal: more web based services,
> >> software and even op/sys thereby turning your local system into
> >> little more than a dumb terminal. Imagine the day when to use
> >> your Windows system, you have to be logged on to MS for dynamic
> >> authentication. Not far off if MS get their way. There's a whole
> >> army of users who are against .Net for these reasons.
>
> >> <back to ATI cards>
> >> If I could install an x1950 or similar in my next build w/o having
> >> to install .NET to install the driver package, I'd want to do that.
> >> I e-mailed nVidia a while back and *their* drivers do not need
> >> .NET to install. hhmmm.- Hide quoted text -
>
> >> - Show quoted text -
>
> >Yeah I was quite bother by .NET. I was thinking what the hell is that
> >and why
> >I've to install that. I couldn't install ATI driver with .NET??? NO
> >no I got it around.
> >Uninstalled that MS NET.
>
> If you uninstalled .NET, were you still able to install ATI drivers?- Hide quoted text -
>
> - Show quoted text -
Ati Radeon and Window Media Player Version 10 do NOT work
together!!!
I deleted Ati genuine drivers. Instead I installed Omega driver, not
require MS .NET stuff..But I still had MS problem with Window Media
Player 10. WMP 10's codec on S-video output does not fully function
100%. ATI Radeon card and WMP 10 do not work together!!!! So I
rolled back Windows media player to version 9. Now it's work perfect.
Does anyone know why WMP 10 have problem
with Ati Radeon card displaying TV signal through S-video output ?
nVidia video card have no problem of such...
Re: Want to go from a nvidia card to ati card, what problems cani expect?
* Mike Ray:
> Somewhat OT but what is the problem with .NET?
The problem with .NET is that most users don't have a ****ing clue what
it really is and therefore are afraid of it for no reason. Some people
also think .NET is for DRM or for web-based services only (which despite
the name it's not).
..NET is nothing more than a framework consisting of a runtime
environment, class libraries and services that is much more flexible and
versatile than using outdated technologies like COM. It's not "yet
another fat layer of MS bloat", in fact it makes software development
more streamlined and efficient. The .NET framework does nothing bad if
you don't have any .NET programs installed.
Since .NET is a replacement for all the outdated things like COM it will
be an increasingly important part of modern Windows programs, even today
lots of applications rely on .NET. Staying away from .NET means also to
stay away from a lot of future applications (and games, too).