Firestorm666

The copyprofile thing i figured it out... kinda dumb from Microsoft.. I use WDS to deploy windows image's 1) Create your image 2) Make your changes in the Administrator account (the real one) 3) Sysprep your image with the copyprofile option 4) Load your image up to the WDS server 5) Set in your unattended install the copyprofile option also So, i believe we all asumed that the default profile was completed during the sysprep and BEFORE the creation of the image.

Here is a method to make MSP files other then the enterprise editition 1) you NEED the enterprise edition 2) Copy the ...WW folders to the root of your office 2007 directory 3) use the setup /admin option 4) now you can select for wich version you want to make an MSP :-), enjoy example: C:\Office 2007\Enterprise.WW when you are done: C:\Office 2007\Enterprise.WW C:\Office 2007\yourofficeversion.WW

I'm trying to figure out how to solve the problems with nforce chipsets, i'm trying to be as clear as possible. my findings: the method RyderOCZ uses actually works, it works also with the 6.70 driver from nvidia. now i have the following problem: I used my unattended install with driverpack's to install, it works, but after a while i get BSOD's, wich i can solve by "reinstalling" the drivers from the nvidia site. (info: i use ALL driverpack's, so including the chipset-drivers, and my motherbord is an A8N32-SLI, so it has the nForce x16 chipset). i figured out that the nvidia drivers are NOT 100% unified. causing that the drivers WILL install, but are not 100% compatible with each other, so causing BSOD's. And as far as i understand, only the "normal" nforce chipset sit's in the driverpacks. So, the only way to fix that (i believe) is to sepparate those drivers, i do not know how windows can detect the right one, because it install's the normal nforce drivers but is not 100% stable when you have an nforce x16 chipset, so actually there must be some way to "force" install the correct one. below you see the differences: nForce3 (latest version is 5.11) IDE driver version 4.46 (WHQL) nForce4 AMD (latest version is 6.70) Legacy PATA RAID driver version 5.52 SATA RAID driver version 5.52 (WHQL) IDE driver version 5.52 (WHQL) nForce 430 (latest version is 8.22) SATA RAID driver version 6.22 (WHQL) IDE driver version 6.22 (WHQL) nForce 4 Intel (latest version is 8.22) IDE SATARAID driver version 6.22 (WHQL) IDE SATA_IDE driver version 6.22 (WHQL) nForce 4 Intel SLI (latest version is 7.15) Legacy PATA RAID driver version 5.52 IDE SATARAID driver version 5.52 (WHQL) IDE driver version 5.52 (WHQL) nForce 4 x16 AMD/Intel (latest version is 6.85) IDE SATARAID driver version 5.52 (WHQL) IDE SATA_IDE driver version 5.52 (WHQL) Now, i find this confusing, maybe Bâshrat understand this better than me (he has the most experience with drivers i believe ) Like i said, RyderOCZ's solution works, but only usefull for your own computer. and because the most people have an nforce 4 "normal" chipset, this solution usually works, and to answer ryderocz's question: the RAID folder is not needed (replacing files in 123 works) btw: sorry if my english is not clear enough, i'm speaking the dutch language. Edit: Apperently the BSOD's i get where from my printer driver (hp psc 1200 series) however, i find it still odd that nvidia had such confusing driver-versions