Re: .Net = 90MB+, 30 seconds longer+, Internet Explorer IS spyware

"Karl E. Peterson" <karl@xxxxxxxx> commented...
: all it does here is this:
: ---------------------------
: The dynamic link library mscoree.dll could not be found in the specified
: path
: C:\WINNT\TEMP\Rar$EX01.437;.;C:\WINNT\system32;C:\WINNT\system;C:\WINNT;C:\P
: rogram Files\WinRAR; ...

"Ian R" <ianr@xxxxxx> stated...
: But in all fairness you would get similar results if you ran a
: VB6 application without the runtime installed. When VB6
: first came out the runtime wasn't shipped on 9x and NT4.

I recently installed .Net 2.0. After a week where the boot time
of the system increased by 30 or more seconds upon each re-
boot, and overactive network activities, and strange things run-
ning in the background, I noticed that .Net 2.0 never finished
installing itself.

I started doing some research and I found the following folder:

C:\WINDOWS\Microsoft.NET\Framework

And inside that folder existed two subfolders (version numbers):

v1.0.3705
v2.0.50727

I thought I noticed at least 90MB of files in the latter folder above.
However, I uninstalled .Net 2.0 because the whole system started
running into some instabilities with the video drivers. I didn't under-
stand where the video drivers come into play, so I decided to look
for the latest release of video drivers (a well know video card ATI).
The latest release of the drivers required .Net. So I installed those
as well, but the video instability didn't go away.

I ended up uninstalling .Net 2.0 and reinstalling the older video
drivers. And the system started working like a champ once again.

Anyways, installing .Net had the same adverse system affects it had
in the past when I installed it on Windows 98 systems. The bootup
times on those systems increased substantially, and installation
problems (or .Net problems) ran amuck, so effectively I ended up
never installing .Net on any Windows 98 preinstalled system and
that made a stores return ration drop from 50% to less than 1%.
People were happier without .Net back then and I'm happier
without .Net today.

Back then, the only thing .Net was Microsoft installation of .Net
and nothing ran .Net. Today, vendors (like ATI and Microsoft) get
people to install .Net in order to force sales of upgrades. Today,
Microsoft creates fear by building their "antispyware" software
with .Net and trying to force people into .Net. However, as we'll
soon see, Microsoft SHOULD NOT be trusted when it comes
to antispyware software.

The biggest vendor of spyware builds operating systems and
the biggest spyware product running around in the world today
is called Internet Explorer. This in no way represents any bash
against the company, Microsoft and in no way represents any
sort of degradation of the company. They do what they do
and they bring it upon themselves.

To demonstrate that Internet Explorer is spyware, just get your
system to lock down Internet Explorer (and Explorer) and notice
what happens when you open any application that uses Internet
Explorer to effectively spy. You'll find that your firewall catches
..CHM files trying to make contact with Microsoft (and possibly
other companies if the HTML files inside it were designed to do
such things), and you'll find other applications, making contact
with other organizations (Axialis, Logitech, etc).

Since Microsoft took over SysInternals website, applications
on their website provide a really good demonstration of objects
which offer a good demostration of identifying Internet Explorer
as spyware (applications that try to secretly make contact through
Internet Explorer).

One thing I noticed, about the AutoRuns software, is that after
deleting the new AutoRuns from the system, and then running the
old version of AutoRuns, while I haven't tracked down what
exactly went on, if it was something in a prefetch cache some-
where on the hard disk that was running, or if it was a registry
key I deleted from the registry (that the new MS AutoRuns
put there), AutoRuns seemed to be running from the newer
version of the file (trying to make contact with Microsoft). I
have since deleted both the New Version of AutoRuns and
one of the registry keys installed by it. So it could have either
started up from a prefetch cache or perhaps something inside
the registry caused the contact to get induced.

Going to sysinternals.com now takes you directly to Microsoft.
And most of the software now uses Internet Explorer to
secretly make contact with Microsoft, identifying Internet Explorer
as the most widely deployed SpyWare product the world ever
knew.

My conclusions, conclusions that I recommend to anyone having
computer problems of any sort, involve uninstalling .Net. Today
I know from personal experience that older drivers can work
better (so keep your old drivers in a safe place) and I can advise
reinstalling older drivers over new drivers.

In summary, .Net creates problems, slows the bootup of the system
down, and the uninstaller fails to work and leaves behind files (at
least 948,006 bytes worth of files).

Keep your old drivers and keep your old versions of SysInternals
software in a safe location.

--
Jim Carlock
Post replies to the group.


.

Relevant Pages

  • wndows 2000 add/remove programs crashes after windows update
    ... Microsoft published this article, see if it works for you. ... Installing Internet Explorer 5.5 or Internet Explorer 6 ... Microsoft Internet Explorer 6 on Windows 2000, ... 303399 You Cannot Finish Installing or Upgrading Internet ...
    (microsoft.public.win2000.windows_update)
  • Re: HP Deskjet1000C manual feed does not work in XP Pro
    ... Responsibility for developing printer drivers lies soley in the hands of the ... > draw is that either Microsoft or HP personnel did not ... > are just copying the drivers, (not even installing them) ...
    (microsoft.public.windowsxp.print_fax)
  • Re: mouse stoped working after your last update
    ... If you have special drivers or software installed for your mouse, ... you might try installing that mouse on the system to see if it has the same ... If reinstalling the drivers or software doesn't resolve the issue, ... Also, you need to realize, you are not talking directly to Microsoft. ...
    (microsoft.public.windowsxp.device_driver.dev)
  • Re: Getting Microsoft branded Media Center Remote to work..
    ... I got the MCE as part of the Partner Action Pack that I subscribe to. ... Microsoft, they recommended NewEgg as a source for the pairing of Microsoft ... I am asking simply how to find those drivers. ... > | infrared receiver attached while installing the OS. ...
    (microsoft.public.windowsxp.hardware)
  • Re: ERROR 1003 HELP
    ... It could be now an av software problem, but I had the same problem when ... installing Windows. ... maybe this was caused by SATA drivers. ... >> I supposed that it could be a virus (read on Microsoft site) but checked ...
    (microsoft.public.windowsxp.hardware)