Re: installing XP Pro copy file errors

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

"Vagabond Software" <vagabondsw-X-@xxxxxxxxxxxx> wrote in
news:uKB8fMTnFHA.3828@xxxxxxxxxxxxxxxxxxxx:

> "McSpreader" <invalid@xxxxxxxxxxx> wrote in message
> news:Xns96ADE5DDA44DMcP@xxxxxxxxxxxxxxxxx
>> Malke <invalid@xxxxxxxxxxxx> wrote in
>> news:#5KkuXSnFHA.1088@xxxxxxxxxxxxxxxxxxxx:
>>
>>> RCOC wrote:
>>>
>>>> When I attempt to install XP Pro on a new hard drive, towards
>>>> the finish I get errors "cannot copy ..." various files,
>>>> although I'm trying 2 different
>>>> new XP Pro CD's, and reformatted the drive after unsuccessful
>>>> attempts. The CD drive has never been malfunctioned before.
>>>> Thanks for any help!
>>>
>>> These types of errors are usually because of hardware
>>> failures. The newness of the hardware is irrelevant; in fact,
>>> if hardware is going to fail it usually does so right away.
>>>
>>> The first thing to test is your RAM. I like Memtest86+ from
>>> www.memtest.org. Obviously, you have to get the program from a
>>> working machine. You will either download the precompiled
>>> Windows binary to make a bootable floppy or the .iso to make a
>>> bootable cd. If you want to use the latter, you'll need to
>>> have third-party burning software on the machine where you
>>> download the file - XP's built-in burning capability won't do
>>> the job. In either case, boot with the media you made. The
>>> test will run immediately. Let the test run for an extended
>>> period of time - unless errors are seen immediately. If you
>>> get any errors, replace the RAM.
>>>
>>> If the RAM tests good, then run the drive mftr.'s diagnostic
>>> on your new hard drive. I've had hard drives fail right out of
>>> the box.
>>
>> Although what you say is true in some cases, I cannot agree
>> with your assertion that hardware fault is *usually* the
>> problem.
>>
>> In my experience the majority of the cases where this error has
>> occurred was on systems that do not exhibit any hardware
>> problems. I have checked the MS CD media and found no problems
>> reading an entire installation CD using XP. However, on the
>> same system including CD drive, read errors are reported during
>> installaion of XP and mostly unrecoverable.
>>
>> The problems have been experienced with original MS XP Home SP2
>> OEM CD media and trying alternative CD media is ineffective.
>>
>> My guess is that the problem is down to a flaky driver or buggy
>> error recovery process in the XP installation environment
>> build.
>
> On the other hand, each time I have encountered these problems,
> it has been a hardware problem... more specifically, memory.
>
> I have seen this problem several times where an installation of
> an operating system craps out with what appear to be read errors
> on the media at various intervals. On every occassion, I have
> found memory problems with the target systems. One such
> occassion was an installation of Small Business Server 2003 on a
> new system with Corsair (one of the best IMHO) memory.
>
> The relatively new DDR RAM can and does go bad with greater
> frequency than the SDRAM of yesteryear.
>

IME memory hardware failure problems during installation usually
result in a BSOD.

In the CD read error cases I am referring to the installation
software reports it cannot read file mumble.dll, and offers retry,
skip or abort the installation.

Each time I have tested the memory and hard drive using Memtest86
and mfr's disk diagnostics, with no errors reported.

Temporarily installing a replacement CD drive has enabled me to
complete the XP installation in each case.

Testing the original CD drive does not show up any read error
problems.


.

Relevant Pages

  • Re: Windows installation problem. Help.
    ... 2004 Windows MVP "Winny" Award ... tries to read the memory, can't find it, generates a processor fault, ... This Stop message usually occurs after the installation of faulty hardware ...
    (microsoft.public.windowsxp.general)
  • Re: Windows XP Professional suddenly stops and a blue screen with error message appears and could no
    ... > restart your computer. ... > Check to make sure any new hardware or software is properly ... If this is a new installation, ... > Beginning dump of physical memory. ...
    (microsoft.public.windowsxp.perform_maintain)
  • Re: Time to fix my PC
    ... Intermittent memory often passes all tests at room temperature. ... such as the crash code or data from system logs in the OS ... only certain hardware can crash a properly designed ... I'll pull out the audio and DVD drives while testing to simplify ...
    (comp.os.linux.hardware)
  • blue screen crash
    ... If this is a new installation, ... hardware or software manufacturer for any updates you need. ... bios memory options such as caching or shadowing. ... Beginning dump of physical memory, ...
    (microsoft.public.windowsxp.general)
  • Re: New motherboard..XP wont boot!
    ... Bios sees all the drives properly, and I went over all the settings in the new bios, and I can access the C: drive and read files from it. ... Normally, and assuming a retail license (many factory-installed OEM installations are BIOS-locked to a specific chipset and therefore *not* transferable to a new motherboard - check yours before starting), unless the new motherboard is virtually identical to the one on which the WinXP installation was originally performed, you'll need to perform a repair installation, at the very least: ... You've pulled the proverbial hardware rug out from under the OS. ...
    (microsoft.public.windowsxp.general)