@AnarethoS question (could not find the answer anywhere in this thread) Why is the System partition 300mb? Can't we just do it with the default 100mb 'System Reservered' partition? Why the extra 200mb?
Hi! Newbie here! I just want to know if I can use this application on a working windows 7? I mean, i saw the instructions that we have to do a clean install, but what if i already have a good working windows 7? I bought my dell 1564 laptop without a pre-installed OS. I manage to get a Dell OEM windows7 ultimate 64bit DVD. I was able to get also the Dell's Datasafe appllication but it was looking for a recovery drive (partition) which I don't have and i found Anarethos application on google. Another thing is, I only have two partitions, there is a system reserved though. I know I can still create one, but will that work? Thanks! Have a nice day!
The ones i have seen use the regular 100mb 'System Reserved' partition, MSI, ACER & Packard Bell Anyway, i just altered the autounattended.xml to create the default 100mb 'System Reserved' partition instead the 300mb 'System' partition, i also made this change in settings.ini...all worked well and saved me another 200mb That raises another question, the recovery partition now is 12GB, my IMAGE.SWM is somewhere arround the 3GB... how much could i skrink the recovery partition (does it need extra space for temporary files? wim operations?)
A fully updated Windows 7 with minimum of software takes not more then 4 GB so if you want you can decrease the size of it It was just a value anarethos used, but you can also increase it if you have alot of apps installed. Just remember to change it in settings.ini Edit: Im pretty sure of this but maybe you should leave some extra space for tempfiles hehe
No, temp file are on the WINDOWS partition. I put 12 gb because that is the size of all installation I do
@tcntad/Anarethos When using the autounattended.xml file created by tcntad to automatically create the partitions (i used 3 partitions with audit mode) a existing unattended.xml file in '\Windows\Panther' directory gets renamed as unattended.old (i used a DVD disc which already had a $OEM$ directory containing a unattended.xml in the DVD's sources directory) Currently, just before syspreping the image, i rename the unattended files, so after sysprep the OEM specific unattended is used (placing OEM logo's, wallpapers, certificate and such) What would be best practice, combine autounattended.xml with the OEM specific unattended.xml or load them separately? Or would you apply OEM customizations in audit mode? @Anarethos Any progress on adding a progress indicator?
Actually Im using searchengines brand to apply oemlogos etc but yes you can do that in audit mode if you want or use the unattend to do that, but then you would have to change oemlogos before installing a new computer. Im not sure what Anarethos is up to but his tool is working perfectly now I also whonder how that part is going.
@tcntad, i removed our last few posts as these were really confusing and not exactly true on my part, hope you don't mind
Not at all, it wasnt really contributing to the thread anyway Hm didnt know it creates a new autounattend file but allright, more problems?