Jump to content

srirammp

Member
  • Posts

    12
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    country-ZZ

About srirammp

srirammp's Achievements

0

Reputation

  1. i am still at loss to find the documents you mentioned..i dont have any WinPE.chm and nor could i get any information from readme.txt. Is there any other link where i could get the information required?? Thanks -Ram
  2. i dont find anything in the documentation i have....can you name the document or post link to any location where i can get some information? Thanks -Ram
  3. Hi, Is it possible to open a COM port in WinPE and read and write to it?? I tried doing it and i get the errors "Create File Failed ", and "The Specified File Not Found" . Anyone else tried it?? -Ram
  4. I could finally have a dual boot of WinXP and WinPE(boot from Hard disk) working on my PC. Thanx for Jonathan Gorenflo, Gosh and likuidkewl for all the useful postings and timely help. Just to get it all at one place i would detail the steps i did to get Dual boot WinPE and WinXP from Hard disk. STEP 1: Create a Custom Version of WinPE Create and name a directory on your hard disk, specified by build_location. Place the Windows OPK CD into the CD-ROM drive, denoted as cd_drive. Copy cd_drive\Winpe\*.* to build_location. Copy Factory.exe and Netcfg.exe from the cd_drive\Tools\platform directory into the build_location directory. To build a 32-bit version of WinPE, the value of platform is x86. To build a 64-bit version of WinPE, the value of platform is ia64, and you also must copy Efinvr.exe into the build_location directory. Remove the Windows OPK CD from the CD-ROM drive. To build a 32-bit version of WinPE: Place the 32-bit Windows product CD in the CD-ROM drive. Navigate to build_location. Run this command: Mkimg.cmd source_directory destination_directory [image_name] source_directory Specifies the location of the Windows product CD. If source_directory is a CD-ROM drive, you need only to specify the drive letter. If source_directory is a network path, the path must be to the parent directory of the \i386 directory. Note Do not include a trailing slash in source_directory. destination_directory Specifies the path where the files necessary to create the image are temporarily stored. If this directory does not already exist, Mkimg.cmd creates it. image_name Optional. Specifies the path and file name of the ISO image file that contains this customized version of WinPE, if you place this version of WinPE onto a CD-ROM. If you are creating a CD-ROM, use CD creation software to burn the ISO image file directly to the CD media STEP 2: To create a bootable WinPE disk (32-bit versions of WinPE) Boot the destination computer into WinPE using a WinPE CD. Create a directory called C:\Minint. You must name the directory "Minint". Copy the contents of build_location\i386 to C:\Minint. For example: xcopy "C:\Build.x86\i386\*.*" C:\Minint /S where C:\Build.x86 is build_location(Which has winPE Image which was created as mentioned in ). Copy Ntdetect.com from build_location to the root of the destination hard disk. For example: xcopy "C:\Build.x86\ntdetect.com" C:\ where C:\Build.X86 is build_location. On the destination hard disk, copy C:\Minint\setupldr.bin to C:\ntldr. For example: xcopy "C:\Minint\setupldr.bin" C:\ntldr STEP 3: You must have the recovery console installed on the machine that you are wanting to dual boot. You can find Microsofts instructions for installing the recovery console at: http://support.microsoft.com/default.aspx?...kb;en-us;307654 STEP 4: Copy "txtsetup.sif" from WinPE(Minint) to the "cmdcons" directory. For further reading: http://www.msfn.org/board/index.php?showtopic=14316 STEP 5: Restart the PC and select "Windows Recovery Console" in the boot menu.
  5. Hi, I am trying to boot WINPE from hard disk. As suggested by microsoft...(given below) ************************************************ To create a bootable WinPE disk (32-bit versions of WinPE) Boot the destination computer into WinPE using a WinPE CD. Create a formatted and active partition. On the active partition, create a directory called C:\Minint. You must name the directory "Minint". Copy the contents of build_location\i386 to C:\Minint. For example: xcopy "C:\Build.x86\i386\*.*" C:\Minint /S where C:\Build.x86 is build_location. Copy Ntdetect.com from build_location to the root of the destination hard disk. For example: xcopy "C:\Build.x86\ntdetect.com" C:\ where C:\Build.X86 is build_location. On the destination hard disk, copy C:\Minint\setupldr.bin to C:\ntldr. For example: xcopy "C:\Minint\setupldr.bin" C:\ntldr Restart the destination computer. The computer starts using WinPE. ************************************************ i have made a active partition and named it C: After doing all steps described above the system dosent boot into WinPE. I am surprised that we have not written anything to the boot sector, probably because of this the system is not able to recognize WinPE. Any Help?? -Ram
  6. Now the CD Boots.... but i still cant connect to network...i copied all NIC files to corresponding folders i dont know if i am missing something...
  7. I found the following driver files for the Intel® PRO/1000 MT Network Connection #2 nic. I copied .inf file to I386/Inf , .sys to System32/Drivers, and other .dll's and .exe to system32 folder. And After making these changes i burn a bootable CD, but the system won't boot from this CD. I fail to understand the reason, if i remove the files i added above and re-write the CD it boots properly.
  8. I added an entry like this [WinPE.Net] IPConfig=DHCP StartNet=Yes in WinBom.ini file, and the CD dint boot. I guess i need to erase it.
  9. do i neet to edit Winbom.ini too?? My current WinBom.ini looks like this.. [Factory] WinBOMType=WinPE Reseal=No [WinPE] Restart=No [PnPDriverUpdate] [PnPDrivers] [NetCards] [updateInis] [FactoryRunOnce] [branding] [AppPreInstall]
  10. i am using Intel® PRO/1000 MT driver.
  11. hi, I created a WinPE CD from Windows XP and able to sucessfully boot into PE. I am unable to ping any computers in my domain probably because the network is not enabled. Can someone help me to enable network. -Ram
×
×
  • Create New...