Tom's Guide | Tom's Hardware | Tom's Games
![]() |
![]() |
![]() |
When installing XP from the CD from DOS, I'm getting a large number of file copy errors during the second part of the setup, (after you reboot once)
Despite this, I proceeded through the setup anyway
and now I just get a B.S.O.D when I try to start up XP
The Blue screen says SYSTEM_LICENSE_VIOLATION, and some other textHere's my system:
Compaq 5000 Series 5WV277
Duron 750MHz
320MB SDRAM
Nvidia Vanta Lt 8Meg video cardI was previously running Windows ME until it went completely FUBAR and I had to re-format
Is there a workaround this?, any suggestions would be greatly appreciated

Are we talking about a purchased copy of WinXp or a copied/downloaded one?
If you are using a downloaded version then errors dont surprise me.

I have a little experience with something like this. I was getting file copy errors at random points, and given 2-5 retries, it would continue on..briefly.
My system stats:
K7S5A MB / 1.2Ghz (133FSB) / Teac 8x IDE CDR / 256 DDROn a whim, I decided to watch my cdrom drive while it was installing - and noticed that my Teac drive, even when it had nothing to do, would activate the IDE bus in regular intervals. Regardless of the CDRom was in use or not. I'm guessing that copying mid-file, the CDRom would interrupt the transfer, each time at different points in the install. (I eventually got a system lockup/BSOD in each failed install)
Swapped the drive with a new one and off I went. I doubt your problem is as specific as mine, but in general, swap out the parts involved if you have tried everything else. If it is failing mid-install at different points, suspect memory, HD, CD, etc. Motherboard, power supply and CPU I'd swap out last. Let someone with a completely different computer use that CD to see if it works for them.
If it always fails in the same spot, I'd suspect the media. Re-download or return it for a different copy.

Had the same problem with my Dad's computer installing XP and I eventually figured out that the two brands of RAM in his computer where not friendly to each other. Took one out and no more errors.

I had similar problems. Search google for MemTest86. Download and run it. It will tell you if you have bad ram. XP is more stringent in its demands that your hardware should work correctly.

![]() |
How do I resolve an IP ad...
|
VIRUSSCAN 5.20 XP
|

This post is quite old and has been locked from receiving new replies. Please create a new posting instead.
| Ads by Google |