Problem installing programs

Discussion in 'OT Technology' started by conduit, Nov 18, 2004.

  1. conduit

    conduit sup

    Joined:
    Oct 27, 2001
    Messages:
    7,024
    Likes Received:
    0
    Location:
    on the interwebs
    I have windows 2000 pro, and everytime i try to install office xp or profile, during the installation it will say it cannot find a .cab file meanwhile its right there on the cd, and other times it says that the .cab file is corrupt and cannot be used. The .cab files change everytime i try to install it. With profile, it says that the file it is copying is corrupt, but when i try to install it on my older pc, they work fine.
    Do you guys know any way in fixing this problem?
    I have tried to re-install windows (2000, XP, ME) many times, and even during the installation part is sometimes gave me "this file is corrupt" or "this file is missing. etc..."
    I have tried to replace the cdrom from my old pc to this one, with the same result. I even tried to copy the files onto my old hard drive, put that in as a slave, and than install the programs but the same thing happends.
    Do you guys know what could be wrong, and how to fix it? :x:
     
  2. P07r0457

    P07r0457 New Member

    Joined:
    Sep 20, 2004
    Messages:
    28,491
    Likes Received:
    0
    Location:
    Southern Oregon
    bad cdrom, bad cable, bad memory.

    if you've tried a new cdrom, then check the ribbon cable and memory.
     
  3. conduit

    conduit sup

    Joined:
    Oct 27, 2001
    Messages:
    7,024
    Likes Received:
    0
    Location:
    on the interwebs
    how would i check the memory? I chceck all the connection and cable connections, and they all seem fine and firm. Is there a program that can check my memory and possibly harddrive?
     
  4. P07r0457

    P07r0457 New Member

    Joined:
    Sep 20, 2004
    Messages:
    28,491
    Likes Received:
    0
    Location:
    Southern Oregon
    memtest86 for the memory. seagate diagnostics for the hdd.

    also try swapping memory.

    A visual check of the cables is not sufficient. You must try a new cable.
     

Share This Page