koawmfot

put shellstyle.dll into the system32 directory of your PE build. hope that helps...

does anyone have any idea? i need to integrate this setting into a build process and want to put it in right off so the patches don't need to be cleaned up later on. thanks!

you shouldn't have to. to build my dell oem cd's, i usually start with an SP0 retail or vlk cd to create the slipstream directory. then copy oembios*, pidgen, dpcdll, setupp.ini, eula.txt, and winnt.sif from any dell oem cd into the sp0 slipstream directory. then slipstream sp3 and build your iso. this way you don't get any of the extra dell oem bs.

i was wondering if there is any registry key or policy setting that can be configured that will set the defualt functionality of update.exe to 'nobackup'? i want no patches to backup, but cannot batch install them. the installation is controlled through a 3rd party patch management system i do not have control over and was wondering if i can configure the clients to never backup patches.

i will definetely try out ImDisk. but both of you guys are telling me you have experience using the SP2 ramdisk... how do i configure it??

The why is that in WinFLP there is an XP ramdisk driver installed by default. We are setting up WinFLP for a VDI environment want to put the cache and temp into ram so that nothing is really captured on the systems. If all it takes is a couple of registry entries, i can have them imported before the system even makes it's first boot without having to install anything extra. I guess i would like to take adavantage of what is already provided. Since you know the sp2/2k3 ramdisk size is 512 max, maybe you know how to configure it as well so that i can set the size and drive letter? Like I said, the parameters in the KB257405 do not have any effect, and i have not been able to find any information anywhere.

That link is the same stuff that the KB article references. i am asking about the XP version of those files included in SP2, but there is no documentation on how to use them, or if it is even possible to. The 32MB limit is one of the things i am hoping is not present in the XPSP2 version of the SYS file.

in sp2 there is an inf and corresponding sys file for a ramdisk, ramdisk.inf and ramdisk.sys. this does not appear to be the same as the ramdisk from here: http://support.microsoft.com/kb/257405, as the version is different and the inf configures a different sub-set of keys/values under the service. i can get the driver installed (on WinFLP it is installed by default). i just cannot get an actual drive to use it, and i have tried the settings in the above KB article. the xp driver can be installed using devcon.exe. devcon install ramdisk.inf Ramdisk does anyone have any experience using this built-in xp ramdisk? i have already read a million pages about 3rd party ramdisks and such, but since this is included in a WinFLP install, i would like to make use of it for cache redirection and such for a VDI template. i also checked and vista has the same (similar) inf and sys files, and checking the registry properties of a running Vista PE environment, i can not see anything that tells the system to assign X: to the ramdisk. so, how do i assign a drive letter and set the disk size?

i know that in winnt.sif you can redirect programfilesdir and commonfilesdir. i was wondering if you can do the same with windows fundamentals. they give you the option to specify where the page file will go, but there is not much info on other available about what elements are available. does anyone know how i can find the undocumented elements? this is the only reference i could find, based on embedded (since winflp technically is embedded...): http://msdn2.microsoft.com/en-us/library/ms912186.aspx

i am creating a new image for corporate deployment (XP Pro). i run sysprep (-nosidgen -factory) using the buildmassstorage=yes section along with my non-standard storage controllers and have the system reboot into factory mode. if i backup this image i can bring it down onto any different client system and it works fine. the problem is that when i now run sysprep -pnp -reseal -mini on this build to be able to truly deploy out to clients, mini-setup will run fine, but then when the system reboots after completing mini-setup, i get the 0x0000007b error. i know this is a mass storage problem, but cannot figure out how the system boots and can run through mini-setup ok, then crap out afterwards. usually if i have a mass storage problem, the system cannot even boot into mini-setup. has anyone seen this? any suggestions on things i can try? this is my entire sysprep.inf for the factory sysprep: this is my sysprep.inf for the reseal: