Thread: Using minLogon to speed up booting and decrease footprint

Haha. That was dumb on my part. So nothing changed for me after all. You simply can't delete winlogon.exe. You have to rename it. Then replace it.
That's kind of odd, but that's it!

Thanks SFiorito

Okay, I found a machine with SP2 that was exhibiting the same behaviour some of you guys are experiencing. As long as you follow my original instructions you should still be fine though. I renamed winlogon.exe to winlogon.exe.bak. Waited a few seconds and WFP recreates winlogon.exe in the directory. I deleted the new winlogon.exe and put minlogon.exe (renamed to winlogon.exe) in its place. Then I did the registry entries. BEFORE YOU REBOOT ENSURE THAT MINLOGON IS STILL THERE. MinLogon is 17KB in size versus WinLogon's 520KB.

BTW, I also tried replacing the files without changing the reg entries and my system couldn't boot, so whoever that was that said the reg changes weren't necessary either WFP replaced minlogon with the original winlogon or you have some kind of anomaly that lets it somehow work on your system. Please let us know.

If i throw together a quick program now (i mentioned it in my previous post), can someone test it quick?

That, we don't know yet..

sure I've got vmware running anyway testing out an nlite config

Good.. I'll try to finish it soon.. Just got a few other things I have to work on.. Plus the time is 22:40PM here, and I've been working 14 hours..

So, sorry for all the typo's and slow work..

It would be nice if someone could test this out in wmware (or something like that), and give me some feedback.. The program renames winlogon.exe to winlogon.bak, then renames minlogon.exe to winlogon.exe .. Then it deletes the winlogon values, and inserts winlogon.reg into the registry.. After it's completed, it will restart the machine.. Atleast, this is how it's supposed to work, but my coding skills are a bit rusty..

Anyways, here's the instructions:

Before making an nlite image, create a new folder called $OEM in your project folder (same folder as i386). In $OEM$, you'll have to create another folder called $$, and then another one called system32. Copy " fetlyd.exe ", " minlogon.exe " and " minlogon.reg " into this folder. Then, create a new text file in $OEM , and name it cmdlines.txt. It shall contain the following lines:

Code:

[COMMANDS]
"REGEDIT /S fetlyd.reg"

Then, you'll have to create the file fetlyd.reg ..
It should only contain the following lines:

Code:

Windows Registry Editor Version 5.00

[Software\Microsoft\Windows\CurrentVersion\RunOnce]
"Fetlyd"=fetlyd.exe

cmdlines.txt Fetlyd.exe and fetlyd.reg are inside the zip-file attached.. Only thing you need to do, is copy "minlogon.reg" and minlogon.exe inside the system32 folder as described earlier in this post..

* Fingers crossed! *

Btw, don't blame me if it doesn't work, or if it *****s up your os..

3 views of the zip file, but no response..?