LinkBack URL
About LinkBacks
Reply With QuoteSolution:Originally Posted by AlienEclipse
FIX: CTRL ALT DEL with "MinLogon"
Regardig bootvis: doesn't that just layout boot files on the hard drive to minimize seek time? I've run it a few times, but saw no difference at all on the CF card. I wouldn't expect to since the CF card has such small seek times. You guys all disabled the auto chkdsk, too right? That was eating up at least a second on my system.
Solution:
FIX: CTRL ALT DEL with "MinLogon"
[H]4 Life
My next generation Front End is right on schedule.
It will be done sometime in the next generation.
I'm a lesbian too.
I am for hire!
I didn't get a WFP pop-up or anything. Presumably my nLite install killed WFP. I just tried to do the minLogon again on a stock SP2 install (i.e. no nLite) and did run into the WFP problem. It never warned me -- just silently replaced the new file with the standard winlogon.
Hmmm... I wonder if it matters that (on the stock SP2 systems) I've always done it logged in as Administrator??
*EDIT*: I double-checked, and I have WFP enabled, so I don't know what it could be.
hmm. I just ran into the problem with my last attempt. nLite. Checked the disable protection checkbox that worked for me before.
This time it didn't work. I wonder if its something else. I wonder if there's a component that nLite removes that results in the file protection not working.
Yeah, there's gotta be some other variable in here. WFP was turned off and I made sure it was the XPe 17Kb file and I followed the registry instructions very carefully. I wonder what else it could be? Maybe some services you all have disabled or enabled that I don't? Hardware? I really have no clue, just throwing out suggestions.
Thanks alot man!Good job FetLyd, that's a great tip! As far as those of you having problems with WFP and copying minlogon: I don't know what to tell you. Every machine I've tried (including a default SP2 install) I got a warning dialog from WFP which I was able to cancel. It looks like most other people got the same thing as well. The problem is that the file and registry entries go hand-in-hand, so if one is screwed up the whole logon process gets screwed up!I'll see if i have the time to put together a small program today, that'll copy the files over AFTER installation.. Should be able to get around that stupid BSOD then...
EDIT: BTW, I didn't delete any reg. entries before running the winlogon.reg file.. Still, it works fine..
Just copy it over in recovery console mode (boot from Win CD), and leave file protection on, its easy!
HoSS
What if you dont have a cd drive?
CarPC status: iPod, 3,456,217 songs so **** you
I get a write access denied error when I try to delete winlogon.exe. It says another program is using etc..
Is that what WFP does? Or is this something else?
Posting Permissions
Bookmarks