jeffwitt41

Dan, Thanks for posting. I am very busy doing other things lately so I have not had time to play around with getting the client to install. I have been thinking that Netbackup is very picky about ip addresses and DNS names. You may have to change the ip address and hostname to the original server name to connect to the master server to get any restores done. Jeff

Has anyone been able to install the Veritas netbackup 4.5 windows client onto WinPE? I am thinking that this would make an excellent bare metal restore type of product. If anyone is also working on this idea lets collaborate on it.

I got it. RTFM

Thanks Liquid, I have reloaded the source code several times also. However, I do not have access to the original media. Perhaps that is what I need to use. I have also run in to the problem of the hives getting farked. This gives me encouragement that is it not a problem with the configuration. Thanks! Jeff

All, Has anyone gotten the ADO part to work in WinPE? I am using MS WinPE version 1.2 I ran the buildoptionalcomponents.vbs script to build the optional components ado, wsh and hta. Both the wsh and hta work just fine but when I run the testado.vbs script I get an error Could not locate automation class named "ADODB.Connection" Code: 80020009 Source Wscript.Createobject. I have recompiled the source code many times in just about all the permutations I could think of and I still get this error. Has anyone gotten this message and resolved it? Jeff

This is also what I am attempting to do. Currently we are using the RDP package from HP that works in conjunction with Altiris. The current method works well in our data centers where we have a pxe boot set up. However when we do this at a remote site we need to keep flipping a floppy disk in and out in order to read the stage flag. I am trying to get winpe to work with Altiris but I don't think their bootwork.exe will run in PE (32bit OS). Evilguinness: Have you looked into using ADS from MS? That is fully supported and it also uses WinPE as a boot media. ADS is part of MS's DSI which is a long term design guideline so it won't be going away anytime soon. http://www.microsoft.com/windowsserver2003...ds/default.mspx You might also want to look at MSA 2.0 which does some of the same things but actually works to provision the servers also. While reading this documentation, in Chapter 5 MS gives the instructions for incorporating a RAM Drive into WinPE. Which works very well you need to have at least 256MB of RAM or the ram drive will not be created. http://www.microsoft.com/resources/documen...k/vmhtm149.mspx Jeff BTW: Guinness is anything but evil!

I have set up WinPE to boot from a cd Added the additional components, WSH HTA and ADO. Added a ramdisk to it. Now I would like to get CDO working. Has anyone done this? Jeff

Spawn, I have tried it with the command.com from XP and also WS03. I'm also starting to believe that it will not work for what I would like to do. I would like to use the 16 bit sudsystem to the smart start scripting tools from HP to configure array conmtrollers, update frimware and bios. The nt kernel will not allow programs to directly address hardware so I don't think it would work. Also in the toolkit documentation it says they do not run correctly in emulated dos. Thanks for all your help. Jeff

Spawn, I am trying to run command.com. I copied it to the ram drive R: now when I run it I get: "config.nt. the system file is not suitable for running MS-Dos and Microsoft Windows applications." I must be missing something here. Jeff

Spawn, Did the ntvdm process start when you launched yout 16 bit application? Jeff

Spawn, I spoke too soon. I'm still having the problem. It is trying to write to a temporary file and is not working. Are you sure that it will work? What 16 bit application are you running to test it? Jeff

Okay, Its working. Helps to make sure the source code is good first. Jeff

Spawn, No those files are not needed. I still cannot get it to work though. I am making it from windows 2000 Pro and have tried it with both Ws03 and xp source code. No go either way. I am installing an XP Virtual machine to try and compile it from that os. I keep getting the error that an initilization file file could not be created. Did you ever get that message? Have a good weekend. Jeff

Try using Virtual PC you can capture an ISO image for the cd rom and not burn any disks. Jeff

Thanks Spawn! I had also tried the same thing. It did not work for me. What are you using for source code? XP or WS03. I am tring it with WS03 and I enabled the ram drive. I get the error: "The system file is not suitable for running MS-DOS and Microsoft Windows applications." I will try to compile it with XP source code next. However, I am trying to do this with the server version to enable network driver support better. One thing that I noticed is that 3 of the files are not in the server source mapi.dll, rasapi16.dll and vcdex.dll. In XP the first 2 files are not there but vcdex.dll is. Where did you get these files from? Jeff