johnhc

Noisrevid, beats is correct and your Preset should be available now unless you have both disabled the Option to save it and deleted it from the Presets folder. Your Last Session.ini should be in your nLited directory and with a date/time code in the nLite/Presets folder in the Program Files folder. Enjoy, John.

Noisrevid, you can certainly try deleting it from the NLDRV folder. It will be in a folder named 001, 002, etc. Just delete the whole folder. I am fairly sure it will not get installed, but may produce errors during Setup. I also found a reference to one of my drivers in DOSNET.INF. You can also delete this reference. You may be digging a deep hole, so please keep copies of the stuff you are deleting or plan on starting over. Please let us know what you tried and the results. Good luck, John.

Okamiryu, please see this forum and the AddOns forum above the nLite forum. Enjoy, John.

Noisrevid, remove it from what? The best way, obviously, is to start over with a fresh source. NLite places the drivers in a folder called NLDRV, but there may be references to them elsewhere. Enjoy, John.

I have learned in further searching that AutoLogon.exe uses LsaStorePrivateData (part of MS LSA, Local Security Authority) to set the AutoLogon PW. What I suspect this means is that the PW can be read from the system on which it is set but not from any other systems on a network. Since I do not have a networked PC, I hope someone will run a test on a machine on a network and try to see the PW on another system on which the PW was set by AutoLogon.exe. In my last reply, I used the NetPass program from the Nirsofts site referenced in -X- last reply. Thanks, John.

EvveLover, I am not familiar with eXPerience Tiny,MicroXP.. and don't know if -X- is correct that it should not be commented on here. I hope a moderator will look at this and give us a opinion. In the meantime, please tell me what it is and where you got it. Is it a legal version of Windows? Did you purchase it and have a valid and legal key? Thanks, John.

dm83737, don't know. Please post a link to the drivers and we will take a look. Also, please attach (not paste) your Last Session.ini. Make sure to always start with a fresh copy of your CD files/folders, do all your work in one nLite session and integrate only one SP. Please report when you have a solution, so others can benefit. Enjoy, John.

tazosmr, not enough of your Last Session is shown to help you. Please do this: Delete the pasted Last Session and, please attach (not paste) your Last Session.ini. Make sure to always start with a fresh copy of your CD files/folders, do all your work in one nLite session and integrate only one SP. Please report when you have a solution, so others can benefit. Enjoy, John.

EvveLover, as requested before, please attach (not paste) your Last Session.ini. Make sure to always start with a fresh copy of your CD files/folders, do all your work in one nLite session and integrate only one SP. Please report when you have a solution, so others can benefit. Enjoy, John.

-X-, I stand corrected, I am wrong and you are correct. I DLed NetPass (XP x64) and it found the AutoLogon PW no matter how I set it. Interestingly, only control userpasswords2 would delete it so that NetPass could not find it. Even deleting it with NetPass did not prevent it from being found. You are correct that the only way yet found to enable AutoLogon exposes the PW. Thanks, John.

It would be nice to hear from the OP, but the nLite Option "Hit any key..." does not work for XP x64. It should not be used in any case because you end up in a boot from CD forever loop during Setup - many threads about this. If we knew, for example, what language the OP's source is in, we could tell, perhaps, why some are not being removed. Windows will not allow certain languages to be removed according to the source language. The OP may really want this fixed, but if it is an nLite bug, which I seriously doubt, nuhi (nLite Owner/Author) has not graced us with his presence in some time and the chances for any changes are indeed slim. Enjoy, John.

EvveLover, perhaps it would help us (me at least) if you would post in your native language and translate it for us using Google Translate, or you favorite site. Thanks, John.

Gray__Fox, several threads have been posted with walks through, but I cannot vouch for their accuracy. This post, is for XP x64, but is a great example of a complete install of all one could possible need. Enjoy, John.

-X- , you will need to run your own experiments. I certainly have not come to your conclusion, in fact, I think if one uses TweakUI, control userpasswords2, or autologon.exe (and delete the DefaultPassWord from the Registry), you will not be able to find the AutoLogon PW any more than you will be able to find the account PW. I do not have a PW scanner on my system. Please read all that has gone before this and let us know the results of your experiments. Enjoy, John.

karchen, thanks for the kind greetings! Post a link to the drivers you are using and, please attach (not paste) your Last Session.ini. Make sure to always start with a fresh copy of your CD files/folders, do all your work in one nLite session and integrate only one SP. Please report when you have a solution, so others can benefit. Enjoy, John.

sam1984, I suspect -X- is correct. What do you mean by "dont install during windows installation"? How do you know it did not install? If you have a hot fix that did not install why would you need to remove it? Please run qfecheck (DL from MS DL center) and see if it thinks the hot fix is there. Also, please attach (not paste) your Last Session.ini. Make sure to always start with a fresh copy of your CD files/folders, do all your work in one nLite session and integrate only one SP. Please report when you have a solution, so others can benefit. Enjoy, John. EDIT: It may be possible to remove a hot fix by DLing the update, then using the uninstall function in it. I have not tried this, but would be curious to see if it works.

masterpointer, advanced I am not. I don't know what "using Autocontrol Logon" is. As far as I know, using AutoLogon.exe, if you delete the DefaultPassword value from the Registry, the PW will be hidden. I don't know the answer, but I suspect the same method is used on the AutoLogon PW as on the account PW. The routine that processes Logon/Logoff (MSgina), reads the PW and I would think the encryption would be the same. Using AutoLogon automatically exposes my machine if I don't have physical protection. What I was concerned about was the possible retrieving of my PW via a 'call home' type of virus/worm. I have edited my first post and added some more 'what I learned' items. Enjoy, John.

Please see this thread for a proposed work around for the plain text PW. Enjoy, John.

In this thread, -X- reported finding the AutoLogon Password in the Registry in plain text. Running TweakUI or Control userpasswords2 hides/encrypts the password and deletes the plain text value (DefaultPassWord). After doing some searching, I found a small free program from Sysinternals that will hide/encrypt the password (but not delete the plain text one). I created a small AutoIt script that would do the necessary actions around AutoLogon.exe to make it unattended and delete the plain text PW. #cs ---------------------------------------------------------------------------- AutoIt Version: 3.3.0.0 Author: johnhc (6-28-2009) Script Function: Encrypt/Hide the AutoLogon Password. #ce ---------------------------------------------------------------------------- ; Read the AutoLogon Parameters and test them for null or missing, quit if so. $PassWord = RegRead("HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon", "DefaultPassword") If $PassWord = "" Then Exit $DomainName = RegRead("HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon", "DefaultDomainName") If $DomainName = "" Then Exit $UserName = RegRead("HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon", "DefaultUserName") If $UserName = "" Then Exit RegDelete ("HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon", "DefaultPassword") $AutoLogonParms = $UserName&" "&$DomainName&" "&$PassWord Run (@ScriptDir&"\Autologon.exe "&$AutoLogonParms) WinWaitActive ("A License Agreement","",2) Send ("!A") WinWaitActive ("Auto") ControlClick ("Auto","","[CLASS:Button; INSTANCE:1]")This is offered with no guarantees. Remember it does read and delete values from the Registry. If you don't like the code, change it to your liking or create you own method, or simply run AutoLogon.exe and accept that it is not unattended and leaves your plain text PW. This source needs to be compiled for your system. I place the compiled AutoIt script and the AutoLogon.exe into the same folder and call the AutoIt script from the nLite RunOnce exit. Some other information I gathered in my searching and testing: If there is there is a plain text PW and a hidden one, the plain text one takes precedence. The AutoLogon PW needs to be the same as the account PW or AutoLogon will fail and ask for the PW. If the account PW is changed, AutoLogon will fail unless its PW is also changed explicitly. The AutoLogon keys are set in nLite.inf (NLITE.IN_). nLite.inf also uses nhelper to setup user accounts with the net (really net1) command. Both of the last two items expose the account PW in plain text. This may well not work on W2000. The bottom line, at this time, is there is no way to enable AutoLogon and prevent a PW finder from exposing the PW. See replies from -X- and me, below. I have tested this on my XP x64 system under VMware Server. Enjoy, John.

EvveLover, most of nLite's Registry changes are in nLite.inf (NLITE.IN_) after running nLite. There are no comments, but the changes are there. Enjoy, John.

gamehead200, thanks for your kind response to my reply. I do not agree with: But, I am glad I have flushed out the Mac expert and you have explained what F5 is about (news to me, as is MBP, Boot Camp, EFI Interface) and answered the OP's question. Enjoy, John.

masterpointer, I, too don't understand how to use the Quote and Quote+, so I just quit using them. No big deal, I was just wondering where you were headed. I have never seen your reply. Enjoy, John.

melissah, I had looked at your Last Session. I just pasted my whole plea. I see no problem there. You did not comment on the F6 question. You cannot use F6 unless you disable OEM Preinstall in Unattended. Have you tried to install with the original CD? If it works OK, try an nLited one with as few changes as possible to get an unattended installation. Please let us know. Enjoy, John.

melissah, I think the big problem here is that we know almost nothing about Mac computers here. I know nothing. Installing on a IBM compatible PC never asked the "Standard PC option" question that I am aware and I don't have a clue what it means. I don't think it is coming from Windows Setup. Where is it coming from? From my Windows experience, I would wonder if you need text mode drivers for your HDDs - SATA? Are you trying to use F6 to install drivers? Have you done a search here and in Google for using nLite against a Mac? I'm kinda thrashing here, sorry. Here is my standard plea - please attach (not paste) your Last Session.ini. Make sure to always start with a fresh copy of your CD files/folders, do all your work in one nLite session and integrate only one SP. Please report when you have a solution, so others can benefit. Enjoy, John.

spinjector, I have not tried any of this, but my suggestion is to give it a try and report what you learn. I highly recommend a virtual system for the testing (VMware Server, VirtualPC, VirtualBox - all free). Enjoy, John.