Acronis Backup&Restore
#1
Posted 09 September 2009 - 01:59 PM
topic moved to apps section
------------------------------------------------------------
Hallo,
did someone have already script for Acronis Backup&Restore?
If yes please post.
Xplod
#2
Posted 11 September 2009 - 01:04 PM
AcronisBackupAndRecovery10_v4.7z 3.02KB 1562 downloads
it is only the BartPE version
Edit:
(
seems mms always should be located
in 'x:\program files' inside the wim)
the BartPE version needs lic
the script try to read it from the host
in that case if it is not successful
then try to run Acronis\WinPE\WinPE\export_license.bat
and should correct the script yourself
look into license.info and put the needed data into the script
Edited by dera, 19 September 2009 - 12:50 PM.
script updated
#3
Posted 11 September 2009 - 10:48 PM
see post #2
now in VistaPE project can select RunFromRam or not RunFromRam
(choice to place the prog. in 'Program Files' inside the vistape.wim or place the prog. in 'Programs' folder in the CD root)
Edited by dera, 12 September 2009 - 12:00 PM.
attachment removed, see post #2
#4
Posted 12 September 2009 - 10:17 AM
updated to version=3
hopefully the script now works in LiveXP project, too
(RunFromRam checkbox has no effect in LiveXP)
mistake:
missing 'UpperFilters' registry entries
corrected
#5
Posted 12 September 2009 - 06:25 PM
another good script at App Scripts
#6
Posted 13 September 2009 - 06:11 AM
but noticed
in that script in the section [allow_mms] at lines #166-167 there are the lines:
//AddAutoRun,start_mms, etc.
AddPostConfig,start_mms, etc.
seems this works in VistaPE,
but seems does not work in Win7RescuePE if the "Run from ram (boot.wim)" checkbox is unchecked,
maybe would be better to change them,
uncomment 'AddAutoRun' and comment out 'AddPostConfig'
so try change them to:
AddAutoRun,start_mms, etc.
//AddPostConfig,start_mms, etc.
#7
Posted 13 September 2009 - 07:19 AM
You found a bug in Win7RescuePE loader.but seems does not work in Win7RescuePE if the "Run from ram (boot.wim)" checkbox is unchecked,
This is easy to fix.
It will work in next version.
Joshua
#8
Posted 15 September 2009 - 11:26 AM
and seems using win7peldr.exe v.1.2.0.7
either AddAutoRun, either AddPostConfig works fine
but noticed
the prog can work only in that case
if in the 'Configuration' script (\Projects\Win7RescuePE\config.script)
'Build model: In RAM (boot.wim)' option selected,
if 'Build model: Normal' option used then the prog. doesn't work at all (seems doesn't get the lic in the running Win7RescuePE)
Any idea why does it happen or how should to solve this problem?
#9
Posted 16 September 2009 - 08:54 AM
Windows Professional 2000 SP4/Professional XP SP2
Windows XP Professional x64 Edition/Home Edition
Windows Vista - all editions
#10
Posted 16 September 2009 - 09:09 AM
I have no AcronisBackupAndRecovery10 for testing!if 'Build model: Normal' option used then the prog. doesn't work at all (seems doesn't get the lic in the running Win7RescuePE)
Any idea why does it happen or how should to solve this problem?
i will look to your script, may be i found something that causes this?
Joshua
#11
Posted 16 September 2009 - 10:46 AM
At the first time when made the script for VistaPE, where i always used the .wim,
noticed that i am unable to place the program outside the .wim,
i.e. in 'Programs' folder in the CD root.
This was solved with that trick : the files of 'mms' services always placed inside the 'Program Files' folder
and in VistaPE it means always placed inside the .wim
Edit:
sorry
now i can see in VistaPE also there is an option "Direct from CD/DVD"
just never used it
the strange is that in LiveXP the program works fine using a plain .iso,
i mean using no writable %SystemDrive% or no writable Program Files folder,
and works also if BootSDI used
#12
Posted 17 September 2009 - 05:02 PM
but noticed
the prog can work only in that case
if in the 'Configuration' script (\Projects\Win7RescuePE\config.script)
'Build model: In RAM (boot.wim)' option selected,
if 'Build model: Normal' option used then the prog. doesn't work at all (seems doesn't get the lic in the running Win7RescuePE)
Any idea why does it happen or how should to solve this problem?
I have made a newer test not using the .wim
and strangely now the program works.
Seems this problem depends on the used Acronis version,
i mean using newer software version it works
using the older version it doesn't work.
Anyone has similar experience?
#13
Posted 19 September 2009 - 08:10 AM
updated to version=4
#14
Posted 01 October 2009 - 09:58 AM
I have tested your V4.
The application is starting fine. Bu you cannot Backup/Restore to a mapped network drive.
The same test with True Image Workstation 9.1 and True Image Workstation Echo is working fine.
Xplod
#17
Posted 02 October 2009 - 07:02 AM
starting the app. with 'TrueImage.exe' is the Solution.
Maybee you can change this in your script.
xplod
#18
Posted 02 October 2009 - 07:18 AM
#19
Posted 02 October 2009 - 07:23 AM
but that winpe_iso.exe always will place the prog inside 'Program Files' inside the .wim
(its size is more than ~130MB)
(and at me this script works in LiveXP project, too)
#20
Posted 02 October 2009 - 07:40 AM
(e.g. to remove:
bootwiz.bin
bootmenu.exe
kernel.dat
ramdisk.dat
BootAgentActiveRestoreDos.run
hddhook.com
mouse.com
f11.cfg)
#21
Posted 20 December 2009 - 11:35 PM
Ken
#22
Posted 02 March 2011 - 11:36 PM
Anyone any ideas?
Doda
#23
Posted 03 March 2011 - 07:48 AM
newer script:
AcronisBackupAndRecovery10_v6.7z 3.49KB 880 downloads
Note:
in the script interface in the "Path to BartPE files:" input field
as default folder the "C:\Program Files\Acronis\BootableComponents\WinPE\Files" mentioned,
it is valid only for older B&R 10 builds
in newer B&R 10 builds the needed files reside in 'C:\Program Files\Acronis\BootableComponents\WinPE\WinPE.zip',
so first should extract these files manually from 'WinPE.zip\Files' to a folder e.g. to '%ScriptDir%\Files' then in the script interface should point to this folder in the "Path to BartPE files:" input field
#24
Posted 21 March 2011 - 06:35 PM
#25
Posted 22 March 2011 - 08:28 PM
as you did not mention any detail about the prblemUnfortunately the script not working on the latest build 12708.
and seeing your topic
can i suppose that the promlem is not 'the script not working on the latest build 12708' but rather 'the script not working in x64 based PE'?
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users