Keep getting file copy errors during installation

[Nate Nygren]

Ok, this is kinda long to explain so I\'ll keep it to a minimum.  Here\'s my system build:

Asus a7v133 (with onboard audio)
512 mb PC133
1.2ghz Athlon
Maxtor 40gig disk
Maxtor 15gig disk
Philips 800 series CDRW
Gforce 2 MX video card
cheap 300 watt case

Ok, the problems I\'ve been having are:

Various file copy errors during the setup no matter what Windows OS I\'m installing making almost impossible to get all the way through an install.
If I do happen, after multiple attempts, to get an OS installed, it only lasts a few days before it gets messed up by the multiple blue screen deaths that occur.

Things I\'ve done to try to fix this:

Returned the Mobo and the memory and exchanged for the same make and model.
Configured the BIOS multiple times trying this and that.
Tried installing Linux.  Worked just fine.
Increased the cooling of the CPU by installing a twin fan orb cooler, and opening the case up and running a box fan right next to the machine to cool off all the components.
Tried using a different brand of RAM.
Tried using a different video card.
Tried using a different CD-Rom drive.
Flashed the BIOS.

As you can see, I\'m running out of options here.  The last two things I can think of is a bad CPU (which I doubt, but I could be wrong) or a bad power supply??  

Does anyone have any input into this?  I would be very much greatfull to anyone who helps me out at this point.  

[email protected]

-Nate

[Josetann]

Very well could be the power supply.  The Athlon 1.2 will suck down a lot of juice, and if you don\'t have a strong power supply, you could have problems later on.  Before you replace it though, can you borrow a friend\'s power supply?  If you can\'t, you can also try downlclocking the cpu.  If it works fine at a lower speed, then it\'s probably the power supply (a lower clocked cpu uses less watts, so there\'s less strain on it then), or a bad/overheating cpu.

And of course, if your cpu is overclocked, the first step is to always try it at its default speed first, before upping the speed.

[Nate Nygren]

Thanks for replying!

My mobo is one of the \"auto\" types where all the clock speeds and core CPU voltage is set by the BIOS automaticly.  I\'m not sure how to \"downclock\" my CPU on this type of mobo, but I\'ll see what I can find on the AMD and ASUS websites.  Otherwise, if you already know how, could you help me out a bit more?

I went through the tutorial on slipstreaming SP2 into Win2K yesterday (thanks for that tut!!) hoping that it would help, but I still got the file copy errors during installation.  Darn!  :-)

-Nate

[MagicNate]

I\'m now registered under the name \"Magicnate\"

-Nate Nygren

[MDK_executive]

Could it be the CD itself?  

I got some copy errors from just trying to manually copy system files to my hard drive using windows 2000.  Maybe the CD has some bad blocks (I traced my problem to the originating ISO).

Check it out by doing a manual copy of all files from the CD to the HDD using a friend\'s win2k computa.

[MagicNate]

No, it\'s not the CD, because I\'ve tried a few different versions of Windows (WinNT, WinME, Win2K, and WinXP RC1) and all give me the same problems.  I\'ve even borrowed a friend\'s Win2K cd (shame on me!) to see if it would work.  No go.

So, no, it\'s not the CD.

Thanks :-)

[Josetann]

I\'d still look into the power supply, if I could.  Also, do you have the chipset drivers loaded?  Get the most recent ones.  Maybe there\'s a problem copying from your CD to your hard drive, that some new drivers could fix (also wouldn\'t hurt to do what the other guy suggested, and copy the files to the hard drive first, and install from there).

[rdc]

I got errors setting up w2k  ,and or repairing too .
I have an abit bf6   440bx chip , and then I had an Intel p3 667 (133) .
When I downgraded my cpu to a p3 500e (100fsb  x 5) the errors were less , when I changed to 6 x 100 fsb the errors augmented .I had sdram 133 too .Later I changed the cpu to a p3 700 (100) the problem was resolved the 133 sdram has no influence in producing the errors only the p3 667 133fsb cpu .Seems the 440bx didn\'t tolerate an 133 cpu .

[MagicNate]

So I should try reducing my FSB to 100 even though I\'ve got PC133 RAM?  Cuz I can do that through my BIOS.  I\'m not sure it\'ll help that way, thought, cuz you had to buy another chip, right?  Hmm.  I hate this problem.  Thanks for the input, though.

[Josetann]

Did you copy the files to the hard drive first, and install from there?  That would rule out your cd drive almost completely (if it didn\'t copy correctly, explorer should complain about that...so you know for sure you\'re installing from good media).  Also, I would try downlclocking your cpu (setting the fsb to 100 would do it) if you can\'t try a more powerful power supply.  If it installs correctly then, you can be pretty sure it\'s either the ram\'s fault, or your power supply (a cpu running at a lower MHz uses less watts, so a weaker power supply could power it).

[Bobcat0070]

i would exchange your proc...
i just made myself a 1.33GHz system on a MSI K7T266 Pro board... and i was gettin registry corruption up the wazooi.
i exchaned: mobo, vid card, ram, and hsf. all led to the same errors. i formatted my IBM 75GXP 45GB bout 6 times throughout the whole process. finally i exchanged the proc.
fixed all my problems
of course i didnt have a cheap case/ps. i have an Enermax 300W ps.
now i have a fully stable system, not a single error since i replaced the proc.
i would absolutely exchange the proc if you have warranty, or at least the ability to exchange.

Bobcat0070

[ace5]

Similar problem with changing speed settings to get install to work.  BUT, the real problem is UDMA-66.  I think on a via or other non intel chip set, the install doesnt have drivers for the UDMA 66 hard drive.  Change your bios setting for your hard drive from auto to pio4, and disable the UDMA.  Now any speed will work, and you can install without getting the blue screen of death.  took me weeks to install, and finally figured it out.

Let me know if it works for you1

[GrimReaper]

Ok I\'ve been havin gthese probs for a while now. I used to be able to load any os on my pc, but now I get all errors, any erros...and nothing had changed on my system, the only thing that had happened was I had a memory resident virus and I had upgraded my bios. All My os cds are original aprt from XP and all have been installed beofre on this pc, so why would I start getting erros now..I only seem to get 2 errors now during xp setup, Ive given in with other os\'s..When installin xp pro it tells me it can\'t copy shell32.dll and main.cpl, this happens while loading from cd or from hdd, full install or upgrade..I even changed my ram, mobo, etc etc..basically I\'ve rebuilt the pc, I\'ve even tried taking the hdd out putting it in my 2nd pc and insatlling xp on there..the install goes well, but as soon as i put it back on this pc I get NTDLR is missing (or whatever the file is called) and it won\'t boot. The only thing left in the pc from original setup is the case...lmao..surely it can\'t be a power supply prob...I have had the case for 13 months and as I said xp used to install..

PLEASE HELP

[Mr. YuckY]

What is your IDE config like? do you have the harddrives on the master and then both cdroms on the slave? maybe you need to make one cdrom the master and use cable select on the second...

[Anonymous]

The power supply would have not cause a blue screen.  If a CPU can\'t draw the power it needs it shutsdown.  No GPF etc just instent shutdown

[Josetann]

I\'m not saying whether that\'s true or not, but a faulty power supply (or just one not powerful enough) could cause a gpf or other problems.  Perhaps the cpu is getting enough power, but the video card doesn\'t so it starts to flake out and causes problems.  Ram doesn\'t get enough power so the contents become corrupted.  Basically, it is very possible that the power supply could be the problem.

[Adi]

Change urgently the CD-ROM!!! All Philips, Sony sucks.
I use NEC 16x10x40x and can succesfully install XP, but 2 friends of mine, one using Phillips 8x4x32x and the other Sony 52x weren\'t able to do it, due to a file copy error in the middle of installation. They also tryied to copy the kit on HD before installing it and again no success!

[michaelsteindel]

I have had similar trouble loading OS\'s onto machines. Constant errors, file cannot be read and so on. The one thing that has worked everytime is using good sdram or DDR. The other things to try are turning off the timing by SPD and cacheing other than L1 or L2 (leave those alone). Also disable the OS plug and PLAY in the BIOS untill it has been fully installed. This has worked on 815 chipset, 266a and 133a chipset mobo\'s. I think when the price of ram went way down there was a flood of bad stuff out there. You might try, if you know how, to flash the CMOS with the latest BIOS upgrade.
good luck

[Kanzetsu]

Do you have a SBLive card installed? If so, that\'s probably what\'s causing it (due to a bug with VIA chipsets and Creative sound boards). I have to remove my sound card from the system during installation.

[jbb23]

I have a SBL card and I had a similar problem.  I was attempting to slipstream SP2 onto my win 2k disc.  The problem occurred when I was trying to copy the win2k disc to my HDD.  Win 2K kept crashing while the files were copying.  It seemed to happen when it reached the DRIVERS.CAB file.  Anyone have any thoughts on this?  Could it be related to the MBs VIA 4in1 drivers and the SBL card?