Exactly.
I remember regularly reinstalling Windows 98 to clean things up and then
only installing a few programs at a time trying to figure out which one
was screwing up the others. It was a total PITA.
Yah, as others have said you shouldn't uninstall them. There's supposed to
be lots and lots of them, I've a couple of dozen installed on my machine.
You can have problems with updated versions of the Microsoft C++ runtime
breaking programs, but you can also have problems with old buggy versions
of the runtime breaking programs.
If nothing is broken, do not try to fix it.
Ross Ridge
--
l/ // Ross Ridge -- The Great HTMU
[oo][oo] rri...@csclub.uwaterloo.ca
-()-/()/ http://www.csclub.uwaterloo.ca/~rridge/
db //
>Half of that clan I mentioned consisted of people who, if you gave
>them access to IRQ jumpers they would probably find a way to get their
>PC in a state where it wouldn't run games at all without freezing,
>then they would spend the next 3 months constantly reformatting their
>hard drive to fix the problem and "get that virus offa there!". lol.
After I typed that I started remembering certain instances of that
scenario above, and literally started laughing out loud. Partially at
the comic value of some of the shit these guys used to do to their
poor PCs, but I guess also I was laughing at relief that I am no
longer actively managing a clan so I don't deal with it on a daily
basis. Ahh..good times.
The same guys that would fuck their PC up the worst were the same guys
that would curse Microsoft on a weekly basis for what a crappy OS it
is! lol
Over the years I've learned that categorically, there is a 1-1
correlation between people who badmouth Windows or Microsoft in
general, and lack of technical knowledge. So whenever you hear
someone cursing Windows, they are mostly a "tweakster" -- a technical
danger to themselves and others.
In those days the way around DLL hell was to install DLLs in the program
directory rather than the system directory. But that was an even bigger
waste of disk space, and not all installers would let you.
- Gerry Quinn
> Someone who cares more about meeting a deadline based on fiscal
> quarters than making sure all the bases are covered. So, not counting
> the one-man-software-company kind of app or utility where one guy
> tries to do everything (and probably does most of it poorly as a
> result of spreading himself too thin), blaming the developers for this
> is about as misaligned as you can get.
The one-man software company apps rarely do much harm to your system.
It's always the big products that mess you up.
- Gerry Quinn
True. Thats because the same person who makes the financial decisions
and has the last say on quality assurance also has to be the same
person who supports the app.
>Why can't MS just collected all the needed bits from
>"Microsoft Visual C++ Redistributable" packs of all vintages
>& bundle them into a update-able unit like DirectX ?
>Which has a standard little installer that checks if any additions are
>needed
>& installs them ?
Its sort of like that now. Just as there are multiple versions of
DirectX, there are multiple versions of VC++ redist.
Haven't you noticed that some games install DirectX even though you're
pretty sure you've already got every version on the planet on your
system?
Aside from that, it is just a generally accepted belief that the
packaging specialist or install package builder is better off to
include everything that is needed to install the game on a bare-bones
system. If he did not, and said "lets assume they already have VC++
and it is accessible via the registry" he runs the risk of his
assumption being wrong, then someone will inevitably say "why did they
assume I already have something I dont? Its stupid not to include
everything I need to run the game in the installer!" and similar
whining.
So why doesn't Microsoft just have one grand pack of files that's on
all Windows machines? Because things like the VC library evolve over
time. Features are added, bugs fixed, things optimized. Sometimes
those changes break backward compatibility, so if one central
all-knowing library sat centrally in some OS location, and a game is
written to run against that in the year 2008, that library will have
evolved such that in the year 2011 games written three years ago might
not work against it. So it makes more sense for the game to install
and maintain its own copy of the 2008 version.
I am trying to simplify things a bit to avoid going into deep
discussions of polymorphism, the history of COM and the Windows OS
itself, and the challenges of maintaining backward compatbility in the
world of professional software development.
The alternative is to just pull an Apple move and say "fuck it, we
broke backward compatibility and you're all screwed, buy the new
version and quit yer bitchen".
It's called Windows Update.