jrzycrim

I didn't see anything in your reg file to account for the problem. Try what Alanoll suggests. If you still have a problem after testing your lastets iso, setup your theme like you want it, apply it, then go to display properties > Theme tab and save your current theme. Use that theme file on your next test.

Mine looks pretty much the same and works. [Shell] CustomDefaultThemeFile = "%systemroot%\Resources\Themes\Jim.theme" I'll look over your tweaks and see if anything is amiss there, hopefully.

Not sure about your winnt.sif problems. Many people have problems with components being installed despite those settings. Not really sure why... cmdlines.txt isn't like a normal cmd file. It needs to look like this: [commands] "command 1" "command 2" I'd suggest you copy all of those commands you have to a .cmd file, say install.cmd, place it in the $OEM$ directory, and make your cmdlines.txt file look like this: [Commands] "install.cmd"

At first glance I can't find anything wrong either. Maybe somebody else will find a problem. Post your reg tweaks as well. If it's a really long file you might want to include it as an attatchment instead of posting insided code tags...

You might also be interested in this thread: http://www.msfn.org/board/index.php?showtopic=23512&st=0 I've switched to using a customized ntuser.dat file which is much easier when it comes to custom desktop/explorer settings. I used a different method than what is outlined in that thread however. Once I installed my unattended installation into vmware (or virtual pc), I set all of my icons, taskbar, explorer settings (basically any HKCU settings), and then logged out and back in as a different administrative *user. I then copied the ntuser.dat file in Documents and settings\user name to $OEM$\$Docs\Default User\ for my CD. * you have to be logged in as another user because windows won't allow you to copy ntuser.dat for the currently logged in user since it is in use. Windows will use the Default User\NTUSER.DAT for all new accounts so your settings will be in place at first logon.

Maybe you have a registry tweak which is causing your problem or something is wrong with your theme file. Make sure the path to your msstyle file is correct in the theme file itself. [VisualStyles] Path=path to .msstyles\.msstyles Also check that the path to your theme file in the winnt.sif is correct. I know you said you can apply the msstyles file to get your visual style working but try loading the theme file and see what happens. If you still have problems, post your theme file and the locations of all relevant files.

VMware uses its own video drivers. Unfortunately they aren't loaded until you install vmware tools after a Guess OS is installed. Not much good for testing our ISOs. A workaround is to put the Vmware video drivers in your OEM driver path. This thread has a link for the drivers; There are only 4 files which amount to only 46KB. You can drop them in an already existing driver folder or make a new folder and add that to your driver path in winnt.sif. http://www.msfn.org/board/index.php?showtopic=23429&st=20

An unattended installation negates the posibility of a repair install. Howerver, there is a work around. http://www.msfn.org/board/index.php?showtopic=20803&st=10 I'd suggest posting a question about this in the Multi-Boot CD/DVDs forum.

I should have been modifying the NTUSER.DAT a long time a go. It's made things a lot simpler for me.

Cool, Thanks!

Great! thanks for the feedback. Great info on customizing the Defualt User Profile. I've never really messed around with ntuser.dat and I never knew about [HKEY_USERS\Custom]. I think I'm going to try tooling around with that. I guess I've been doing some things the hard way. After modifying the NTUSER.DAT, do you place yours in $OEM$\$DOCS\Default User ?

Thanks for the warning. I haven't downloaded it yet however. I won't have SP2 for a while longer yet.

Refer to this for info about the "default user". http://www.mvps.org/sramesh2k/customprofile.htm

Thanks. Saving for future use.

You might want to try setting it and then rebooting. Then export that Key. Settings like that usually get written to the registry when windows is logging off. I'd try importing it to [HKEY_CURRENT_USER] from cmdlines.txt, before first logon. That may or may not work. I had a similar problem with Icon arrangements. I couldn't get that tweak to work at all. It didn't work importing from RunOnceEx. It didn't work importing from cmdlines.txt either. I think setup may overwrite some of the desktop settings during the Saving Settings phase which happens at T9 - T2. Can't be sure though. I had to set up a RunOnce entry (not RunOnceEx) in HKLM which would import my settings during the second logon. Just would not work during first logon.

Importing my Icon arrangement settings from [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnce] on the second logon worked in case anyone is interested. I placed a self-deleting batch file in my startup folder which set a value in RunOnce at first logon. The runonce entry imported my icon.reg at second logon. It just wouldn't work during first logon. *shrug*

I did some testing with Nero's Image Drive. I blocked the installation of unsigned drivers. Tried to install Image Drive and of course windows blocked the installation. I then imported this into the registry: Windows Registry Editor Version 5.00 [HKEY_CURRENT_USER\SOFTWARE\Microsoft\Driver Signing] "Policy"=dword:00000000 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Driver Signing] "Policy"=hex:00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup] "PrivateHash"=hex:b5,d8,e5,40,81,96,7f,61,8e,11,34,97,82,bb,7d,01 This time, when I installed Nero Image Drive, It installed without warning. It wouldn't work unless I imorted all three keys. The true test will be when you try it on your unattended install. Again, you should set your Driver Signing to ignore and export that third key from your own registry. I'm not sure what else that PrivateHash value may control. Good Luck.

Importing this into your registry before installing the device might work. I haven't tested it though... [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Driver Signing] "Policy"=hex:00 I was testing this on my system. That first tweak I gave you probably won't work. It didn't for me. This one did: [HKEY_CURRENT_USER\SOFTWARE\Microsoft\Driver Signing] "Policy"=dword:00000000 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup] "PrivateHash"=hex:b5,d8,e5,40,81,96,7f,61,8e,11,34,97,82,bb,7d,01 That second entry(PrivateHash) you might want to import from your own registry. Right click on my Computer, Select Properties, Go to the Hardware Tab, click Driver Signing, Check Ignore and Make this action the system default, Click ok, Click Ok. Reboot. Launch Regedit and export this key: [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup]. You only need the "PrivateHash" Value so delete the others. If importing this right before you install the Virtual drive doesn't work, you might try importing it from cmdlines.txt. Still might not work. You neve know about these tweaks.

Perhaps you can terminate that with taskkill or pskill. I haven't really thought about this so it might be a bad idea...

%userprofile% would be the currently logged on user. I do mine from RunOnceEx while logged on as Administrator. Before logon, say from cmdlines.txt, the default user would apply. I'd recommend doing it from GUIRunOnce or RunOnceEx since doing it before the guisetup finishes wouldn't work so well. I've never used Winrar so I'm not sure.

The last thing I did before finishing my CD was organize all my shortcuts. Desktop, quick launch, Start menu. I then made an SFX archive which contains all of my shortcuts for each of these areas. I just deleted everything and extracted my archive which contains all of my shortcuts. @echo off del /Q /F "%userprofile%\Desktop\*.*" del /Q /F "%allusersprofile%\Desktop\*.*" del /Q /F "%userprofile%\Application Data\Microsoft\Internet Explorer\Quick Launch\*.*" RD /Q /S "%userprofile%\Start Menu\" RD /Q /S "%allusersprofile%\Start Menu\" For my archive, I created the folders 'Administrator' and 'All Users'. Then In Each of those I placed a copy of the Start Menu folder and Desktop Folder. And then added the appropriate folder for Quick Launch. 7zipped everything and placed it in $OEM$\$Docs. The above cmd file I named Cleanup1.cmd. I call it from RunOnceEx, then extract my 7zip archive, then a second cleanup cmd file: REG ADD %KEY%\240 /VE /D "Organizing Desktop, Start Menu and Cleaning Up..." /f REG ADD %KEY%\240 /V 1 /D "%systemdrive%\Install\CleanUp1.cmd" /f REG ADD %KEY%\240 /V 2 /D "\"%systemdrive%\Documents and Settings\Shortcuts.exe\" -y" /f REG ADD %KEY%\240 /V 3 /D "%systemdrive%\install\CleanUp2.cmd" /f Obviously this can be done any number of ways and of course, you can easily add things for 'Default User', 'All Users' or any other User you need. Cleanup2.cmd is just your standard cleanup batch. Nothing special happening there... Originally I tried placing an archive inside $OEM$\$Docs\User name but when setup sees that there is already a particular user folder present it will create a new folder called user name-computer name and everything ends up in the wrong place. That's why I placed it in $Docs and extracted everything after setup creates these folders. You could probably place the archive anywhere and just extract to the appropriate path. I just opted to do it this way. I like this method because you do not have to deal with individual shortcuts and it makes organizing a lot easier.

//

No sweat. I was just curious if those drivers worked for you.

Did you ever get your video problem solved?

No problem