Jump to content

Test Zero

Member
  • Posts

    55
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United Kingdom

Posts posted by Test Zero

  1. Here's my boot.ini file:

    [boot loader]timeout=30

    default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS

    [operating systems]

    multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windows XP" /FASTDETECT

    multi(0)disk(0)rdisk(0)partition(3)\ntldr\SETUPLDR.BIN="Windows PE"

    When I boot into Windows PE, I get the error:

    Windows could not start because file is missing or corrupt:

    <Windows root>\system32\ntoskrnl.exe

    Please re-install a copy of the file.

    There are no files called ntoskrnl.exe on my Windows PE partition, but my Windows PE CD boots up fine.

    Could someone give me a hand with this? :)

  2. I'm trying to get Windows PE running with the explorer.exe shell. This doesn't work with BartPE and so the only way I can get a copy of Microsoft's Windows PE is by using Longhorn Setup's. So I'm trying to get Longhorn's WinPE working properly. At the moment, I'm running in to problems with it.

    Unless there's a way I can get the Windows PE files of Windows 2000 or Windows XP Home? :)

  3. I'm having a go using the version of Windows PE that Longhorn 4053's Setup uses.

    I ran Longhorn's \SOURCES\SETUP.EXE in Windows XP. This copies the installation files from \SOURCES\INSTALL.WIM to C:\$WINDOWS.~BT

    Setup then reboots the computer.

    C:\$WINDOWS.~BT\BOOTSECT.DAT boots up, which launches Windows PE.

    C:\$WINDOWS.~BT\system32\winpeshl.exe launches. Hex edit this file:

    hexedit.png

    winpeshl.exe launches C:\$WINDOWS.~BT\system32\startnet.cmd and then C:\$WINDOWS.~BT\Sources\SETUP.EXE and then finally reboots the computer.

    factory -winpe

    This sets the screen resolution and then installs network components.

    SETUP.EXE should then load. However, I deleted this file beforehand. netstart.cmd's command prompt window stays on-screen. However, when this window is closed, winpeshl.exe restarts the computer because it thinks that SETUP.EXE has finished installing Longhorn (when it actually hasn't, because it doesn't even exist).

    I'm going to have a play with this; see if I can stop winpeshl.exe from rebooting, and see if it's possible to add Explorer to this. If anyone could point me in the right direction, please give me a hand with this. :) I'll let you know if I find out how to get this going properly.



×
×
  • Create New...