Feature REQUESTS

[n8chavez]

Here's an odd issue. It's not a bug, but something quirky. There seems to be a difference in PE/RE builds. When you use the option to add HBS to the boot menu it creates a c:\boot option, just like pretty much every other imaging apps. However, when you initiate a restore within Windows it creates an .iso and uses that as a temporary PE. My question is, why? Why not use the same PE instance that the boot entry uses? It seems needlessly redundant to use two variation of the same PE.

[admin]

Here's an odd issue.  It's not a bug, but something quirky.  There seems to be a difference in PE/RE builds.  When you use the option to add HBS to the boot menu it creates a c:\boot option, just like pretty much every other imaging apps.  However, when you initiate a restore within Windows it creates an .iso and uses that as a temporary PE.  My question is, why?  Why not use the same PE instance that the boot entry uses?  It seems needlessly redundant to use two variation of the same PE.

Why do you think HBS does not use the same WinPE instance? In fact they use the same WinPE instance.

[n8chavez]

Because they don't. Every time I try to restore an image within Windows, thus forcing it to reboot, HBS creates an .iso and uses that. If I delete that file I get prompted that I need to create the iso. The timestamp on that .iso is the same as when I try to restore from within Windows.

[admin]

Because they don't.  Every time I try to restore an image within Windows, thus forcing it to reboot, HBS creates an .iso and uses that.  If I delete that file I get prompted that I need to create the iso.  The timestamp on that .iso is the same as when I try to restore from within Windows.

I'm sorry that in order to ensure that the restore can be completed successfully, HBS always re-extracts the WIM file from the ISO file. Why do you have to delete ISO file?