i use ver 2.0.9 after finishing configuring and select reboot when continu to stage setup is starting services show error Windows Could Not Finish Configuring The System . To Attempet to resume Configuring restart the computer after computer restarting i get same msg how i can resolve the problem
What did you configure? Reinstall with no antivirus or tweak any services (or be very carefeul with those)
Just wow. I am immensely impressed. Great program, will save hours of hassle from useless (L)users. Looks really clean, and I was very impressed that it integrates into the windows recovery option on the F8 boot menu. Also, It appears to work correctly with DAZ' Loader. Big thumbs up.
Hi! I added as the 12o. language, the portuguese brazilian, in the settings.ini as well the help_pt-br.txt In case you wanna add them in future releases...
Oh guys, just as a thought, could all the commands required to create the correct partitions and recovery stuff be simply added to a batch file, and then run from the installation media? IE a usb stick? I'm thinking to create a batchfile for example like this... diskpart select disk 0 clean create partition primary size=12000 firnat fs=ntfs quick label=Recovery set id=27 assign letter=R create partition primary size=300 active format fs=ntfs quick label=System assign letter=S create partition primary format fs=ntfs quick label=Windows assign letter=C exit exit Does anyone see why this wouldn't work? Obviously, you would have to be installing on the first disk, and the easiest way would be to be installing from a USB stick... but still, it should be possible? Whaddya think?
i sitll think an update button is a good idea you you could add this. But the main reason im on today is to ask if there is a way to have the autounattend.xml file could work on the recovery DVD created but the tools ie create the partioins needed to install from a universal recovey disk also if there is away please post the answer of how to do it thanks in advance
The only problem with the autounattend.xml, is that (correct me if i'm wrong) it will run every time I do an install. In some situations, I don't want to create a recovery partition.
Then I suggest you use a usbstick to install W7 and everytime you dont want to create a partition, rename it.
Same here I have an ISO if its not possible to install from USB with only W7 and then a full 8GB usbstick with apps etc I could download the latest release but coudnt open it, fixed?
Ok, I have recompiled my EXE files. I think the problem come from the UPX compression. File is a little bigger now. I have also added the polish and the portuguese language
Had to use the new F7 function, and im very impressed you got it workings, I had a look but whent straight over my head Great Job AnarethoS I bowe to the master
I don't know if its been mentioned before so I'd like to report a minor bug. If you boot to AUDIT mode and don't close the system prep tool, then when installing the recovery tool, an error pops up that says sysprep tool already running. After this happens, the system reboots and captures the image as normal, but after the image has been captured and the system reboots, it automatically boots back to audit mode, not to normal mode where you enter the user name and info. I couldn't see it mentioned anywhere that you MUST close the sys prep tool, only that Tcntad said to close it because the tool will take care of everything. In the guide it doesn't mention that it will bug out if you don't close it. So perhaps it's worth adding some sort of check to the installer to make sure the sysprep tool is already closed? This bug appeared on windows 7 32 bit home premium, using VMware Workstation 7.1.4 build-385536
Yeah not a bug, if you read documentation with the tool, it will say close sysprep. the tools will then sort out sysprep. before the reboot and recovery then when the image is taken it will boot into normal mode.
yeeees.... as I said... Looking through the rest of the instructions.doc, I see the line The tone of this bit doesn't suggest that anything bad will happen if it's not closed. Nowhere is it mentioned that if you don't close it, it will bug. So, either the instructions need to be made more clear, or something needs to be added to the program to make sure sysprep is closed before install begins. Either way, its a bug.