Topic: Disk imagers in PE/SE: Basic build info - Comparison - News  (Read 37371 times)

0 Members and 1 Guest are viewing this topic.

Re: Disk imagers in PE/SE: Basic build info - Comparison - News
« Reply #20 on: January 07, 2015, 10:33:30 AM »

Atari800xl

  • Code Baker
  • Sr. Chef
  • ****
  • Date Registered: Feb 2013
  • Posts: 754
LinhHonHuynhDe told me it's alright to share his batchfile for starting the Acronis TrueImage services "on demand" (thus making Acronis "semi-portable!), so I can share the write-up I made if anyone's interested (if not, I will share it anyway).

I've tested his solution with
- Acronis TrueImage 2014 (which has 32bit program files) on 32bit PE, and
- Acronis 2015 (64bit program files) on 64bit PE.
I've tested with Gena, Win7PESE, Win8PESE and Win8.1SE, all working fine.
Of course, running 32bit 2014 on 64bit PE is also possible, but I feel that would confuse things for this topic, we can always discuss that later.

I want to thank Anshad and LinhHonHuynhDe again for this great tip!

Re: Disk imagers in PE/SE: Basic build info - Comparison - News
« Reply #21 on: January 08, 2015, 08:34:36 AM »

JFX

  • Moderator, Code Baker
  • Sr. Chef
  • *****
  • Date Registered: Dec 2010
  • Posts: 808
For command line user ShadowProtect can be reduces to just 2 files.
SbRun.exe and stcsnap.dll (or stcsna64.dll if you use x64 version)

That makes ShadowProtect winning, with fastest restore time and smallest program size :grin:
« Last Edit: January 08, 2015, 08:44:00 AM by JFX »

Re: Disk imagers in PE/SE: Basic build info - Comparison - News
« Reply #22 on: January 08, 2015, 09:08:59 AM »

Atari800xl

  • Code Baker
  • Sr. Chef
  • ****
  • Date Registered: Feb 2013
  • Posts: 754
Thanks JFX, looks interesting. I did a quick search on sbrun.exe, but it looks it's not really easy to use? Do you use it yourself? Also, do you really think these two files are all you need? I read something about the command line tool needing the shadowprotect services?

I find all this stuff very interesting, but I will only write more about that great Acronis batchfile if anybody else is interested.

JFX, I would normally never ask, but since you replied to this Disk Imager thread, and told us yesterday you were "slightly bored": Have you ever played around with Aomei Backupper? It's driving me crazy  :lol:

I did some tests with it (32bit), and it's also "almost portable": You only need to copy a few files (that is: after the PE has booted) to system32 (ammntdrv.sys, ambakdrv.sys, amwrtsrv.sys) and start "LoadDrv.exe".
Problem is: this only works if I use this builder script:
Code: [Select]
RegHiveLoad,Tmp_Default,%RegDefault%
RegWrite,HKLM,0x0,"Tmp_Default\Software\AOMEI\AOMEI Backupper Standard Edition 2.2.0.0"
RegHiveUnLoad,Tmp_Default

RegWrite,HKLM,0x3,Tmp_Software\Microsoft\Windows\CurrentVersion,ProgramData,be,1e,2f,f2,9e,6a,19,a6,1e,e2,3e,e2,ef,7b,18,b5,1d,d3,4d,d2,1c,9b,19,92,31,93,64,f6,5a,f0,61,92,2c,85,3f,80,56,eb,1b,ee,2a,97,9e,a4,89,a9,b5,51,b2,88,c8,df,d1,df,64,a9,21,d1,a1,b5,85,b9,71,d4,5c,41,8a,26,8e,45,01,2b,16,6a,b6,62,c6,6d,46,6e,15,5b
RegHiveUnLoad,Tmp_Software

RegHiveLoad,Tmp_System,%RegSystem%
RegWrite,HKLM,0x7,Tmp_System\ControlSet001\Control\Class\{71A27CDD-812A-11D0-BEC7-08002BE2092F},UpperFilters,ambakdrv

One of these seems to be the "magic" one (although I have NO IDEA which one, or WHY!!??), because if I leave out this script, it doesn't work, and I can't set these entries "on demand" (=after I boot the PE). Do you have any idea how to resolve this? (Would a nircmd "refresh" command or something help here, you think?)
If you never use Aomei (or don't intend to either), please forget about it, but I just HAD to ask! Thanks anyway!

Re: Disk imagers in PE/SE: Basic build info - Comparison - News
« Reply #23 on: January 08, 2015, 08:59:20 PM »

JFX

  • Moderator, Code Baker
  • Sr. Chef
  • *****
  • Date Registered: Dec 2010
  • Posts: 808
Yes, I use ShadowProtect myself. The command line is a bit uneasy, but the GUI version display the command line for the used task.
So the only problem is that it want a volume name (the one you can get from mountvol.exe) and not a simple drive letter.

Actually the lack of command line support in Acronis pushed me to change to StorageCraft.

Not sure what's your problem with Aomei Backupper?
Works here, copied the 3 .sys in system32 and run Loaddrv.exe.

Loaddrv writes this UpperFilters value and Backupper the other 2.
What happens if you run the setup inside PE?

Re: Disk imagers in PE/SE: Basic build info - Comparison - News
« Reply #24 on: January 09, 2015, 02:33:21 AM »

Atari800xl

  • Code Baker
  • Sr. Chef
  • ****
  • Date Registered: Feb 2013
  • Posts: 754
Thanks for the great ShadowProtect tip, JFX!!! :thumbsup:

I only recently "discovered" this great program, and had not noticed the command line in the "details" view yet. Very nice, it really only needs the two files you mentioned, unbelievable!! 774 kb total... But then again, you're a master in tiny exe files as well (GetWAIKTools...) Thanks for the mountvol tip as well, it should be pretty easy to process the output of that. I guess it doesn't cover hidden volumes, but maybe I'll find a solution for that as well.

Thanks for looking into Aomei. I would really like to run this "portable" as well, but there are a few weird twists, it would be great it you could shed some light on that. As you said, you can just copy the 3 files, start LoadDrv.exe and start Backupper.exe, but if I don't use the builder script I mentioned: I'm getting the dreaded "Register" screen! (just tested it again on a "clean" Win7PESE-32): "The software has expired - Please copy the "Machine Code" below and the "License Code" you received when purchasing the program to ...etc."
:white_flag: This is the part that's driving me crazy.  :wacko:


Of course the script that ChrisR made works fine, so I always have that working version, but I just don't understand what is the "magic part". As I mentioned above, these seem to be the only three lines in the script that make the difference between working or not working (although I can't reproduce that in a normal "on-demand" scenario). I've also written to Aomei to ask why they use this check in a "Free" version at all!!! The drivers were a bit of a problem before (and still are in 64bit, but we can discuss that later), but now with the "copy files and start loaddrv.exe" method, this seems to be taken care of, so there's only that horrible "Expired" dialog that's driving me nuts...  :deadhorse:

Re: Disk imagers in PE/SE: Basic build info - Comparison - News
« Reply #25 on: January 09, 2015, 03:01:18 AM »

Atari800xl

  • Code Baker
  • Sr. Chef
  • ****
  • Date Registered: Feb 2013
  • Posts: 754
One more thanks: For the tip of installing Aomei in PE (never thought of that, not even for testing. Only used the ChrisR innounp method until now). Did that just now and it works. Now I'm still trying to figure out which setting/ file is the "magic" one, ie which setting I need to make in PE so I can use the portable program files in the next PE boot. (Must be amcore.dll?)

I copied the intalled files from x:\program files to a hard disk folder, then rebooted (to PE). Started backupper from the hd folder: worked... (Hmm, why? <g>). So this is without any reg settings at all. Makes me think it's amcore.dll after all. But please note, I *did* have an amcore.dll file in my previous tests.

Oh well, if this is really working, and keeps working, I will have to follow these steps in future: (1) Boot PE, install Aomei (2) Save the installed folder to HD (3) On next PE boot: copy 4 driver .sys files myself, start LoadDrv.exe (4) Start backupper.
At least this is giving me some new chances to test, so thanks again for your help.
BTW, have you also tried the 64bit PE files?


« Last Edit: January 09, 2015, 03:20:32 AM by Atari800xl »

Re: Disk imagers in PE/SE: Basic build info - Comparison - News
« Reply #26 on: January 09, 2015, 08:14:21 AM »

Atari800xl

  • Code Baker
  • Sr. Chef
  • ****
  • Date Registered: Feb 2013
  • Posts: 754
Did a few more tries, and the method seems to work for now (32 bit program files only): (1) Run the installer in PE (so it doesn't modify your normal Windows) (2) Copy the program files folder (with AmCore.dll!) (3) Reboot your PE (4) This time, all you need is: copy the driver files, start LoadDrv.exe, run Backupper from saved files of step (2).

This only leaves the WinPE64 subfolder. Copying the 64bit drivers and starting the 64bit LoadDrv.exe is not enough. Any ideas? Of course, the 64bit program files can't be "installed" in the normal method, they just kind of "sit there" in the installer. (They *do* work with the ChrisR script, so it must be a "tiny" little thing...)

Re: Disk imagers in PE/SE: Basic build info - Comparison - News
« Reply #27 on: January 09, 2015, 08:51:55 AM »

JFX

  • Moderator, Code Baker
  • Sr. Chef
  • *****
  • Date Registered: Dec 2010
  • Posts: 808
Just wait what Aomei support says about registration of a freeware  :confused:

Don't know if I install it in WinPE x64, system get's instable  :blink:
« Last Edit: January 09, 2015, 08:52:09 AM by JFX »

Re: Disk imagers in PE/SE: Basic build info - Comparison - News
« Reply #28 on: January 09, 2015, 08:58:34 AM »

SIW2

  • Code Baker
  • Chef
  • ***
  • Date Registered: Jul 2012
  • Posts: 167
Where did you get 64bit LoadDrv.exe ? I haven't got one of those in Backupper.


Not sure why you are having difficulty.

I copy the 3 sys files to mount\system32 ( or Target\system32 - whatever you are using for that ), and the contents of the AOMEI\WINPE64 folder to mount\program files\aomei.

I also copy amcore.dll from AOMEI folder to  mount\program files\aomei. Just a small reg entry. Job done.

Code: [Select]
[HKEY_LOCAL_MACHINE\PE_SYS\ControlSet001\Control\Class\{71a27cdd-812a-11d0-bec7-08002be2092f}]
"UpperFilters"=hex(7):61,00,6d,00,62,00,61,00,6b,00,64,00,72,00,76,00,00,00,00,\
  00

[HKEY_LOCAL_MACHINE\PE_SYS\ControlSet001\Services]

[HKEY_LOCAL_MACHINE\PE_SYS\ControlSet001\Services\ambakdrv]
"DisplayName"="ambakdrv"
"ErrorControl"=dword:00000000
"ImagePath"=hex(2):5c,00,3f,00,3f,00,5c,00,58,00,3a,00,5c,00,77,00,69,00,6e,00,\
  64,00,6f,00,77,00,73,00,5c,00,73,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,\
  00,5c,00,61,00,6d,00,62,00,61,00,6b,00,64,00,72,00,76,00,2e,00,73,00,79,00,\
  73,00,00,00
"Start"=dword:00000002
"Type"=dword:00000001
« Last Edit: January 09, 2015, 09:07:24 AM by SIW2 »

Re: Disk imagers in PE/SE: Basic build info - Comparison - News
« Reply #29 on: January 09, 2015, 09:25:51 AM »

Atari800xl

  • Code Baker
  • Sr. Chef
  • ****
  • Date Registered: Feb 2013
  • Posts: 754
Thanks SIW2. You are talking about "building" stuff into the wim, *before* booting the PE, correct?

I was also talking about pure "on the fly"/ "portable" use of Aomei, just as a point of interest. As it seems so many of the current imagers can run (almost) completely portable/ on demand (even Acronis, with the LinhHon batch), I was just interested in how this could be done with Aomei.
I discovered by accident that on a running PE (no previous reg stuff done) all it needs is the 3 driver files, then a LoadDrv.exe, and the AmCore.dll file. Have you made any "discoveries" on AmCore.dll? Has it ever "expired" on you?
For running the 32-bit PE program files, there's a 32bit LoadDrv.exe (68kb) and a 64bit LoadDrv.exe (72kb).

For the 64bit  PE program files, there's no LoadDrv.exe it seems, using the 72kb LoadDrv.exe doesn't seem to work.

Thanks for any insights in this. Thanks JFX, for agreeing with me on the fact that it's strange that Aomei has a built in "License check" on their "Freeware" version....

Re: Disk imagers in PE/SE: Basic build info - Comparison - News
« Reply #30 on: January 09, 2015, 09:45:24 AM »

Atari800xl

  • Code Baker
  • Sr. Chef
  • ****
  • Date Registered: Feb 2013
  • Posts: 754
So the question is: Could the Aomei 64bit PE program files be used "on demand"? (As the 32bit files can, but they have LoadDrv.exe 32/64)
If I compare it with the Acronis batch method, and the script based stuff, maybe something like this?
- Boot your "clean" 64bit PE
- Copy the 4 64bit sys files to system32
- Load the reg file (like SIW2's version)
- Create and start the ambakdrv service "on the fly" (Is that even possible? It is with Acronis TI)
  Something like
  "sc create ambakdrv type= kernel start= demand binpath= "system32\ambakdrv.sys"
  net start ambakdrv
- Run the 64bit PE files.

Just trying to learn here...  :embarrassed:

Re: Disk imagers in PE/SE: Basic build info - Comparison - News
« Reply #31 on: January 09, 2015, 10:00:06 AM »

Atari800xl

  • Code Baker
  • Sr. Chef
  • ****
  • Date Registered: Feb 2013
  • Posts: 754
Oh right, I never even posted that Acronis "drivers on demand" script by LinhHon.

To be clear: This can be run on a "running" PE, so this is making Acronis "Portable".

Code: [Select]
copy snapapi.dll %windir%\system32
copy snapman.sys %windir%\system32\drivers
copy fltsrv.sys %windir%\system32\drivers

REG.exe ADD HKLM\SYSTEM\ControlSet001\Control\Class\{1860459D-4692-4825-B761-44A725991050} /f /v "Class" /T REG_MULTI_SZ /D "Acronis Devices"
REG.exe ADD HKLM\SYSTEM\ControlSet001\Control\Class\{1860459D-4692-4825-B761-44A725991050} /f /v "Icon" /T REG_MULTI_SZ /D "-5"
REG.exe ADD HKLM\SYSTEM\ControlSet001\Control\Class\{71A27CDD-812A-11D0-BEC7-08002BE2092F} /f /v "UpperFilters" /T REG_MULTI_SZ /D "fltsrv"
REG.exe ADD HKLM\SYSTEM\ControlSet001\Services\fltsrv /f /v "ErrorControl" /T REG_DWORD /D "0"
REG.exe ADD HKLM\SYSTEM\ControlSet001\Services\fltsrv /f /v "DisplayName" /T REG_SZ /D "Acronis Storage Filter Management"
REG.exe ADD HKLM\SYSTEM\ControlSet001\Services\fltsrv /f /v "ImagePath" /T REG_SZ /D "system32\DRIVERS\fltsrv.sys"
REG.exe ADD HKLM\SYSTEM\ControlSet001\Services\fltsrv /f /v "Start" /T REG_DWORD /D "3"
REG.exe ADD HKLM\SYSTEM\ControlSet001\Services\fltsrv /f /v "Type" /T REG_DWORD /D "1"
REG.exe ADD HKLM\SYSTEM\ControlSet001\Services\fltsrv /f /v "Tag" /T REG_DWORD /D "8"
sc create fltsrv type= kernel start= demand binpath= "system32\DRIVERS\fltsrv.sys"
net start fltsrv

REG.exe ADD HKLM\SYSTEM\ControlSet001\Services\snapman /f /v "ErrorControl" /T REG_DWORD /D "1"
REG.exe ADD HKLM\SYSTEM\ControlSet001\Services\snapman /f /v "ImagePath" /T REG_SZ /D "system32\DRIVERS\snapman.sys"
REG.exe ADD HKLM\SYSTEM\ControlSet001\Services\snapman /f /v "Start" /T REG_DWORD /D "0"
REG.exe ADD HKLM\SYSTEM\ControlSet001\Services\snapman /f /v "Type" /T REG_DWORD /D "1"
sc create snapman type= kernel start= boot binpath= "system32\DRIVERS\snapman.sys"
net start snapman

REG.EXE ADD "HKLM\SOFTWARE\Acronis\TrueImage" /f /v "standard" /t REG_SZ /d "*** YOUR ENCODED SERIAL HERE ***"
« Last Edit: January 09, 2015, 10:01:18 AM by Atari800xl »

Re: Disk imagers in PE/SE: Basic build info - Comparison - News
« Reply #32 on: January 09, 2015, 01:08:40 PM »

SIW2

  • Code Baker
  • Chef
  • ***
  • Date Registered: Jul 2012
  • Posts: 167
Yes , I expect you could use similar to create the service for Aomei. Haven't needed to try it though.

Code: [Select]
Reg.exe add "HKLM\PE_SYS\ControlSet001\Control\Class\{71a27cdd-812a-11d0-bec7-08002be2092f}" /v "UpperFilters" /t REG_MULTI_SZ /d "ambakdrv" /f
Reg.exe add "HKLM\PE_SYS\ControlSet001\Services\ambakdrv" /v "DisplayName" /t REG_SZ /d "ambakdrv" /f
Reg.exe add "HKLM\PE_SYS\ControlSet001\Services\ambakdrv" /v "ErrorControl" /t REG_DWORD /d "0" /f
Reg.exe add "HKLM\PE_SYS\ControlSet001\Services\ambakdrv" /v "ImagePath" /t REG_EXPAND_SZ /d "\??\X:\windows\system32\ambakdrv.sys" /f
Reg.exe add "HKLM\PE_SYS\ControlSet001\Services\ambakdrv" /v "Start" /t REG_DWORD /d "2" /f
Reg.exe add "HKLM\PE_SYS\ControlSet001\Services\ambakdrv" /v "Type" /t REG_DWORD /d "1" /f
« Last Edit: January 09, 2015, 01:13:00 PM by SIW2 »

Re: Disk imagers in PE/SE: Basic build info - Comparison - News
« Reply #33 on: January 09, 2015, 06:40:16 PM »

gbrao

  • Chef
  • ***
  • Date Registered: Sep 2011
  • Posts: 176
Yes, I use ShadowProtect myself. The command line is a bit uneasy, but the GUI version display the command line for the used task.
So the only problem is that it want a volume name (the one you can get from mountvol.exe) and not a simple drive letter.

Could you please share one of the SProtect cmd/scripts (as an example) ?

Re: Disk imagers in PE/SE: Basic build info - Comparison - News
« Reply #34 on: January 09, 2015, 08:11:35 PM »

Atari800xl

  • Code Baker
  • Sr. Chef
  • ****
  • Date Registered: Feb 2013
  • Posts: 754
Yes , I expect you could use similar to create the service for Aomei. Haven't needed to try it though.

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

Thanks for your reply. I feel a solution can't be far...
So what we're trying to do here is have a "LoadDrv.exe"-type solution for Aomei64, to load the 64bit drivers for the 64bit PE files "on demand", without the need for a build script. (Just trying to be clear).

This is what I've tried so far: (1) Boot 64bit PE (2) Copy 64bit drivers to system32 (msahci.sys, ambakdrv.sys, ammntdrv.sys, amwrtdrv.sys) (3) Start SIW2's batch quoted above (replacing "PE_SYS" with "SYSTEM"
(4) sc create ambakdrv type= kernel start= demand binpath= "system32\ambakdrv.sys"
net start ambakdrv

This results in "The service cannot be started, either because it is disabled or because it has no enabled devices associated with it".

Any more hints would be appreciated. Thanks!


Re: Disk imagers in PE/SE: Basic build info - Comparison - News
« Reply #35 on: January 09, 2015, 08:36:54 PM »

SIW2

  • Code Baker
  • Chef
  • ***
  • Date Registered: Jul 2012
  • Posts: 167
You don't need msahci.sys. Not sure why it is there - maybe for pe2.

demand is start type 3
auto is start type 2

sc create ambakdrv  type= kernel start= auto binpath= "system32\ambakdrv.sys"
net start ambakdrv
« Last Edit: January 09, 2015, 08:51:25 PM by SIW2 »

Re: Disk imagers in PE/SE: Basic build info - Comparison - News
« Reply #36 on: January 09, 2015, 09:02:24 PM »

Atari800xl

  • Code Baker
  • Sr. Chef
  • ****
  • Date Registered: Feb 2013
  • Posts: 754
Thanks SIW2. Getting closer all the time...
Same error though. Don't we need to create a service for the other sys file(s) [amwrtdrv, ammntdrv], like the Acronis batch file does? (Just throwing out ideas).
Thanks for your input!!
(Oh, and for anyone wondering what's the point: I'm just interested to learn where the exact differences are in starting these kinds of services "beforehand" [=in a script or modifying the wim by hand], and starting them on demand).
« Last Edit: January 09, 2015, 09:22:21 PM by Atari800xl »

Re: Disk imagers in PE/SE: Basic build info - Comparison - News
« Reply #37 on: January 09, 2015, 09:26:47 PM »

SIW2

  • Code Baker
  • Chef
  • ***
  • Date Registered: Jul 2012
  • Posts: 167
I wouldn't put msahci in, it is the win7 version. Win8 already has it ( so does 7 so no idea what it is doing there).

You don't need to start the other linked drivers. Backupper will do that as soon as you fire it up.

Don't worry about the message, it works perfectly. You can test by mounting an .adi image.

If you want to get really fancy, you can copy adi.ico to Program Files\aomei as well and it makes the .adi images look pretty.

Code: [Select]
Reg.exe add "HKLM\SOFTWARE\Classes\AOMEI Backupper Backup File" /ve /t REG_SZ /d "AOMEI Backupper Backup File" /f
Reg.exe add "HKLM\SOFTWARE\Classes\AOMEI Backupper Backup File\DefaultIcon" /ve /t REG_SZ /d "X:\Program Files\AOMEI\adi.ico" /f
Reg.exe add "HKLM\SOFTWARE\Classes\.adi" /ve /t REG_SZ /d "AOMEI Backupper Backup File" /f
Reg.exe add "HKLM\SOFTWARE\Classes\.afi" /ve /t REG_SZ /d "AOMEI Backupper Backup File" /f

« Last Edit: January 09, 2015, 09:28:01 PM by SIW2 »

Re: Disk imagers in PE/SE: Basic build info - Comparison - News
« Reply #38 on: January 09, 2015, 09:50:32 PM »

Atari800xl

  • Code Baker
  • Sr. Chef
  • ****
  • Date Registered: Feb 2013
  • Posts: 754
OK, so we should ignore the error?
I tried again: (1) Boot 64bit PE (2) Copy ambakdrv.sys, ammntdrv.sys, amwrtdrv.sys (3) Start your batch (4) sc create ambakdrv type= kernel start= demand binpath= "system32\ambakdrv.sys" (5) net start ambakdrv (6) ignore error (7) Start backupper.exe from WinPE64 folder (added amcode.dll before) (8) "The backup driver works improperly, etc.
Too bad, had already begun celebrating...  :lol:

Thanks for all your help SIW2, I hope you will find the missing link... :great:


Re: Disk imagers in PE/SE: Basic build info - Comparison - News
« Reply #39 on: January 09, 2015, 10:10:35 PM »

SIW2

  • Code Baker
  • Chef
  • ***
  • Date Registered: Jul 2012
  • Posts: 167
It works for me:

Code: [Select]
@Echo Off
Reg.exe add "HKLM\SOFTWARE\Classes\AOMEI Backupper Backup File" /ve /t REG_SZ /d "AOMEI Backupper Backup File" /f
Reg.exe add "HKLM\SOFTWARE\Classes\AOMEI Backupper Backup File\DefaultIcon" /ve /t REG_SZ /d "X:\Program Files\AOMEI\adi.ico" /f
Reg.exe add "HKLM\SOFTWARE\Classes\.adi" /ve /t REG_SZ /d "AOMEI Backupper Backup File" /f
Reg.exe add "HKLM\SOFTWARE\Classes\.afi" /ve /t REG_SZ /d "AOMEI Backupper Backup File" /f

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
PAUSE

 

Powered by EzPortal