PXE Ramdisk Boot With Win2003 SP1, ISO Ramdisk virtual CD Options

[Metzen]

Does this method still work if my BartPE 3.12 ISO is 600MBs?

Microsoft set a hardlimit of 512MB for the ISO.

[kar]

My question was not relevant to this subject.

This post has been edited by kar: Apr 26 2005, 06:44 AM

[j.man]

Hi all,

I am using this method and have everything set up using Tftp32. I have the following options enabled on the TFTP server:
TFTP Security = Standard
Option negotiation (enabled)
PXE Compatibility (NOT enabled)
Use anticipation window: 256 bytes
Allow '\' as virtual root

My machine boots and starts to boot, only to return the error that my WINPE.ISO could not be loaded, reporting that "the error code is 16".

The TFTP server reports the following:
Read request for file <WINPE.ISO>. Mode octet
OACK: <blksize=1432,tsize=204763136,>
Peer returns ERROR <File too big> -> aborting transfer

My WINPE.ISO file is a hair below 200M. I am using MS's WINPE, but I this doesn't seem to me to be a version-related issue.

The "ntdetect.com," "ntldr" (renamed from setupldr.exe), etc. are all from the W2k3SP1 file.

Can anyone tell me why 200M is too large or how to adjust something to make this work?

Thanks,

Jacob
jacob@jvpiping.com
---

[kar]

Hi all,

I am using this method and have everything set up using Tftp32.  I have the following options enabled on the TFTP server:
  TFTP Security = Standard
  Option negotiation (enabled)
  PXE Compatibility (NOT enabled)
  Use anticipation window: 256 bytes
  Allow '\' as virtual root

My machine boots and starts to boot, only to return the error that my WINPE.ISO could not be loaded, reporting that "the error code is 16".

The TFTP server reports the following:
  Read request for file <WINPE.ISO>.  Mode octet
  OACK: <blksize=1432,tsize=204763136,>
  Peer returns ERROR <File too big> -> aborting transfer

My WINPE.ISO file is a hair below 200M.  I am using MS's WINPE, but I this doesn't seem to me to be a version-related issue.

The "ntdetect.com," "ntldr" (renamed from setupldr.exe), etc. are all from the W2k3SP1 file.

Can anyone tell me why 200M is too large or how to adjust something to make this work?

Thanks,

Jacob
jacob@jvpiping.com
---

The remote boot client needs at least 200MB (for the image) + 64MB (for WinPE itself) of RAM. In this situation 256MB might do, but it might also not.

How much WinPE requires of RAM is nothing I know for sure - it's something that is being said and recommended by others.

[getwired]

The limit you are hitting is one on your TFTP server, not your system. TFTP has an upper bound you have to break on many servers to get a WinPE image down. Consult your TFTP docs for more info on how to change it...

[manouman]

Hi,

I have a problem with this method.
After the loading into the Ramdisk, my machine displays "Please Wait..." then it displays an error message (blue screen).

This error is:

STOP: c000021a {Fatal System Error}
The Non-DLL file included in KnownDLL list. System process terminated unexpectedly with a status of 0xc000036f (0xe1131ec8 0x00000000)
The system has been shut down.

My settings are:
BartPE image (2003 SP1 rc1).
Booting on PXE with (winnt.sif, startrom.n12, NTLDR, NTDETECT.COM)

Any idea ?

[valexvo]

@ALL

Thanks for the posts in this topic.

After a few test I managed to boot the pebuilder.iso via network.

I wrote a small tutorial for those who don't have succeded until now . You can read it here , or here.

good luck

alex

[allens]

Hello All,

This is great work!
I have followed the instructions and have got the image to load into ramdisk.
BartPe then starts, with the white bar across the bottom of the the screen (very fast), I then get the BSOD Stop 0x0000007B error.

My iso is from XP Pro SP2, and I would like to try making an image from Win2003 SP1 RC1 to see if this is the cause of my error.

I am not sure how to build Bart PE with Win2003(Eval) SP1(RC1).
I have downloaded WindowsServer2003-KB889101-SP1-X86-ENU as described, and use startrom.com, ntdetect.com etc in my tftp root.

Can I make a W2003 RC1 bartpe version on a XP Pro SP2 machine?

Regards,

Stevea

[Macfox]

Check the ramdisk.sys version is the same as the Win2003 SP1. This version is needed as it support the RAM DISK boot. Previous version from Win2003 and XP don't.

You can use XP SP2. Just make sure your using the NTLDR NTDETECT.COM startrom.com and ramdisk.sys from Win2003 SP1.

It should work then.

Regards
Rob

[allens]

Thanks Macfox that worked !!!!

Here is my summary to get to work with a Win Pro XP SP2 iso made with bartpe v3.0.32
My server is Win2003 and I am using tftpd32 by ph.Jounin V2.80

I have added one extra step to give me a basic menu after the pxe boot, I'm trying to emulate my CDShell multiboot CD

I should add none of this work in mine, credit goes elsewhere, just hopeing this will stop others making the same errors I have. I have taken the liberty of repeating mainly Macfox's work just to get it in one place. Hope you don't mind.


1- On the server make a sub called (say) tftpboot

2- From Win2003 SP1 RC1 extract
NTDETECT.COM
setupldr.exe and rename NTLDR
STARTROM.COM
startrom.n12 renamed startrom.0 but pretty sure this does not matter
WINPE.ISO or whatever yours is called
winnt.sif as decsribed.

CODE

[SetupData]
BootDevice = "ramdisk(0)"
BootPath = "\i386\System32\"
OsLoadOptions = "/noguiboot /fastdetect /minint /rdexportascd /rdpath=<image>.iso"

and put in your server tftp root
If you get the wrong versions you are likely to get "ntdetect error"

3- From Win2003 SP1 PC1 extract
RAMDISK.SY_
RAMDISK.IN_

and replace your XP Pro SP2 source ie c:\XPPRO_SP2\I386.
My new files are dated 24/03/2005, my original XP Pro SP2 are 04/08/2004
This prevents the STOP 0x0000007B BSOD. Thanks to Macfox

4-If you use the QSoft Ramdisk plugin make sure RAMDRIV.SYS is version 5.2.10.2
It comes with BartPe (at least) V3.1.4
If you don't do this you lose your ramdrive when booted from ramdisk iso but ok when boot from CD etc. Thanks to Chris Woods http://www.911cd.net/forums//index.php?sho...382&#entry78382
Make new iso


5-If using tftpd32 by ph.Jounin (I'm using v2.80) , change settings, turn off PXE compatibility and turn on Option Negotiate. Try experimenting with Settings\use anticipation window of 256Bytes, to speed up download. This was from Metzen. This worked for me.

6-The next stage is based on sherpya and H. Peter Anvin work.
Instead of my dhcp service, "Server Options 067 Bootfile name" set to startrom,com. I set it to \tftpboot\pxelinux.0

Then make a new sub directory c:\tftp\pxelinux.cfg and in make a file called default.
I have a rudimentary menu including BartpE, which is run via startrom.0. This avoids the messy "select F12" message on the client.

CODE

default 1
display menu.txt
prompt 1

# hd
label 0
localboot 0x80
# floppy
label a
localboot 0x00
# cancel and try next boot device
label q
localboot -1

# menu.txt options
label 1
kernel memdisk
append initrd=images\60slxxx.ima

label 2
kernel memdisk
append initrd=dellbios\lat\c800.ima

label 3
kernel memdisk
append initrd=images\sa53bcmb.ima

label 4
kernel memtest

label 5
kernel STARTROM.0

This file loads the "menu" which is:

CODE


1f

EAF Menu Loader

At the boot prompt :
1 -> 60slxxx.img
2 -> C800 bios
3 -> System Analyser
4 -> Memtest
5 -> WinPe Wip

Note: The first digits are control codes, (eg clear screen) which I finally had to do with edit.com.
See here: http://syslinux.zytor.com/faq.php

If any one knows how to improve on this menu, I would be keen on learing.
This is the first linux type cfg file I have looked at.

Apologies if I have forgotten to credit the correct people. Please persevere this is worth having.

Regards,
Steve A

[jaclaz]

Note: The first digits are control codes, (eg clear screen) which I finally had to do with edit.com.

This:
http://members.chello.at/bobby100/

IsoLinux Mate (ILM) - Win32
I wrote this program to make writing of Isolinux/Syslinux messages easier.
Isolinux/Syslinux message files contains plain text and commands. All this can be done with any text editor, but ILM should make this easier and faster.
With ILM you can insert color commands, insert ASCII graphics with "not a real on-screen keyboard",  preview your work...

might be useful


jaclaz

[allens]

Hello all, again.
Just a quick update.

I was just completeing my TFTPF32 settings following to the tutor suggested by valexvo from caromet ? here and cannot set this option under settings of "Use Tftpd32 only on this interface".

CODE

Error can't bind BOOTP port!
Either you do not have the necessary privilage or a BOOTP daemon is already started or IP config has hanged.
Get last error 10048

Every thing is working OK, I do have the privilages, I can't find another BOOTP service and I don't think the IP has changed.

Interestingly, WIN.ISO still loads but I do not get any messages in the main Tftpd32 screen.

Any ideas

[Metzen]

Hi,

I have a problem with this method.
After the loading into the Ramdisk, my machine displays "Please Wait..." then it displays an error message (blue screen).

This error is:

STOP: c000021a {Fatal System Error}
The Non-DLL file included in KnownDLL list. System process terminated unexpectedly with a status of 0xc000036f (0xe1131ec8 0x00000000)
The system has been shut down.

My settings are:
BartPE image (2003 SP1 rc1).
Booting on PXE with (winnt.sif, startrom.n12, NTLDR, NTDETECT.COM)

Any idea ?

Edit the WinPE SYSTEM registry file (C:\winpe\i386\system32\setupreg.hiv).

Edit the hive as PESYSTEM

Edit HKLM\PESYSTEM\ControlSet001\Control\Session Manager\KnownDLLs and delete all entries except for "DLLDirectory"

This should resolve that problem.

[Turbo Donkey]

Edit the WinPE SYSTEM registry file (C:\winpe\i386\system32\setupreg.hiv).

Edit the hive as PESYSTEM

Edit HKLM\PESYSTEM\ControlSet001\Control\Session Manager\KnownDLLs and delete all entries except for "DLLDirectory"

This should resolve that problem.

How exactly do you edit the registry hive before or after you've built the image?

John

[Metzen]

How exactly do you edit the registry hive before or after you've built the image?

John

After you built the image (I assume it's the same for BartPE as it is for Windows PE).

START > Run > Regedit > File > Load Hive > choose HIVE > name it as PE_SYSTEM (or whatever) > edit hive accordingly.

[risky]

Hi everybody

This is my first post and hopefully one of many to follow.
My name is Dennis from South Africa < >

I have arrived here out of sheer frustration ...and hopefully lots more are in the same boat as me

!

I have been researching for months now and have come to realize that there is something missing in

our everyday lives as techies/computer entusiasts / experimenters and technologists ...!

All I want is clients that can boot themselves up and be controlled by a central server so their

drives can be cloned/imaged.
(There are a few unaffordable commercial utils that support this but they are far from efficient

and support is an issue! And as soon as there is a good one, does it get bought out ?)

It seems there are very few tools and software or application available that can perform a very

simple task(s).
These tasks are as follows :
1.Client must boot from PXE/Network <<no problem now since most BIOS and NIC's have PXE option
2.A tftp boot server delivers the file <<Great found many a TFTP boot server TFTP32 by JOUNIN is

awesome (there were a few hassles but all is well now!
3.For the Bootrom (I think!) I was using BPBATCH which worked well but only supports 1,44 images

<<very limiting
And then a miracle happened, Microsoft released Win2k3 SP1 which allows a PE iso to be loaded into

ram across the network ..with modification to winnt.sif
AWESOME!! Bart PE is just perfect for this operation
4. The cloning utility ??? Now this is the PROBLEM What is best ?
Some only work from DOS
Others only work from within Windows and those that work in Windows don't allow themselves to be

controlled by a central server for disk cloning.

SO here's the request ...
Does anyone out there have a solution ? If not how many are keen to start a project to get it

going and perhaps be able to offer a solution ?

Hope I get some sensible replies ....
Dennis

[Macfox]

Take a look at Ghost32 and the ghostcast server.

You make and ISO to boot WinPE, then into ghost connect the ghostcast server session and wait for a image to be sent. From the server console, you then just kick off the image DL and it deploys to every PC in that session.

I've done this for a few mass deployments and it has saved considerable time.

Rob

[risky]

Take a look at Ghost32 and the ghostcast server.

You make and ISO to boot WinPE, then into ghost connect the ghostcast server session and wait for a image to be sent. From the server console, you then just kick off the image DL and it deploys to every PC in that session.

I've done this for a few mass deployments and it has saved considerable time.

Rob

Hey Rob
Thanks for the reply ...
I have had a look at ACRONIS ... it bombs with some issue about a license server !! And it's a trial version ...
Will check out GHOST32 << do I just add this to my BartPE/WinPE cd and then make it autoexecute ?
I found when I used ghost for dos (corporate) and launched the boot disk off PXE, everytime it would hang at the startup screen with a mouse cursor :-( <<combed the web for answers but found none !! (That was ghost version *.0 corporate trial!)

It seems like there are no decent products out there to achive my goals !!
PS I am a firm believer in fast efficient and free software! If I pay for it , it must really be awesome ...so far there is nothing outrageous ... and presently I am looking into IBM/Powerquest products ...
Any comments?
Dennis

[Macfox]

Hey Rob
Thanks for the reply ...
I have had a look at ACRONIS ... it bombs with some issue about a license server !! And it's a trial version ...
Will check out GHOST32 << do I just add this to my BartPE/WinPE cd and then make it autoexecute ?
I found when I used ghost for dos  (corporate) and launched the boot disk off PXE, everytime it would hang at the startup screen with a mouse cursor :-( <<combed the web for answers but found none !! (That was ghost version *.0 corporate trial!)

It seems like there are no decent products out there to achive my goals !!
PS I am a firm believer in fast efficient and free software! If I pay for it , it must really be awesome ...so far there is nothing outrageous ... and presently I am looking into IBM/Powerquest products ...
Any comments?
Dennis

I can quote on the Acronis, but Symantec have bought out Powerquest Partition magic to replace ghost.

Yes, just set Ghost32 to load a startup with the required command line. Ghost32 has a few command line options. Most relevant is the session switch. This tells ghost32 which session to listen for and connect to.

GHOST32.EXE -ja=%MCSESSIONNAME% -jm=%MCMODE% -quiet -sure

MCmode = m | d | u (Multicast/direct broadcast/Unicast)

FYI the Ghostcast session must be running before hand.

[mace]

Ghost will do it, so will the command line version of Driveimage,pqideploy to.

we are using PE and PQIdeploy to PXE boot and deploy Xp images to about 19K Client boxes