ChrisBaksa

That is 100% incorrect. You CAN boot PE sucesfully if the proper Mass Controller Driver is not there. You will simply be unable to access the disk. Chris

Doh! My bad. I knew what you wanted... but gave you the wrong example. Sorry Here is what you want. This mounts the XP registry under PE and allows you to change it. You will need to modify it for your needs. reg.exe load HKLM\PEtemp c:\windows\system32\config\software <mounts the Software key hive to PE as PETEMP> reg.exe delete HKLM\PEtemp\Microsoft\Windows\CurrentVersion /v DevicePath /f <deletes the DEVICE PATH key> reg.exe add HKLM\PEtemp\Microsoft\Windows\CurrentVersion /v DevicePath /t REG_EXPAND_SZ /d yadda...yadda...yadda <added the DEVICEPATH Key and the value "yadda...yadda...yadda" as a REG_Expand_sz> reg.exe unload HKLM\PEtemp <unmounts the PETEMP hive> Chris

Use the search. This question has been answered a million times. Chris

Yes this is possible. You can do what is called a REG SLAM to put the run once value in the registry. You will need to create a REG file with the values in it. Take a look at Ram Disk CMD file that MS provides. It should do what you want. Copying your files to the Hard Drive is the easy part. Chris <SNIP> @if not defined Debug echo off :: :: Program to "Slam" the contents of ramdrv.reg into a WinPE Registry Hive. :: This step is performed against a WinPE build, before the ISO image is created. :: :: The RamDrv sample is provided as-is. :: :TestEnvironment if not exist "%~dp0\ramdrv.reg" echo ERROR: .\RamDrv.reg not found & goto :Usage if not exist %1\system32\setupreg.hiv echo ERROR: WinPE System Not Found at %%1 & goto :Usage if not exist %1\system32\drivers\ramdrv.sys Echo ERROR: RamDrv.sys not found at %%1 & goto :Usage :LoadRegistry reg.exe load HKLM\NewSys %1\system32\setupreg.hiv :RegistrySlam RegEdit.exe /s "%~dp0\ramdrv.reg" :UNLoadRegistry reg.exe unload HKLM\NewSys goto :EOF :Usage @echo Usage: %~n0 ^<WinPE_Path^> @echo Where <WinPE_Path> is the location of the WinPE directory. @echo Example: %~n0 c:\MyWinPE\i386 @echo or %~n0 c:\minint

But do I need to do anything differently to create the ISO? Any switches? If the ISO is 2 gig... Will it simply know to that it is a DVD?

Has anyone created a Bootable WINPE 2005 DVD? It is not documented in the help file. Anyone know how to do it? I want to store a Ghost image on the same disk. But to do that I have to boot a DVD instead of a CD. Chris

Are the drivers publicly available? Or do you have to call in and get them? If I need to call, what drivers should I ask for? <{POST_SNAPBACK}> I don't know. I can ask. My Tech just mailed me a zip file with teh drivers. I've been out of the offfice since last week so I'm just catching up now. Chris

Update... Dell provided me with drivers that work properly under PE 2005. Yahoo! Chris

Edit the OC.bat and remove the last line that says EXIT. Chris

Ok folks. After speaking with several people here is what I have found. The problem is with the NIC driver, not w/WinPe. You need the HP 7.103 q57win32.sys driver; previous versions of the driver (including generic BroadCom driver) mangle the MAC. The newer HP systems introduce side-band technology in their LOMs, which their driver didn't handle appropriately causing the problem. Predominately exposes itself when booted in later versions of WinPe. HP has a preliminary driver which will be the same one that is released with teh Support Pack 7.4 in early September. This of course does not fix my Dell problem. Chris

I am still having Issues. I have replaced the Broadcomm driver (sys and inf) and still have the same results. FACTORY.EXE - Failed to Install Network Adapter - Check WINBOM.ini. This only happen on WINPE2005 (32bit). My WINPE 1.2 build works fine. Same build process. I have contacted DELL but they are way behind the times with WINPE. Chris

I already do that. My scripting Pings the DNS server as a network test. I have even used a GUI network config tool and it shows No NICS present. I am going to convert my Build from RC2 Binaries to Release Binaries today. Maybe that will help a bit. Chris

An engineer at HP told me of an issue with Factory and Broadcomm NICS where it will crash the NIC or the system when Factory runs. I have seen it happen on a few machines. I have an issue rigthnow where PE 1.2 works fine with a poweredge 1850/2850/6850 but WILL not work with PE 2005. When 2005 loads it does not find any NICS. Have you seen this? Chris

This is true. I personally don't like Hard Coded Values like that in my code. Call it a pet peeve. Chris

In a pefect world... DMI/WMI would be great. But in my testing it returned flaky results based on the Manufacturer. The WMI query itself returned different values on the same exact hardware models with newer bios versions. I provide drop down for each OS with the model. Based on that I reference a section in an INI file for the build details. It works very well and I have total control over what I want to push out (or not want to push out) for a particular model. My PXE build works in a similar fashion except the data presented on the web page for the models is stored in a database. I still keep the INI file method for CD builds and for DR. I'd love to see some of your code for what you are doing. Chris

Are you doing CD based installs or Network based installs? You can script anything you want to do and run the installs from a Network share. Consider this option. All your install scripts would reside on the network rather than teh CD cutting down on the CD's you would nee to burn everytime you made a chage. Logical Steps (overview) 1 - Boot PE. 2 - Select OS to install 3 - Connect to Network Share 4 - Run OS install 5 - Post scripting (aplication installs... custom settings.. Yadda yadda yadda...) This is Very basic .. but you get the jist. I have one PE CD that you can Install 3 different OS'S (Windows XP, Windows 2000 Server and WIndows 2003 Server). It's all in the scripting. Don't expect to do it overnight. It will take time and Alot of testing. I support 30 different Server Models by various vendors (IBM, HP, Dell, Vmware) as well as another 2 dozen Desktop models. Chris

Correct. You cannot change the Drive letter. To overcome any Drive Letter scripting issues use %SYSTEMDRIVE% in your scripts. Chris

Make the ISO and use VMWARE. Or use a Re-Writeable CD so you can re-use it. Chris

All I can say is call your Veritas Rep and inquire. I'm not playing an "I have a secret game"... I can't talk about it. Legal reasons. I can say that in talking to their engineers I have requested that it NOT be a locked in - out of the box product and that they allow us to integrate the product into our own PE solutions. In the businees domian you have 2 types. "Mom and Pop Shops" and Enterprise clients. The first use the product out of the box and Enterprise clients engineer the solution to meet their needs. They understood my concerns. Chris

Yes they are. I would use Dependancy Walker on your app. Maybe you are missing something else. I install ALL the optional components. Take a bit longer to load, But I don't miss anything. Chris

Non Disclosure Agreement. It's a legal contact binds you from discolsing any details about the new product. In laymans terms... Sign this stating that you will not tell/show anyone our new product and we will tell/show it to you before it gets released. Chris

Did you load the optional components? Did you download and install teh VB6runtime components. Did you register the necessary components? Chris

Veritas is activly looking into PE. Due to NDA.. I can't tell you any more.

You can put the drivers files anywhere.... you don't need to use the $OEM$ folder. Simply do an XCOPY of the dir structure you want to the host before you run winnt32. Put that path in your unattend.txt. The only files I keep in the $oem$ folder is what is in the TEXTMODE dir (Mass Storage Controllers) Every thing else is in a different dir that is much easier to manage and is common to all versions of of the OS. (Standard, Enterprise and Web) Hope this helps. Chris

Interesting... Microsoft has a new Ram Disk driver for PE 2005 that has a simplified process of installation. It uses what MS calls "REG SLAM". It's a one step process (rather then the 2 step process that the PE 1.2 driver required). MS even provides a cmd file to launch the installation process. All settings are in a reg file that you can modify... Size, Drive letter... If you are using the old PE 1.2 driver... Get teh newer one. Chris