Hey guys, been using nLite for some time with hardly ever any problems, but with 1.3 I'm suddenly completely unable to log in. I've tried doing the unattended part of the nLite with 1.2.1 but it doesn't make any difference, so I think it must be something weird going on with the new components.. no idea what though. I've attached my last session.ini for your perusal, and below is some unattended information from my last session_u.ini. I'll try it by adding an account instead of renaming the Administrator one next, so I'll get back to you on that.

Nope, I just tried adding myself as a new user (besides the Administrator account) and it still fails to log me on.. This must have something to do with a component I'm removing, but I don't know what. Can you guys check it out for me?

Hey guys,

I do have the same problem.. The wierd thing is that I didn't remove any of the new components.. I just used a Session I made with 1.2.1 and added some Unattended-Stuff and updated the Update- and DriverPacks..

The winnt.sif says (among other things of course):


I also renamed my Admin-Account and didn't want to have any password.. I know that it's possible as I always use these settings..

I'll attach my last_session.ini, if I can .. (Seems it worked)

MelTraX

I just finished an nLite with 1.2.1 with the exact same settings (but none of the new components removed, of course) and it works fine. If MelTraX above me is right, this is a general problem that 1.3 is having on our systems and not related to us removing the new components.

Edit: MelTraX, I'm wondering about something.. Are you assigning your computer to a specific workgroup?

I don't know what you are aiming at but yeah, I do.. No Domain but a workgroup..

If you find a solution, please let me know

It's just that I noticed the unattended section has changed a bit in nLite 1.3.. And I set a workgroup too as you can see. It's a long shot but.. I've got everything working now with 1.2.1 and I have to get some work done; I'll get back to testing tomorrow and see if I can nail this down.

Now... I don't know if this helps but I have the opposite problem... sorta...

I made an installation, used WORKGROUP for workgroup, NEVER touched ANYTHING at the accounts tab.
HOWEVER, having already read this thread BEFORE making my installation CD I alterred the WINNT.SIF some to resemble the one the previous versions created.

So, the installation goes as planned (and at this point I must stress out that it WASN'T a test installation, I actually needed to install windows on my system and that was that), however, subsequently, when windows starts it auto logs on using the Administrator account!!!

In order to log on to my account I have to manually log off and then log on...

I attached the WINNT.SIF I used and the LAST_SESSION.INIs.

So, happy hunting...

Because a few things have changed in 1.2.1 and 1.3beta in terms of the Unattended pages, I'd suggest not using a last session file from a previous nLite version.

I have to admit, I didn't think about that one, Pixelated. Good idea.
Have you tried 1.3 yourself? How's it fare compared to 1.2.1?

Sorry, but I completely started from scratch with 1.3 so that can't be it...

Yup, started from scratch and the results have been very pleasing. A couple of things have been moved/changed in the unattended section in 1.3beta, and I overlooked them (such as Name fieed) but no big deal, I just entered them manually when I reinstalled.

Am running on an nLitendXp install now, and I'm very happy with it

However I can't compare with 1.2.1 as I didn't use that build to create an install that I actually used.

@ people who "cant log on"

What errors are you getting with logging on? Invalid password?

If invalid password, decompress nlite.in_ in your i386 folder, and check the resulting inf file at the very bottom. one of the last few lines should have something like nhelper net1 user xxxxx /add blah blah blah

in there should be your password. Perhaps if you used nlite on top of a cd that was already done with nlite (even without loading a last session), you used a different password and so the correct password is higher up in the file..

That's the line you're refering to I guess (and yes Windows says "Invalid Password"):



As you can see there shouldn't be a password required..

Since I have a physical computer without any use atm, I will revert to 1.2.1.. Actually I already tried twice but my own PC crashed with two different reasons during the nlite-process..

If I have the time I will do some tests in a VM but you know: it's Christmas

Edit: I just gave it another try.. I used the same ini but gave my renamed Admin a password. Installed it in a VM but couldn't login with that password either..

Well, I myself just gave up on 'Unattended' since 1.2.1
...too much of a hassle.

Why go through all those leaps and hurdles, just to have to enter info manually after install anyways? Not worth the headache.

To me, nLite is supposed to save time, which for the most part it does. Spending hours online trying figure out how to save 2 minutes of it seems a little counter-productive. No offense.

Yeah, you have a point there..

But it worked like a charm with 1.2.1... That's why I asked... And I would appreciate if it would work in the non-beta 1.3 ..

Hey guys, I just noticed this post. I don't have time to check it out right now, but if you could confirm that this is what's going on nuhi should be able to fix it easily enough..

That is indeed the line. Are there any other lines within that file that mention that user name and have a format similar to that?

If so, remove them. If not, try removing the /fullname:""""[removed]"""" part of the line.

Once that is done, go back to i386 folder in command prompt and do:

del nlite.in_
makecab nlite.inf

Then test it out. I dont expect to hear from anyone here during the holidays, so its no big deal and take your time.