VistaPE and DriveImage XML? External links Options

[Lex Luthor]

I have 1 Vista PC and 2 XP PCs. I created a Bart PE CD with the DriveImage XML plugin and that works great on the XP PCs, but it doesn't recognize my C drive on the Vista PC.

Does Vista PE have a DriveImage XML plugin?

How can I get DriveImage XML working from a bootable CD on my Vista PC m?

Thanks!

[JonF]

Nobody's gotten DriveImage XML to work reliably under VistaPE yet. Your Vista system probably has a SATA drive for which there's no driver on the XP source CD; that's why your BartPE CD doesn't see your Vista system's C drive. Try adding the driverpacks plugin to your BartPE CD: Official BTS Driverpack Support.

[Lex Luthor]

Actually, I had some success.

From the documentation, I couldn't there was already a script for DriveImage XML under VistaPE, so I did a build and saw I could add it. I was able to create a VistaPE CD successfully.

It detects me SATA drive and seems to work.


The only issue is that when it tries to make a shadow copy of the drive, I get an error about vssvc.exe not being there. It does continue with a warning that it couldn't make a shadow of the drive. Since the drive isn't in use for anything else since I've booted from the CD, I'd imagine it'd work fine without making a shadow of the drive.

Still, how do I get vssvc.exe and (and I think associated file xolehelp.dll) onto a new VistaPE CD?

Or would it be easier to add that driver back to a new BartPE CD? I think I'm close enough with my VistaPE though.

[JonF]

Or would it be easier to add that driver back to a new BartPE CD?

Driver pack. Yes. Far easier.

I think I'm close enough with my VistaPE though.

I thought so too, back in April. I'm still not there, nor (AFAICT) is anyone else. I'm not as experienced as some but I've been doing this sort of thing for several years. DriveImage XML under VistaPE is a difficult problem.

[Lex Luthor]

Well, maybe I'll try the driver pack tomorrow.

I do think I have DriveImage XML working with VistaPE. It just doesn't have that vssvc.exe file so it can create a shadow of the drive, but since the drive isn't in use (except for the driveimage backup), I don't see how that would matter. I guess I'll have to let it make a full copy sometime and see if it's readable at the end, but I don't see why not.

If I wanted to try to get vssvc.exe onto the VistaPE so that DriveImage XML would have it to use, what would be the procedure for hat?

[Lex Luthor]

No go. With the driverpack and BartPE, I got an error message saying I need admin rights when I tried to backup/restore using DriveImage XML on my Vista PC. BartPE without the driverpack didn't give me that message, but I couldn't see my C: drive at all.

When I tried on BartPE w/driverpack on my XP PC (no SATA drive), it worked fine.

I guess the thing I'd like help with is how do I get that VSSVC.exe file into my VistaPE installation so that it has access to the volume shadow service. I think if I had the file on VistaPE, I'd be in great shape.

[Nuno Brito]

DriveImageXML was added to the LiveXP project some months ago.

You find the script here --> http://livexp.boot-land.net/LiveXP/Apps/Ba...ImageXML.script

Since the script is using API format it should work very well under VistaPE or you can simply use the LiveXP project which already comes with SATA drivers.

Good luck!

[Lex Luthor]

DriveImageXML was added to the LiveXP project some months ago.

You find the script here --> http://livexp.boot-land.net/LiveXP/Apps/Ba...ImageXML.script

Since the script is using API format it should work very well under VistaPE or you can simply use the LiveXP project which already comes with SATA drivers.

Good luck!

Well, looking at the LiveXP DriveImageXML script, I don't see how that's going to work under VistaPE. I see references to files that appear to be XP files and not Vista files (like VSSXP.dll). I can't just replace the VistaPE DriveImageXML script with this one and find that all will work, can I?

If not, I'm up for trying a LiveXP CD with this DriveImageXML script though. But, maybe I'm missing something. Where do I a Live XP builder from? I've been searching, but I must be missing something.

[Nuno Brito]

Open the download center inside wb and select the livexp.boot-land.net server to get all updated project files.


There's also a single pack for download on the project gallery here --> http://winbuilder.net/download.php?list.5

-------------------

Why do you need VSSXP.dll to work under Vista?

If you're booting from a CD/DVD/USB drive then the volume can safely be locked since the OS is running from a removable media.

Good enough to create or restore disk images.

------------------

Which references are specific to XP?

Look inside the code, it will look for 4 files inside the windows source to include on the boot disk

require_file,APPHELP.DLL
require_file,LZ32.DLL
require_file,WOW32.DLL
require_file,NTVDM.EXE

And write the needed registry keys.

Will also add a few shortcuts:

If,%pCheckBox1%,Equal,True,Add_Shortcut,Desktop
Add_Shortcut,StartMenu

CODE

[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

[JonF]

I think if I had the file on VistaPE, I'd be in great shape.

Sorry, you are wrong. You would still be far from having it work. But go ahead and try; in WinBuilder, select the DriveImage XML script. Click the edit button (second from the top next to the script's icon). Select the "Attach" tab. Click "Add". Select vssvista.dll from your DriveImage XML installation. Click Start. Click the red X at the top right of the editor window to return to the main screen. Build your project. Test it. Curse when it fails again.

Then you can add lines to the script to copy vsssvc.exe and xolehelp.dll:

CODE

FileCopy,"%InstallSRC%\Windows\System32\vsssvc.exe","%TargetDir%\Windows\System32"
FileCopy,"%InstallSRC%\Windows\System32\xolehelp.dll","%TargetDir%\Windows\System32"

(I don't know how to do that in the new API).

Then in VistaPE you can run services.msc and start both the Volume Shadow Copy services. And curse again when DriveImage XML fails again.

If you figure out anyting beyond that, please let me know.