1. You are viewing our forum as a guest. For full access please Register. WindowsBBS.com is completely free, paid for by advertisers and donations.

Resolved XP Pro - Corrupt File on Boot CD

Discussion in 'Windows XP' started by dcm30096, 2009/10/13.

  1. 2009/10/13
    dcm30096

    dcm30096 Well-Known Member Thread Starter

    Joined:
    2009/08/17
    Messages:
    6
    Likes Received:
    0
    I believe I have a corrupt file on the XP Pro SP1 installation CD that came with my PC. I need help in locating a good copy of this file.

    Hardware:
    Dell Dimension 8300
    Intel Pentium4 Processor @2.66 GHz
    2.5 GB RAM

    Operating System:
    Windows XP Pro SP1

    Situation:
    I am attempting to start the new installation of XP Pro and upgrade from SP1 to SP3. I am making the new installation on a reformatted hard drive (HD). The system operates normally when I use only the old HD (also XP Pro, SP1).

    When the new installation of XP Pro SP1 was performed, the reformatted HD was the ONLY HD in the system. I used the XP Pro SP1 disk provided by Dell. The installation proceeded normally except for the following two "˜bumps in the road’.

    BUMP ONE: Error message:

    Setup cannot copy the file MSAFD.DLL.

    One of the options was to press ENTER to try again. I pressed ENTER and the file appeared to copy OK. The copy time for this file was fairly short; maybe 10-15 seconds.

    BUMP TWO: Error message:

    Setup cannot copy the file MSASN1.DLL.

    One of the options was to press ENTER to try again. I pressed ENTER and the file appeared to copy OK. However, this time the copy time for this file seemed to be long; about 2 minutes. That said, the installation did continue and completed.

    After installation, the system rebooted and ran through the screen splash indicating that XP Pro was loading. This was a second screen splash; after the first that included:

    ‘F1 = SETUP’
    ‘F2 = BOOT SELECT (I think)’.

    Part way through booting, with the second splash screen showing, the machine generated the following message:

    STOP: c0000221 {Bad image checksum}
    The image MSASN1.DLL is possibly
    corrupt. The header checksum does not
    match the computed checksum.

    At this point I restarted the machine using the XP Pro SP1 installation CD and entered the "˜Recovery Console’ mode. I confirmed that the file existed using the command:

    D:\I386> DIR NSASN*.*

    The response received:

    The volume in drive D is XPSP1_PRO_ENG
    The volume Serial Number is f8ee-e1bd

    Directory of D:\I386\MSASN*.*

    09/03/02 07:46p --r----- 23707 MSASN1.DL_
    1 file(s) 23707 bytes
    0 bytes free

    I then attempted to expand MSASN1.DL_ from the boot CD using the command:

    D:\I386> EXPAND MSASN1.DL_ C:\I386\ MSASN1.DL_

    The machine ran for more than a minute and then returned:

    The file could not be expanded

    I then tried to copy the file from the XP Pro SP1 installation CD to the HD so that it could be expanded there using:

    D:\I386> COPY MSASN1.DL_ C:\I386\ MSASN1.DL_

    This time the machine ran for about a minute and then returned:

    1 file(s) copied.

    So, I moved to C:\I386 and generated the following command:

    C:\I386> EXPAND MSASN1.DL_ C:\I386\ MSASN1.DL_

    And received the following response:

    The file could not be expanded

    I am at a loss as to what to try next. Can someone help?

    D
     
  2. 2009/10/13
    Steve R Jones

    Steve R Jones SuperGeek Staff

    Joined:
    2001/12/30
    Messages:
    12,315
    Likes Received:
    252
    Welcome to WindowsBBS;)

    One little spec of dust on the cd or inside the cd drive can cause this. Try cleaning both.
     

  3. to hide this advert.

  4. 2009/10/13
    dcm30096

    dcm30096 Well-Known Member Thread Starter

    Joined:
    2009/08/17
    Messages:
    6
    Likes Received:
    0
    Steve,

    Thanks for the prompt response. The CD Drive will not eject the CD. It was working fine until the long expand and copy eptisodes mentioned above. I tried to override the eject button by using the end of a paperclip in the small hole in the front of the drice to no avail. I am hesitant to turn off the system because of the length of the restart from the XP Pro Installation CD and the possibility that the system may not reboot. Any suggestions on to get the CD to eject?
     
  5. 2009/10/13
    surferdude2

    surferdude2 Inactive

    Joined:
    2004/07/04
    Messages:
    4,009
    Likes Received:
    23
    Also recheck your Copy and Expand command lines. They will not work if they were as you posted them.

    1. There is an inappropriate space between the \symbol and the M on each command. Another one between the > and the start of the command line.

    2. You are trying to expand the file upon itself, which won't execute. You must either change the name or location to get the command to succeed.

    I suggest:

    1. D:\I386>COPY MSASN1.DL_ C:\I386\MSASN1.DL_

    2. C:\I386>EXPAND C:\I386\MSASN1.DL_ C:\I386\MSASN1.DLL

    or simply, EXPAND MSASN1.DL_ MSASN1.dll if you are resident in the C:\I386 directory.
     
    Last edited: 2009/10/13
  6. 2009/10/13
    dcm30096

    dcm30096 Well-Known Member Thread Starter

    Joined:
    2009/08/17
    Messages:
    6
    Likes Received:
    0
    REPLY AT 12:07 PM, 10/13/2009
    Hi surferdude2,

    Thanks for your response. The commands shown in the initial post were wrong. That section should have read:

    ~====~====~====~====~====~====~
    I then tried to copy the file from the XP Pro SP1 installation CD to the HD so that it could be expanded there using:

    D:\I386> COPY MSASN1.DL_ C:\I386\MSASN1.DL_

    This time the machine ran for about a minute and then returned:

    1 file(s) copied.

    So, I moved to C:\I386 and generated the following command:

    C:\I386> EXPAND MSASN1.DL_ C:\I386\MSASN1.DLL

    And received the following response:

    The file could not be expanded
    ~====~====~====~====~====~====~

    I just tried the following command:

    C:\I386> EXPAND MSASN1.DL_ MSASN1.DLL

    And received the following response:

    The file could not be expanded

    I then confirmed that the file existed in C:\I386 using the command:

    C:\I386> DIR NSASN*.*

    The response received:

    The volume in drive C is Boot 1007
    The volume Serial Number is fc86-f372

    Directory of D:\I386\MSASN*.*

    08/29/02 10:00a -a------ 51200 MSASN1.DLL
    09/03/02 07:46p -a------ 23707 MSASN1.DL_
    2 file(s) 102400 bytes
    72867065856 bytes free

    I also noticed that your proposed EXPAND command was working with files in root (\), not \I386. Was that intended?

    Finally, do you know of a way to eject a CD if both the button and a paperclip in the small hole in the drive tray do not work? Is there a way to stop the drive in the Recovery Console mode? I am interested in do this so that I can clean the XP Pro Installation CD.

    Thanks for your help,

    Dave
     
  7. 2009/10/13
    surferdude2

    surferdude2 Inactive

    Joined:
    2004/07/04
    Messages:
    4,009
    Likes Received:
    23
    No, I edited in haste to simplify your command and left out part of the path. I have since corrected it.

    As for ejecting the CD, try right-clicking the drive and clicking the Eject command. If that fails, you'll have to bite the bullet and reboot.

    Edit, Now that I read all of your post, I don't think the right-click method is applicable since you aren't in a Windows session. I Guess you're stuck with rebooting or trying the paper clip method again. I have never had that to fail. hmm..
     
    Last edited: 2009/10/13
  8. 2009/10/13
    TonyT

    TonyT SuperGeek Staff

    Joined:
    2002/01/18
    Messages:
    9,072
    Likes Received:
    400
    Don't reboot, just shut off the comp. Then use the paperclicp to remove the cd. Otherwise the disk may be spinning when you use the clip.
     
  9. 2009/10/13
    dcm30096

    dcm30096 Well-Known Member Thread Starter

    Joined:
    2009/08/17
    Messages:
    6
    Likes Received:
    0
    Hi surferdude2,

    I went ahead and shut down the PC. On restart, the eject button and I was able to remove the CD. Careful visual examination, using a 10x magnifier, revealed a small set of three humps in the foil layer of the CD, not on the surface. That said I am looking for another source of the file MSASN1.DLL.

    I was able to find MSASN1.DLL on the working HD that was removed from the machine. Can I copy that file, using another computer, to a removable 3.5” floppy drive and then copy it from the floppy to the HD in the computer that is having trouble?

    On the same subject I noticed that on the working boot drive, the directory \I386 contains over 8,000 files and 50+ folders. On the drive that is being built, the directory C:\I386 contains only three files and no directories. Also of note, all three files are the ones that had to be copied a second time using ENTER during initial setup. Those files are:

    1. MSASN1.DLL
    2. MSAUD32.ACM
    3. MSIDENT.DLL

    Should I replicate these files from the working disk to the appropriate directory? On the working boot disk they are located as follows:

    C:\I386\MSASN1.DLL
    C:\WINDOWS\SYSTEM32\MSASN1.DLL

    C:\WINDOWS\SYSTEM32\MSIDENT.DLL
    C:\I386\MSIDENT.DLL

    C:\I386\MSAUD32.ACM
    C:\WINDOWS\SYSTEM32\ MSAUD32.ACM

    I am also curious as to why the working boot drive has 8,000+ files and the drive that is being setup only has a few. Is it related to the fact that the XP Pro operating system setup process is not yet complete?

    Dave
     
  10. 2009/10/14
    TonyT

    TonyT SuperGeek Staff

    Joined:
    2002/01/18
    Messages:
    9,072
    Likes Received:
    400
    In actuality, data burned onto a cd or dvd is closer to the label side than the shiny side. The data is at the top of the disk.
    yes

    Try copying all the files from the cd onto the hard drive of a working system, then make a new bootable cd out of it. If you get no errors during that copy then all should be well.
     
  11. 2009/10/16
    dcm30096

    dcm30096 Well-Known Member Thread Starter

    Joined:
    2009/08/17
    Messages:
    6
    Likes Received:
    0
    This problem is RESOLVED. Thanks to all that have helped out with this problem.

    To summarize:

    I ran into a problem while loading Microsoft XP Pro, SP1 on to a newly formatted hard drive. During initial installation on the freshly formatted drive, the setup process stalled three times complaining that:

    Setup cannot copy the file MSASN1.DLL
    Setup cannot copy the file MSIDENT.DLL
    Setup cannot copy the file MSAUD32.ACM

    One of the options at each of these hiccups was to press ENTER to try again. I pressed ENTER and the files appeared to load OK.

    Part way through booting from Dell’s XP Pro SP1 installation CD, with the second splash screen showing, the machine generated the following message:

    STOP: c0000221 {Bad image checksum}
    The image MSASN1.DLL is possibly
    corrupt. The header checksum does not
    match the computed checksum.

    At this point I restarted the machine using the XP Pro SP1 Installation CD and entered the "˜Recovery Console’ mode.

    Attempting to expand the file MSASN1.DLL, in several different ways, from both the new installation on the hard drive and the XP Pro SP1 Installation CD from Dell produced the same results:

    The file could not be expanded

    Next the CD was inspected for scratches. Careful visual examination, using a 10x magnifier, revealed a small set of three humps in the foil layer of the CD, not on the surface. Speculating that these humps were causing the file problems, I went looking for another source of the three files in question.

    Since I still had the working, boot-capable hard drive taken out of this machine, I got copies of those files and loaded them on to the new drive (used another computer, copied to a removable 3.5" floppy drive and then copied from the floppy to the HD in the computer that was having trouble).

    With the new files, Windows XP Pro, SP1 completed its set up processes (relief at last). The PC has now been upgraded to SP2 and then SP3 with Windows Explorer 8 and McAfee Total Protection. The only actions that remain are to check for updated drivers for Dell hardware and printers, load the applications, and transfer data files from the old boot disk to the new boot disk.

    Thanks again to all for keeping me pointed in the right direction.

    Dave
     

Share This Page

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.