Jump to content


  • Posts

  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country


Posts posted by pankajtakawale

  1. Yeah, I didn't find it in WAIK either. I do believe bcdedit is not part of WAIK.

    bcdedit is part of WinPE.wim.

    In WAIK, you can see different folders (ia64, amd64, x86) for different platforms, these folders contain basic WinPE.wim image files. When you mount WinPE.wim file using imagex, u can find bcdedit.exe in that mounted folder.

  2. what is alternative to findstr in WinPE 2.0. findstr is unrecognized in WinPE.

    Once WinPE starts I want to wait untill ipaddress is being assigned to WinPE box.

    Following is the script I found on the net:

    rem if not defined Debug echo off

    set i=0


    ipconfig.exe /all | findstr "Lease Obtained" > NUL & goto :Found

    set /A i=%i%+1

    echo DHCP address not found. Wait for 10 seconds and try again. [%i%/6]

    sleep 10

    if not "%i%"=="6" goto :Loop


    @echo The DHCP address was not acquired.

    @echo Please ensure that you have a netcard with a valid driver.

    netcfg -v -s a


    goto :EOF


    @echo Found!

  3. I can not login to winxp+sp2 share using guest account from WinPE 2.0, wherein i can successfuly connect to same share from any other windows box.

    X:\Windows\system32>net use t: \\\guestShare

    The password is invalid for \\\guestShare.

    Enter the user name for '': guest

    Enter the password for

    The user context supplied is invalid.

    More help is available by typing NET HELPMSG 3775.

    I could not connect to share by changing registry settings mentioned in thread: http://www.msfn.org/board/lofiversion/index.php/t81650.html

    Please advice....

  4. I have VC8 built C utilty, when i try to run this utility from x64 WInPE, it gives me error:

    "The application has failed to start because its side-by-side configuration is incorrect. Please see the application event log for more details"

    After googling, i came to know that msvcr80.dll is absent on the x64 winPE, after copying msvcr80.dll, it still shows same error. there are other system dlls absent on x64 winpe like:








    I also tried to execute vcredist_x64.exe from x64 WinPE (http://msdn2.microsoft.com/en-us/library/ms235291(VS.80).aspx)

    for vcredist_x64.exe, it throws error: "System can not execute the specified program"

  5. StuffIt V3.10ß © Terje Mathisen 1989-91

    Syntax: Stuffit <commands>

    +|=[[hh:]mm:]ss | Delay for(+) or until(=) a specified time.

    +45 will wait for 45 seconds.

    =14:: will wait until 2pm.

    +0 will wait until the kbd buffer is empty.

    <character code> | Stuff a given character code.

    stuffit +2 13

    would feed "ENTER" to stdin after 2 secs.

    Anything similar to stuffit on WinPE?

  6. Im confused how would it (nbtstat) help?

    Just another case:

    machine has 2 NICs NIC1 & NIC2

    NIC1 is on n/w 1 and NIC2 is on n/w 2.

    Both n/ws have DHCP server running.

    NIC1 has priority over NIC2 in BIOS boot loading.

    I have configured WinPE network booting on n/w 2 (to which NIC2 is connected)

    Once machine boots up, NIC1 gets ipaddress from DHCP server of n/w 1.

    NIC2 gets ipaddress from DHCP server of n/w 2 and also it receives boot-server & boot-filename details. It starts booting WinPE.

    Now in above case, WinPE has been booted on NIC2.

    How can i detect it thru any command, api from WinPE?

  7. Is there any command, wmi script or api which returns the NIC info (mac addr) from which WinPE has been network booted on?


    If I have multiple NICs and each NIC is attached to different subnet.

    I have configured NIC1 at the 1st position of boot loader in BIOS and NIC2 at 2nd position.

    Say, DHCP server is not present on NIC1 network, and its present on NIC2 n/w.

    so obviously my WinPE will be network booted from NIC2.

    Is there any api, command, WMI query to information about n/w adapter from which WInPE has been booted on (in this case NIC2)?


  8. Im trying to run my simple UDP time server on WinPE 2.0

    It calls recvfrom to receive any time-requests from clients.

    But whenever I send time-request to this server, it never comes out of recvfrom.

    If I run same UDP server on Win2k3 it responds fine.

    I want to see whether UDP packet from client is actually reaching to WinPE machine.

    I tried installing etheral on Winpe but it gives me error (unable to write to X:\windows\temp\nsrDE40.tmp\system.dll)

    I also tried installing WinPCAP setup on WinPE - it also gives me "illegal instruction error"

    Can anyone suggest me solution of my original problem? or any network trace tool which can run on WinPE?

  9. This is very interesting so I tried it out in VMWare.. here is what I did..

    1. use ghost to layed down a Syspreped image onto a new VM Machine.

    2. Boot up PE and run imagex /capture c: and saved the WIM to a network share.

    3. created a new VM machine, and boot up WinPE.

    4. Diskpart the new drive and format it to NTFS

    5. run imagex /apply the.wim back to C:

    In the VM preped with ghost in step 1, a reboot will cause the VM go into mini-setup, but in the VM applied with ImageX, it bluescreens at me.

    anyone have any suggestions? Is this a VM issue? thanks.

    I tried it on VM instance only.

    Only difference between your and my steps are:

    Instead of your (1) step , I install OS on VM manually - then syspreped it.

    You can try followin steps:

    1. deploy normal (NOT syspreped) image to new VM m/c

    2. sysprep it

    and then ur normal steps....

  10. Would following steps work for 2k/xp/2k3 image based deployment?

    1. Prepare master installation with sysprep tool (generalize it)

    2. Capture the image of sysprepe'd active partition using imagex (may be by network booting into WinPE)

    3. To parameterized the image:

    - mount the image using imagex

    - parameterize the image by editing sysprep.ini file (add custom info)

    - commit the changes to image

    4. Deploy the image to target machine

  11. let me get this right, you have a Windows 2k/XP/2003 installation, prepared with sysprep, captured to a wim-file. And now you are trying to get the 2k/XP/2003 sysprep to use your unattended.xml as answer file, right?

    I want to deploy captured wim-file image to bare metal machine.

    The only way i can deploy this wim file to bare metal is

    - boot bare metal with winpe 2.0

    - create appropriate partitions etc

    - imagex /apply captured-generic-image.wim 1 c:

    Now my concern is - captured-generic-image.wim is generic - it doesnt have host specific information like host name etc.

    How to specify these parameters for deploying "image".

    For setup based installation, we use unattend.txt

    It looks like to me that winpe 2.0 unattend.xml mechanism is only used for parametrizing *vista* wim images and not other?

    Then what is the mechanism to apply custom parameters to 2k/xp/2k3 images captured using imagex?

  12. If I'm not mistaken the setup/sysprep itself interprets the answer file. So I think you have to use the "old" unattend.txt (INI-)format to specify answers for Win2k, XP and 2k3.

    I dont want to deploy OS using setup method (win32.exe /unattend:unattend.txt).

    Instead I have generic .wim image which doesnt contain host specific info like host name, users etc.

    The only mechanism i have to deploy this image to bare-metal machine is to apply using imagex.

    For vista image, i can parameterize the the image deployment using winpe2.0 & unattend.xml.

    But what about other windows flavors?

  13. It seems that I can not use unattend.xml (WinPE 2.0) technique to deploy win2k,xp, 2k3 images to deploy server.

    If I generalize master server using sysprep, capture wim image of generic master using imagex, then

    to deploy generic wim image using imagex, how to apply my own custom parameters like machine name etc?

    I dont think WinPE 2.0 unattend.xml is useful in case of 2k, 2k3 & xp. Its only useful in case of deploying vista wim images.

    Note: I tried to create unattend.xml file for winxp wim image using Windows System Image Manager , but it throws error.

  • Create New...