|
|
| Post Number: 1
|
leekirk 
Group: Members
Posts: 4
Joined: Jun. 2007
|
 |
Posted on: Aug. 30 2008,12:45 |
|
   |
Error: txtsetup.sif Corrupt or missing
I test XP build without ezboot and it is fine is it a file attribute setting corrupting it Or?
Edited by leekirk on Sep. 01 2008,20:54
|
 |
|
|
| Post Number: 2
|
Guest
Unregistered
|
|
Posted on: Sep. 01 2008,08:49 |
|
 |
To leekirk
Sorry for delay…
Quote:” Error: setup.sif Corrupt or missing”. I guess you mean txtsetup.sif 
Again I guess you get this message: “Txtsetup.sif missing status (or code):14”. Correct?
This means that setupldr.bin-file can’t find Txtsetup.sif-file.
You have managed to start your boot-file in ezboot-folder, that then starts setupldr.bin
Setupldr.bin starts to look around for txtsetup.sif-file, but no file found… 
Question 1: What Windows-system are we discussion here?
Question 2: How does your structure look like in EasyBoot\folder1
Regards heureka
|
|
|
|
| Post Number: 3
|
leekirk
Group: Members
Posts: 4
Joined: Jun. 2007
|
|
Posted on: Sep. 01 2008,20:27 |
|
|
Windows XP
structure
$OEM$
ACRONIS
BCDW
BOOT
BOOTCD
EFI
ezboot
I386
KNOPPIX
loaderOEM
Software
SOURCES
When I compile the exact same build, without the boot menu, it works fine.
It happens when I integrate the driverpacks.
with driverpack base. Before that it works fine.
|
|
|
|
| Post Number: 4
|
Guest
Unregistered
|
|
Posted on: Sep. 02 2008,08:06 |
|
|
To leekirk
Quote: ”It happens when I integrate the driver packs.
With driver pack base. Before that it works fine.”
It could be that size of txtsetup.sif changes when integrating driver packs and is not accepted, when running setup. Unsure how you made integration - but I now that Nlight in most cases works.
I notice you have i386-folder on the root. I assume this folder has been grabbed from CD/ISO-file in original shape. But if you have run Nlight on i386-folder and later run integration using “Bâshrat the Sneaky way” - you are in trouble.
I must admit that this issue seems to be a hard one to solve. As the logical thinking person you are, you now what causes this problem? Unfortunately I cannot delivery any solution straight off
Regards heureka
|
|
|
|
| Post Number: 5
|
leekirk
Group: Members
Posts: 4
Joined: Jun. 2007
|
|
Posted on: Sep. 02 2008,09:49 |
|
|
Okay thanks I integrated my drivers with nLte
and it works now.
|
|
|
|
|
|
