Jump to content

jungle_warrior

Member
  • Posts

    34
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    China

Everything posted by jungle_warrior

  1. try assign another drive letter to it. >select volume c >assign letter = y >select volume d >assign letter = z >exit at leat drive letter c and d was released....... looking for better ideas.
  2. your version maybe WinPE2004. Microsoft document says PE2004 support only XPSP2.
  3. really boot WinPE2005 from Vista bootloader? are there more details? Microsoft document says PE2005 only supports Win2K3 SP1 and XPSP2, and I just installed Vista beta(5259), C:\NTLDR was not found, C:\NTDETECT.COM not found too, it seems to be replaced by C:\BOOTMGR, not knowing the interface for dual-boot....
  4. you can try use WINPEOEM.SIF file to load a SATA driver, do not need to modify txtsetup.sif. here is a WINPEOEM.SIF file: [Version] signature="$Windows NT$" [OemDriverParams] OemDriverRoot="" OemDriverDirs=Sata and find the TXTSETUP.OEM file in your SATA driver disk, copy that file and other necessary ".sys", ".inf" and so on, to winpe's system32\sata directory (create directory yourself). dir x:\i386\system32\sata si3112r.cat si3112r.sys si3112r.inf txtsetup.oem
  5. yes it may not be a hardware problem. I think it is because there are only 2 available boot loaders, actually: the normal \NTLDR and \CMLDR. NTLDR loads the XP system, or NTLDR loads CMLDR, but CMLDR cannot process BOOT.INI, It seems that CMLDR will then process the file cmdcons\txtsetup.sif, in which "osloadoption..." line instructs it to load WinPE or RC. It is not possible to make a choice at runtime. Maybe, try use 3 loaders: NTLDR, CMLDR of RC, and SETUPLDR.BIN of winpe. you can rename SETUPLDR.BIN to, for example, STLDR; then edit \BOOTSECT.DAT file, replace the ASCII string "CMLDR" to STLDR.
  6. Thanks a lot. you are quite right. I made many tests these days, and find that, adding anything into .ISO file (by UltraISO) sometimes can cause problems. while OSCDIMG.EXE is safe. still not knowing why...........notepad.exe can not run (Other things seems no problem). Thanks.
  7. Winpe2005 can work with both Server 2003 SP1 and XP sp2 source, refer to it's OPK document.
  8. I make a .ISO for winpe 2005, and it runs normally on VMWare. and I add a folder to the .ISO file, named "双字"(in chinese). when I boot the .ISO in VMWare again, notepad.exe cannot run. "The system cannot run the specified program". after I removed the chinese-named-folder from the .ISO file, the problem PERSISTS, any advices or ideas? thanks in advance.
  9. In WinPE 2004(with WinXP SP2), the boot volume was assigned drive letter X:, can I change this drive letter? can I achieve this in older version of WinPE, i.e., assigne a fixed drive letter to the CD-ROM drive. thanx.
  10. thanks a lot, it's very kind of you
  11. Hi people... This is jungle_warrior from China... i joined the forum now... i always visited the forum earlier to read some posts but finally decided to join... Hope to know many friends.
×
×
  • Create New...