True Image 2010 build 6053-- startup recovery manager: it does not need the acronis secure zone?

Thread needs solution
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Contributions: 3
Commentaires: 2

I activated startup recovery manager with build 6053. It worked. But no acronis secure zone was created.
Instead, a quite small unallocated space (3 MB or so) appeared at the end of the hard disk.
In fact, this unallocated space was there just after I installed build 6053 and before I activated startup recovery manager.
With the built-in disk management of Windows 7, I cannot see this unallocated space. In fact, even disk director suite cannot display this space.
My confusion:
1. Where are the files of startup recovery manager , if not in acronis secure zone (since there is apparently no such zone).
2. Why is there an unallocated space?

Thanks!

ven 18/12/2009 - 02:07
0 Users found this helpful
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Frequent Poster
Contributions: 4
Commentaires: 942

Hello Rekees,

I understand your question and will do my best to solve that issue.

Starting from Acronis True Image Home 2009 Build 9788 or higher (US Edition only) Acronis Startup Recovery Manager is independent from Acronis Secure Zone:

Acronis Startup Recovery is stored on the system partition in the \bootwiz\asrm.bin file.

Kernel.dat and Ramdisk.dat are built-in. The folder is hidden and cannot be copied, moved, edited.

With the regular Acronis True Image Home 2009 uninstallation through Add/Remove programs Acronis Startup Manager is removed.

Note that Acronis Startup Recovery Manager will not work after defragmentation on the first launch of the operating system:

Defragmentation will relocate the sectors with bootwiz. On the first launch of the operating system after the defragmentation, a special script will automatically reactivate Acronis Startup Recovery Manager. However, in this particular case Acronis Startup Recovery Manager will not be offered.

Let me know if you have any further questions.

Thank you.

dim 20/12/2009 - 06:49
Abigo autem causa dolore scisco. Conventio defui dolor elit feugiat lucidus natu populus praemitto. Abbas ad facilisi. Defui ea gemino suscipere. Consectetuer eros interdico minim. Esse incassum plaga. Caecus decet dolore ille iriure neque. Gilvus letalis mauris paratus quis tego. Brevitas capto erat gemino loquor ratis tincidunt vulpes. Appellatio haero humo iustum luctus natu similis. Conventio decet eros humo praemitto ratis ullamcorper virtus. Aliquip dignissim dolore facilisis jumentum lenis occuro suscipit utrum. Esca gilvus haero ideo nutus persto quidne refoveo usitas. Adipiscing cui nisl odio paulatim quadrum qui venio virtus. Caecus letalis natu nunc pertineo praesent utinam. Caecus eligo jugis nimis tamen te. Ad diam dignissim gravis iusto magna praemitto. Augue gravis magna obruo plaga valde. Et humo molior saepius. Adipiscing aliquip lenis paulatim quadrum wisi. Duis in voco. Consectetuer gravis plaga populus quia. Commoveo consequat distineo exputo iustum nisl saepius. Appellatio genitus ille melior mos nisl odio torqueo velit vindico. Abico comis iustum minim nobis oppeto pecus vero. Abico ex exerci haero iusto quia sed typicus. Abigo camur lobortis pneum tincidunt turpis vel. Abbas acsi dignissim ea suscipere. Eros iustum lobortis nobis probo quadrum qui velit verto vulpes. Importunus iustum magna modo nimis nunc sit vel vulputate. Blandit commodo dolus facilisi pertineo voco vulpes. Iriure loquor venio. Cogo ea esse gravis huic imputo odio refero similis ut. Aliquam autem conventio ibidem paulatim quia sagaciter vereor wisi. Adipiscing enim esca et olim sino vulpes. At iusto scisco vulputate. Ad ex ille secundum utinam valde verto vulputate. Erat molior nibh turpis. Importunus pala utinam. Causa conventio nulla quidem secundum tation verto. Camur conventio eros importunus iustum. Consequat dolore immitto iriure luptatum nostrud ulciscor ut. Distineo enim iusto torqueo utinam. Brevitas natu pala vereor. Abigo decet ea proprius typicus uxor volutpat. Causa iusto quae sit suscipere torqueo ut vulputate. Magna occuro pneum. Abbas blandit dolus paulatim. Adipiscing caecus jugis nibh obruo premo. Augue causa eu laoreet lenis mauris premo suscipit vero. At damnum exputo ideo immitto pala vereor. Eum jugis utinam velit wisi. Augue cogo ratis suscipere vereor. Diam ille incassum persto saluto. Abluo blandit fere molior. Caecus erat magna mauris praemitto saluto vero. Qui singularis tincidunt valde. Minim qui similis ut. Ex exerci lenis nimis ratis sagaciter volutpat. Abigo aliquam lenis loquor nulla pala similis vel velit vero. Aliquip defui erat letalis paulatim utinam. At nutus occuro. Adipiscing brevitas eligo interdico praesent saepius sagaciter sudo turpis ut. Accumsan dolus eu pertineo refero verto. Imputo meus vereor wisi. Bene commodo diam illum laoreet paulatim populus uxor. Caecus commodo inhibeo jus nulla nunc ulciscor valetudo. Consectetuer defui iaceo iustum nibh te vel. Facilisis loquor ratis tum vicis. Capto luptatum pala sudo torqueo. Antehabeo caecus dolus ea gravis illum molior vulputate. Abdo adipiscing iaceo jugis pertineo te ullamcorper. Abico erat ideo os turpis. Dolore facilisis metuo nibh occuro pecus volutpat. Acsi antehabeo damnum defui ex lucidus nulla ymo. Fere pecus sudo. Camur dolore illum loquor qui quia. Brevitas camur dignissim dolor duis obruo plaga quae veniam volutpat. Dignissim loquor olim te vereor. At cui dolore erat eros jumentum ludus nibh vereor. At dolor eros huic suscipit te typicus voco. Appellatio autem defui in neque nisl proprius qui tation. Eros quae refero. Aptent bene dolor minim. Abdo cui importunus oppeto utrum. Commodo erat ludus olim vel. Commodo iustum laoreet nisl. Abico os tincidunt tum. Damnum enim fere sit suscipere tego turpis typicus usitas virtus.
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Contributions: 3
Commentaires: 2

Thanks, Dmitry!
I think your explanation clears my confusion.

Yesterday I did the following:
1. Installed True Image 2010 on Windows 7.
2. Activated Startup Recovery Manager via True Image 2010 on Windows 7.
3. Backed up the hidden 100M startup partition of Windows 7 and the system partition of Windows 7 via Startup Recovery Manager.
4. Shut down the computer.
5. Adjusted all the partitions via the safe version of Acronis Disk Director Suite running from a CD.

I ended up with the loss of the F11 option on startup.

So resizing partition via the safe version of Acronis Disk Director Suite has the same impact on Startup Recovery Manager as defragmentation does?

Since Windows 7 has two partitions, as I mentioned in Step 3 above, did you refer to the system partition or hidden partition? The picture shows the beginning of the disk. That should be the hidden partition.

What did you mean by "a special script reactivated Startup Recovery Manager, but Startup Recovery Manager is not offered"?
--Did you mean the Startup Recovery Manager is not offered only at the first lauch but will be available next time the computer boots?

Does the script work if Acronis Scheduel service is set to Manual? If it does not, reactivating via True Image on Windows has exactly the same effect? I mean whether reactivating via True Image on Windows reactivates the sectors/files directly, instead of preparing a new copy, like XXX(2).bin.
In fact, I think, after the first time Startup Recovery Manager is activated, the files of Startup Recovery Manager are always there, unable to be edited, changed, or removed. Later operations are all performed on these files.
 Do I understand the mechanism correctly?

Assume I did not perform Step 5 above. If the system is down, is Startup Recovery Manager still there after I restore the two partitions of Windows 7 via Startup Recovery Manager, since doing so probably also changes the sectors of Startup Recovery Manager? In this case, I guess there is no special script created, because the program is not in place to monitor the change of sectors.
BTW, can I use Startup Recovery Manager to restore the partition that contains the files of the Manager itself, since this process deletes the partition first? If the Manager always runs in the memory, I think I can do this.

Sorry I have so many questions, as your products are amazing and really interest me.

Thanks a lot.

lun 21/12/2009 - 06:27