Salta al contenuto principale

TIH 2012 - BartPE acronis.inf Error

Thread needs solution

Line 63 in the [SetupReg.AddReg] section of the acronis.inf file is NOT correct.

0x4, "ControlSet001\Services\fltsrv", "Group", "PnP Filter"
should be
0x1, "ControlSet001\Services\fltsrv", "Group", "PnP Filter"

Attempting to use 0x4 (dword) for adding a registry string will result in a fatal error. The same would apply to any such usage in other WinPE builds such as WinBuilder scripts.

0 Users found this helpful

Hello Richard,

Thank you for reporting about the issue, I really appreciate it.

I have forwarded this information to the Development team, hopefully we'll get an update on this tomorrow. I'll keep you posted.

Thank you.

You're entirely welcome.

It sure would help us WinPE builders if you could also persuade them to make the Acronis executables capable of handling 0x2 (REG_EXPAND_SZ) registry entries so that the location of common component files can be specified with environment variables such as %SystemDrive% for example. In fact, that's a very basic capability for almost all applications these days and I'd think it would avoid a lot of problems for your developers themselves.

Dear Richard,

Thank you for reporting this issue. You are indeed right - developers confirmed the value is incorrect - this will be fixed in the next official update for Acronis True Image Home 2012.

Once again, thank you for pointing this out. We appreciate your help.

--
Best regards,
Ahmad Ibrahimov
Expert Team Manager | Forum Team Manager
Acronis Customer Central

Does this not imply that this process has never even be tested with this release? What, pray tell, do you test?

OK, is this a TI 2012 issue only, or a TI/WinPE issue in general??

As a TI2010 user, and just starting to play with PE, this is an attention getter!! Ahmad Ibrahimov said in post #3 "this will be fixed in the next official update for Acronis True Image Home 2012." Does this mean that 2012 will be required for any PE use, or are earlier TI versions not affected?
... Bob ..

Robert,

It is a BartPE issue only, for someone using WAIK there shouldn't be a problem. BartPE is for XP users, but the script can also be used by those who use WinBuilder another 3rd party PE builder program.

As Colin has said, the issue relates to the BartPE addon. More specifically, it is an error in the BartPE acronis.inf file that is included in the TIH 2012 Plus Pack. In fact, for previous TIH versions, it was also available as a free download, but that "freebie" option appears to have been withdrawn for this version.

However, the same error would also apply to any other Windows PE build that might use that same pattern for installing its drivers and filters. Under those circumstances, therefore, the issue becomes more general and would thus extend beyond just those PE builds that use Windows XP as the source to include both 64-bit and 32-bit versions of Vista and Windows 7.

For the benefit of those many multi-purpose WinPE builders and "rescue disk" users who may be interested, here are a couple of other points to keep in mind:

1) TIH 2012 uses a new and different registry [CurrentControlSet] set-up for its drivers and filters. In particular, the UpperFilters entries for Class\{4D36E967-E325-11CE-BFC1-08002BE10318} and Class\{71A27CDD-812A-11D0-BEC7-08002BE2092F} are now "fltsrv" instead of "snapman" and the fltsrv service needs to be added accordingly. That new arrangement is backward compatibile with some other Acronis apps (e.g., DiskDirector 2011) but not vice versa. So you'll need to ensure that it takes precedence over any previous Acronis utility inclusions in your PE builds.

2) For creating a 64-bit WinPE build, you need to use the version-matched fltsrv.sys, snapman.sys and snapapi.dll files from an existing full TIH 2012 installation under an actual x64 Windows OS. The 32-bit files that are included in the Acronis Plus Pack won't work, of course.

The "tricky" part for any WinPE scripting is accommodating both x86 and x64 builds which requires some reorganization of the Plus Pack to add those 64-bit fltsrv.sys, snapman.sys and snapapi.dll files. And, for x64, snapapi.dll needs to be copied to the "%target_win%\SysWOW64\" folder instead of the "%target_sys%\" folder. The relevant ControlSet001 entries are then handled (including the above-mentioned correction to the fltsrv Group entry) as follows:

Hive_Load,HKLM
reg_add,0x7,"%reg%\ControlSet001\Control\Class\{4D36E967-E325-11CE-BFC1-08002BE10318}","UpperFilters","fltsrv"
reg_add,0x7,"%reg%\ControlSet001\Control\Class\{71A27CDD-812A-11D0-BEC7-08002BE2092F}","UpperFilters","fltsrv"
reg_add,0x1,"%reg%\ControlSet001\Services\fltsrv","DisplayName","Acronis Storage Filter"
reg_add,0x2,"%reg%\ControlSet001\Services\fltsrv","ImagePath","system32\drivers\fltsrv.sys"
reg_add,0x4,"%reg%\ControlSet001\Services\fltsrv","ErrorControl","1"
reg_add,0x1,"%reg%\ControlSet001\Services\fltsrv","Group","PnP Filter"
reg_add,0x4,"%reg%\ControlSet001\Services\fltsrv","Type","1"
reg_add,0x4,"%reg%\ControlSet001\Services\fltsrv","Tag","8"
reg_add,0x4,"%reg%\ControlSet001\Services\fltsrv","Start","0"
If,Not,%SourceArch%,Equal,x86,reg_add,0x4,"%reg%\ControlSet001\Services\fltsrv","WOW64","1"
reg_add,0x1,"%reg%\ControlSet001\Services\snapman","DisplayName","Acronis Snapshots Manager"
reg_add,0x2,"%reg%\ControlSet001\Services\snapman","ImagePath","system32\drivers\snapman.sys"
reg_add,0x4,"%reg%\ControlSet001\Services\snapman","ErrorControl","1"
reg_add,0x4,"%reg%\ControlSet001\Services\snapman","Type","1"
reg_add,0x4,"%reg%\ControlSet001\Services\snapman","Start","0"
If,Not,%SourceArch%,Equal,x86,reg_add,0x4,"%reg%\ControlSet001\Services\snapman","WOW64","1"
Hive_Unload,HKLM

Note in particular the "WOW64" entries for for x64 builds.

Hi this is my 1st. post here i have ran ti2009, ti2010 error free since 2009-2010, i upgraded to TI 2011 it installed okay but i liked TI 2010 better, i upgrade again when TI 2012 was released the other day and I can not get TI 2012 to install i have done a Fresh install, i have did uninstalls of older ver. but everytime i try to install TI 2012 it freezes up my mouse and locks up my system WinXP. when i reboot sometimes i get a Snapman error other times nothing i'm 72 and not sure i will be around long enough to figure this out on my own, so please feel free to make suggestions for the time beinging i will run TI 2010 i love it but just wanted to stay current with my software
also i have ran %Temp% to clean my Temp files Help

thx in advance

First suggestion would be to start your own topic here rather than appending to this one. That's not meant to be snarky, but you're more likely to get more relevant help that way as your issue doesn't appear to be related in any way to this thread.

The most likely reason for a snapman error would be some problem with the driver/filter entries made during the TIH 2012 installation process. A "clean" install (i.e., completely removing all previous versions first) is usually the best way to avoid such issues. If possible, restore to your prior state, and try again.

@nomoney,

I'll just say here, run the 2011 Acronis cleaner and then try re-installing. The cleaner can be downloaded from here

Richard Virtue wrote:
TIH 2012 uses a new and different registry [CurrentControlSet] set-up for its drivers and filters. In particular, the UpperFilters entries for Class\{4D36E967-E325-11CE-BFC1-08002BE10318} and Class\{71A27CDD-812A-11D0-BEC7-08002BE2092F} are now "fltsrv" instead of "snapman" and the fltsrv service needs to be added accordingly.

Richard I wish only to express my thanks to you for making this post, which I first found from you on another forum (that I don't belong to).

I've been comparing registry entries between my (older) ATIH2010 installation and my new ATIH2011NE (Netbook Edition) and the NE has the fltsrv entries but not snapman. Completely threw me for a loop (I'm tshooting an issue with my netbook). Anyway thanks to you I see these entries are not faulty!

Glad that you found it helpful. Perhaps the difference (fltsrv + snapman vs fltsrv only) might be due, at least in part, to backward support for Disk Director installations. Apparently the most recent DD version currently available (DD 2011) does appear to need snapman.sys (as well as fltsrv.sys?) in order to function properly. Not sure about TIH2012 alone. Since all of my WinPE builds included both apps, I haven't actually tried TIH myself with fltsrv.sys only.

Richard
I have a need to insert the 2012 TI into a x64 winre boot.wim.

Richard Virtue wrote:

2) For creating a 64-bit WinPE build, you need to use the version-matched fltsrv.sys, snapman.sys and snapapi.dll files from an existing full TIH 2012 installation under an actual x64 Windows OS. The 32-bit files that are included in the Acronis Plus Pack won't work, of course.

The "tricky" part for any WinPE scripting is accommodating both x86 and x64 builds which requires some reorganization of the Plus Pack to add those 64-bit fltsrv.sys, snapman.sys and snapapi.dll files. And, for x64, snapapi.dll needs to be copied to the "%target_win%\SysWOW64\" folder instead of the "%target_sys%\" folder. The relevant ControlSet001 entries are then handled (including the above-mentioned correction to the fltsrv Group entry) as follows:

Hive_Load,HKLM
reg_add,0x7,"%reg%\ControlSet001\Control\Class\{4D36E967-E325-11CE-BFC1-08002BE10318}","UpperFilters","fltsrv"
reg_add,0x7,"%reg%\ControlSet001\Control\Class\{71A27CDD-812A-11D0-BEC7-08002BE2092F}","UpperFilters","fltsrv"
reg_add,0x1,"%reg%\ControlSet001\Services\fltsrv","DisplayName","Acronis Storage Filter"
reg_add,0x2,"%reg%\ControlSet001\Services\fltsrv","ImagePath","system32\drivers\fltsrv.sys"
reg_add,0x4,"%reg%\ControlSet001\Services\fltsrv","ErrorControl","1"
reg_add,0x1,"%reg%\ControlSet001\Services\fltsrv","Group","PnP Filter"
reg_add,0x4,"%reg%\ControlSet001\Services\fltsrv","Type","1"
reg_add,0x4,"%reg%\ControlSet001\Services\fltsrv","Tag","8"
reg_add,0x4,"%reg%\ControlSet001\Services\fltsrv","Start","0"
If,Not,%SourceArch%,Equal,x86,reg_add,0x4,"%reg%\ControlSet001\Services\fltsrv","WOW64","1"
reg_add,0x1,"%reg%\ControlSet001\Services\snapman","DisplayName","Acronis Snapshots Manager"
reg_add,0x2,"%reg%\ControlSet001\Services\snapman","ImagePath","system32\drivers\snapman.sys"
reg_add,0x4,"%reg%\ControlSet001\Services\snapman","ErrorControl","1"
reg_add,0x4,"%reg%\ControlSet001\Services\snapman","Type","1"
reg_add,0x4,"%reg%\ControlSet001\Services\snapman","Start","0"
If,Not,%SourceArch%,Equal,x86,reg_add,0x4,"%reg%\ControlSet001\Services\snapman","WOW64","1"
Hive_Unload,HKLM

Note in particular the "WOW64" entries for for x64 builds.

I have used and moved the 3 files mentioned above to their places as you indicated on a mounted wim.
Prior to this I used the 2012 Plus Pack WinPE ISO Builder after replacing the equivalent registry entry in the BartPE acronis.inf file with yours:

[SetupReg.AddReg]
0x7, "ControlSet001\Control\Class\{4D36E967-E325-11CE-BFC1-08002BE10318}","UpperFilters","fltsrv"
0x7, "ControlSet001\Control\Class\{71A27CDD-812A-11D0-BEC7-08002BE2092F}", "UpperFilters", "fltsrv"
0x1, "ControlSet001\Services\fltsrv","DisplayName","Acronis Storage Filter"
0x2, "ControlSet001\Services\fltsrv", "ImagePath", "system32\DRIVERS\fltsrv.sys"
0x4, "ControlSet001\Services\fltsrv","ErrorControl","1"
0x1, "ControlSet001\Services\fltsrv", "Group", "PnP Filter"
0x4, "ControlSet001\Services\fltsrv","Type","1"
0x4, "ControlSet001\Services\fltsrv","Tag","8"
0x4, "ControlSet001\Services\fltsrv","Start","0"
0x4, "ControlSet001\Services\fltsrv","WOW64","1"
0x1, "ControlSet001\Services\snapman","DisplayName","Acronis Snapshots Manager"
0x2, "ControlSet001\Services\snapman", "ImagePath", "system32\DRIVERS\snapman.sys"
0x4, "ControlSet001\Services\snapman","ErrorControl","1"
0x4, "trolSet001\Services\snapman","Type","1"
0x4, "ControlSet001\Services\snapman","Start","0"
0x4, "ControlSet001\Services\snapman","WOW64","1"

The x64 boot.win boots but when I try to run TI I get an error message saying something similar to "subsystem is missing". Is there something I have missed, is there more to add or am I completely on the wrong track? Thanks.
,

Sorry. I should have made it clear that those [SetupReg.AddReg] specs were written for use with WinBuilder scripts. If you are you creating your .WIM file manually or in some other way, the method for creating those registry entries will need to be adjusted accordingly.

See http://reboot.pro/ for additional info on the WinBuilder WinPE scripting utility and my posting there at http://reboot.pro/15323/ .