Jump to content

joakim

Member
  • Posts

    153
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    Norway

Everything posted by joakim

  1. Adding Norton Ghost 14 or Symantec Backup Exec 8.5.3 is not much of a problem to add to a PE. But it will increase the size of your disk with a couple of hundred Mb's.. It also depends on dotnet 2. For that reason you may want to just hotplug it to a running PE, instead of rebuilding your bootdisk. Some call this LODR (Load On Demand Ready). Hotplugging dotnet 2 to a running PE is also possible. http://www.boot-land.net/forums/index.php?showtopic=7825 For questions about the package: they will only be answered here! Joakim
  2. It is the setup loader that loads "PE" on nt5.x. The /minint only means "read-only registry". You can add /minint to boot.ini and have read-only registry!! Kernel and hal can be specified in each respective config file for setupldr.bin and ntldr. Setupldr.bin load setupreg.hiv while ntldr load system, then kernel and hal will be executed, and then kernel will load rest of boot configured drivers. You can verify the order by adding /sos or attaching a debugger (ie remove setupreg.hiv while booting setupldr.bin and see what happens). You don't need to reference kernel/hal in setupreg.hiv/system. Joakim
  3. These two version are not identical. Question 1: Is there any functional difference between them? I am asking because I can ramboot "Universal" XP without boot.ini/ntldr/ntdetect.com, by using bootmgr/winload.exe. It works for versions up to and including Vista and makes no difference wether system32\winload.exe or system32\boot\winload.exe is used as osloader. Look here for wimbooting diskless xp; http://sanbarrow.com/phpBB2/viewtopic.php?t=1695 (faster network transfer because of high compression - 550 Mb >> 220 Mb) Question 2: Is there a known way of forcing winload.exe to read txtsetup.sif, as in PE. Question 3: Is winload.exe even supposed to handle NT5.x PE? You can sure enough set "winpe yes" in BCD, but the only effect is that systemdrive is mapped to X:\, with winload.exe still seeking after config\system without reading txtsetup.sif (and non-volatile hives loaded to ram). Joakim
×
×
  • Create New...