DriveImageXML script

In the XP Project is a Script for DriveImageXMl. There are registry entries.Are they needed, because it isn't working. The apphelp.dll is missing.

[Main]
Title=DriveImage XML
Type=script
Level=5
Description=DriveImage XML is an easy to use and reliable program for imaging and backing up partitions and logical drives.
Locked=True
Selected=True
Author=Boot Land Community
Date=2007-01-12
Contact=http://boot-land.net
Version=003
Credits=Runtime Software for releasing DriveImage XML as freeware - Thanks!
Upload=2007-May-04 17:52:34
Updates=http://beta.boot-land.net
Download_Level=2

[Interface]
pCheckBox1="Add shortcut on Desktop",1,3,38,53,164,18,False

[variables]
%ProgramTitle%=DriveImage XML
%ProgramEXE%=dixml.exe
%ProgramFolder%=DriveImageXML

[process]
If,%pCheckBox1%,Equal,True,Add_Shortcut,Desktop
Add_Shortcut,StartMenu
unpack
echo,"Expanding DLLs..."
require_file,APPHELP.DLL
require_file,LZ32.DLL
require_file,WOW32.DLL
require_file,NTVDM.EXE
hive_load,HKU
reg_add,0x1,"%reg%\Microsoft\Windows NT\CurrentVersion\Fonts","MS Sans Serif 8,10,12,14,18,24 (VGA res)","SSERIFE.FON"
reg_add,0x1,"%reg%\Microsoft\Windows NT\CurrentVersion\Fonts","MS Serif 8,10,12,14,18,24 (VGA res)","SERIFE.FON"
reg_add,0x1,"%reg%\Microsoft\Windows NT\CurrentVersion\Fonts","Small Fonts (VGA res)","SMALLE.FON"
reg_add,0x1,"%reg%\Classes\CLSID\{43A8F463-4222-11d2-B641-006097DF5BD4}","","Shell Name Space ListView"
reg_add,0x2,"%reg%\Classes\CLSID\{43A8F463-4222-11d2-B641-006097DF5BD4}\InProcServer32","","%SystemRoot%\System32\shdocvw.dll"
reg_add,0x1,"%reg%\Classes\CLSID\{43A8F463-4222-11d2-B641-006097DF5BD4}\InProcServer32","ThreadingModel","Apartment"
reg_add,0x1,"%reg%\Classes\CLSID\{603D3800-BD81-11d0-A3A5-00C04FD706EC}","","Background Task Scheduler"
reg_add,0x2,"%reg%\Classes\CLSID\{603D3800-BD81-11d0-A3A5-00C04FD706EC}\InProcServer32","","%SystemRoot%\System32\browseui.dll"
reg_add,0x1,"%reg%\Classes\CLSID\{603D3800-BD81-11d0-A3A5-00C04FD706EC}\InProcServer32","ThreadingModel","Apartment"
reg_add,0x1,"%reg%\Classes\CLSID\{13709620-C279-11CE-A49E-444553540000}","","Shell Automation Service"
reg_add,0x2,"%reg%\Classes\CLSID\{13709620-C279-11CE-A49E-444553540000}\InProcServer32","","%SystemRoot%\system32\SHELL32.dll"
reg_add,0x1,"%reg%\Classes\CLSID\{13709620-C279-11CE-A49E-444553540000}\InProcServer32","ThreadingModel","Apartment"
reg_add,0x1,"%reg%\Classes\CLSID\{13709620-C279-11CE-A49E-444553540000}\ProgID","","Shell.Application.1"
reg_add,0x1,"%reg%\Classes\CLSID\{13709620-C279-11CE-A49E-444553540000}\TypeLib","","{50a7e9b0-70ef-11d1-b75a-00a0c90564fe}"
reg_add,0x1,"%reg%\Classes\CLSID\{13709620-C279-11CE-A49E-444553540000}\Version","","1.1"
reg_add,0x1,"%reg%\Classes\CLSID\{13709620-C279-11CE-A49E-444553540000}\VersionIndependentProgID","","Shell.Application"
reg_add,0x1,"%reg%\Classes\Shell.Application","","Shell Automation Service"
reg_add,0x1,"%reg%\Classes\Shell.Application\CLSID","","{13709620-C279-11CE-A49E-444553540000}"
reg_add,0x1,"%reg%\Classes\Shell.Application\CurVer","","Shell.Application.1"
reg_add,0x1,"%reg%\Classes\Shell.Application.1","","Shell Automation Service"
reg_add,0x1,"%reg%\Classes\Shell.Application.1\CLSID","","{13709620-C279-11CE-A49E-444553540000}"
hive_unload,HKU

Well, the enclosed was working as well as any last time I looked. It probably copies some unneeded files, I've been trying all sorts of stuff trying to get VSS working.

 DriveImageXML.7z   1.28MB   1898 downloads

VSS service requires the following:

CopyOrExpand,%source_win%\vssvc.exe,%target_sys%

CopyOrExpand,%source_win%\vssapi.dll,%target_sys%

CopyOrExpand,%source_win%\SWPRV.DLL,%target_sys%

RegHiveLoad,Tmp_software,%TargetDir%\i386\System32\Config\software

RegWrite,HKLM,0x1,"Tmp_software\Classes\CLSID\{65EE1DBA-8FF4-4a58-AC1C-3470EE2F376A}","","VSSoftwareProvider Class"

RegWrite,HKLM,0x1,"Tmp_software\Classes\CLSID\{65EE1DBA-8FF4-4a58-AC1C-3470EE2F376A}\InprocServer32","ThreadingModel","Both"

RegWrite,HKLM,0x2,"Tmp_software\Classes\CLSID\{65EE1DBA-8FF4-4a58-AC1C-3470EE2F376A}\InprocServer32","","swprv.dll"

RegWrite,HKLM,0x1,"Tmp_software\Classes\CLSID\{65EE1DBA-8FF4-4a58-AC1C-3470EE2F376A}\ProgID","","VSSW.VSSoftwareProvider.1"

RegWrite,HKLM,0x1,"Tmp_software\Classes\CLSID\{65EE1DBA-8FF4-4a58-AC1C-3470EE2F376A}\TypeLib","","{93BB06B6-B6DA-43c8-BC9B-E32DB49AA6F7}"

RegWrite,HKLM,0x1,"Tmp_software\Classes\CLSID\{65EE1DBA-8FF4-4a58-AC1C-3470EE2F376A}\VersionIndependentProgID","","VSSW.VSSoftwareProvider"

RegWrite,HKLM,0x1,"Tmp_software\Classes\TypeLib\{93BB06B6-B6DA-43C8-BC9B-E32DB49AA6F7}\1.0","","Software Shadow Copy provider 1.0 Type Library"

RegWrite,HKLM,0x2,"Tmp_software\Classes\TypeLib\{93BB06B6-B6DA-43C8-BC9B-E32DB49AA6F7}\1.0\0\win32","","swprv.dll"

RegWrite,HKLM,0x1,"Tmp_software\Classes\TypeLib\{93BB06B6-B6DA-43C8-BC9B-E32DB49AA6F7}\1.0\FLAGS","","0"

RegWrite,HKLM,0x2,"Tmp_software\Classes\TypeLib\{93BB06B6-B6DA-43C8-BC9B-E32DB49AA6F7}\1.0\HELPDIR","","%SystemRoot%\Help"

RegWrite,HKLM,0x1,"Tmp_software\Classes\VSSW.VSSoftwareProvider","","VSSoftwareProvider Class"

RegWrite,HKLM,0x1,"Tmp_software\Classes\VSSW.VSSoftwareProvider.1","","VSSoftwareProvider Class"

RegWrite,HKLM,0x1,"Tmp_software\Classes\VSSW.VSSoftwareProvider.1\CLSID","","{65EE1DBA-8FF4-4a58-AC1C-3470EE2F376A}"

RegWrite,HKLM,0x1,"Tmp_software\Classes\VSSW.VSSoftwareProvider\CLSID","","{65EE1DBA-8FF4-4a58-AC1C-3470EE2F376A}"

RegWrite,HKLM,0x1,"Tmp_software\Classes\VSSW.VSSoftwareProvider\CurVer","","VSSW.VSSoftwareProvider.1"

RegWrite,HKLM,0x1,"Tmp_software\Classes\CLSID\{72970BEB-81F8-46D4-B220-D743F4E49C95}","","Volume Shadow Copy WMI Provider"

RegWrite,HKLM,0x2,"Tmp_software\Classes\CLSID\{72970BEB-81F8-46D4-B220-D743F4E49C95}\InprocServer32","","vsswmi.dll"

RegWrite,HKLM,0x1,"Tmp_software\Classes\CLSID\{72970BEB-81F8-46D4-B220-D743F4E49C95}\InprocServer32","ThreadingModel","Both"

RegHiveUnLoad,Tmp_software

RegHiveLoad,Tmp_setupreg_hiv,%TargetDir%\i386\System32\setupreg.hiv

RegWrite,HKLM,0x4,"Tmp_setupreg_hiv\ControlSet001\Services\VSS\Providers\{b5946137-7b9f-4925-af80-51abd60b20d5}","Type","1"

RegWrite,HKLM,0x1,"Tmp_setupreg_hiv\ControlSet001\Services\VSS\Providers\{b5946137-7b9f-4925-af80-51abd60b20d5}","Version","1.0.0.7"

RegWrite,HKLM,0x1,"Tmp_setupreg_hiv\ControlSet001\Services\VSS\Providers\{b5946137-7b9f-4925-af80-51abd60b20d5}","VersionId","{00000001-0000-0000-0007-000000000001}"

RegWrite,HKLM,0x1,"Tmp_setupreg_hiv\ControlSet001\Services\VSS\Providers\{b5946137-7b9f-4925-af80-51abd60b20d5}","","MS Software Shadow Copy provider 1.0"

RegWrite,HKLM,0x1,"Tmp_setupreg_hiv\ControlSet001\Services\VSS\Providers\{b5946137-7b9f-4925-af80-51abd60b20d5}\CLSID","","{65EE1DBA-8FF4-4a58-AC1C-3470EE2F376A}"

RegWrite,HKLM,0x4,"Tmp_setupreg_hiv\ControlSet001\Services\Eventlog\Application\VSS","TypesSupported","7"

RegWrite,HKLM,0x2,"Tmp_setupreg_hiv\ControlSet001\Services\Eventlog\Application\VSS","EventMessageFile","%SystemRoot%\System32\vssvc.exe"

RegHiveUnLoad,Tmp_setupreg_hiv

regards,
Galapo.

Sorry, I forgot to say, that I want to use DriveImage XML in VistaPe.

JonF I tested your script in VistaPE, but wow32 and some other files were missing.
I added them.
Now I can open DriveImage XML.

I can open DIX, but then mistakes.
If I want to Backup a partition a mistake and if I want to restore I need Admin Rights.
What can I do?

Now the UAC Restoring mistake is away.
But the Backup mistake is there still.
How can I make vss work?

Galapo: Your lines above are for XP Project, aren't they?
What can I do, in order to make them work in VistaPE?

Galapo: Your lines above are for XP Project, aren't they?
What can I do, in order to make them work in VistaPE?

Try this:

require_file,vssvc.exe

require_file,vssapi.dll

require_file,SWPRV.DLL

Hive_Load,HKU

reg_add,0x1,"%reg%\Classes\CLSID\{65EE1DBA-8FF4-4a58-AC1C-3470EE2F376A}","","VSSoftwareProvider Class"

reg_add,0x1,"%reg%\Classes\CLSID\{65EE1DBA-8FF4-4a58-AC1C-3470EE2F376A}\InprocServer32","ThreadingModel","Both"

reg_add,0x2,"%reg%\Classes\CLSID\{65EE1DBA-8FF4-4a58-AC1C-3470EE2F376A}\InprocServer32","","swprv.dll"

reg_add,0x1,"%reg%\Classes\CLSID\{65EE1DBA-8FF4-4a58-AC1C-3470EE2F376A}\ProgID","","VSSW.VSSoftwareProvider.1"

reg_add,0x1,"%reg%\Classes\CLSID\{65EE1DBA-8FF4-4a58-AC1C-3470EE2F376A}\TypeLib","","{93BB06B6-B6DA-43c8-BC9B-E32DB49AA6F7}"

reg_add,0x1,"%reg%\Classes\CLSID\{65EE1DBA-8FF4-4a58-AC1C-3470EE2F376A}\VersionIndependentProgID","","VSSW.VSSoftwareProvider"

reg_add,0x1,"%reg%\Classes\TypeLib\{93BB06B6-B6DA-43C8-BC9B-E32DB49AA6F7}\1.0","","Software Shadow Copy provider 1.0 Type Library"

reg_add,0x2,"%reg%\Classes\TypeLib\{93BB06B6-B6DA-43C8-BC9B-E32DB49AA6F7}\1.0\0\win32","","swprv.dll"

reg_add,0x1,"%reg%\Classes\TypeLib\{93BB06B6-B6DA-43C8-BC9B-E32DB49AA6F7}\1.0\FLAGS","","0"

reg_add,0x2,"%reg%\Classes\TypeLib\{93BB06B6-B6DA-43C8-BC9B-E32DB49AA6F7}\1.0\HELPDIR","","#$pSystemRoot#$p\Help"

reg_add,0x1,"%reg%\Classes\VSSW.VSSoftwareProvider","","VSSoftwareProvider Class"

reg_add,0x1,"%reg%\Classes\VSSW.VSSoftwareProvider.1","","VSSoftwareProvider Class"

reg_add,0x1,"%reg%\Classes\VSSW.VSSoftwareProvider.1\CLSID","","{65EE1DBA-8FF4-4a58-AC1C-3470EE2F376A}"

reg_add,0x1,"%reg%\Classes\VSSW.VSSoftwareProvider\CLSID","","{65EE1DBA-8FF4-4a58-AC1C-3470EE2F376A}"

reg_add,0x1,"%reg%\Classes\VSSW.VSSoftwareProvider\CurVer","","VSSW.VSSoftwareProvider.1"

reg_add,0x1,"%reg%\Classes\CLSID\{72970BEB-81F8-46D4-B220-D743F4E49C95}","","Volume Shadow Copy WMI Provider"

reg_add,0x2,"%reg%\Classes\CLSID\{72970BEB-81F8-46D4-B220-D743F4E49C95}\InprocServer32","","vsswmi.dll"

reg_add,0x1,"%reg%\Classes\CLSID\{72970BEB-81F8-46D4-B220-D743F4E49C95}\InprocServer32","ThreadingModel","Both"

Hive_Unload,HKU

Hive_Load,HKLM

reg_add,0x4,"%reg%\ControlSet001\Services\VSS\Providers\{b5946137-7b9f-4925-af80-51abd60b20d5}","Type","1"

reg_add,0x1,"%reg%\ControlSet001\Services\VSS\Providers\{b5946137-7b9f-4925-af80-51abd60b20d5}","Version","1.0.0.7"

reg_add,0x1,"%reg%\ControlSet001\Services\VSS\Providers\{b5946137-7b9f-4925-af80-51abd60b20d5}","VersionId","{00000001-0000-0000-0007-000000000001}"

reg_add,0x1,"%reg%\ControlSet001\Services\VSS\Providers\{b5946137-7b9f-4925-af80-51abd60b20d5}","","MS Software Shadow Copy provider 1.0"

reg_add,0x1,"%reg%\ControlSet001\Services\VSS\Providers\{b5946137-7b9f-4925-af80-51abd60b20d5}\CLSID","","{65EE1DBA-8FF4-4a58-AC1C-3470EE2F376A}"

reg_add,0x4,"%reg%\ControlSet001\Services\Eventlog\Application\VSS","TypesSupported","7"

reg_add,0x2,"%reg%\ControlSet001\Services\Eventlog\Application\VSS","EventMessageFile","#$pSystemRoot#$p\System32\vssvc.exe"

Hive_Unload,HKLM

I am not entirely sure if 'vsswmi.dll' is needed or not. For me, vss service starts without so I have not included it.

Regards,
Galapo.

Where I must add this Code?
I add it to the code box and I add it to the source of the DriveImageXML script, but the mistake is there still.

Under [process]

I have tried it now with your lines in process, but it still doesn't work.
I started vssvc.exe in VistaPE manually but nothing changed.

Now the UAC Restoring mistake is away.
But the Backup mistake is there still.
How can I make vss work?

As far as anyone knows, you can't. Maybe the future will be different, but I don't have any ideas of how to try. I've tried everything I can think of. Repeating what I wrote in another topic:

DriveImage XML sort of works under VistaPE. It does not work well with NTFS partitions.

Vista (and VistaPE) uses Transactional NTFS (TxF). The significance is that TxF keeps a file open on every NTFS partition it finds. So DriveImage XML can never lock an NTFS partition under any flavor of Vista. It has to make a shadow copy using Volume Shadow Snapshot (VSS). But nobody has figured out how to get VSS working in VistaPE. (I suspect that it may be some really fundamental issue, not just missing files or registry keys.) But right now it is not possible to use DriveImage XML to make a backup copy of an NTFS partition under VistaPE unless you say OK to the "You can still continue but the backup image might be damaged" warning message. I have no idea how likely that is to produce a useful backup. I suspect it would be useful if the partition is not being used by other programs, but I have not made any tests.

Luckily, you seldom need to back up from VistaPE; you can do your backup from a working Vista system. You need DriveImage XML to restore a backup to a system that isn't working any more. You can do that under VistaPE, I've done it, but it requires a trick.

Since VistaPE TxF keeps a file open on every NTFS partition, DriveImage XML cannot restore an image to an NTFS partition. You must use an appropriate tool to destroy the partition and re-create it as a FAT32 partition. Then DriveImage XML can restore the NTFS backup to the FAT32 partition, changing it to NTFS in the process.

I haven't tested manipulating FAT32 partitions with DriveImage XML under VistaPE, but I suspect it will work as long as the partition is lockable (not being actively used by other programs).

Try this:

Hum, that gives me an idea ...

JonF:
Yes, Backup I will do in my "real" Vista.
About the trick:
I would try it to create a partition with diskpart, but there I can only create FAT32 until 32GB.
So I thought: Is it needed to format the partition, to restore with DriveImage XML.
Can I not restore with DIX a Image to a unformat partition?
Has anybody tried this yet?
If not, I will try this in Virtualbox.

Thank you all!

What do you mean with your last entry?:
Hum, that gives me an idea ...

JonF:
Yes, Backup I will do in my "real" Vista.
About the trick:
I would try it to create a partition with diskpart, but there I can only create FAT32 until 32GB.
So I thought: Is it needed to format the partition, to restore with DriveImage XML.
Can I not restore with DIX a Image to a unformat partition?

No, you can not. DriveImage XML only restores to a partition that has a drive letter, which requires format. There are some free tools available to mess with partitions ... I'm not familiar with them.
Has anybody tried this yet?

Hum, that gives me an idea ...

Gives me an idea of how to get VSS working.

I think there you are wrong.
You only must create a partition, but not format.

I think there you are wrong.
You only must create a partition, but not format.

Yes.

DriveimageXL backups (and thus restores) a volume, not an entire hard disk.

It skips the MBR and hidden sectors.

You need another utility to backup the MBR:
http://www.911cd.net...showtopic=21679

A GUI tool can be HDhacker:
http://dimio.altervista.org/eng/

If you want to automate the making of the partition on a new drive you can use my MBRBATCH:
http://www.boot-land...?showtopic=3191
http://www.boot-land...?showtopic=5000

But using tools capable of doing that internally may be better, besides partition saving and selfimage, there are more listed here:
http://www.911cd.net...showtopic=16534

jaclaz

I think, if you use RAW Mode in DriveImage XML all will be copy, even unused sectors.
This disk you restore to will partitioned as well as the other and will be probably active.
About MBR I don't know.

NO.

Last time I checked DriveimageXML made images out of volumes (read drive letters if you prefer) thus NOT saving the MBR (that contains the partition table) and subsequent hidden sectors.(i.e. usually the first 63 sectors on the drive, not on the volume)

An image can be a RAW image or skip unused sectors (unused sectors are within the filesystem, hidden sectors are outside it), but the first sector will always be a bootsector, no MBR, no partitions data available in the saved image.

A modern hard disk is usually having a CHS geometry of nx255x63, where the first sector is the MBR and contains the partition table, then follow 62 more hidden sectors and the bootsector of first partition (first sector of the volume) if the first partition is a Primary one (99.99% of cases) . if it's an extended partition, the 64th sector is the EPBR, and the bootsector of the partition is further on.
Check this:
http://www.ranish.com/part/primer.htm

An image made with DriveimageXML (an image of the first partition, of course) starts from it's bootsector.

Thus there is no need to format, but the partition must be created, in old "DOS" terminology, the target drive for restoring should be FDISKed, but there is no need for it to be FORMATted.

jaclaz

I use driveimage xml only for backup.
If my system is crashed I'll start VistaPE, with diskpart delete the partition and then I will create the partition again and then I restore my image with driveImage XML.

This is possible, isn't it?

Yes, it is.

But the resulting drive may (or may not) have the same size or beginning for the partitions, unless you use exactly the same method for creating the original partition (or, of course, if you have just one BIG partition spanning all the drive it will work, but that is not - believe me - the proper way to setup a system).

Backing up the MBR too (or at least the partition tables within it) and if logical partitions are used the EPBR's, allows for having the restored system a clone of the original saved one.

jaclaz

OK
I have 2 partitions a system and a recovery partition.
I would then only delete c and then create a new partition out of the free space.
The new partition would then be as big as the old partition and it should work.

Thanks

I think there you are wrong.
You only must create a partition, but not format.

By gosh you are correct! My mistake.