[embe]

Hi all,

1st of all excuse my english as it`s not excellent.

I`m quite familiar to nLite and since I found this SW some months ago I didn`t use full XP...
My lite XP installation (install CD has cca 150-155 MB)works since Oct 2005 without any problem, nor during the instllation and also after installing necessary software, playing games, etc.. everything work perfect, fast and stable. Since I found nLite is not the end in my experiments I started to focus on adding addons to my XP install CD. I`m absolutely noob in this so I was lookin here what and how to do and I found utility called USSF or so (this util helps you to identify silent switch etc). I tested it, a lot of "sorry, unknown installer but after some changes it worked and I identified some installers (even if it cannot recognize NERO etc...) Then I went sleep and using SW "Turn off" I turned it of after 1 hour. I heard PC turned off and in the morning I get windows message: System is not completely installed, please run setup again. It pop up very near to moment when icons on desktop shows. One of my nLite tweaks is "show WIN version on the desktop. I saw WIN version on the desktop (maybe this info might help to identify what happened). I tried to run PC in safe mode but the result is the same. Does anybody met such situation?

Tks,
embe

This post has been edited by embe: 04 August 2006 - 02:50 AM

[Camarade_Tux]

Start -> Run -> setuperr.log.
Does it says anything.

[embe]

Camarade_Tux, on Aug 4 2006, 02:15 PM, said:

Start -> Run -> setuperr.log.
Does it says anything.

Hi, the problem is that WIN stops prior to showing anything except it`s version (tweak from nLite in right bottom corner). I can`t do anything excpet press OK and if I do so it results into restart:-(

[Camarade_Tux]

Use a bootcd to get it.

[embe]

Camarade_Tux, on Aug 4 2006, 05:08 PM, said:

Use a bootcd to get it.

Too late , system reinstalled...anyway, thanks

[jkey]

For me this was .NET silent installer fault!

[Camarade_Tux]

jkey, on Aug 5 2006, 04:15 PM, said:

For me this was .NET silent installer fault!

This happens/happened when you ran .net silent installer with T-12/T-13 modification after installation is complete (after the second reboot).
Windows simply reads a reg key to know if installation has completed. .Net installer checks the value of this key and depending on the result : it installs or not.
.Net unattended installer sets this registry key to something meaning 'installation completed', runs classic .net installer, waits for it to finish and set the key back to 'installation not completed' whatever was the original value.
(I ran this installer days after windows was installed. Solved with UBCD4Win.)


I don't know if Aserone's installer has been updated.

[embe]

Camarade_Tux, on Aug 5 2006, 04:47 PM, said:

jkey, on Aug 5 2006, 04:15 PM, said:

For me this was .NET silent installer fault!

This happens/happened when you ran .net silent installer with T-12/T-13 modification after installation is complete (after the second reboot).
Windows simply reads a reg key to know if installation has completed. .Net installer checks the value of this key and depending on the result : it installs or not.
.Net unattended installer sets this registry key to something meaning 'installation completed', runs classic .net installer, waits for it to finish and set the key back to 'installation not completed' whatever was the original value.
(I ran this installer days after windows was installed. Solved with UBCD4Win.)


I don't know if Aserone's installer has been updated.

My Lite XP CD was pure XP with SP2 and with no hotfixes and addons. Framework added after installation completed; I run this WIN since Oct/2005. I think it happend because I installed one SW from here but I can remember it`s name - it has several options by right clicking on any file (including AutoIt and recognizing istallation type/switch for silent install)....

[embe]

Camarade_Tux, on Aug 5 2006, 04:47 PM, said:

jkey, on Aug 5 2006, 04:15 PM, said:

For me this was .NET silent installer fault!

This happens/happened when you ran .net silent installer with T-12/T-13 modification after installation is complete (after the second reboot).
Windows simply reads a reg key to know if installation has completed. .Net installer checks the value of this key and depending on the result : it installs or not.
.Net unattended installer sets this registry key to something meaning 'installation completed', runs classic .net installer, waits for it to finish and set the key back to 'installation not completed' whatever was the original value.
(I ran this installer days after windows was installed. Solved with UBCD4Win.)


I don't know if Aserone's installer has been updated.

It`s pity that I just reinstalled win after this happened and I didn`t check for the solution. So it happens again after I included framework 2.0 (Framework 1.1 added a long time ago and tested several times wiith other wares in VMW many times - after each programm added).
What I have to do now? Is there a chance to return Windows to work without reinstalling? What`s the UBCD4Win and what to do with it?

Thanks, embe