Installation mode legacy does not appear in the choice menu...Why ???????
 
I tried every thing but I only loose time and money on your wintousb...
Does not seem to work at all...
Please refund !!!!!!!!!!!

Just noticed that after some extensive (powered) testing in this area, Event triggering fails (or stops working in its entirety) when the testing laptop is ON BATTERY and not on AC ADAPTER.

If not by design, maybe this is a bug (it seems to be undocumented in the appropriate manual section).

If by design... can an option CheckBox be made available in the Event Trigger window to control this activity (would like to do "low power" <battery> operations)?

Any help, greatly appreciated...

Much like the post here:
https://www.easyuefi.com/forums/showthread.php?tid=1158
which unfortunately does not appear to be responded to, I wanted to create a Grandfather, Father, Son backup scheme.

However, I started with trying Father Son first.

For clarity, Grandfather, Father, Son backs are something like this:
   1 full back up monthly
   differential backups weekly
   incremental backups daily

What I tried to start with was:
   1 full backup weekly
   incremental backups daily

What I got however was:
   1 full backup on day 1 (as expected)
   1 incremental backup, slightly larger than the prior days full backup, on day 2 (not as expected)

Of note, I did this with two schedules, one for the full backup weekly on Sundays, and one for the daily backups on (Monday - Saturday)

Also, the two schedules result in backups going to separate sub-directories, as I can't seem to specify the same directory for both in the settings.

A solution might be to do a post backup move, but it appears that is what @Dinar did in the post referenced above, but to no avail.

Any help would be appreciated

Why do you have a separate app called Hasleo Disk Clone?  All of its features are already integrated in Hasleo Backup Suite? Do you plan on discontinuing the Hasleo Disk Clone app?

What version of Windows is WinPE based on by default?

Currently the merge strategy seems to be: create a new file with all the data of the merged files combined, then delete the obsolete files.

This doesn't scale.

Example: a full backup using 51% of the available backup space. Merging any incremental backup with this is not possible, as the aforementioned method would occupy 51% twice during the merge operation.

A solution to this dilemma is non-trivial (and I don't know anything about the backup file format).

One strategy I could imagine: "melt" the older backup into the newer file. Say a full backup and an increment shall be merged:

• Mark the full backup file as "incomplete, use increment file for restore if selected"
  
• Read a chunk from the end of the full backup file
  
• Append all the data from that chunk which isn't obsolete as a new chunk to the increment file
  
• Truncate the full backup file to a new size, freeing exactly the copied chunk
  

• Mark the increment file as "incomplete, use full backup file for restore if selected"
  
• Read a chunk from the end of the increment file
  
• Append all the data from that chunk to the full backup file
  
• Truncate the increment file, freeing exactly the copied chunk
  

• Read a chunk from the full backup file
  
• If it contains obsolete data, copy and append to the end of the full backup file, discarding the obsolete data, and punch a hole at the old location
  

See Post #385 from the Wilders Security Forum (LOGs attached, just bringing the problem home)...

The current download is v3.4.1 and internally dated 10Mar2023.  The one offered for testing in a couple of the Forum areas is v3.4.1 and internally dated 13Mar2023.  Are these two versions functionally the same (they are different sizes, no ChangeLogs for either ) and if not, what might be the difference?

Is it possible to install windows on a mac OS ? Thanks

When deleting a backup task, an offer is made to delete the backup files as well.  When I check this option, and the target disk where the backup chain lives is not on-line (an off-line EXTERNAL USB), the process continues without mention of the fact that the backup chain files themselves were never deleted during this task deletion process (and don't get deleted later when the target device is brought back on-line).

This occurs in the latest release (don't know about earlier releases)... v3.4.1 Build#20230313.