Prev: power options issue
Next: Explorer crash - Network connections
From: Paul on 16 Jun 2010 01:20
Kernel wrote:
> Yes, I copied it for the purpose of slipstreaming SP3. During that process
> it also indicated that there was a problem with the OEM.
>

Have you tried any optical disc data recovery software ?
This is the first thing that comes up in a search - http://www.isobuster.com/
If the data is still good, but the disc a bit marginal,
maybe you can get it that way. It makes you wonder
though, what the origins of the disc are. Pressed
or burned ? A copy perhaps ?

Maybe you'll be needing one of these soon :-)

"Microsoft Get Genuine Kit"
http://www.newegg.com/Product/Product.aspx?Item=N82E16832116574

Paul
From: Andy on 16 Jun 2010 01:46
On Tue, 15 Jun 2010 17:48:38 -0700, "Kernel" <kernel64(a)bosworth33net>
wrote:

>I purchased a Win XP Pro OEM CD on ebay several months back. The package
>was sealed, and it included a COA. When I ran the setup today in a new PC I
>built, it stopped numerous times with a popup saying a certain .dll can not
>be copied (duser.dll; wind_w.chg.wmp.dll, etc). It gave me the choice to
>try again with Enter; and most of the time it went on copying dlls in the
>setup. I got thru about half a dozen of those problems, and when the
>copying portion of the installation was about completed, a popup said STOP:
>c0000221 {Bad Image Checksum} The image dll url.dll is possibly corrupt.
>The header checksum does not match the computed checksum. From that point
>the installation failed, of course.
>
>I'm past the 45 day deadline for ebay to help me. Is there any chance
>Microsoft will provide a replacement CD? Yeah, I know, two chances,
>slim and none...
>
>TIA
>
Verify that your new PC hardware is not defective. Check the system
memory using memtest86+.
From: Jose on 16 Jun 2010 07:11
On Jun 15, 10:37 pm, "Kernel" <kernel64(a)bosworth33net> wrote:
> Yes, I copied it for the purpose of slipstreaming SP3.  During that process
> it also indicated that there was a problem with the OEM.
>
> "Doum" <m...(a)domain.net> wrote in message
>
> news:XnF9D98DC2B570D4doumdomainnet(a)207.46.248.16...
>
>
>
> > "Kernel" <kernel64(a)bosworth33net> écrivait
> >news:u3taw2ODLHA.5808(a)TK2MSFTNGP02.phx.gbl:
>
> >> I purchased a Win XP Pro OEM CD on ebay several months back.  The
> >> package was sealed, and it included a COA.  When I ran the setup today
> >> in a new PC I built, it stopped numerous times with a popup saying a
> >> certain .dll can not be copied (duser.dll; wind_w.chg.wmp.dll, etc).
> >> It gave me the choice to try again with Enter; and most of the time it
> >> went on copying dlls in the setup.   I got thru about half a dozen of
> >> those problems, and when the copying portion of the installation was
> >> about completed, a popup said STOP: c0000221 {Bad Image Checksum} The
> >> image dll url.dll is possibly corrupt. The header checksum does not
> >> match the computed checksum.  From that point the installation failed,
> >> of course.
>
> >> I'm past the 45 day deadline for ebay to help me.  Is there any chance
> >> Microsoft will provide a replacement CD?   Yeah, I know, two chances,
> >> slim and none...
>
> >> TIA
>
> > Have you tried copying your CD? If the copy process goes through, the copy
> > might work.
>
> > or...
>
> > Do you know someone who has an XP pro OEM CD?
>
> > Just make a copy and used that copy instead with your own COA.

If you are going to slipstream SP3 to make a new CD (a good idea), you
need to copy the contents of the CD to some new folder on your HDD
first (there is no need to make a copy of the CD - you are going to
make a new CD), Then you do the slipstream process using the files on
your HDD, then you make a new CD from the files on your HDD and use
the original CD to make a coaster or an attractive shiny mobile.

If you make a new folder on your HDD and just copy the files from the
CD to the HDD, what happens?

If the copy fails, does the message really say "there is a problem
with the OEM" or does it say something else?

If you think your CD drive itself might be faulty, copy the contents
of the CD to the HDD on another system.

Use the process of elimination to see if the CD media is defective or
there is some other problem.


If you want to test your RAM with memtest86+, here is how to do that:

Run a test of your RAM with memtest86+ (I know it is boring and will
cost you a CD).

Memtest86+ is a more up to date version of the old memtest86 program
and they are not the same.

The memtest86+ will not run under Windows, so you will need to
download the ISO file and create a bootable CD, boot on that and then
run the memtest86+ program.

If even a single error is reported that is a failure and should make
you suspicious of your RAM.

If you have multiple sticks of RAM you may need to run the test on
them one at a time and change them out to isolate the failure to a
particular single stick. Always keep at least the first bank of RAM
occupied so the test will find something to do and there is enough to
boot your system.

Sometimes, reseating the RAM in the slots will relieve the error but a
failure is still cause for suspicion.

The file and instructions are here:

http://www.memtest.org/

Here is a link that show you have to create and use the memtest86+ CD:

http://www.geekstogo.com/forum/Guide-to-using-Memtest86-t246994.html

If someone says to run memtest86, you can tell them to go pound sand
and that you know memtest86+ supercedes memtest86 and here's why:

http://en.wikipedia.org/wiki/Memtest86
From: Daave on 16 Jun 2010 10:06
Kernel wrote:
> I purchased a Win XP Pro OEM CD on ebay several months back. The
> package was sealed, and it included a COA. When I ran the setup
> today in a new PC I built, it stopped numerous times with a popup
> saying a certain .dll can not be copied (duser.dll;
> wind_w.chg.wmp.dll, etc). It gave me the choice to try again with
> Enter; and most of the time it went on copying dlls in the setup. I
> got thru about half a dozen of those problems, and when the copying
> portion of the installation was about completed, a popup said STOP:
> c0000221 {Bad Image Checksum} The image dll url.dll is possibly
> corrupt. The header checksum does not match the computed checksum.
> From that point the installation failed, of course.
> I'm past the 45 day deadline for ebay to help me. Is there any chance
> Microsoft will provide a replacement CD? Yeah, I know, two chances,
> slim and none...
>
> TIA

Have you ruled out hardware problems such as a bad optical drive or bad
RAM?


From: Doug W. on 16 Jun 2010 11:34
Sometimes "factory" discs are just plain dirty. I have had some
that just required a few swipes with a clean old T-shirt to make
them perfectly readable. You would be surprised how smeary some
of them are. Another thing is how people handle discs, geez I
just wince to see how some users put fingerprints all over them.

A lens cleaner doesn't cost much either and should be used
periodically, especially for drives where smoke and smoking is
involved.
==

"Daave" <daave(a)example.com> wrote in message
news:uj3pO0VDLHA.3776(a)TK2MSFTNGP04.phx.gbl...
> Kernel wrote:
>> I purchased a Win XP Pro OEM CD on ebay several months back.
>> The
>> package was sealed, and it included a COA. When I ran the
>> setup
>> today in a new PC I built, it stopped numerous times with a
>> popup
>> saying a certain .dll can not be copied (duser.dll;
>> wind_w.chg.wmp.dll, etc). It gave me the choice to try again
>> with
>> Enter; and most of the time it went on copying dlls in the
>> setup. I
>> got thru about half a dozen of those problems, and when the
>> copying
>> portion of the installation was about completed, a popup said
>> STOP:
>> c0000221 {Bad Image Checksum} The image dll url.dll is
>> possibly
>> corrupt. The header checksum does not match the computed
>> checksum. From that point the installation failed, of course.
>> I'm past the 45 day deadline for ebay to help me. Is there
>> any chance
>> Microsoft will provide a replacement CD? Yeah, I know, two
>> chances,
>> slim and none...
>>
>> TIA
>
> Have you ruled out hardware problems such as a bad optical
> drive or bad RAM?
>

First  |  Prev  |  Next  |  Last
Pages: 1 2 3 4
Prev: power options issue
Next: Explorer crash - Network connections