MrJinje

1) IDA 4.9 Freeware - on the 32bit .dll - Sorry freeware version cannot do x64 .dll's - Need pay version for that. 2) LOL, why you keep calling me John

Off the top of my head I don't see anything in your removed sections that would mess with Home Networking. But then again, Liquid24 is more knowledgeable about these things than I, have you asked in this thread. I assume it is those scripts you are using/modifying. EDIT: When it freezes during installation, can you try removing your network cable and see if that unfreezes it. I have had issues in the past where freezing network issue is resolved by unplugging the cable temporarily. That could rule out packages/features as the cause.

Dumb question : Wouldn't you rather have a fully automated installation using AutoUnattend.xml ? or do you need to manually select which type of network you want to use every time you install ?

What does Performance Monitor on your server say. Could just be an over-taxed machine. Take a look at these reg settings and see if local cache for roaming profiles is disabled or not. Roaming Profiles Local Cache

Ayup, that should do it.If they have logging off (i.e. No events in Security Log at all), might be a little harder to track down. Most home users would not know how to do that so probably non-issue. EDIT: Only mentioned because when searched my XP VM log files, they were empty. Changed passwords, still no log entry. Don't even remember disabling it. But the VM runs really fast. No Pagefile either.

Smaller directories yes, larger directories no. Config directory is relatively small (number of files-wise), but it would take nearly half an hour to take ownership of the entire Windows directory. (depending on you HDD speed) The number of files in the directory is your acid-test. See what I'm saying.

While M$ claims you are safer having it disabled, there are others who will claim you are no safer than if you had simply renamed your Administrator account. (via control userpasswords2) Both situations will prevent malicious software from hacking an account called "Administrator", now malicious programmers not only need to crack the password, but also need to guess the account name. All this is assuming said malicious software actually attacks via user/password, instead of buffer exploit like a normal piece of malware.If said malware can access you non-administrator user account (which in M$ infinite wisdom has local administrator privileges), your false sense of security is out the window (pun not intended), as hacking any account with Local Admin rights will allow malicious software full access. I rank this up there with "Editing the Registry can cause catastrophic failure", sure technically that is true, but has it ever stopped anyone ?

That is because you have not given yourself full permission yet (even though you now own the files) Halfway done. Icacls gives your account permissions to access an object (file or folder). So in short, yes you both have to take ownership and use icacls to grant your self permissions after taking ownership. We all gotta learn sometime This example, takes ownership of the sppcc.dll file, and the second command grants all local administrators Full (F) permissions. Third command shows how to use a batch variable / and how to set Read/Write (RX). Here are more examples + icacls syntax

Have a read over here. TrustedInstaller Ownerships/Permissions There is a couple other links at the end of the post that may be interesting too. (for batch scripting these things)

Easy, you either need to take ownership via elevated command prompt, or use the TakeOwnership.reg and right click to take ownership, which makes things easier.Take Ownership Reg Info After ownership is sorted, run your BAT and it should work. EDIT: If you still cannot take ownership of a particular file, try taking ownership of it's folder.

Disassembled spwizeng.dll and think that is where the the GUI language is originating from, it is not stored in a STRING table, but did find these in the export section. WizardUI::GetFontCharSet(void) 12F917C6 550 WizardUI::GetFontName(void) 12F917B0 551 WizardUI::GetFontSize(void) 12F917CF 552haven't used IDA since it was called SoftICE, not sure if this is on right track or just sending you on snipe hunt.

Just the XML file. All the other stuff is useful in creating the XML file, but it is unneeded by 99% of readers

Fully working Autounattend.xml link Post #11Reference files (unattend.chm) should be available inside the WAIK Copy all the Help Docs (about 10MB) from it and then you can uninstall if you want, WAIK is 1.7GB in size. Edit t/y Urie: Autounattend.xml is the name used when it is at the root of any available drive. Windows automagically looks for that filename on every drive and copy/renames that file into your C:\Windows\Panther\Unattend.xml.

I think that that GUI is inside SOURCES\spwizimg.dll but after some checking on my DVD, have not found the strings or dialogs needed to change you fonts. There was no spwizimg.dll.mui in the en-us folder, not sure where is the next place we should be checking. Already took poke around in these files, but not finding the right strings. D:\WINDOWS_7\sources\spwizeng.dll D:\WINDOWS_7\sources\spwizres.dll D:\WINDOWS_7\sources\unattend.dll D:\WINDOWS_7\sources\winsetup.dll D:\WINDOWS_7\sources\en-us\spwizres.dll.mui EDIT: N/M seen your other threads, you are looking at a Vista Build, not my thing. Threw away my Vista DVD 2 weeks ago.

So close yet so far, you are looking for NirCMD, it can directly set the volume or mute via command line. Mouse Wheel Not Required. Increase the system volume by 2000 units (out of 65535) nircmd.exe changesysvolume 2000 Decrease the system volume by 5000 units (out of 65535) nircmd.exe changesysvolume -5000 Set the volume to the highest value nircmd.exe setsysvolume 65535 Mute the system volume nircmd.exe mutesysvolume 1 Unmute the system volume nircmd.exe mutesysvolume 0 Switch the system volume between the mute and normal state. nircmd.exe mutesysvolume 2

Haven't used MDT yet, but I assume is just like everything else, you will need to edit your AutoUnattend.xml file to remove the automated disk wipe, and instead have it prompt for manual partitioning. The key part you are look for is the <ImageInstall> block. Here is mine, it prompts me to choose a partition to install to. (i.e. it will shows the GUI on error). The error being that I deleted the automated disk wipe from my XML. <ImageInstall> <OSImage> <InstallFrom> <MetaData wcm:action="add"> <Key>/IMAGE/NAME</Key> <Value>Windows 7 ULTIMATE</Value> </MetaData> </InstallFrom> <WillShowUI>OnError</WillShowUI> </OSImage> </ImageInstall> Post back everything you find in you <ImageInstall> block, and we will take a look at what needs changing.

Try this one, is basically my working AutoUnattend.xml. It's pretty lackluster, but the only prompt you should get is Which partition to format. It is set to install Ultimate, but you can change it if you like. Search your WAIK folder for Unattend.chm, I use the OPK, so I not sure the exact link, but that file has all the syntax for AutoUnattend.xml AutoUnattend_MSFN.xml

Thanks Rick, but I think the OP is looking for a way to do this with-out having to mount each image separately. With DISM Tool, he will need to manually mount each image. I was toying with scripting a batch file to do this, here it is. You will need place your x86 updates in the x86 folder, and x64 in x64 folder. and run this batch, Install WIM and this cmd file need be in the same folder as those x86 and x64 folder. Easy way to get your updates (and these two folders), is use my 10-13-2009 ULZ batch scripted file - Get it here. Not sure if your images are 1-5 x86 6-9 x64, or if you also have Enterprise edition (2 more images) so you may have to do some alterations on this batch. But for the most part this will mount each image and integrate the proper set of updates. Run "DISM.exe /Get-WimInfo /WimFile:%~dp0Install.wim" to find out what the correct order is and adjust accordingly AIO_Updates.cmd MD %~dp0MOUNT Dism.exe /Mount-Wim /WimFile:%~dp0install.wim /Index:1 /MountDir:%~dp0MOUNT Dism.exe /image:%~dp0MOUNT /Add-Package /PackagePath:"%~dp0x86" Dism.exe /Unmount-Wim /MountDir:%~dp0MOUNT /commit Dism.exe /Mount-Wim /WimFile:%~dp0install.wim /Index:2 /MountDir:%~dp0MOUNT Dism.exe /image:%~dp0MOUNT /Add-Package /PackagePath:"%~dp0x86" Dism.exe /Unmount-Wim /MountDir:%~dp0MOUNT /commit Dism.exe /Mount-Wim /WimFile:%~dp0install.wim /Index:3 /MountDir:%~dp0MOUNT Dism.exe /image:%~dp0MOUNT /Add-Package /PackagePath:"%~dp0x86" Dism.exe /Unmount-Wim /MountDir:%~dp0MOUNT /commit Dism.exe /Mount-Wim /WimFile:%~dp0install.wim /Index:4 /MountDir:%~dp0MOUNT Dism.exe /image:%~dp0MOUNT /Add-Package /PackagePath:"%~dp0x86" Dism.exe /Unmount-Wim /MountDir:%~dp0MOUNT /commit Dism.exe /Mount-Wim /WimFile:%~dp0install.wim /Index:5 /MountDir:%~dp0MOUNT Dism.exe /image:%~dp0MOUNT /Add-Package /PackagePath:"%~dp0x86" Dism.exe /Unmount-Wim /MountDir:%~dp0MOUNT /commit Dism.exe /Mount-Wim /WimFile:%~dp0install.wim /Index:6 /MountDir:%~dp0MOUNT Dism.exe /image:%~dp0MOUNT /Add-Package /PackagePath:"%~dp0x64" Dism.exe /Unmount-Wim /MountDir:%~dp0MOUNT /commit Dism.exe /Mount-Wim /WimFile:%~dp0install.wim /Index:7 /MountDir:%~dp0MOUNT Dism.exe /image:%~dp0MOUNT /Add-Package /PackagePath:"%~dp0x64" Dism.exe /Unmount-Wim /MountDir:%~dp0MOUNT /commit Dism.exe /Mount-Wim /WimFile:%~dp0install.wim /Index:8 /MountDir:%~dp0MOUNT Dism.exe /image:%~dp0MOUNT /Add-Package /PackagePath:"%~dp0x64" Dism.exe /Unmount-Wim /MountDir:%~dp0MOUNT /commit Dism.exe /Mount-Wim /WimFile:%~dp0install.wim /Index:9 /MountDir:%~dp0MOUNT Dism.exe /image:%~dp0MOUNT /Add-Package /PackagePath:"%~dp0x64" Dism.exe /Unmount-Wim /MountDir:%~dp0MOUNT /commit

As always, test ISO in VMware before wasting a DVD.Also might want to look into changing img0.jpg and edit imageres.dll inside Install.wim so that you theme/background was available on first boot. Think it was images # 5031-5043 in imageres.dll (images 5044-5056 were R2 logon screens)

I was thinking, why not use SetupComplete.cmd to enable the Administrator account and force Auto Login. I think it can be done, M$ only disabled the account, is very simple to re-enable. Maybe I would try something like this.SetupComplete.cmd Net user administrator /active:yes Regedit /s %~dp0AUTOLOGIN.REG NET USER MrJinje /DELETEAUTOLOGIN.REG Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon] "DefaultUserName"="Administrator" "DefaultPassword"="" "AutoAdminLogon"="1" "ForceAutoLogon"="1" Just add an AutoUnattend.xml and change the Net User Delete Script with whatever account name your use. In theory, this should avoid ever having to login with that account, thus preventing a folder from being created in the users directory.

with xp all you had to do was parse the 750 or so .inf files and it was easy to see what to remove and what files.With Vista and 7 you need to look at globalinstallorder.xml. I'm like cluberti where i really don't see any need reducing Se7en unless you trying to fit it on a CD but with a big usb drive who need's to do that anymore? I'd rather just disable things I don't want so later on I can bring them back if needed. I know someone ran 7 on a 1200 MHz with 224mb ram and all he done was just disable the services starting. Seven is a good OS like XP was. I prefer reducing somewhat - Tablet Stuff, Natural Language, all the big packages is gone from my image (mostly for smaller Acronis backups). Also I have one machine with a 4GB I-RAM DDR SSD, so I had to remove everything just to fit the drive. But my real question is with globalinstallorder.xml, can we just write a tool that edits that file and bypass having to "Remove Packages" via DISM, after your comments I assume that is all DISM is really doing anyway. It can't be that simple can it ?

Ayup, only need be run once. For future readers this can also can be done from GUI. Open Computer Management > Local Users and Groups > Users > Administrator > Properties and uncheck the "Account is Disabled" check box. Just a thought, but probably could run the NET USER snip from the SetupComplete.cmd and couple that with AutoLogin to avoid having to create a user account at all.

Dang, that is what I was trying to do. IF I setup "TOM" acount in /oobe, is it possible that TOM to have the same or very similar settings. This configuration is for laptops to be used by admins, but the admins name (ex. TOM) is used instead of administrator. I would like to do this with either unattend or a script(either I can run manually or runonce) Any help is highly apprecated. No such thing as super admin account in windows - Is a myth started by comparison of Administrator account to linux root user - aka - Super User - aka SU. All accounts within the local Administrators group are equally powerfull. If "TOM" account gets hacked by malware, you are just as screwed as if Administrator gets hacked. To enable the Administrator account in W7 is snap. Just run this line of code Net user administrator /active:yes Only real difference in W7 is that the account is set disabled, just like when Creating a new account in AD. Old Hat. Some people say things about UAC and super-admin blah blah blah, but I haven't ran into any issues using MrJinje Account with a disabled Administrator on my machine yet.

Sounds like same issue someone had earlier in the DISM Tool thread. Basically, he mounted the wrong Image (image 1 instead of image 4), so when he made his changes they only applied to the x64 Home Basic, but not the x64 Ultimate version like wanted. If that is the case the easy fix is to re-mount your image and apply updates to the correct version. 4 for x64, 5 for x86 You could probably do it with the DISM Tool if you want, IMO it makes the job alot easier.

since RTW I cannot install in AHCI, just IDE and switch it all over post install with a reg hack and update drivers to Intel in Device Manager Ayup, probably Boot.wim is missing the AHCI drivers, never tried that before, but sounds like could work. Report back if it does. Edit: OK, guess it don't work. FIX IT Ballmer