Backupper "portable" and 64bit PE files

I like Aomei Backupper a lot, thanks for this great program.

I like to run it on my own custom PE, if I put the service settings in boot.wim beforehand, and add AmCore.dll to the program files, the program almost runs like a "portable app". Of course, most other disk imagers are portable as well, so there's no reason Aomei couldn't be portable, too.

I have even "discovered" a way to make the *32* bit program files *fully* portable. For this, on an unmodified, standard PE, I copy 3 files to "windows\system32" (ambakdrv.sys, amwrtdrv.sys, ammntdrv.sys), then start "loaddrv.exe". After this, I can run Backupper.exe and it runs perfectly. This works in 32bit and 64bit PE (both use different sys and loaddrv files, obviously). I would like this opportunity to request once again that the "AmCore.dll" dependency be removed, why does a free product check for a license? But that is not the real issue of this question.

 

My main question is: How can I use the *64* bit Aomei program files (located in the WinPE64 subfolder), using the same method described above? I have this tested and working by using the "builder script" method (that is: insert the sys files "offline" into boot.wim and set the service entries in the registry). Again, using this method the 64bit program files are working fine.

 

I would, however, like to know why the "on demand" method describe above, doesn't work with the **64bit program files**. Here's what I've tried:

[A] (1) Boot a clean 64bit PE (2) Copy the 3 64bit sys files to Windows\system32 (3) Run the 64bit Loaddrv.exe --> Backupper will run, but can't backup dus to driver error.

[B] (1) Boot a clean 64bit PE (2) Copy 3 64bit sys files (3) Set the service settings by hand:

Reg.exe add "HKLM\SYSTEM\ControlSet001\Control\Class\{71a27cdd-812a-11d0-bec7-08002be2092f}" /v "UpperFilters" /t REG_MULTI_SZ /d "ambakdrv" /f
Reg.exe add "HKLM\SYSTEM\ControlSet001\Services\ambakdrv" /v "DisplayName" /t REG_SZ /d "ambakdrv" /f
Reg.exe add "HKLM\SYSTEM\ControlSet001\Services\ambakdrv" /v "ErrorControl" /t REG_DWORD /d "0" /f
Reg.exe add "HKLM\SYSTEM\ControlSet001\Services\ambakdrv" /v "ImagePath" /t REG_EXPAND_SZ /d "\??\X:\windows\system32\ambakdrv.sys" /f
Reg.exe add "HKLM\SYSTEM\ControlSet001\Services\ambakdrv" /v "Start" /t REG_DWORD /d "2" /f
Reg.exe add "HKLM\SYSTEM\ControlSet001\Services\ambakdrv" /v "Type" /t REG_DWORD /d "1" /f

sc create ambakdrv  type= kernel start= auto binpath= "system32\ambakdrv.sys"
net start ambakdrv

This doesn't work either. Can you please look in to this matter and tell us how we can use the 64bit program files in a "clean" 64bit PE. The method works fine for 32bit program files, so I think it could work. The 64bit program files are there for a reason, aren't they? So why not explain how to use them in this (portable/ on demenad) manner. Also, please remove the AmCore.dll dependency. Any info would be greatly appreciated.

Comments

  • Hi atari800xl,


    I must say there are problems indeedly with Backupper if you want to run it in a third-party 64-bit WinPE, currently there are many relatively complicated operations needed to do if you want to add Backupper to WinPE yourself maunally.  We will release a PE edition of Backupper in the future.


    The file AmCore.dll, we will modify it in future versions, please keep an eye on our updates. Thank you very much for your attention to our Backupper.

  • Thank you very much for your reply. It would be great if you could make Aomei Backupper more "portable", and remove the unnecessary license checks in the free version.

    I'm looking forward to the new "PE-friendly" version!

  • I have a similar scenario having a custom Win7PE 32-bit build complied with Winbuilder and using a
    clean (i.e. standard Microsoft not Dell, HP etc) Win7 SP1 source which I
    would like to add Backupper to.


    I found this


    I have even "discovered" a way to make the *32* bit program files
    *fully* portable. For this, on an unmodified, standard PE, I copy 3
    files to "windows\system32" (ambakdrv.sys, amwrtdrv.sys, ammntdrv.sys),
    then start "loaddrv.exe". After this, I can run Backupper.exe and it
    runs perfectly.


    Noting the date post date was over 2 years ago this must have been with a much older version of Backupper. I have tried the same with backupper 4.0.2 but so far can not get it to run. The front end load but once it tries to create the backup falls over with the 4140 ' backup driver works improperly ' message.


    I created my file set from a Backupper created PE. To generate this I Used a Dell Windows 7 32 bit machine just with the installation as supplied i.e. I restored the factory image. I installed Backupper 4.0.2 then built the PE from within that. This PE runs.


    I have copied the Backupper folder from the expanded WIM file and added the drivers\i386 files.


    For the desktop icon I created this batch file based on the winPEshl.ini file


          copy driver\i386\*.* x:\windows\system32

          PeLoadDrv.exe

          Start Backupper.exe


    I have checked that the driver files have copied to x:\windows\system32.


    Any pointers as to what I am missing to get this to work will be appreciated.


  • The AOMEI Backupper support the portable version now, but you need to get the Tech or Tech plus version. For other version you cannot use it.

  • I will have to say there are actually difficulties indeedly with Backupper for those who would like to run it within a third-party with essentialpim pro 64-bit WinPE, currently there are several comparatively complicated operations needed to perform when you want to add Backupper to WinPE oneself maunally. We are going to release a PE edition of Backupper within the future.

Sign In or Register to comment.