Re: Unable to install .NET 1.1 via Windows Update and Redistributa

YW & thanks for your feedback.

sensei wrote:
I must sheepishly apologize for what seems to be a cry-wolf incident. It
turns out that the culprit was a bad stick of ram! I'm not sure what caused
me to suspect it, but I used Microsoft's RAM testing application, and I
discovered that one of my two sticks of ram had failed the
uncached-walking-ones-and-zeroes test.

The defect in the ram was so slight as to be undetectable by any basic test
and didn't even raise any other alarms in Windows, not even during
installation. However, it was causing all of my downloads to get corrupted,
and it also caused my CD Rom drive to have trouble reading certain files. In
any case, after replacing the ram, all installations have proceeded smoothly
and I have gone on to enjoy my new machine.

Thanks for all your patience and help, PA Bear. Sorry to waste your time!


"PA Bear [MS MVP]" wrote:

1. See this archived post about the problem:
http://groups.google.com/group/microsoft.public.windowsxp.general/msg/bf083ccff1446ac2

2. Post to this .NET Framework-specific newsgroup instead:
microsoft.public.dotnet.framework.setup
--
~Robear Dyer (PA Bear)
MS MVP-Windows (IE, OE, Security, Shell/User)
AumHa VSOP & Admin http://aumha.net
DTS-L http://dts-l.net/


sensei wrote:
Thanks for getting back to me so quickly, PA Bear.

I was able to successfully uninstall .NET using the utility on that page,
but whenever I try to reinstall the .NET framework 1.0 using the
redistributable, it fails when trying to extract "dotnetfx.exe" by saying:

"Extracting file failed. It is most likely caused by low memory(low disk
space for swapping file) or corrupted Cabinet file."

I've redownloaded this file several times, and I know I have a ton of free
memory and disk space. What to do?


"PA Bear [MS MVP]" wrote:

See http://support.microsoft.com/kb/923100 (ignore the title)
--
~Robear Dyer (PA Bear)
MS MVP-Windows (IE, OE, Security, Shell/User)
AumHa VSOP & Admin http://aumha.net
DTS-L http://dts-l.net/

sensei wrote:
I return with new information:

I've downloaded the .NET 1.1 and .NET 3.0 setup files from
(C|Net)Download.com and those files also experienced much the same
problems
-- although the .NET 3.0 actually had a valid certificate. After doing a
bytewise-comparison between the two files, I noticed that only ONE
single
byte was different, but that was enough to throw off the certification.

As fascinating as this all is, it brings me to the bleak realization
that
there probably isn't anything that corrupt about the .NET files sitting
on
Microsoft's servers because the behaviour is the same for both copies of
the
file.

"sensei" wrote:

I've installed Windows XP Pro on many systems, but this is the first
time
I've encountered this problem.

I just can't seem to get the following software installed via Microsoft
Update without an error code of: 0x80246002

.NET 1.1
.NET 3.0

I'm starting with a fresh install of Windows XP Pro on a brand new
quad-core workstation.

I installed software in the following order:

Windows XP SP1 (from original installation CD)
SP2 (redistributable executable from microsoft)
Microsoft Update (and every critical and major update successfully
installed)

I was, however, able to install .NET 1.0 from the XP CD-Rom, and .NET
2.0
worked from a redistributable file. Nothing unusual happened during the
installation of those two programs, but I cannot apply service packs to
them without the same 0x80246002 error.

Finally, one more conundrum:

I've noticed that the .NET 1.1 redistributable does not have a proper
certificate -- Windows claims that it comes from an "Unknown
Publisher",
and when I run it anyways, it dies when extracting InstMsiW.exe with
the
error:

"Extracting file failed. It is most likely caused by low memory (low
disk
space for swapping file) or corrupted Cabinet file."

This can't be the case, since this is a brand new computer with over
700GB
of free space and 2 GB of ram, with nothing running in the background.
I've
attempted redownloading the same file several times, but I'm led to
believe
that maybe the file on Microsoft's website is corrupted because the
file
does not change in any way with each successive download, even after
clearing my cache.

I'm dying to get this new workstation started. Your help is greatly
appreciated.

.

Relevant Pages

  • Re: Unable to install .NET 1.1 via Windows Update and Redistributa
    ... me to suspect it, but I used Microsoft's RAM testing application, and I ... there probably isn't anything that corrupt about the .NET files sitting ... I'm starting with a fresh install of Windows XP Pro on a brand new ... Windows XP SP1 (from original installation CD) ...
    (microsoft.public.windowsupdate)
  • Re: Unable to install .NET 1.1 via Windows Update and Redistributables
    ... there probably isn't anything that corrupt about the .NET files sitting on ... "sensei" wrote: ... I just can't seem to get the following software installed via Microsoft ... Windows XP SP1 (from original installation CD) ...
    (microsoft.public.windowsupdate)
  • Re: XP Pro in 128 MB
    ... "Glacial" is the term that comes to my mind, I'm afraid, if your computer doesn't have a CPU of at least 500 MHz along with at least 256 Mb of RAM. ... If you turn off all of WinXP GUI eye-candy, it will still be very slow, but it might usable for simple word processing, email, web-browsing, etc. ... compatible with both the motherboard and/or any other RAM module ... On installation it "tailors" itself to the specific hardware found. ...
    (microsoft.public.windowsxp.general)
  • Re: XP Reinstall Gone Awry - i386 tkrnlmp.exe Error
    ... that you just might have faulty ram. ... pull out one stick and try the installation. ... was bad and as soon as I removed it, setup worked just fine. ... Dell and the RAM was working prior to my decision to reinstall and seems ...
    (microsoft.public.windowsxp.help_and_support)
  • Re: Help with making a Windows XP slipstreaming bootable cd
    ... I eventually aborted the "repair" sequence and checked the disk. ... Repair installation) are most often caused by defective, incompatible, or ... Start with testing the RAM. ... The philosopher has never killed any priests, ...
    (microsoft.public.windowsxp.general)