InTheWayBoy

If you would just open the inf's for a second, you'll see that hivedef.inf deals mostly with HKCU, which is not what you need. Now if you open hivesft.inf, you'll see most of the list is for HKLM, which is what you need. Now take that a step further, and see how it's broken down: HKLM,"SOFTWARE\Microsoft\DataAccess","FullInstallVer","2.81.1117.0" So looking at the code (And yeah, I grabbed the wrong one): ;Disable Windows File Protection (WFP) (to enable, change to 0) [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon] "SFCDisable"=dword:FFFFFF9D You'll should see how it all works out...I can't verify this but it should be something like this: HKLM,"SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon","SFCDisable","dword:FFFFFF9D" That last part I'm a little unsure off...maybe try it with "dword:FFFFFF9D", and if that doesn't work then try "FFFFFF9D" Looks like most of the *.inf's have different sections: AddReg, DelReg, etc I would think you would need to input this into the AddReg section.

Well I haven't seen a program that does it, but you can do it all manually if you are willing to invest the time. In truth, I wouldn't trust a program to perform that duty, as every program (And every version of said program) seems to be a slightly different. Best tactic is to research your applications and then do a bunch of testing. Good Luck!

Hmmm...thats quite a problem then. Can't say I really have any suggestions...other than to disable the Intel startup, but that's just cause it's useless in my opinion. But I don't see that being the problem here. So when it's off, you power it on and log in with ANY user and it freezes? And then when you logoff and the logon with that same user it works? Or is it just one user who is getting the issue when they first logon?

Well this is the code for it according to the guide: ;Re-enable WFP [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon] "SFCDisable"=dword:00000000 So it's in HKLM...I haven't ever edited the *.inf's before install, but I think they are different, one for HKLM and the other for HKCU. But I might be wrong...and this should probably be in the Unattended Section.

Well no problem thus far...but of course that's after removing the player manually. I'll try it later on this weekend in it's original form...just paranoid, that's all

You could download this: http://www.msfn.org/board/index.php?showtopic=47647 It's an "older" version of the RegTweaks that people have amassed here at MSFN. If you open in with notepad or something similar you should be able to search for the text and you'll see the corresponding location. It usually looks like this: ; Disable Indexing Service [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\cisvc] "Start"=dword:00000004 Alternatively, you could try loading RegEdit and searching for the key that way...might take a while, but should work just as well. Good Luck!

Hey, I recently requested for a RIS forum, and they gave us one! Woohoo! Of course, that doesn't answer your question, but it might be a nice place to check out and maybe repost this there: http://www.msfn.org/board/index.php?showforum=127

Okay...so then focus on the second half of the post...what kinda applications are installed, and what's starting up.

Nope...all it is a command line environment...if you know what commands to issue to repair a system then I guess you could script a repair, but I don't believe it's that useful. It's all simple commands...copy, dir, del, etc. If you boot to it and type "help" it should list all the commands you can use. As I understand it, you would really only use it to maybe backup files or delete a specific file that you already know of. Again...command line...so you don't get much.

Are all your posts recently related to one PC? Cause if it is, then I would take a step back and think it through. If you installed the copy of WinXP via a unattended, then you might be goofing something up in the process. I would try a vanilla install of WinXP, and then once you verify that it works you can try step by step to customize your unattended. Now if these are all different PC's then that's a different story. I'm just asking cause I see a lot of post by you lately... In regards to the explorer.exe hanging, that could be many things truthfully. If it was just WinXP installed, I would look at drivers...if you have other programs installed then they might be getting in the way...boy Also, what do you have starting up...sounds like it's freezing as Windows loads, so maybe a startup program is causing the problems.

Recovery Console is nothing more than a command line environment...it allows basic commands. I can't say I've ever really used it...in a situation where a computer won't boot anymore I either do an "In-Place Upgrade" or use BartPE. An "In-Place Upgrade" is a fancy term for a repair install, and it sounds like you already know of it. That usually fixes any issues with lost system files and what not. BartPE is basically a bootable copy of WinXP, with a full GUI and support for third party tools. I use that when I have a system that has issues with viruses or spyware. Another tool similar to this is ERD Commander, which is better in many cases but isn't free like BartPE. ERD can access the systems Registry much better than BartPE, and can automatically fix many problems.

Very nice...saw the new sub-forum, and I've very happy! Thanx again!

WinPE or BartPE would do that...can't say I know of any DOS level NTFS driver that I would really stand behind. I've used the older NTFSPro and it was just too buggy for me. WinPE or BartPE is built off WinXP, so the NTFS driver is very stable, and usable.

That's what I was gonna suggest...

Well I guess it could be a rouge DHCP server, but the error seems to be very specific on what computer is causing the errors: DC. And you say it's your domain controller which is causing the error, so I would really check again to make sure you're not missing something. Maybe the DC is thinking there should be a DHCP server elsewhere...I'm really out of ideas at this point.

I probably wouldn't try to manually uninstall virus protection. You could try to script something that would initiate the uninstall process...maybe AutoIT or something that you can program to 'click' the appropriate buttons. The problem with manually removing it is that it's almost a guarantee you're gonna miss something, leaving it half-installed. And by then you have no chance of uninstalling it unless you reinstall it first...and even then, that may not work.

Well isn't that what got us all in trouble last time? I mean I don't doubt you fixed it, but I don't like to get burned twice if you know what I mean...I'll test out the easy way and see what happens. Thanx!

Well if you don't use DHCP, then why not just uninstall it? By the looks of the error message, it seems that you have your DHCP server setup on one IP range, but it's configured to hand out a different range of IP's. I don't think you can do that...least, that is what it looks like according to that error message.

Same here...I guess that's what got me in his cross-hairs, as I made mention that he didn't seem to know what he was talking about. Oh well, one less head case to deal with

I guess it would be something like this: [Data] MSDOSInitiated="0" UnattendedInstall="Yes" [Unattended] DriverSigningPolicy="Ignore" NonDriverSigningPolicy="Ignore" I think that would be it, if that's all you want to do. Normally mine is like this: [Data] MSDOSInitiated="0" UnattendedInstall="Yes" AutoPartition="0" AutomaticUpdates="Yes" [Unattended] DUDisable="Yes" UnattendMode="FullUnattended" UnattendSwitch="Yes" OemPreinstall="Yes" FileSystem="*" Repartition="No" TargetPath="\WINDOWS" OemSkipEula="Yes" WaitForReboot="No" DriverSigningPolicy="Ignore" NonDriverSigningPolicy="Ignore" [UserData] ProductKey="" FullName="NAME" OrgName="COMPANY" ComputerName="TEMP" [GuiUnattended] OemSkipWelcome="1" OemSkipRegional="1" TimeZone="035" AdminPassword="*" [Display] AutoConfirm="1" BitsPerPel="32" XResolution="800" YResolution="600" VRefresh="75" [Networking] InstallDefaultComponents="Yes" [Components] msmsgs="Off" msnexplr="Off" indexsrv_system="Off" fax="Off" OEAccess="Off" [WindowsFirewall] Profiles="WindowsFirewall.TurnOffFirewall" [WindowsFirewall.TurnOffFirewall] Mode="0"

Yay! Someone else saw through his crap...thanx for the vote of confidence Zxian.

I've ran across this same issue before...except mine wanted to bug me about a Battery driver! I always had to break-down and either deal with it or include the above mentioned config in my winnt.sif. http://www.msfn.org/board/index.php?showtopic=44868&hl= Never got an answer in the end.

Well I found the answer...it's not in the WPA.HTA, but in the WPA.HTM located in the themes folder. Now if you can suggest to me a better way of doing it I'm all ears, but it looks like if I remove any references to the audio player in the WPA.HTM then it doesn't load up or get in the way anymore! Woohoo!

I see the advantage of the audio player, but in light of past problems I am thinking I just want to eliminate it. I see there are various files that look to be associated with them, and was wondering how I could remove it. Will it be as simple as editing the WPI.HTA? I tried that, and removed the following: <script language="JavaScript1.2" src="./wpiscripts/audio.js" type="text/javascript" APPLICATION="yes"> </SCRIPT> <script language="JavaScript1.2" src="./wpiscripts/audiowizard.js" type="text/javascript" APPLICATION="yes"> </SCRIPT> But it still loaded and looked to be playing music...I don't have the ability to use sound during the day...people stare Anywho, any advice would be very much appreciated! Thanx in advance!

If you're asking for my batch, then you're s.o.l. I never really bothered to integrate it into an unattended, since I only have one burner on the network I just do it manually whenever I reload. Sorry!