Winclone 5 Download Free PORTABLE
Antonette Hespe
So I opened a relatively recent .winclone image file using Show Package Contents but there is no winclone.dmg file inside. However, there is a 140GB file named boot.img.gz inside. Any chance that it can be imported into Fusion?
Hey all, anyone have any experience with Winclone4 images not installing right during imaging? I've tried a .winclone and a .pkg version, but they both boot to a black "No bootable device -- insert boot disk and press any key" screen.
I'm the author of Winclone. The newer versions of Winclone detect the version of Windows 8 and newer Mac hardware, and it is possible that Winclone is incorrectly assuming it is EFI versus MBR. If you are doing the package install, can you send me the /tmp/winclone_package.log when installing the package? Also, what hardware and version of windows are you restoring?
@chlaird - I'm certainly not as authoritative on the subject as the guy who wrote the software, but I found that I could not get my windows7 winclone image (deployable .pkg version) to restore correctly if the partition was pre-formatted to ntfs. If I pre-formatted the partition to fat32 instead, it worked.
Finally, if I install it as a .pkg "after" reboot, as part of the first-run script, and without creating a prior partition for it, it has worked. That just happened a few minutes ago, so I haven't yet had time to try it more than once to confirm. That may be how I was supposed to do it all along, but I've spent my of my time trying to get the .winclone working from those instructions
for your .pkg A suggest to check the the winclone section. how do you create the package from winclone?
There are 3 options 1. create bootcamp partition as percentage...
2. create bootcamp partition ...
3. restore to specific partition. eg 1,2,3, 4 etc
Have you use casper to pre-create the bootcamp partition then you execute winclone with same option 1 and 2 above?
I might be wrong on this suggestion due to there is no information on your environment of setting.
This might cause you the error. if you already create a bootcamp partition by casper then the package of winclone image trying to recreate a boot camp partiton again(option 1 and 2).
I have Casper Imaging partition the drive (two partitions - mac / fat32). I restore the the packaged version of the winclone image to the 4th partition. It failed for me if I did it while netbooted, so I have it installing the package post boot in the first run script. You can see what partition number your windows partition is with:
Experiencing the same issue here as Myo and Chris reported.
Tried various Casper Imaging 9.x versions to no avail.
It previously worked like a charm in Casper 8.64 using a .winclone file. Even my configuration then which worked in 2013 when we were running Casper 8.64 won't work now. Honestly the only thing that changes was upgrading to version 9.x