docmorris-17

Thanks , johnhc, for your interest and investigations. i thought to get to the origin of this problem if i know how nlite.inf is evoked. Formerly i did modification on the nlite.inf by myself, but soon noticed that this is laborious and often causes other problems. Now, to integrate my registry tweaks, i use the entries.ini and within the [registry_addreg]-section. I did a lot of work in this file and -by mistake- inserted a "malicious" entry, that was integrated just at the beginnig of the nlite.inf: (f.e.) HKU,"SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Advanced","SeparateProcess",0x00010001,1 Do you discover whats wrong with this? Normally a typing error causes an error at the end of textmode-setup when the HIVEs are beeing loaded. This doesn't. correct is: HKU,".DEFAULT\Software\Microsoft\Windows\CurrentVersion\Explorer\Advanced","SeparateProcess",0x00010001,1 Now i suppose this is what stopped processing nlite.inf immediately. It seemed that nlite.inf wasn't processed at all. Still i don't know why your nlite.inf is so huge. Mine never has been bigger (32-bit). [bitReg]-section is of nlite's origin. As far as i understand, nlite does analyse the keys to be integrated whether they are a sort of general HKLM,[... or specific HKCU,[... ! HKLM-keys can be processed during T-13, so they get into [T]-section. HKCU-key get into [CT]-section. In additon, for some reason, nlite seems to convert HKCU-keys to HKU-keys that, in turn, get into the [T]-section. Do you understand what i mean? I'm not sure if i make it clearly? [TO] (...) HKU,".DEFAULT\Software\Microsoft\Windows\CurrentVersion\RunOnce","_nltide_3",0x00020000,"rundll32 advpack.dll,LaunchINFSectionEx nLite.inf,C,,4,N" (...) [C] BitReg = B AddReg = CT [CT] HKCU,"Control.... HKCU,"Control.... ..... many thanks so far for your help. maybe this helps somebody else too. Pay attention to your tweaks!!

you're right, this would be possible. But all of nlite's own tweaks then still won't be applied. Nhelper.exe for example would not be deleted, etc. I'd prefer to solve this problem before i switch to another method.

hi, thnx for your answer. But... none of the tweaks are applied. I have already tested this. That is the reason I noticed and came to the conlusion nlite.inf isen't run anymore. I tried tho following modification on the nlite.inf before xp-setup: "\Run" instead of "\RunOnce" ... just to try and proove if i*m right [TO] HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\Run","nlite_post_00",0x00000000,"nhelper net1 accounts /maxpwage:unlimited" HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\Run","nlite_post_01",0x00000000,"nhelper net1 user """"Administrator"""" /comment:""Eigentümer"" /passwordreq:no" HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\Run","nlite_post_02",0x00020000,"nhelper rd /q /s """"%SystemRoot%\System32\ime""""" HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\Run","nlite_post_03",0x00020000,"nhelper rd /q /s """"%SystemRoot%\msagent""""" HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\Run","nlite_post_04",0x00020000,"nhelper rd /q /s """"%SystemRoot%\Srchasst""""" HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\Run","nlite_post_05",0x00020000,"nhelper rd /q /s """"%SystemRoot%\Help\Tours""""" HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\Run","nlite_post_06",0x00020000,"nhelper delete ""%SystemRoot%\System32\drivers\flpydisk.sys""" HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\Run","nlite_post_07",0x00020000,"nhelper rd /q /s """"%\Connection Wizard""""" HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\Run","nlite_post_08",0x00020000,"nhelper rd /q /s """"%SystemRoot%\System32\dllcache""""" HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\Run","nlite_post_09",0x00020000,"nhelper md """"%SystemRoot%\System32\dllcache""""" HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\Run","nlite_post_s01",0x00000000,"rundll32 advpack.dll,LaunchINFSection nlite.inf,U" HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\Run","nlite_post_s02",0x00020000,"nhelper del /q /s """"%\SET*.TMP""""" HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\Run","nlite_post_s03",0x00020000,"nhelper delete ""%\SET3.TMP""" HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\Run","nlite_post_s04",0x00020000,"nhelper delete ""%\INFCACHE.1""" HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\Run","nlite_post_s05",0x00020000,"nhelper moveex ""%\syssbck.dll"" ""%\syssetup.dll""" HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\Run","nlite_post_s06",0x00020000,"nhelper moveex ""%\syssbck.inf"" ""%\syssetup.inf""" HKU,".DEFAULT\Software\Microsoft\Windows\CurrentVersion\Run","_nltide_3",0x00020000,"rundll32 advpack.dll,LaunchINFSectionEx nLite.inf,C,,,N" HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\Run","nlite_post_s07",0x00020000,"nhelper delete ""%\nhelper.exe""" ((don't mind the symbol here - thats just an copy-paste error of %11% for example.)) Now, after xp-setup none of the tweaks were found in the registry. Even switching to "automatic" (processortype) has no influence on executing nlite.inf. I guess Nuhi will know whats the matter about. @ Nuhi: Is there a log-file after xp-setup? How can i make sure nlite.inf will be processed during setup? Consider that i already tried to reinstall new nlite-version. I never do nlite twice. I did a clean copy of the xpcd.

@johnhc i*m using 32-bit XP-version of mce. Its the entire nlite.inf that i provided here. next time i*ll try an english run-through so that you can read my LS.ini my processor actually is a AMD Turion64x2, so it meant to be a dual-core proc. But the thing about your concern what still makes me consider about to be correct is that i do test-installations an a virtual-machine (VirtualBox). Possible that it cannot emulate a multi-core processor? but no errors occured during xp-setup nor nlite-run.. concerning MCE an SP3: there never was doubt about it in the many installations before, where a noticed no problems. still i just remarked that WINDOWS\System32\nhelper.exe isn*t deletet anymore, so i wonder if nlite.inf is actually installed/processed. i already found out that sysoc.inf calls nlite.inf, dosen*t it? then how can i make sure that my nlite.inf will be processed before i do the next xp-setup? Please help, i*m almost

i aready did my best to refind the missing tweaks, but no success yet. i always use i clean copy and never do twice nlite on the same copy. have no ideas anymore.

Hi, since some installations I noticed two problems with the nlite.inf-file. Im using nlite Ver. 1.4.9.1 on XP MCE 2005. Maybe you can halp me with these questions: 1) I used to integrate my own reg-tweaks with the entries.ini through [registry_addreg]. Most of them i can find in the nlite.inf-file, but not all. Why? Is there any other place nlite stores the tweaks? 2) Some of nlites own tweaks doesn*t appear in the registry after the xp-setup. For example HKCR,"Directory\shell\cmd","",0x00000000,"@%SystemRoot%\system32\shell32.dll,-22022" HKCR,"Directory\shell\cmd\command","",0x00020000,"cmd.exe /k cd ""%L""" HKCR,"Drive\shell\cmd","",0x00000000,"@%SystemRoot%\system32\shell32.dll,-22022" HKCR,"Drive\shell\cmd\command","",0x00020000,"cmd.exe /k cd ""%L""" 3) Is it correct that i find HKCU-key in the [T]-section of nlite.inf? I thought there only might be HKCR and HKLM-keys, cause at the moment nlite processes this section there isen*t a user-profile yet. 4) Many or most registry-keys of the nlite.inf can be found in the uncompressed HIVE*.inf files in the I386-folder on the XPCD. where can be found the rest? [edit] here is the LS.ini an the nlite.inf: LETZTE_SESSION.INI NLITE.INF i don't know why this problem suddenly occured . but it botheres me a lot Many thanks-