Keep getting file copy errors during installation

[Anonymous #007]

I think the hard drive (even if new) on which you\'re trying to copy/install the OS is defective. I had this problem before, and what I did, was to put my HDD into a friend\'s computer and try to install OS for this computer and I got the same error messages during copy. Second, I put the hard drive of my friend into my computer and try to use it. Of course OS detected new devices and I had to install them (he was a VERY good friend), but at the end it worked fine ! So no doubt anymore about my problem. May it help you !

[Deckard]

Hi Magicnate,

Interesting.  I have had these exact same problems when attempting to install 2000 on PCs with VIA chipsets, using an Athlon/K6-2 or III processor.  I think the problem revolves around UDMA.  It certainly worked for me once I had disabled UDMA in the BIOS and changed the access modes on both CD-ROM drive and HDD to Mode 4 PIO.

Hope this helps.

[Anonymous]

Concur that is probably hard drive problem as have had same experience.

[Anonymous]

im not 100% sure here but .... it could be a hard drive failure! u have got two maxtor hard drives there and trust me they go wrong very easily! i work as a technician at a school and they are forever going wrong and being replaced! borrow another hard drive and see if that works.... i got my fingures crossed 4 ya mate

[Anonymous]

In my experience with 30 PC\'s a day everyday, most of which are Win Xp, these errors you describe are usually caused by in this order......  RAM, CD-ROM/CDRW, MB, HDD, VCard.  Especially file copying errors during first stage of setup = RAM.  You say you\'ve changed it, but for same brand??  XP seems a LOT more fussy about RAM and hardware than 98 or Me.

[Anonymous]

um, hardrive controller? (on the hardrive itself) in other words-swap the hardrive

[Anonymous]

I had nearly the same problem with an Aopen MB with VIA K133 with an AMD Athlon 1.4Ghz 266FSB and 256 PC133 SDRAM.
Win 98 would install but with an hour or so was trashed. Win2k would half install before crashing and XP got nowhere.
I now have a working system.
Found it was all to do with the memory speed. Clocking it back from 133Mhz to 100Mhz fixed it. A side effect is the CPU runs slower, but it is now overclocked to 1.2Ghz.
(you may think it was my memory, I tried several different kinds and 2 different CPU\'s (initial thoughts were cor damage).

It\'s worth a try

[Anonymous]

Had all the familiar problems.  Took the advise here and killed UDMA, went to pio4 and pulled back to 100mhz on the ram.  Nothing worked for me until I disabled the on board audio.  Install completed fine after that.

[pcorreia]

Nate, I\'m having the exact same problem as you.  I was wondering if you (or anyone else in this forum) managed to fix the problem using the suggestions earlier in the thread?  Was it an issue with UDMA-66, or a bad processor, or what?  I\'m getting ready to tear my hair out here!

[Recessa Annie]

Problem:

BIOS bug and/or 4-in-One driver bug.

Here\'s the fix:  

Update your BIOS and VIA 4-in-One drivers.  I can\'t remember off-hand exactly which version of BIOS I used to fix this, but they were the ones available about the same time v4.32 of the 4-in-1\'s came out (early 2001?).  This was a very confusing issue, as VIA released updates that claimed to correct this problem, but the bugfix didn\'t actually work (or was not included) until the version that was released *AFTER* the version that was supposed to correct the problem.

I wasted approximately 30 hours of my life tackling this same problem with an Asus A7Pro motherboard.  I believe your mobo and the A7pro use the same Southbridge chipset which had a BIOS bug (namely the harddrive controller drivers on the Southbridge).  This particular bug (different than the SBLive bug mentioned earlier in this thread) affected files written to any disk (basically any data passing through the drive controller).  This was especially problematic for large files (greater than 50MB) but can/did affect any and all files.  

Good luck with that,
Ann

[Chris]

Working in a computer shop, I\'ve worked on 30 or more computers with errors installing Windows XP. Ranging from rebooting randomly during install, files missing, file copy errors, blue screens, to anything. And I will tell you, every time it was a memory issue. I swapped memory, and it would work EVERY time. Never the CD, or anything else in the computer. Sometimes I might put in another flawed stick of memory, but swapping it out again would get it going. XP and 2000 are memory sensitive when installing and running it. I wouldn\'t recommend buying \"generic\" memory on the net cheaply to save a buck, because most of those are really [censored]ty.

Michigander Technician
-Chris

[justin]

Dear Nate.
Just spotted your thread.
Have been using W2K PRO for some years -no probs on installation. Recently upgraded to Athlon 1800 system (see below) and on fresh installs I get multiple \'cannot copy file errors\'. I have managed to complete the installation by 1) taking the CD out and replacing it (this sometimes works) and 2) by inserting a friend\'s installation disk (this seems to allow the files that the first disk will not).

I know that the friend\'s CD is fine and he has no probs when installing from it. I also know that it is not the CD drive - have tried with 2 separate drives.

Did you ever resolve this? Could it be because I have ATA 133 enabled?

GA7-VRXP Board no: 203048E 1.1
XP1800
Starnet 350 PSU
AK 785 SE cooler
256 PC 2700 2.5
GeForce 4200 Ultra 650 (64 Meg)
Maxtor 40 7200, ATA 133
IBM GXP 13 gig
WIN 2K

Bios F4
Top performace
+.5v
CPU temp 44 - case closed
Board temp 35 - case closed

[Krazy Hawaiian]

VIA SUX plain and simple! I have a Tyan Trinity 450 with VIA and a SB Live and LOL what POS!! I\'ll never buy a TYAN product again, the support manager verbally attacked me whan I emailed them a simple question about weather or not my board supported anything above a G Force 2 !! The way he reacted was as if he had not read my letter at all, he just started going off!  And he sent 3 follow up attacks afterwards wjen I asked if they planned on doing anything about the file corruption problem. His answer amongst several swear words was NO its not our fault you bought the motherboard !!! Can you F***ing believe that poo? I know this is off topic but it does fall into the problem, I had/have the same problem I need to do several things to get a clean instal goin in. First is turn off the USB mouse support in the bios, if its left on the comp will hang everytime when it reboots. Secondly clean the CD before attempting to install with dishsoap and warm water, be careful not to drop it in the sink full of dirty dishes! I did and got a big scratch for my efforts LOL. You\'d be suprised how much cleaning the disc will help if you are having trouble installing. Soap and warm water seems to work better than any of the voodoo mixtures on the market. Also turn off support in bios for dma until it reads and writes the cab files. and oh ya, yank the SB Live out until its completed the inital instal, infact dont have any cards in the mobo but the graphics card that seems to help a good deal. Then get down on your knees, and begin to chant some unintelligble mumbojumbo as its installing keeping your fingers crossed while its doing it. Then swear at the top of your lungs at VIA and anyone connected to them if you even see the tiniest hint of blue screen! Gawd I hate my POS comp it cannot even transfer a 25mb file across my lan without making the file unuseable! It took several months of frustration and trying every concieveable combination of vid cards drivers via 4in1\'s you name it I tried it. Suprisingly  Mandrake Linux 8.1 will install without any of the afore mentioned antics, it just goes right in error free like its a \"normal\" comp, and not a \"special\" retarded model that it is.... I am leaning toward the ol aspi issue and something along thoes lines. I\'m not too familiar with Linux since I downloaded that version to try it but being \"weaned\" on winbloz I find Linux similar to attempting communication with a martian on crack or something.... LOL

[EdG]

I went through hell with very similar problems. As a last resort I went in to the BIOS and did a \"Restore BIOS Defaults\" and amazingly my ASUS/AMD system is running absolutely perfectly.  Try it! then format c: and re-install..