AOMEI Backupper Plugin

Dear Lancelot, are you really sure it will be better not to use "RequireIt"? I am kind of "in love" with it...

I am very sure with reasons I wrote above and experience behind
 We also could do copy files with autoit ,
   even with a Macro through MacroLibrary ,
     for very same reasons we did not... (keep in mind how much I like current builder  and how much I like Autoit still I did not  )

 Further it is your decision

Aeolis, we can have a vote about it

No vote required Atari800xl, come on , it is Aeolis plugin Aeolis decision.

We do not play vote games around here  we know it is plugin author decision.

Hence you are free to eat your shoes whenever you like. 
Like you are free to create some tutorials around or not 

On the other hand, If (personally) I put one of Aeolis plugin to a project in future,
 I would rewrite without this requireit.exe with reasons I wrote above, like all project maintainers around 

See You

Hello folks,

Dear Lancelot, thank you for your input. Well, it's always good to follow old Lancelot's advises, so I will just do that!

Well, I do "love" the current builder too, but I will go back to the previous AOMEI script structure for debug and continuity purposes as Lancelot pointed out.

Best regards,

Aeolis

Dear folks,

The new version v2.0 just came out. Would you please update your script to make it compatible to the new version?

Thanks,
oliverjia

Oliverjia, thanks for the tip, I was watching the demo page for days now, but that still mentioned the demo version that expired 15 March.
I downloaded the new version just now, and extracted the exe with InnoUnpack. It looks like the installer system hasn't changed much, so changing the script should not be too difficult. I'm sure Aeolis will adapt his script soon, meanwhile I'll be testing the "portable" program files with the current driver versions (looks like ambakdrv.sys, ammntdrv.sys and amwrtdrv.sys haven't changed from the previous version).
I will just copy the files from the (Inno-)extracted folder and rename (for 64bit)
LoadDrv,2.exe to LoadDrv.exe
vss,3.dll to vss.dll
vsscom,2.exe to vsscom.exe

This seems to work OK (just testing now). I see they changed the very first "It is loading" message (which always looked kinda weird to me) to "Loading", so that's a nice "feature" already!! 

Well, maybe I spoke a bit too soon. There's a new feature in 2.0 ("File Backup"), which doesn't seem to work with the current script version. Maybe there are some extra file dependencies after all. It crashes at the "Checking authority system" stage.
I really don't need this new File Backup function, but of course it would be nice if it worked.
I tested File Backup in a "normal" Windows 7 system, it works OK. Also tested on XP, seems to crash there as well.

Thanks Atari800xl for your testing.
Did not see a changelog for this version yet, hopefully it will fully support Win8.1.

Hello folks,

@oliverjia: Here is the link with version 2 changes: http://www.backup-utility.com/new-features.html

@oliverjia and @Atari800xl: I did a very fast test with version 2 under Win8.1SE x86 build and everything worked as expected (I tested the File Backup option and it worked as expected too). The only small "glitch" I have noticed for now is that the new .afi files does not have icons (can be easily fixed). So, i do recommend you both test the new version 2 with the current script and post back here the results. When posting the results of your tests, please, be very descriptive about the steps to reproduce any errors you've found.

Best regards,

Aeolis

Dear Aeolis,

    I encountered the same error when run your script in Winbuilder 0.82: "unable to open file "install_script.iss"". Before I click "Ok", I tried to look for it in workbench folder but could not find it. You script v9 works fine. Please check.

You script v9 works fine. Please check.

Oliverjia, is the new File Backup feature working at your end? Maybe I should check for components/ other stuff I turned off in WB.

Since the ISO building process failed, I don't have a chance to test it yet. Hope Aeolis can fix the extraction bug.

OK, sorry 'bout that, I thought you tested it already because you said "v9 works fine".

Sorry for the confusion - I meant to say v9 works fine when I tried it before. I deleted v9 afterwards.

Hello folks,

@oliverjia: the error you are experiencing is due the fact that "ISISPECreator.exe" can't read/access "install_script.iss". That file is extracted from the AOMEI Backupper installer using "innounp.exe" which is the Inno Setup Unpacker. So, this can be related to the following scenarios:

1) "install_script.iss" is locked because an application is accessing it;

2) "install_script.iss" is not there because an application has deleted it; and

3) "install_script.iss" is not there because an application has prevented "innounp.exe" from running.

Then I ask you the following questions:

1) Have you experienced any security alerts from your Antivirus (with HIPS, Behavior Block or Sandbox), Firewall (with HIPS, Behavior Block or Sandbox) or Anti-Key logger (with HIPS, Behavior Block or Sandbox) regarding "innounp.exe" trying to run? If not, please, check your security application logs to be sure they are not preventing "innounp.exe" from running properly.

2) Have you white-listed the path to your PE Projects in your security applications configurations? If not, please, do that. It will really speed up your work when building PE and will give you less problems.

Best regards,

Aeolis

Hi Aeolis,

I guess I know the problem, (inounp .iss etc..)
we have solved it long while ago  (no report since than  )

Long to short:
*
Check
Gena\Apps\HD Tasks\"Partition Wizard Home"
[Extract]
section,
use same with your plugin  for innounp extraction
(change folders for your needs  )
benefits:
+ above will not occur
+ no need innounp inside plugin 
+ innounp updated when required 

 




*
Another thing I noticed for your plugin:
if ISISPECreator.exe is not a secret,
you can use ISISPECreator.au3 directly with /AutoIt3ExecuteScript parameter

Something like that

Code: [Select]

ShellExecute,Open,%Tools%\x86\AU3381.exe,"#$q/AutoIt3ExecuteScript#$q #$q%pFileBox1%Backuper\ISISPECreator.exe#$q #$q%Keep1%#$q #$q%Keep2%#$q #$q#$q,"%pFileBox1%Backuper"

This would gain more space for plugin 

ps: on Macro Library and lots of plugin, we use /AutoIt3ExecuteScript 


*
See You

Thanks Aeolis. I saw innounp.exe and backupper.exe in the workbench folder but it appears somehow the backupper.exe. It appears the extraction process did not happen, therefore there is no install_script.iss file in there.
I also checked my antivirus log, there is no indication of blocked program.

Regards,
oliverjia

Hello folks,

@oliverjia: the error you are experiencing is due the fact that "ISISPECreator.exe" can't read/access "install_script.iss". That file is extracted from the AOMEI Backupper installer using "innounp.exe" which is the Inno Setup Unpacker. So, this can be related to the following scenarios:

1) "install_script.iss" is locked because an application is accessing it;

2) "install_script.iss" is not there because an application has deleted it; and

3) "install_script.iss" is not there because an application has prevented "innounp.exe" from running.

Then I ask you the following questions:

1) Have you experienced any security alerts from your Antivirus (with HIPS, Behavior Block or Sandbox), Firewall (with HIPS, Behavior Block or Sandbox) or Anti-Key logger (with HIPS, Behavior Block or Sandbox) regarding "innounp.exe" trying to run? If not, please, check your security application logs to be sure they are not preventing "innounp.exe" from running properly.

2) Have you white-listed the path to your PE Projects in your security applications configurations? If not, please, do that. It will really speed up your work when building PE and will give you less problems.

Best regards,

Aeolis

Hello folks,

@oliverjia: Check the new version 11 and, please, post back here your experience.

Best regards,

Aeolis

Thanks Aeolis for the updated script.. Just tried on two computers, however same error. backupper.exe is not being extracted when ran the script in Winbuilder. It appears ISISPECreator.exe is running as indicated by tray icon. The problems appears to be innounp.exe not being able to extract backupper.exe.

Hello folks,

@oliverjia: Yes, you're right "innounp.exe" have been prevented from running. The one million dollars question is: Who is preventing it from running?

Well, you said it happened in two different machines. So, I ask you: Have the two machines the same configuration? I mean, do they have the same Operational System or Security applications?

You could do a test to find out the application that is preventing "innounp.exe" from running.

1) Go to Inno Unpacker homepage: http://innounp.sourceforge.net/
2) Download the latest Inno Unpacker version (0.40 by now - "innounp040.rar")
3) Extract it to your Desktop
4) Run Windows Command Line Interpreter (cmd.exe - in System32 folder)
5) Drag and drop "innounp.exe" into cmd.exe window (the one  that was extracted to your Desktop - in step 3)
6) Press Enter

Now you should see the help information from Inno Unpacker with commands that the "innounp.exe" executable accepts etc. If you do not see that you should instead receive an alert from some application regarding "innounp.exe" trying to run and then you will have found the culprit.

Best regards,

Aeolis

Thanks Aeolis for the updated script.. Just tried on two computers, however same error. backupper.exe is not being extracted when ran the script in Winbuilder. It appears ISISPECreator.exe is running as indicated by tray icon. The problems appears to be innounp.exe not being able to extract backupper.exe.

It appears innounp.exe runs fine.



innounp, the Inno Setup Unpacker. Version 0.40
Usage: innounp [command] [options] <setup.exe or setup.0> [@filelist] [filemask
...]
Commands:
  (no)   display general installation info
  -v     verbosely list the files (with sizes and timestamps)
  -x     extract the files from the installation (to the current directory, also
 see -d)
  -e     extract files without paths
  -t     test files for integrity
Options:
  -b     batch (non-interactive) mode - will not prompt for password or disk cha
nges
  -q     do not indicate progress while extracting
  -m     extract internal embedded files (such as license and uninstall.exe)
  -pPASS decrypt the installation with a password
  -dDIR  extract the files into DIR (can be absolute or relative path)
  -cDIR  specifies that DIR is the current directory in the installation
  -n     don't attempt to unpack new versions
  -fFILE same as -p but reads the password from FILE
  -a     extract all copies of duplicate files
  -y     assume Yes on all queries (e.g. overwrite files)

oh, to answer your other questions:

yes the configuration of the two computers are the same: Kaspersky Internet Security 2014 + Malwarebytes Anti-Malware Pro v2.0. I tried to disable both when run your script but still same problem. The OS is Windows 8.1 Enterprise x64.