Line xxxx of the INF file \i386\txtsetup.sif is invalid...

June 20, 2013 at 14:45:57
Specs: Windows XP, Pentium 4
Windows XP setup canot continue. I have the this problem in a Fujitsu Amilo pc which I have reinstalled several times each time with success. The last time I formated HD and installed WinXP as usual. After a few days my wife who is using it, brought it back because the pc could not boot, reporting damaged boot.ini file.
When i try to set up windows Xp from a MS Gold original disk i get this same message with different line number each time.
Could it be a virus?

edited by moderator: email removed

See More: Line xxxx of the INF file \i386\txtsetup.sif is invalid...

Report •

June 20, 2013 at 15:48:50
"Could it be a virus?"
Sounds like it,.

Make sure when you reinstall, you delete ALL partitions & format to NTFS.
XP - D to Delete the selected partition

Here are some examples of why you delete all partitions.

Report •

June 20, 2013 at 17:36:01
If you're getting the 'invalid line' message during an install attempt on a newly formatted drive it could be a dirty or scratched cd or failing cd/DVD drive or a problem with the hard drive.

Oh, it could be bad ram too.

Report •

June 21, 2013 at 14:24:44
My money is on the hard drive being faulty. For confirmation you can test it with purpose-made diagnostic software which loads from a bootable floppy-disk or CD.
Hard drive manufacturer's supply this software for free. The links are here:

Report •

Related Solutions

June 27, 2013 at 15:32:54
It is not a virus. It is not the hard drive. I placed another clean newly partionned and formatted hard drive and the same thing start s happened

Might be the DVD? I suspect the motherboard now or the RAM

Report •

June 27, 2013 at 16:56:24
Nice work, process of elimination.
"Might be the DVD?"
If you can put a clean HD into another comp & use your CD/DVD, that will confirm either way.

Report •

Report •

June 27, 2013 at 17:00:08
"I suspect the motherboard now or the RAM"
Clean the contacts with an pencil eraser & try it again. May need cleaning or reseating. If multi sticks, try just one stick to test.
Troubleshooting Category 1 Memory Problems

Report •

Ask Question