Hasleo Backup Suite V5.9.2.3 Released!

[Froggie]

Hello everyone,

We invite community users to download and test the Hasleo Backup Suite V6.0.0.0 internal test build.

What's new in V6.0.0.0:

8. Improved the Automatic driver injection feature

@Admin, can you explain the improvements related to #8 above?  I constantly hear where users don't get all the needed drivers in the PE build when using this feature.  Specifically sometimes NETWORKING, HID (mice, keyboards), etc.

I'm curious what the improvements really are... thanks!

[Froggie]

Hello everyone,

We invite community users to download and test the Hasleo Backup Suite V6.0.0.0 internal test build.

What's new in V6.0.0.0:

1. Added Backup Image Protection feature

C'mon... put your name on that feature!  How 'bout the Hasleo Image Protector (HIP)... no one else has one of those 

[Bespoken]

Very limited tests with V6 as I am away from home. Installs and replaces old version successfully. Observations:

1. The create ED seems to have taken much more time. Will record the time with the next build.
2. The ED is huge at 2GB which is double the size of previous versions
3. 2-finger scroll on my HP still does not work in the ED environment

Many more tests to be done when I am back next weekend.

[admin]

@al3x,

Glad to hear that the image protection feature is working really well.

Actually, when HBS is uninstalled, hasleopi is uninstalled and removed, and the protection configuration is temporarily saved to the registry, along with a flag indicating whether image protection is enabled. When HBS is installed again, the installer will determine whether to restore image protection based on that flag.

Yes, hasleopi protects partitions by drive letter. Your idea of using GUIDs to protect partitions/drives is very good. The only issue is that comparing GUID strings would introduce more performance overhead, so we will consider it carefully.

Also, your suggestion to mark the partition itself (a hidden system file in the root directory) is excellent. Perhaps we can consider implementing a combination of the two approaches, and I think we can improve this in future versions.

To be honest, reimplementing either of the two approaches you mentioned would take a lot of time, because driver code must be written with extreme care, testing takes a lot of time, and it also has to pass Microsoft WHQL testing to get the driver signed. If we change it now, it could take about a month to complete. My idea is to first use partition drive letters for protection, and then gradually improve it by using GUIDs and creating a marker on the partition itself.

I have to say, you are a very thoughtful and talented person, and we should consult you before implementing important features.

Have a nice day!

Best regards,

[admin]

Hello everyone,

We invite community users to download and test the Hasleo Backup Suite V6.0.0.0 internal test build.

What's new in V6.0.0.0:

8. Improved the Automatic driver injection feature

@Admin, can you explain the improvements related to #8 above?  I constantly hear where users don't get all the needed drivers in the PE build when using this feature.  Specifically sometimes NETWORKING, HID (mice, keyboards), etc.

I'm curious what the improvements really are... thanks!

Wireless network adapters often don't work because the standard WinPE does not include the components required for Wi-Fi support, and Microsoft does not provide that component separately. As for HID devices not being recognized, modern laptops usually use I2C to connect HID devices. I2C is more complex than traditional PS/2 and requires support from an entire low-level driver chain, which the standard WinPE also does not provide. WinRE includes Wi-Fi and the components needed for I2C to work, so a WinPE built from WinRE can usually support Wi-Fi and HID devices properly. V6 will try to download WinRE from Microsoft instead of the standard WinPE, so it will provide better support for Wi-Fi and HID than previous versions.

HBS's Automatic driver injection attempts to extract the OEM drivers already installed in the current system and inject them into WinPE when creating WinPE. The key point is which drivers should be extracted. Injecting too many drivers will increase the size of WinPE and may cause WinPE to fail to boot properly.

[admin]

Hello everyone,

We invite community users to download and test the Hasleo Backup Suite V6.0.0.0 internal test build.

What's new in V6.0.0.0:

1. Added Backup Image Protection feature

C'mon... put your name on that feature!  How 'bout the Hasleo Image Protector (HIP)... no one else has one of those 

Wouldn't it be a bit awkward to put "Hasleo" in front? It's fine to call it that in tutorials, but what about when it appears on the Tools page in HBS? 

[admin]

Very limited tests with V6 as I am away from home. Installs and replaces old version successfully. Observations:

1. The create ED seems to have taken much more time. Will record the time with the next build.
2. The ED is huge at 2GB which is double the size of previous versions
3. 2-finger scroll on my HP still does not work in the ED environment

Many more tests to be done when I am back next weekend.

The reason the ED has become larger is due to the improvements to Automatic driver injection. It is difficult to determine which OEM drivers should be injected and which should not. 

[Epictetus]

Installed 6.0.0.0 and all went smoothly. It did take a bit longer but not much and I too noticed that the ED was much bigger, but no problem there. I also noticed that when making the ED, parts of the comments on my very high-scaled screen (225% I think) was no longer obscured/overlapped so that is great.

All up - very happy so thanks to the Hasleo team again.

[n8chavez]

Congratulations Hasleo on version 6! That's awesome. I haven't had a lot of time to test this new build, but there are a couple glaring issues I thought worth mentioned. The first is that I was unable to create the boot entry. I tried WinRE and downloading WinPE and using that. Both resulted in the same error, Failed to run System API (0x011F0015C0AAB132) That is a new issue that did not exist on 5.9.2.3. The second issue I came across has to do with the image protection feature. HBS was unable to see the drive I store my backups on, in my case b:\, thus I cannot enable the protection feature. That location is accessible, but the drive letter is hidden using a registry tweak. "Unhiding" the drive letter did not resolve the issue.

Off to test v6 more.