Used the basic v1.3 beta and it worked great on my wife's lappy.....just wished the new version had the dvd creation as well as usb. Any thought of adding it back in final release? Other then that, I luv it! I like it better then Arconis. Thanks again!
Hi bro, need u to check on something, I using dell dvd windows 7, the thing is when I using xml in USB, it will not copy the SLIC, thus windows is not activated, my bios contain SLIC 2.1. If I use manual install without USB xml, it will install the SLIC and my windows is activated. And another thing, is it this partition recovery not working on all laptop/PC? I tried another pc/laptop, the partition is corrupted and some success... I don know what the reason... Please advise...
I MAY be adding this option in a future release, but not before I am sure at 100% taht both the Windows 7/8 verions works correctly, as I don't want to split my time on too much different "module".
For the SLIC/Cert/OEM_SLP_Key, Dell has probably hard-codded the settings/files in their XML file during the creation of the image. Your best solution here would be to activate with Slic/Cert/Key before capturing. If I remember correctly, the activation status will then be kept. Otherwise, you may try to use a SetupComplete.Cmd script to this for you on the first boot after OOBE. As for the corrupted partition, what do you mean? Unreadable one? Missing parttions? Setup failed after the capture? Which version of the tools are you using on thieses laptop? My latest one or 1.2 ou Legacy? Thanks.
No bro, I means when I fresh install windows 7 using the xml u provided, It will not install SLIC from my Dell DVD. The corrupted thing is like, the second step install.cmd, sometimes it can mount (SUCCESS), sometimes it cannot mount and restart windows, the windows cannot be access anymore, it boot "CAPTURE" there and keep repeating booting.... I'm using Basic 1.3....
Ok, so you are using a Dell Windows 7 media rather than a Microsoft original iso? These kind of media as their own script to do stuff (install certificates, drivers, etc.). This script is overrided by the XML provied to create the partion, as such, the certificate won't be installed. You will have to do this by hand or not use my XML. If you don't use my XML, you will have to create the partitions manually before installing into Windows. You will also have to switch to AUDIT mode on the first boot, while in OOBE by pressing CRTL-SHIFT-F3 keys.
For the computer that gives you problem, is the problem random or it always happen? Before running my script, - Can you check the partition layout of the computer? Should have only 3 partitions - Also, be sure the letter W and R and S are NOT IN USE - Also, check that a file named WINRE.WIM exist in C:\Windows\System32\Recovery. The file may be hidden
OK bro, can U give me guideline create partition manually? I know its a lot, but I have knowledge in command prompt Its happen randomly. Yeah it got 3 partition, and sometimes I got R letter in partition, but I don know whether its in use or not. After all, I think manually create partition is the best way am I right? Hope u can give me the whole guide, thanks a lot. And one thing, pressing F8 before boot windows, there is no REPAIR MY COMPUTER option, the only way to enable is using this command in windows "reagentc /enable /auditmode", but in some case, it failed, even I'm on Administrator account. Do u got any idea 100% enabled REPAIR MY COMPUTER to shown up?
To create manually the partition, simply press SHIFT+F10 when you are in the menu to install Windows, then launch DISKPART and then do the following commands : Code: SELECT DISK 0 CLEAN CREATE PARTITION PRIMARY SIZE=12000 FORMAT FS=NTFS QUICK LABEL=RECOVERY CREATE PARTITION PRIMARY SIZE=150 ACTIVE FORMAT FS=NTFS QUICK LABEL=SYSTEM CREATE PARTITION PRIMARY FORMAT FS=NTFS QUICK LABEL=WINDOWS The proceed to install Windows. One the first boot (in OOBE - Where you create your user account), press CTRL+SHIFT+F3 to switch to AUDIT mode. Then proceed to install your drivers and applications. Also, the "Repair my computer" will be only available AFTER the image creation, once the OOBE is finished. Forcing the activation of the Recovery Environment while in AUDIT mode will "move" the WINRE.WIM file required and will crash the whole process!
Version 1.3.1 is out. Now check to be sure the recovery partition is mounted and that the WINRE.WIM file is available. If there is an error, the process will abort with an error message.
Thanks for the manual command... Bro are you sure after creation image, the repair option will be available? Because I have tried about 4 success, and none of the 4 computer shown repair computer option.
Pressing F7 should boot into the Recovery Environment or pressing F8 and then selecting Repair your computer. Then, from there, once you have authentified, you can select the "Reinstall Windows" option. When my tool install, do you see the capture process? Also, can you give me the list of all the files in your recovery partition? To do so, open a command prompt in admin mode. Mount the recovery partition, say letter R and to this : DIR R:\ /s /a | clip And paste the content here. The "|clip" option is to ouput the result directly in the clipboard. also, do you have the following file on your installation : C:\windows\system32\recovery\backup\winre.wim ?
I'm doing manually installation windows, installing driver and application now, will feedback to u later... I'm trying latest v1.3.1
Also, be sure to use MBR settings file with MBR XML or GPT settings with GPT XML. MBR = 3 partitions 1 - Recovery 2 - System 3 - Windows GPT - 4 partitions 1 - Recovery 2 - System 3 - MSR 4 - Windows If you use the MBR XML but with the GPT settings, is will fail to capture as the capture environment will try to mount the 4th partition, which does not exist. If you use GPT XML but with MBR settings, it will try to capture the 3th partition which can not be mounted then fail also. In either case you will have a working system, but without any recovery solution working!
Also, may I suggest you to capture your whole installation using Acronis or similar software prior running my software? If something fail, you can always restore the image without having to redo the whole process. I always do that when I work on a unknow computer in case of drivers conflict with sysprep.