New install advice... just install. BOOTable UFDs are available but I don't know whether their version is BOOTable in both Legacy-MBR and UEFI. Whatever System they are created on I know works fine, never checked interoperability.
@Krusty - I just created Hasleo's Emergency Media on an UEFI System and it BOOTed fine on both UEFI and Legacy-MBR Systems. I looked at the media and it's one FAT32 partition marked as ACTIVE and contains UEFI BOOTing code in that partition. That's the way most people create BOOT media for both System types.
Awesome! Thank you, kind Sir. I am going to try Hasleo later after MR runs its scheduled backup, just in case anything should go south, as unlikely as that is. Oh, the irony! I went to the shop and bought a couple of spare UFDs anyway, so was prepared either way.
Yeah...no. I don't think so. I couldn't make it past the first sentence. You cannot demand anything with free software. Suggestions are one thing, but to say "The user has the right to take a screenshot from under WinPE!" is out of line. Where is that right written down? Who says? If you want to make a suggestion, fine. But it's best to not come off an entitled and rude because you'll never get what you want.
Of course you are right. But I think aldist meant something different. His wording is misleading. I assume he wanted to say: It's no violation of the license terms of WinPE to take a screenshot. In other words: It is allowed for the user (of WinPE) to take a screenshot / the user is entitled to do it. Therefore there would be no (legal) obstacle to implement such a feature e.g. in Hasleo's software. As the rest of aldist's posting is written in a polite way, it seems plausible that this is the intention of what he wanted to say with the first sentence. Otherwise it would indeed be not o.k.
I edited the post, but it doesn't change the essence of the issue. I'm sure it's not a deliberate action of the developers, I think it just happened (side effect) that it's a bug that the developers just don't know about. Otherwise it would look strange "we give you a free backup program, but forbid you to take a screenshot". Hasleo clearly and easily solves the issues of creating WinRE, WinPE ISOs, integrating custom drivers, and integrating into the Windows boot menu. Users should like it. WinRE is 200mB larger than WinPE, as you would expect.
Now the program is being tested in a wide public, bugs will be eliminated and features will be added, and further - the developers previously wrote on the official forum that the program will become paid, but the timing is still unknown. And the program already has developments for this. I treat it with understanding and quite calmly, because the work should bring income. Depending on the business model that Hasleo chooses, a real quest will arise - Macrium vs HBS.
Please help me find this menu item, I remember it was there but now I can't find it Create a separate folder for the task
When you start a new task, there's a DESTINATION DropDown available in the first window offered (underneath the "Task Name" and "Description"). You may use that to change the original DEFAULT for your new task folder. Once the task is established, this cannot change.
The developers are only busy improving existing features and fixing identified flaws for the next release, not adding new features - official forum. I want to try replication via post-commands. Tried it, via post commands with Robocopy replication works wonders.
The new version (no public release yet) fixes and improves some nuances. Сan't take a screenshot by booting from under WinPE Comment window bug Uninstaller leaves trash Time and Date in WinPE are incorrect
Does Retention policy work for any backup tasks (manually run + scheduled), or only for scheduled tasks?
My experience has shown me that their betas are really BETAs... be careful when using them. Their formal releases are quite solid...
The basic imaging/restoration modes appear to be the same (tested them). The TASK DropDown has a few more convenient option entries. The Devs claimed in the recent past that they were concentrating their effort in the file restoration area. I have a question into their Forum as to exactly what "feature enhancement" additions were made to this BETA (for testing purposes)... hopefully we'll here back.
No "ofishul" ChangeLog but the information below was garnered from their Development team. Pls remember, this is a BETA... feel free to try at your own risk but, please, report back any anomalies (best to do it in their Forum) you discover, thanks! ------------------------------------------------------------------- This BETA release includes the following enhancements: 1. Allows cloning and restoring between disks with different sector sizes. For example, cloning and restoring between a Windows Storage Pool (with a sector size of 4K bytes) and a physical disk (sector size is usually 512 bytes, 4K bytes is rare). 2. Reduce the wait time for canceling backup and restore operations. 3. Sort multiple scheduling tasks that need to be executed by the trigger time of scheduling. For example, if the execution time of a task is too long resulting in multiple scheduling tasks not being executed at the specified time, the missed scheduling tasks will be executed in the order of the trigger time of scheduling after the completion of that task. 4. Allows you to change the size of the main window within a certain range. The Devs can see that both the cloning algorithm and the scheduling algorithm have been improved and therefore need to be tested. More bug fixes/changes in addition to the enhancements above: 1. Fixed the window for entering comments not appearing. 2. Fixed the time displayed in WinPE does not match the time displayed in Windows. 3. The image retention policy is not available in WinPE. 4. You must enter access credentials to open the remote shared folder where the backup image files are stored, unless the current user is able to browse the folder through Explorer. 5. Fixed an issue where the last few sectors of the device could not be read. 6. Perform a full backup after the file system type of the partition to be backed up has changed (for example, from FAT to NTFS). 7. Virtual memory is too small causing memory allocation to fail, reduce the size of memory to be allocated and try again. 8. Added Ukrainian language support.
