Win XP retail w SP1 installs fine WinXP OEM w SP2 wont install - Detailed info within

edited April 2009 in Science & Tech
Bear with me as I have tried to be as detailed as possible in explaining my issues. The first portion labled background give you the story up til 2-22-05. The section labled update give you the most recent happenings. I finish off the post with a question for those of you in the the know or with a helpful opinion. THANKS FOR LOOKING!

BACKGROUND

I am having a heck of a time with this computer build. I will list the specs at the bottom of the message for everyones review. Here is the MAIN issue.

I cannot get Windows XP to load fully without experiencing the following error:

Fatal Error

One or many of the components required to complete setup cannot be installed. Check to make sure that the disc is not damaged or dirty or that all of the files are at the source (network Install)

Data Error (cyclic redundency error)

Cannot load "ASMS" component d:\i386


Resolution:

I have been back to the store where I bought the Windows XP and witnessed them switch it for another sealed new copy of the disc. I got back home and experienced the same error. Always at the same point in the installation process which is after the first reboot and with ~39 minutes left to complete installation. You can hear the CD "spin-up" real fast and then all of a sudden the drive clicks and moments later the error will appear. I have tried 3 different CD/DVD-ROM/DVD drives to read the disc's and each time with each different drive I get the error at the same point in the installation. The system does not exhibit any other signs of problems (during the numerous re-formatting from NTFS to FAT back to NTFS) with retaining the information that does copy to the hard drive. And NEVER has the system had any issue posting or entering the BIOS etc... Everything seems to be pretty standard with all my previous builds.

Also I have tried using the Xcopy function in FAT configurations and at that time there were errors in copying some of the files to the hard drive. They didn't seem important (gifs, jpgs...) so I continued with the installation and lo and behold I got an error asking me to point the PC to the i386 directory on the hard drive. I try and try to direct it to the source files in these cases and it doesn't take, it just blinks and doesn't proceed to continue.

Theory:

THIS IS THE FIRST system that I have attempted to build using SATA devices (The hard drive and dvd writer). I have been attempting to load the NVidia Nforce Storage Controller driver (from the ASUS CD) during the F6 screen but whether I load it or not (in NTFS or FAT) I get the same results. I have not yet had the chance to try any other type of HDD with the current setup, hopefully I will be able to do so soon. I am using the onboard SATA ports on the motherboard NOT a controller card.

The XP Home disc that I was sold is a full version INCLUDING SP2 but was sold to me as a "OEM" disc, on the documentation it states that it should only be distributed with a new PC. This was sold to me by a large computer superstore because I was buying all the part to build a PC from them. I am curious to know if perhaps this OEM version is not all that it should be in terms of installation prompts/pathes and data as compared with the Retail Upgrade or Full version...

Bad disc, what is the chances of getting two bad discs in two days... I am thinking that this is not the true cause as the discs look fine.

Help is appreciated in advance, I leave it to you folks to show me the way on this install. If I can get it running it should be a blazing setup...

Specs: Only what is currently connected to get this thing going...
AMD Athlon 64 3200+
ASUS K8N mobo with onboard audio
Nvidia Nforce3 chipset
2 IDE ports
2 SATA ports
Numerous onboard USB connections
1 512meg DDR 3200 Kingston Xtreme Dimm
Maxtor 250 Gig Sata Ultra series hard drive (SATA 1)
ATI All in Wonder 9600
Samsung CD/DVD-ROM combo drive (IDE 1)

UPDATE

2-23-05

Made the following changes to the configuration without an OS loaded.

1)Flashed the BIOS with 1004 (even though the POST screen stated that it was already in use)
2) Reset the RTC RAM by moving jumpers as guided in the manual (this reset the system clock and CMOS)
3) Replaced the SATA interface cable going from the HDD to the Motherboard.
4) Downloaded the newest unified driver pack from Nvidia for the Nforce3 chipset. (from another PC)
a) extracted the file using Winrar to a folder on the HDD (on another PC)
b) browsed to the IDE folder on the extracted files and placed the following on a floppy
nvatabus.sys
nvatabus.inf
idecoi.dll
nvata.cat
textsetup oem
disk1
5)Changed the voltage to the memory from 2.5 to 2.7

The next change that I decided to do was try the Win Xp UPGRADE disc with SP1 from my other home computer rather than the OEM disc with SP2.

THE COMPUTER WAS SUCCESSFUL IN COMPLETING INSTALLATION OF XP after the above changes were made!!!

At this point I was relieved to have made some progress and silly was I to think that all the changes above had corrected the issue and that changing to a different install CD was irrelevant. So I immediately reformatted the HDD and proceeded to install using the OEM disc. I am unhappy to report that the installation hung on the same exact point as earlier described. What the heck is going on here…

Hoping that the successful install earlier was not a fluke I proceeded to install using my upgrade disc and lo and behold the installation was successful. So for those who are keeping score:

Windows XP Home retail Upgrade CD with SP1 - 2 for 2
Windows XP OEM CD with SP 2 - 0 for 20

Keep in mind that I already replaced the first OEM disc thinking the the disc was bad so the 20 attempts also included the attempted installs with the same type of disc.

So at this point my mind is running a million miles a minute and I suspect that the moment I attempt to patch the working XP install with Service Pack 2 I will be back to square 1. So I proceed to install SP 2 and paint me pink it works with no problems. I then proceeded to load every driver know to man with no problems rebooting or hangin during POST. I seemingly have a stable system with all the components responding and this rig is blazing fast.

So I talked with Microsoft yesterday and they are going to send out a replacement disc as part of my case number. They intend to send out the retail version of XP home with SP 2 integrated into it.

My Question to myself and those of you still interested is should I expect the same results as I am getting with the OEM disc with SP2 integrated. COULD IT BE that the issue with installing an OS on this system is inherent upon SP2 being present from the initial install?

Should I contact Microsoft and ask that they change the replacement request to a retail version with SP1 intergrated?

Whatdoyathink?

Comments

  • b0wzb0wz Tri-Cities Washington, USA
    edited February 2005
    bennybone wrote:
    Bear with me as I have tried to be as detailed as possible in explaining my issues. The first portion labled background give you the story up til 2-22-05. The section labled update give you the most recent happenings. I finish off the post with a question for those of you in the the know or with a helpful opinion. THANKS FOR LOOKING!

    BACKGROUND

    I am having a heck of a time with this computer build. I will list the specs at the bottom of the message for everyones review. Here is the MAIN issue.

    I cannot get Windows XP to load fully without experiencing the following error:

    Fatal Error

    One or many of the components required to complete setup cannot be installed. Check to make sure that the disc is not damaged or dirty or that all of the files are at the source (network Install)

    Data Error (cyclic redundency error)

    Cannot load "ASMS" component d:\i386


    Resolution:

    I have been back to the store where I bought the Windows XP and witnessed them switch it for another sealed new copy of the disc. I got back home and experienced the same error. Always at the same point in the installation process which is after the first reboot and with ~39 minutes left to complete installation. You can hear the CD "spin-up" real fast and then all of a sudden the drive clicks and moments later the error will appear. I have tried 3 different CD/DVD-ROM/DVD drives to read the disc's and each time with each different drive I get the error at the same point in the installation. The system does not exhibit any other signs of problems (during the numerous re-formatting from NTFS to FAT back to NTFS) with retaining the information that does copy to the hard drive. And NEVER has the system had any issue posting or entering the BIOS etc... Everything seems to be pretty standard with all my previous builds.

    Also I have tried using the Xcopy function in FAT configurations and at that time there were errors in copying some of the files to the hard drive. They didn't seem important (gifs, jpgs...) so I continued with the installation and lo and behold I got an error asking me to point the PC to the i386 directory on the hard drive. I try and try to direct it to the source files in these cases and it doesn't take, it just blinks and doesn't proceed to continue.

    Theory:

    THIS IS THE FIRST system that I have attempted to build using SATA devices (The hard drive and dvd writer). I have been attempting to load the NVidia Nforce Storage Controller driver (from the ASUS CD) during the F6 screen but whether I load it or not (in NTFS or FAT) I get the same results. I have not yet had the chance to try any other type of HDD with the current setup, hopefully I will be able to do so soon. I am using the onboard SATA ports on the motherboard NOT a controller card.

    The XP Home disc that I was sold is a full version INCLUDING SP2 but was sold to me as a "OEM" disc, on the documentation it states that it should only be distributed with a new PC. This was sold to me by a large computer superstore because I was buying all the part to build a PC from them. I am curious to know if perhaps this OEM version is not all that it should be in terms of installation prompts/pathes and data as compared with the Retail Upgrade or Full version...

    Bad disc, what is the chances of getting two bad discs in two days... I am thinking that this is not the true cause as the discs look fine.

    Help is appreciated in advance, I leave it to you folks to show me the way on this install. If I can get it running it should be a blazing setup...

    Specs: Only what is currently connected to get this thing going...
    AMD Athlon 64 3200+
    ASUS K8N mobo with onboard audio
    Nvidia Nforce3 chipset
    2 IDE ports
    2 SATA ports
    Numerous onboard USB connections
    1 512meg DDR 3200 Kingston Xtreme Dimm
    Maxtor 250 Gig Sata Ultra series hard drive (SATA 1)
    ATI All in Wonder 9600
    Samsung CD/DVD-ROM combo drive (IDE 1)

    UPDATE

    2-23-05

    Made the following changes to the configuration without an OS loaded.

    1)Flashed the BIOS with 1004 (even though the POST screen stated that it was already in use)
    2) Reset the RTC RAM by moving jumpers as guided in the manual (this reset the system clock and CMOS)
    3) Replaced the SATA interface cable going from the HDD to the Motherboard.
    4) Downloaded the newest unified driver pack from Nvidia for the Nforce3 chipset. (from another PC)
    a) extracted the file using Winrar to a folder on the HDD (on another PC)
    b) browsed to the IDE folder on the extracted files and placed the following on a floppy
    nvatabus.sys
    nvatabus.inf
    idecoi.dll
    nvata.cat
    textsetup oem
    disk1
    5)Changed the voltage to the memory from 2.5 to 2.7

    The next change that I decided to do was try the Win Xp UPGRADE disc with SP1 from my other home computer rather than the OEM disc with SP2.

    THE COMPUTER WAS SUCCESSFUL IN COMPLETING INSTALLATION OF XP after the above changes were made!!!

    At this point I was relieved to have made some progress and silly was I to think that all the changes above had corrected the issue and that changing to a different install CD was irrelevant. So I immediately reformatted the HDD and proceeded to install using the OEM disc. I am unhappy to report that the installation hung on the same exact point as earlier described. What the heck is going on here…

    Hoping that the successful install earlier was not a fluke I proceeded to install using my upgrade disc and lo and behold the installation was successful. So for those who are keeping score:

    Windows XP Home retail Upgrade CD with SP1 - 2 for 2
    Windows XP OEM CD with SP 2 - 0 for 20

    Keep in mind that I already replaced the first OEM disc thinking the the disc was bad so the 20 attempts also included the attempted installs with the same type of disc.

    So at this point my mind is running a million miles a minute and I suspect that the moment I attempt to patch the working XP install with Service Pack 2 I will be back to square 1. So I proceed to install SP 2 and paint me pink it works with no problems. I then proceeded to load every driver know to man with no problems rebooting or hangin during POST. I seemingly have a stable system with all the components responding and this rig is blazing fast.

    So I talked with Microsoft yesterday and they are going to send out a replacement disc as part of my case number. They intend to send out the retail version of XP home with SP 2 integrated into it.

    My Question to myself and those of you still interested is should I expect the same results as I am getting with the OEM disc with SP2 integrated. COULD IT BE that the issue with installing an OS on this system is inherent upon SP2 being present from the initial install?

    Should I contact Microsoft and ask that they change the replacement request to a retail version with SP1 intergrated?

    Whatdoyathink?


    If you have a good upgrade disk, why not just sliptream in sp2?
    I have a pre sp1 xp pro disk, found that stuff i needed (sp2 network install) and nforce drivers, and made myself a new installation disk. Works great, boots into sp2 on the first go round. Lots of good artilces out there on slipstreaming sp2....think the one at tom's hardware was the most usefull to me. will post the link later after work...........if i can find it again.....
  • b0wzb0wz Tri-Cities Washington, USA
    edited February 2005
    http://www4.tomshardware.com/howto/20040908/index.html

    Good article on slipstreaming, and adding drivers to your old xp install disk. Worked great on my Raid0 amd64 3400, my origanal disk was a pre sp1 xp pro upgrade, my new slipstreamed disk, is a fully loaded sp2 version of xp pro upgrade, with nvidia divers to boot. :)

    dfi ut 754 amd 64 3400nc @ 2.54 ghz
    2 hitachi 160's raid0 sata 1+2
    2 hitachi 250's sata 3+4 (non raid)
    BFG 6800 ultra
    Enermax 600watt ps
  • edited February 2005
    b0wz wrote:
    http://www4.tomshardware.com/howto/20040908/index.html

    Good article on slipstreaming, and adding drivers to your old xp install disk. Worked great on my Raid0 amd64 3400, my origanal disk was a pre sp1 xp pro upgrade, my new slipstreamed disk, is a fully loaded sp2 version of xp pro upgrade, with nvidia divers to boot. :)

    dfi ut 754 amd 64 3400nc @ 2.54 ghz
    2 hitachi 160's raid0 sata 1+2
    2 hitachi 250's sata 3+4 (non raid)
    BFG 6800 ultra
    Enermax 600watt ps

    It certainly saves some time when reloading the software on a machine. I am not sure that it would be a valid method to diagnose the issue that I am having which centers around Microsoft product variations and their behavior during the install process.

    In other words if I was to slip stream SP2 into the working upgrade disc I am not convinced that it would then duplicate the processes as would a Microsoft product that contained SP2. To finish out the thought I also wouldn't be able to use the slipstreamed product as a OS because its license is for one of my computers and not both.

    Currently with the operating state of the new PC I do not have it connected to the Internet so it is on the 30 day countdown. Again I am only evaluating the performance and do not intend to carry forward using the working installation.

    Thanks for the info I will save it for when this dilema is solved :thumbsup:
  • Insight-DriverInsight-Driver California
    edited April 2009
    bennybone, if you haven't root-caused the issue, yet, try this: Let the XP disc that fails the install, delete the partition, create a new partition and format the volume for it's install. It just may work then.
  • ThraxThrax 🐌 Austin, TX Icrontian
    edited April 2009
    This thread is 4 years old.
Sign In or Register to comment.