Jazkal

I had a problem like that with WinPE x64 and another type of NIC. I opened a PSS case with Microsoft. They reproduced the issue and are debugging it now.

You need a WinPE/BartPE CD with all the NICs you will see in your environment. Then you need to setup a network share with the source files for the OS you want to install. Then you boot the PE CD on the system you want to install to Map a drive to the share Run the winnt32.exe in the share You can either do a manual install, or you can automate everything, depends on how much you want to do.

The way I get a full XP desktop, is use the XPE plugin: http://oss.netfarm.it/winpe/

my guess is that ntdetect.com or spcmdcon.sys is doing some kind of checksum on setupldr.bin. Anyone know if this can be debuged somehow?

I've never used IBM servers, so couldn't tell you for sure. I'd search around thier online support pages for command line tools. Maybe someone else will know.

Depends on the controller. Some controllers (Dell and others) have command line tools that will configure the controller. So what kind of controller are you using?

Jito463, gave that a try, but didn't see any changes. Sounded good though.

I agree. I have modified setupldr.bin files working fine on linux (for WinPE PXE booting). So I think there is some other file (DLL maybe?) doing a checksum on the setupldr.bin file durring boot.

Maybe a XP x64 or 2k3 x64 boot sector would act as a replacement. If your not doing any x64 PE builds, then the other should work.

If you mean VMWare SCSI disks? Just download and install the VMware scsi drivers into PE.

it's in the same directory as mkimg and oscdimg.

If you are using WinPE 2005, it's a simple command line: drvinst.exe /inf:%DRIVERINF% %PESOURCE% /q %DRIVERINF% = the full path to your INF file %PESOURCE% = the full path to your WinPE build directory If your putting files in manually which version of WinPE are you using?

I don't know if any of these will help, but figured I'd post them, just in case Decompilers: * Boomerang [GNU GPL] * NASM [GNU LGPL] EDIT: removed the Java decompilers.

I don't have this problem. I'm using WinPE 1.6 with Win2k3 SP1 source, and the diskpart works fine. I havn't tried it with BartsPE, so couldn't say about that. This is with CD's and PXE.

You can add Windows PE 2005 to the list of OS's that have issues with the setupldr.bin file. Same problems, and the coming solution will probably fix this also.

The only other thing I can think of, is to disable the NIC is the BIOS (if possible). Then test it. we want to narrow it down to a specific item, that we can say "when we turn this off, it works".

I would run a test. Remove the riser card and test BartPE. I would bet it is a problem with the riser card and interaction with BartsPE. This would narrow down the possible issue.

do you have a riser card in the system?

Which version of WinPE are you using? What source OS are you building it from?

This blog page sounds intresting. Haven't tried it myself yet, but it sounds like it will fix the shell context menu problems as a temp workaround. Brandon Paddock's Blog

The mkimg.cmd creates a new hive each time it is run. So to make changes to the hive, you have to do after mkimg.cmd and before the iso is generated.

I may be mistaken, but it doesn't have to be in the EULA. It’s a little bit of Federal law called "Fair Use". As far as the EULA is concerned, it hasn't been tested in court about whether or not it's even legally binding. Fair Use and the right of first purchase have been around for a while and are proven in court. Can't say the same for the EULA. If you followed BartsPE when it first came out, Microsoft did attack it, and quickly I might add. All they came up with was copyright violations. These have since been addressed, and Microsoft isn't doing anything towards BartsPE now.

this is why I use a script to re-create my WinPE images. I am creating a GUI front end for it, once it's done, I'll release it. Just create a batch file, or vbs script to handle it for you. That way if you need to edit things before the iso is created, your script can be modified to mount the reg hive, make the changes, then unload the hiv.

It would help if you explained how you updated the nic drivers in your winpe image.

IMO, WinPE should only be used if you want a network based unattended installer. For a CD/DVD installer, WinPE isn't needed. I've built unattended WinPE iso's. I used HTA docs/scripts for the GUI front end. But that isn't required. My users have the option to pick between all the OS flavors, partition options, then winnt32 is called. Once all the options are choosen, then it proceeds all unattended from there. If your only going to have one option, then you wouldn't even need that. First thing would be to create the WinPE iso with all needed drivers (nics and disk controllers are the most important).