shinedog

Yet another problem I have been troubleshooting. I boot from WinPE 2.1 in order to XCOPY a bunch of drivers, I386, and a bunch of software over before I actually begin the installation. Ever since upgrading to WinPE 2.1, XCOPY.EXE acts really flaky. It often times out with the error "the handle is invalid" during any portion of the 3-4 XCOPY commands I execute. If I just boot WinPE 2.1 to a command prompt and run XCOPY on the same folders, I get the same issue. Some times just changing directories using the CD command can result in semaphore error. These exact same scripts/commands processed fine under WinPE 1.6. Not really sure why XCOPY is acting so flaky for me.

Hey All. I'm using WinPE 2.1 in conjunction with HP's RDP 3.81 software. the problem that I am experiencing is that when it boots into WinPE 2.1, it seems to get "stuck" processing commands. It seems to happen randomly. A command prompt box appears and it begins to load drivers, the Altiris client then execute batch scripts. For some reason it seems to stick randomly in that it will begin processing commands and then just stops. And it will remain there indefinitely until I press any key on the keyboard and then in continues. It doesn't matter where in the process I am and it can happen in any DOS window but always within a CMD script. The script itself is not looking for any key input and I've verified its not hanging with a "are you sure" type prompt that I just can't see. Any one seen anything like this before?