razormoon

Could it be my version of 7? I'm vivisecting 7068 currently and trying to keep as up to date with the 7s as possible. If you can MaxXP, what directories are your drivers in and what was the command line? I'd hate to think I foibled something... I notice you have a pnp directory..I'm just pointing DISM to an x:\drivers\nVidia folder. <shrug> I mount with DISM: DISM /MOUNT-WIM /WIMFILE:D:\UA7\SOURCES\INSTALL.WIM /INDEX:1 /MOUNTDIR:D:\TEMP Add drivers: DISM /IMAGE:D:\TEMP /ADD-DRIVER /DRIVER:D:\DRIVERS\NVIDIA Unmount: DISM /UNMOUNT-WIM /MOUNTDIR:D:\TEMP /COMMIT Quite simple, no? Be aware that this works for my IR drivers...

fizban, I was expecting your response from MaxXP. He's been going on about $OEM$ extinction since Vista beta which is why I posted on this thread. You're preaching to the choir... That being said, I am just diving into Win7 and would like to know more about datawim. Quick rundown? Is it part of DSIM? Because I just started poking at it yesterday. Verification code and what have you - I do not mind. I agree with you there on time taken. However, if you're running a slower processor it seems like a mindless waste and you find yourself wondering exactly what the **** thing is doing. You don't notice the expanse on say, a quad core. As long as it works, I'll wait.

ty Spoof. Playing with DISM now. Pretty powerful stuff. Too bad there are no docs on it that I can find...especially when it possesses an excruciatingly granular command line. Found this from muiz http://www.wincert.net/forum/index.php?showtopic=4939 Not having luck with the driver integration (hit and miss), it does mount/unmount at a good speed though. BTW, tested removing everything but the *.wims from sources on VM. Seems to WANT to work, but keeps looking for HDD drivers (?). Skipping that road for now. On the flip, I did extract Win7 Ultimate image and injected my own security templates/files (for built-in *renamed* Administrator account) and NTUSER.DATs in Users\Default. Works like a charm. SOURCES\$OEM$\$$\SETUP\SCRIPTS\SETUPCOMPLETE.CMD working SOURCES\$OEM$\$$\WEB is also working (desktop images) SOURCES\$OEM$\$Docs\Default\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Whateverfolder also working. Woohoo

Same here with NVidia drivers. I've tried both 181.71 (Win7) and 182.08 (Vista) with no luck. The Win7 drivers are terrible under Win7. Oddly enough, the Vista version works fantastic! I've also tried SoundMAX drivers with poor results. Seems at least the NVidia drivers get parsed at least... About the only thing that worked for me is an IR device driver (for my PVR program).

@Max Glad to see you're still working on VistaUA (7). It's one of my favorite pieces of software... Looking to add my 2 cents in this particular forum. I just found out it exists! Anyone tried implementing Themes yet? AND has anyone deleted all files from sources with *.WIM exception?

Seeing the exact same thing with build 7022. I was thinking that it was the Kaspersky preview for Windows 7. The same mess with connector for WHS. When logging on in the mornings (PC has been left on) it takes several minutes before a) connector software "connects" B) folder opens to view network files stored on WHS c) RDP to connect. It says to "check to make sure that name is spelled correctly". If I wait those several minutes then all goes back to normal...til the next morning.

I've been using patched uxtheme, shsvcs and themeui for unattend with SP1. I've recently slipstreamed (if that's what you call it) SP2 BETA and my patches won't work anymore. After scouting around for updated patches I happen to come across one here: UXTHEME SP2 Strangely, it changed everything except what really matters. Windows and styles. As far as I can tell, it changed my mouse pointers and wallpaper only. Anyone witness this yet or am I missing something? btw - I imbedded the dlls within WIM and even added in $OEM$ for added measure. I can't figure this one out...

This is just to show that it goes into oobeSystem: <settings pass="oobeSystem"> <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <OOBE> <HideEULAPage>true</HideEULAPage> <NetworkLocation>Home</NetworkLocation> <SkipUserOOBE>true</SkipUserOOBE> <SkipMachineOOBE>true</SkipMachineOOBE> <ProtectYourPC>3</ProtectYourPC> </OOBE> </component> </settings> I have my account as well as my wife' and child's account in here also, hence the SkipUserOOBE.

You guys are friggin' awesome!

Here's an answer you may not like... You will have to learn to build an unattend from scratch in order for you to know what is ok to remove and what isn't, otherwise you'd be headed to a disastrous place. The Vista unattend forum will be a good place to start.

Hi all! Just wondering if there is a list of these switches somewhere (i.e -extreme)...or is this the only one?I am so unenlightened these days.

<OOBE> <HideEULAPage>true</HideEULAPage> <NetworkLocation>Home</NetworkLocation> <SkipUserOOBE>true</SkipUserOOBE> <SkipMachineOOBE>true</SkipMachineOOBE> <ProtectYourPC>3</ProtectYourPC> </OOBE> UserAccounts> - <AdministratorPassword> <Value>admin1password</Value> </AdministratorPassword> - <LocalAccounts> - <LocalAccount wcm:action="add"> <Group>Administrators</Group> <Name>Admin2</Name> </LocalAccount> - <LocalAccount wcm:action="add"> <Group>Users</Group> <Name>User1</Name> </LocalAccount> - <LocalAccount wcm:action="add"> <Group>Users</Group> <Name>User2</Name> </LocalAccount> </LocalAccounts> </UserAccounts> - <AutoLogon> - <Password> <Value>admin1password</Value> <PlainText>true</PlainText> </Password> <Enabled>true</Enabled> <LogonCount>3</LogonCount> <Username>Administrator</Username> </AutoLogon> I haven't figured out (or tried to) how to rename the built-in Administrator account. If you want to enable it, you must use username Administrator. You should have a password for Administrator, don't know if that one is mandatory. As for the rest, they are optional.

Great Post! I can't get to the April x86 or the Ultimate Extras files though. Links down?

Yup, I agree. I do my own unattend.xml. Still no help. EDIT: I think I hear what you're saying...what would that have to do with security folder if all I do is remove languages, backup and \sources files?

Issue gone? Although I have never seen that screen before, it'd be nice if you shared what you did...? No?

What AV software are you using?

Nope. autounattend.xml is of no help. Am I missing something under SP1?

If you know something I don't please share. I know how to activate and logon and KEEP Administrator on logon screen. That is not what I meant. As you know, I was able to rename the Administrator account before first logon. Ramifications being that if you use programs such as Acronis TrueImage...Even with SP1 and logging on with Administrator and then RENAMING Administrator, this superb piece of backup software does not recognize MAVERICK the Administrator as defined before first logon and MAVERICK the Administrator...logging on as Administrator and rename Administrator to MAVERICK (Even though they have the same user name and same god modes). EDIT: WAIT...! ANSWER FILE? For crying out loud

Since using previous SP1 (the beta before RTM), I've notice some of my USB ports becoming inactive (losing battery/voltage and otherwise). My Zune and USB HDD works on only half of my USB ports. I am currently using SP1 RTM...haven't had a chance to test Zune yet.

Works fine here...! [Components] ;# Accessories # Paint Welcome Center Wordpad ;# Languages # Japanese Korean Simplified Chinese Table Driven Text Input Processor Traditional Chinese ;# Multimedia # Sample Pictures Screensavers Sound Recorder ;# System # Disk Defragmenter Manual Install (Setup.exe) Windows Backup Windows Defender Windows Easy Transfer

Ah, alas.. it was good while it lasted but the \Windows\Security folder has gone away and what to do with renaming Administrator account now???

Thanks for the files. I throw 'em in \SOURCES\$OEM$\$$\SYSTEM32 and it works fine. EDIT: Oops...reverse integrated!

BUMP FOR UPDATE

Yeah, I thought I did post in your page...hmm. I try running VistaUA and nothing happens. I've tried uninstalling and reinstalling with no results.

Anyone else having trouble running certain unattend tools under SP1 V.668? Namely, VistaUA and some dlls NOT being processed by Vize?