Reply
Old June 17th, 2005 Top | #1
 
rainer79's Avatar
OSNN Junior Addict
Joined: June 2005
Posts: 4
Reputation: 0
Power: 0

Default Boot Problem (txtsetup.sif is corrupt)

Last night I restarted Windows (XP PRO), and it hung on the reboot before getting to the Win logo. I rebooted again and again and it never progressed to Windows. Nothing had been troubling before this. I tried booting from the Windows CD, but got the following error:

Inf file txtsetup.sif is corrupt or missing, status 32768. Setup cannot continue. Press any key to exit.

Any suggestions would be most appreciated!
rainer79 is offline   Reply With Quote
Old June 17th, 2005 Top | #2
 
American Zombie's Avatar
OSNN Veteran Addict
Joined: June 2004
Location: Seattle
Posts: 2,864
Reputation: 2689
Power: 151

Default Re: Boot Problem (txtsetup.sif is corrupt)

Look into either bad media or hardware.

May want to test your memory as well.
American Zombie is offline   Reply With Quote
Old June 17th, 2005 Top | #3
 
Petros's Avatar
Thief IV
Joined: May 2003
Location: Pacific Northwest
Posts: 3,038
Reputation: 1647
Power: 156

Default Re: Boot Problem (txtsetup.sif is corrupt)

If you have the opportunity, try taking out one stick of RAM at a time (if you have two) or replacing the RAM with something else. Usually, setup problems are due to bad memory. Although I have had a persistent setup problem that never went away until I replaced a power supply...maybe the voltage spikes were causing logic problems. Who knows?
Petros is offline   Reply With Quote
Old June 17th, 2005 Top | #4
 
rainer79's Avatar
OSNN Junior Addict
Joined: June 2005
Posts: 4
Reputation: 0
Power: 0

Default Re: Boot Problem (txtsetup.sif is corrupt)

I'll try removing each memory stick in turn and will repost tomorrow (or tonight if it works!). Thanks.
rainer79 is offline   Reply With Quote
Old June 18th, 2005 Top | #5
 
bush dogg's Avatar
OSNN Senior Addict
Joined: January 2004
Location: Kansas
Posts: 431
Reputation: 590
Power: 112

Default Re: Boot Problem (txtsetup.sif is corrupt)

Also run the hard drive manufacturer's diagnostic utilities on the hard drive it may have died.

Just last month a friend of mine had the same problem (the hard drive failed the test) he replaced the hard drive and everything went fine.

I just replace the hard drive in one of my systems today this system would take 15 minutes to get to windows the few time it did. (it to would hang just before the windows logo or windows loading)

What sucks is this was the second hard drive this week to go down in two different machines.
bush dogg is offline   Reply With Quote
Old June 20th, 2005 Top | #6
 
rainer79's Avatar
OSNN Junior Addict
Joined: June 2005
Posts: 4
Reputation: 0
Power: 0

Default Re: Boot Problem (txtsetup.sif is corrupt)

I swapped out the RAM as suggested, but the memory was fine. I've tried restarting in all the various safe modes, but the computer always hangs. I'd like to try running the hard drive diagnostics as bush dogg suggests, but I don't know how to do this. Could someone provide instructions or a link to such? Assuming the hard drive *has* died, what options do I have for recovering data? Also very much interested in any other ideas as to what to check. Thanks!
rainer79 is offline   Reply With Quote
Old June 20th, 2005 Top | #7
 
American Zombie's Avatar
OSNN Veteran Addict
Joined: June 2004
Location: Seattle
Posts: 2,864
Reputation: 2689
Power: 151

Default Re: Boot Problem (txtsetup.sif is corrupt)

Originally Posted by rainer79
I'd like to try running the hard drive diagnostics as bush dogg suggests, but I don't know how to do this. Could someone provide instructions or a link to such?
Need manufacture of drive.
American Zombie is offline   Reply With Quote
Old June 20th, 2005 Top | #8

OSNN Folding Team  
VenomXt's Avatar
Blame me for the RAZR's
Joined: March 2004
Location: Houston, Texas
Posts: 3,442
Reputation: 1240
Power: 146

Default Re: Boot Problem (txtsetup.sif is corrupt)

What sucks is this was the second hard drive this week to go down in two different machines.

I would tell him to change his PSU i had a similar problem and lost 3 drives before i relized it was my PSU going on slowely and taking things with it.
VenomXt is offline   Reply With Quote
Old June 21st, 2005 Top | #9
 
rainer79's Avatar
OSNN Junior Addict
Joined: June 2005
Posts: 4
Reputation: 0
Power: 0

Default Re: Boot Problem (txtsetup.sif is corrupt)

I disconnect both CD-ROMs, the floppy drive, and audio card, and still it won't boot (I'd already tried the memory). When I disconnected the ZIP drive (Primary Slave), I got an error saying no OS was installed. Ideas? Was wondering if a bad power supply could give such problems (would like to know whether this is possible before going out and getting a new one). Thanks!
rainer79 is offline   Reply With Quote
Old June 21st, 2005 Top | #10
 
Mastershakes's Avatar
OSNN Veteran Addict
Joined: July 2004
Location: Montreal
Posts: 1,721
Reputation: 1040
Power: 124

Default Re: Boot Problem (txtsetup.sif is corrupt)

http://support.microsoft.com/default...b;EN-US;310064

Here you are Rainer, good luck. The final suggestion should be standard on any XP install. copy the i386 folder over first.

This behavior may occur if any one of the following conditions is true: • Your Windows XP CD-ROM is scratched, smudged, or dirty. Clean the Windows XP CD-ROM with a soft cloth, insert it in the CD-ROM drive, and then click OK.
• Your CD-ROM drive is not working correctly or the CD-ROM might be vibrating too much for the laser to accurately read the data. For more information about this problem, see your hardware documentation or contact the CD-ROM manufacturer.
• If you are using multiple CD-ROM drives, your computer may be trying to locate files on the wrong drive. If your hardware has a feature to disable CD-ROM drives that are not being used, disable the CD-ROM drives that you are not using.
• Your computer is over-clocked. Because over-clocking is very memory-intensive, decoding errors may occur when you extract files from your Windows XP CD-ROM.
• Try to use the default clock timings for your motherboard and processor. For more information about how to do this, see your hardware documentation or contact the motherboard manufacturer.
• Your computer has damaged or mismatched random access memory (RAM) or cache memory. For example, you might be using a combination of extended data out (EDO) and non-EDO RAM, or different RAM speeds.

Decoding errors may occur even if Windows appears to be running correctly. These errors occur because of the additional stress that is put on your computer when Windows tries to extract files and to access the hard disk.

To determine how to make your computer cache memory unavailable while you are running the Setup program, see your hardware documentation or contact your hardware manufacturer.
• Ultra direct memory access (DMA) is turned on in your computer's CMOS settings, and the data is moving too quickly.
• Change from DMA mode to Processor Input/Output (PIO) mode to lower your data transfer rate. If this does not resolve the problem, lower your PIO mode settings. The higher your PIO mode settings are, the faster your data transfer is.
• You are using a third-party memory manager.
• There is a virus on your computer.
If you continue to receive this error message, copy the i386 folder from the CD-ROM drive to your local hard disk, and then try to run the Setup program from your hard disk.
Mastershakes is offline   Reply With Quote

Reply

Bookmarks

Thread Tools

Posting Rules

Similar Threads
Thread Thread Starter Forum Replies Last Post
XP can not boot, Corrupt HAL.DLL Recovery console doesn't see my SATA drive gonaads Windows Desktop Systems 5 May 25th, 2007 8:23pm
Big Problem with corrupt folder...please help Summmer Windows Desktop Systems 5 February 25th, 2007 1:31pm
system can't boot because of C:\Windows\System32\Config\System is corrupt logisticprism Windows Desktop Systems 11 August 20th, 2004 7:03pm
txtsetup.sif error understarz1180 Windows Desktop Systems 1 December 12th, 2003 12:16am
Boot Problem HELP Jz1397-5 Windows Desktop Systems 1 June 13th, 2002 11:22am