Pe On A Hd, need to put PE on a HD Options

[cryton2707]

Hi

Im needing to install PE onto a HD partition.. Ive used the FAQ on www.nu2.nu to make a recovery console PE and that boots fine.. But I need to put PE on its own hard disk (partition) without having XP already installed (as per the recovery console method) and get the partition to boot the PE.. (not from CD but from the HD)

But I cant get the PE to boot.. it keeps just hanging the workstation when trying to boot from the HD.

Can anyone help!?!?!


Thanks

[Former_enigma06_post]

Who step are you following?

1. xcopy CD:\i386\ C:\Minint /S
2. xcopy "Documents and Settings" C: /s
3. xcopy "Programs" C: /s
4. Copy i386\Ntdetect.com to the root of the hard drive
4. On the destination hard disk, copy C:\Minint\setupldr.bin to C:\ntldr

Did you miss any steps?

[mmeierbier]

If you've done all the above mentioned steps correctly, you should check on your plugins. Did the vesion you installed to hd work from cd on the same machine?
Try disabling all plugins and install again, if it works, enable the plugins one by one.
Personally. I had difficulties with a network driver when starting from hd.

Hoping to be of help,
Manfred

[cryton2707]

thanks working now

Id missed

4. On the destination hard disk, copy C:\Minint\setupldr.bin to C:\ntldr

Ta

[cyberkid]

Hi,
I'm trying to achieve booting from a separate partion as well, using the ntloader.
same disk, just a different partition.

I,ve followed the above steps and I get a partial boot, but it stops at an error:

<Windows root>\system32\ntoskrnl.exe missing or corrupt.

Now the file in PE has a different name: ntkrnlmp.exe, whether it's relevant.

My question to you guys who have got this to work is, how??
What do I do next?

CK.

[Bart Lagerweij]

@cryton2707

Boot from the winpe cd and run script "pe2hdd.cmd" below.
Be carefull! On an existing system it wipes the entire harddisk!!!!

pe2hdd.cmd

CODE

@echo on
diskpart.exe /s "%~dpn0.scr"
if errorlevel 1 goto _abort
format c: /fs:ntfs /v:winpe /q
if errorlevel 1 goto _abort
rem Copying files...
xcopy /s %systemdrive%\i386\*.* c:\minint\
if errorlevel 1 goto _abort
xcopy /s %systemdrive%\programs\*.* c:\programs\
if errorlevel 1 goto _abort
copy c:\minint\ntdetect.com c:\
if errorlevel 1 goto _abort
copy c:\minint\setupldr.bin c:\ntldr
if errorlevel 1 goto _abort
echo.
pause
goto _end
:_abort
echo.
echo [Aborted...]
pause
:_end

pe2hdd.scr

CODE

select disk 0
clean
create partition primary
active
assign letter=c
exit

Bart.

[Bart Lagerweij]

Created a plugin for it...
http://www.nu2.nu/pebuilder/pecd2hd.zip

USE AT OWN RISK!

You should run the p2cd2hd install script on a testing machine!!!

Bart.

[airburst]

@Bart

I ran your script to install pe to hard drive; it seemed to work flawlessly. However, when I rebooted I got the error message "bad or missing ntldr".

The system was running in Virtual PC. Has anyone else had this problem?

[Bart Lagerweij]

@airburst

Try on a real system...

Bart.

[Xephion]

@airburst
I have used Bart's p2cd2hd script in Virtual PC and it worked fine for me. Check your installation - must be something wrong on your side.

[don03]

Hi,

in VMWARE it works fine too. :-)

don03

[darthyoda6]

Agreed, no problems with VMware 4.

[airburst]

Thanks all - I rebuilt with v 3.0.22 and it does work fine. Nice job.

[cdob]

Reactivate old thread...

I don't want PE at c:, I like to use a separate partition.

I'm using a 160 gb hard disk, connected to a Promise Ultra100TX2. I created another primary partition at end of disk, start sector is after 128 gb. After testing, all data still exist

Next I copied BartPE files to this new partition x:, compare enigma06 infos, thanks.

I can boot with several boot managers, e.g. Smart Boot Manager http://btmgr.sourceforge.net/

Another task is using the existing NT boot loader. Finally I got:

c:\>bootpart 7 bartpe BartPE

Boot Partition 2.50 for WinNT/2K/XP ©1995-2002 G. Vollant (info@winimage.com)
WEB : http://www.winimage.com and http://www.winimage.com/bootpart.htm
Add partition in the Windows NT/2000/XP Multi-boot loader

Physical number of disk 0 : 40478e1f
0 : C:* type=7  (HPFS/NTFS), size= 12289693 KB, Lba Pos=63
...
7 : C:  type=7  (HPFS/NTFS), size= 16876282 KB, Lba Pos=278824140

Writing a boot sector using LBA position 278824140 (0x109e84cc)
C:\bartpe written
C:\BOOT.INI updated

c:\boot.ini

C:\bartpe="BartPE"

Active partition on my hard disk is a NTFS primary partition.

Now I don't need a additional boot manager anymore, just NT boot loader: c:\ntldr reads c:\boot.ini and I choose BartPE and BartPE works.

[Cqz]

I have just discovered what I think is a simpler way to boot pe from C: and still keep the volume letter as C: when pe is run. Harddisk installation is using the normal peinst.cmd from pebuilder3.1.3.

Please see this new thread for details.
http://www.911cd.net/forums/index.php?act=...ST&f=20&t=11206

[stuartr]

I have just discovered what I think is a simpler way to boot pe from C: and still keep the volume letter as C: when pe is run.  Harddisk installation is using the normal peinst.cmd from pebuilder3.1.3.

Please see this new thread for details.
http://www.911cd.net/forums/index.php?act=...ST&f=20&t=11206

I noticed that if you want the bootable image stored in a root named anything other than "minint", the existing configuration won't work because this value is hardcoded into setupldr.bin. I presume editing this file would be required?

[Wendy]

Another thing you have to keep an eye out for is if there are stray txtsetup.inf files in the root directory: bartpe and winpe are after all pre-install environments, and will process these before any minint directory.

[stuartr]

Another thing you have to keep an eye out for is if there are stray txtsetup.inf files in the root directory: bartpe and winpe are after all pre-install environments, and will process these before any minint directory.

Hmmm... are you saying that the txtsetup.inf file that gets created by PELoader shouldn't be copied to the target disk that you want bootable?

[Wendy]

I had problems where c:\txtsetup.inf is created by the win2k install under bartpe, but not removed.

BartPE then reads it and gives strange messages about $WIN_NT$.~BT directory.

None the same, i don't have any txtsetup.inf, and bartpe boots quite nicely. I don't think that bartpe has a txtsetup.inf file in the root directory at all anyway.

W

[stuartr]

I had problems where c:\txtsetup.inf is created by the win2k install under bartpe, but not removed. 

BartPE then reads it and gives strange messages about $WIN_NT$.~BT directory.

None the same,  i don't have any txtsetup.inf, and bartpe boots quite nicely.  I don't think that bartpe has a txtsetup.inf file in the root directory at all anyway.

W

Sorry... my brain was thinking txtsetup.sif and not txtsetup.inf. You're right, there isn't a txtsetup.inf on the build.