Jump to content

jungle_warrior

Member
  • Posts

    34
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    China

Posts posted by jungle_warrior

  1. The M$ OPK winpe.chm(Sep.2006) says it can, in "Customizing WinPE"->"WinPE walkthroughs"->"walk through: boot PE from hard disk".

    but I failed, following its instructions. and especially,

    bcdedit reports error message: cannot open system store,

    and I use bcdedit /store to explicitly specify it to work around, but

    when finished, it still cannot boot, report some errors like "C000000F, winload.exe missing or corrupt".

    any ideas? thanks in advance.

  2. Additionally, I think the primary usage of WinPE is system recovery, and what does "Official release" of WinPE means, is not important, IMHO, WinPE is originally for OEM customers.

    above posters are very nice. and this "not pure technical" topic is interesting.

    I touch WinPE in 2003, by accident. In fact, I'm doing R&D job in a system recovery company, and in a meeting by then, someone talks about WinPE, and I asked my boss:"What is WinPE? is it WinCE?". In a moment I feel quite ashamed, and I swear, to study WinPE hard.

    by now, I agree the above friend, that WinPE2.0(Vista) is much better to use, especially for network connections.

  3. M$ says the following in the winpe.chm file of the opk CD:

    Windows PE Build Environment

    A Windows PE package contains the following:

    Filename Description

    Boot.wim

    Default Windows PE boot image. This image contains all components and cannot be customized.

    Winpe.wim

    A customizable Windows PE image, also called the base image.

    although opk CD is not WAIK, but I think M$ do not wish you to modify a file originally named "boot.wim", you may try to remove some components of winpe.wim(of the new version), hope to cut down 50MB :P

  4. Yes it is DHCP, I boot pe2 from local hard disk, and, there is a wpeinit.log file in the x:\windows\system32 directory, the content of the file includes:

    no unattend file was found... wpeinit use default settings...

    ipv6 initialized ok, parameters is ...

    ipv4 initialized ok, found DHCP server at 192.168.0.2

    default gate is 192.168.0.1

    default DNS is 192.168.0.1

    ipv4 address is 192.168.0.87(Perferred)

    NETBIOS over TCP/IP is ok...

    node type: hybrid

    ...

    ...

    but what and where is the "unattend" file? in previous versions of winpe, there is winbom.ini, but what it is for the pe2.0's wpeinit.exe? like some friends have said, the pe2.0's help documents is "not helpful" :w00t:

  5. Many thanks for your warm hearted help... :angel

    however the problem is still there. have anyone successfully use network in winpe2.0?

    The operating system I connect to is XP SP2 and Win2K advanced server.

    and I give full control to the Everyone group, but still not work.

    I tried net.exe many times with many arguments, and the most often receive helpmsg 1312.

    and to my surprise, in WinPE, ping another machine is ok(such as 192.168.0.135), but on another machine,ping the WinPE machine is not ok!

  6. I type the following command under winpe 2.0

    X:\windows\system32> net use k: \\192.168.0.135\share

    user name:guest

    password:

    The user context supplied is invalid

    and if use net /add to add a user, then
    X:\windows\system32> net use k: \\192.168.0.135\share username

    It shows net helpmsg 1312.

    The network seems working, IP address is 192.168.0.74, and ping 192.168.0.135 is ok.

    :angel

    how to make net use work? thanks in advance.

  7. format a USB drive with NTFS, under vista 5308, and attach it under 5365 or later, cannot eject.(in system tray), and vise versa.

    5365: if a removable drive is empty(i.e. not one file on it. it's FAT format, so no "system volume information..." and $RECYCLE.BIN ect...), cannot open it with explorer.(messagebox appears: cannot access the \ directory).

    5456: cannot run lusrmgr.msc on the RUN menu.(messagebox: network path not found.)

  8. for ghost recover and fail to boot, can you describe in detail what happens when booting? have you seen some messages on the screen?

    it will be much better to apply ghost image to primary partitions, and if your WinPE rely on boot.ini, you need to modify it after ghost.

  9. I just made a HD boot, but not certain if it is a RAM-disk version.

    suppose \\harddisk1\partition1 is D:, then

    1. format D: /FS:NTFS /q

    2. c:\opk\tools\x86\bootsect /nt60 D:

    3. copy c:\opk\tools\x86\bootmgr D:\

    4. xcopy c:\opk\tools\x86\boot d:\ /s

    5. md d:\sources

    6. copy boot.wim d:\sources

  10. this could be a MBR problem, boot code is missing, so there's a blank screen.

    in DOS environment, there are lots of tools to fix the MBR, but the diskpart tool in WinPE..........seems to have no support.

    Try format drive C during windows installation.

  11. I have installed WinXP-64 professional but it cannot recognize the display adaptor, and in the Device Manager it says my display card is "Standard VGA",

    I have downloaded NVIDIA ForceWare Driver 81.98 but the Driver won't install,

    it says something like "cannot locate a driver for your display device...".

    The display card is GeForce2MX, in WinXP-32, it was recognized as "NV11".

    any ideas? thanks in advance.

×
×
  • Create New...