Jazkal

I have tested the newest test build and it works great now via network. thanks

You need to make sure you have the latest version of "iaStor.sys", and you need to check and see if the device ID's for that device are actually listed in the storage.ini file. If not, then you need to add them. In a Windows environment (windows or Winpe) run: devcon find pci* This will give you a list of all devices, then you can look at the device ID's for your sata controller and compare.

Yes, that is what I do, I just add the file list to the other section. Sorry I wasn't more clear.

Yes, just the sys files. I just copy over the list from the other section that you modify in the dosnet.inf file. I haven't tried a true DOS based install in some time, I've been using DVD installs or WinPE for deployments. But i can give it a try tomorrow and make sure it doesn't break anything. I don't think it will, but i will verify.

I wanted to request a small addition/change: When hfslip integrates the driver sys files, and makes the changes to txtsetup and dosnet.inf; can you please add the entries in dosnet.inf under the "[FloppyFiles.2]" section. This is required if you are doing an install from network.

removed

I use Win2k3 drivers in my WinPE2 build. NetExtreme II nics require a special RIS driver to work in WinPE. ( i posted a set that will work in another post somewhere near the top of this forum.

it is available for download from the microsoft website, do a search for WAIK.

I checked the device id's in the Hp driver pack, and these drivers I'm including should work. They were meant for RIS, but they work in WinPE also. let me know how they work out. ris.zip

From that drivers list of supported nic cards: your card isn't listed. Check the devcon device id's in the driver INF, and see if they are there.

can you give us a devcon output? devcon find pci* mainly intrested in the NIC device id's On this page: HP DL360 Driver Page : Which nic are you talking about? EDIT: I ask about the drivers, because I don't see that the NC375I is supported on any of those.

ZoRoNaX, any progress on the write up?

I was hoping it would come with an updated WAIK.

let us know when you find it.

Anyone tried mounting the default user hive and loading the tweaks that way? Not even sure that would work or not.

We are using the WIM file for our pxe booting. we tried the ISO at first, because that is what we were using with WinPE v1.6, but didn't have good luck using it. Here are the files we are using in our "Boot" folder: And we are booting the pxeboot.0 file.

rename startrom.n12 to startrom.0 And give me the error message your getting.

Have you tried looking at a devcon output? devcon find *

Your file system is fat32. I think it needs to be NTFS.

which version of WinPE? v1.6 or 2.0?

WinPE v2 has a 72 hour limit.

That is strange. I'm wondering if Microsoft asked a Mod to remove the attachments? Wouldn't they tell us if they did that?

It seems that the new diskpart has "issues". On some motherboard chipsets, it can corrupt the MBR of the drives. I ended up using gdisk32 to wipe the mbr, and seems to have fixed the problem. EDIT: I'll have to look into the "convert mbr" and "ID=06" commands. Thanks for the heads up.

I know this script works to create a working WinPE2 ISO that will run VBS script. I just tested it in VMWare, booted up, mapped a drive, and ran a couple of vbs scripts. rem ***************** Set your own paths if they are different *********************** set PETOOLS=C:\Program Files\Windows AIK\Tools\PETools set IMAGEX=C:\Program Files\Windows AIK\Tools\x86 set ISOSOURCE=C:\winpe_2x86 set ISONAME=WINPEv2.ISO %COMSPEC% /c "%PETOOLS%\copype.cmd" x86 %ISOSOURCE% "%IMAGEX%\imagex.exe" /mountrw %ISOSOURCE%\winpe.wim 1 %ISOSOURCE%\mount xcopy "%ISOSOURCE%\mount\Windows\System32\Boot\*.*" %ISOSOURCE%\mount\Windows\System32\*.* /e /y rem ***************** Installing packages *********************** "%PETOOLS%\peimg.exe" /install=WinPE-HTA-Package %ISOSOURCE%\Mount\Windows "%PETOOLS%\peimg.exe" /install=WinPE-WMI-Package %ISOSOURCE%\Mount\Windows "%PETOOLS%\peimg.exe" /install=WinPE-Scripting-Package %ISOSOURCE%\Mount\Windows "%PETOOLS%\peimg.exe" /install=WinPE-XML-Package %ISOSOURCE%\Mount\Windows "%PETOOLS%\peimg.exe" /install=WinPE-MDAC-Package %ISOSOURCE%\Mount\Windows rem ***************** This is were you would install drivers and copy over files if needed *********************** rem "%PETOOLS%\peimg.exe" /inf:{FULL PATH}\{DRIVER.INF} %ISOSOURCE%\Mount\Windows rem ***************** Finalizing the WIM *********************** "%PETOOLS%\peimg.exe" /prep /f %ISOSOURCE%\Mount\Windows rem ***************** Deleting the ISO boot WIM so we can use ours *********************** del %ISOSOURCE%\ISO\sources\boot.wim rem ***************** Creating a compressed WIM *********************** "%IMAGEX%\imagex.exe" /boot /compress maximum /capture %ISOSOURCE%\Mount %ISOSOURCE%\ISO\sources\boot.wim "WinPE2" rem ***************** Closing the WIM *********************** "%IMAGEX%\imagex.exe" /unmount %ISOSOURCE%\mount /commit rem ***************** Building ISO *********************** "%PETOOLS%\oscdimg.exe" -n -b%ISOSOURCE%\etfsboot.com %ISOSOURCE%\ISO %ISOSOURCE%\%ISONAME% try this out, and tell me how it works.

Post the steps your going through to build your WinPE2 WIM. I know it works, because mine is using HTA's with built in WMI calls, calling VBS scripts, doing XML parsing, etc.