If windows is trashed so badly that you are considering a repair then a reload is the only viable solution. The result of a repair is a complete disaster as far as registry and related windows files are concerned. I'ts kinda like repairing a nail hole in a bald tire. Why bother patching something that is beyond repair, just replace it with a new one and fix it properly.

If you insist that a repair has to be done in certain instances then I would have a separate disc just for that. That way you can have an unattended install disc and a repair disc. If you are talented you could have a multiboot disc with both attended and unattended on it.

this is the most detailed discussion about it... http://forum.driverpacks.net/viewtopic.php?id=2723

And here is the thread from the "Feature Requests" Forum. http://forum.driverpacks.net/viewtopic.php?id=2733

The repair feature is lost if the [Unattended] section exists in winnt.sif. The unattended section in winnt.sif must exist to prevent the popup of user input dialogs during the install. Winnt.sif is not created if ONLY mass storage textmode is selected... one of the main packs must also be selected (like mass storage) for the Winnt.sif to be created. DriverPacks only supports unattended installations, if you modify your winnt.sif for an attended installation then you do so at your own risk. No issues other than popup user input dialogs have been reported so it should be no problem, it is just not supported by us.

Review: You must make an either or choice, Unattended or Attended (repair is an attended install). If you choose to enable the repair feature then you will give up your (fully) unattended install.

Jeff

; Generated by nLite 1.4.9.1

[Data]
Autopartition=0
MsDosInitiated=0
UnattendedInstall="Yes"

[SystemRestore]

[GuiUnattended]
OemSkipWelcome=1

[Components]

[UserData]
ProductKey="XXXXX-XXXXX-XXXXX-XXXXX-XXXXX"

[RegionalSettings]
LanguageGroup=1
Language= "0409"

[Networking]
InstallDefaultComponents="Yes"

[Identification]
JoinWorkgroup="WORKGROUP"

At this point it prompts me to repair, it shows Eula, prompts me to format the partition and to choose regional settings. It's exactly like I wanted.

After integrating Mass Storage drivers winnt.sif looks like this:

; Generated by nLite 1.4.9.1

[Data]
Autopartition=0
UnattendedInstall="Yes"
	MsDosInitiated=No

[SystemRestore]

[GuiUnattended]
OemSkipWelcome=1

[Components]

[UserData]
ProductKey="XXXXX-XXXXX-XXXXX-XXXXX-XXXXX"

[RegionalSettings]
LanguageGroup=1
Language= "0409"

[Networking]
InstallDefaultComponents="Yes"

[Identification]
JoinWorkgroup="WORKGROUP"


;
; Edited by DriverPacks BASE 10.06
; http://www.driverpacks.net/
;


[Unattended]
	DriverSigningPolicy=Ignore
	NonDriverSigningPolicy=Ignore
[GUIRunOnce]
	command9="%SystemDrive%\DPsFnshr.exe"

But it doesn't prompt me to repair, it doesn't show Eula, it doesn't prompt me to format the partition (just installs over) and to choose regional settings.

In Nlite if I choose "Unattended=DefaultHide" (until now I have chosen "PromptRepair") it allows me to format the partition and I can set regional parameters in winnt.sif. But it's not enough.
If I erase "DriverSigningPolicy=Ignore" and "NonDriverSigningPolicy=Ignore" from winnt.sif all is fine (it prompts me to repair, Eula, format etc). But I think it will generate other problems...

My question is: how can I build a XP installation CD with serial number and mass storage drivers included that prompts me to repair, shows Eula, prompts me to format the partition and let me choose regional settings?

I know, this seems like a question for msfn forums (nlite section) but I'm asking here because integrating mass storage drivers triggers the problem.

Thanks in advance for any reply.

Best regards, Cosmin3