Yes I followed the instructions as above. I used pebuilder 3032
The option I had turned on were
Barts free stuff
Check Disk
Customize
Network Support [partpe/penetcfg]
Network Support [partpe/penetcfg] [Auto-start]
Intel PRO 100/1000 Apadtor Drivers
Nu2Menu
PuTTY
Startup Group
TightVNC Viewer
Did you slipstream/merge your Win2003 with the SP1 RC1 correctly. Other than that I don't know. Sorry
Have you tried the HAL compatability modes. F6 I think at the load screen. Like safe mode. You can turn off ACPI etc.
Rob
Full Version: PXE Ramdisk Boot With Win2003 SP1
I believe I have, I installed SP1 on the Server 2003 box, and I used the integrate switch to place the files in the I386 directory. THat is how you are suppose to do it correct?
Does anyone have an ISO they have created that is working for them that I could try? I have tried everything, and I would like to know if it is how I am building the ISO or if it is the hardware I am trying to run it on.
QUOTE (alpay @ Dec 16 2004, 05:56 PM)
@androidtopp
Not sure if the stuff you're talking about is the same issues discussed here... maybe a seperate post would get you the help you're looking for faster?
@dicht
i did a little hunting and found out that versions of NTDETECT.COM from XP and later, need BOOTFONT.BIN, it's has something to do with the font used during the initial boot. maybe international too...
anyway, it's halting my boot process, I cannot find it, compressed or otherwise on my cd's. any suggs on this?
Not sure if the stuff you're talking about is the same issues discussed here... maybe a seperate post would get you the help you're looking for faster?
@dicht
i did a little hunting and found out that versions of NTDETECT.COM from XP and later, need BOOTFONT.BIN, it's has something to do with the font used during the initial boot. maybe international too...
anyway, it's halting my boot process, I cannot find it, compressed or otherwise on my cd's. any suggs on this?
BOOTFONT.BIN error is due to tftpd32.
you should not select the option 'pxe compatible'
i'm able to get the iso booted, but after the progress bar showing 'bart pe', i get a blue screen for winxpsp2 & win2k3. i'll try win2k3sp1 tonight
I have been having the same problem with Win 2003 SP1 as well. Please let me know if you hear of a solution for this.
I've been having problems pxe-booting WinPE from a Linux server.
Most of the files get transferred, and the client screen displayed: "Setup is inspecting your computer's hardware configuration...".
However, then it displayed "NTDETECT failed". Not so good.
I looked at the log file for my atftpd server, and there were some entries there that look like the below:
Jan 20 17:09:35 rct tftpd[8954]: received ACK <block: 515>
Jan 20 17:09:35 rct tftpd[8954]: sent DATA <block: 516, size 512>
Jan 20 17:09:35 rct tftpd[8954]: received ACK <block: 516>
Jan 20 17:09:35 rct tftpd[8954]: sent DATA <block: 517, size 0>
Jan 20 17:09:35 rct tftpd[8954]: received ACK <block: 517>
Jan 20 17:09:35 rct tftpd[8954]: End of transfer
Jan 20 17:09:35 rct tftpd[8954]: Server thread exiting
Jan 20 17:09:35 rct tftpd[8970]: Serving BOOTFONT.BIN to 10.100.191.1:60687
Jan 20 17:09:35 rct tftpd[8970]: received RRQ <filename: BOOTFONT.BIN, mode: octet, tsize: 0>
Jan 20 17:09:35 rct tftpd[8970]: tsize option -> 30
Jan 20 17:09:35 rct tftpd[8970]: sent OACK <tsize: 30>
Jan 20 17:09:35 rct tftpd[8970]: received ERROR <code: 8, msg: Bad TFTP options>
Jan 20 17:09:35 rct tftpd[8970]: Aborting transfer
Jan 20 17:09:35 rct tftpd[8970]: Server thread exiting
Jan 20 17:09:35 rct tftpd[8971]: Serving ntdetect.com to 10.100.191.1:60688
Jan 20 17:09:35 rct tftpd[8971]: received RRQ <filename: ntdetect.com, mode: octet, tsize: 0>
Jan 20 17:09:35 rct tftpd[8971]: tsize option -> 47548
Jan 20 17:09:35 rct tftpd[8971]: sent OACK <tsize: 47548>
Jan 20 17:09:35 rct tftpd[8971]: received ERROR <code: 8, msg: Bad TFTP options>
Jan 20 17:09:35 rct tftpd[8971]: Aborting transfer
Others have discussed the fact that BOOTFONT.BIN is being requested. Here too, BOOTFONT.BIN is being requested for download. However, I'm guessing that if it's not present, then the process will go on. I even put together a dummy BOOTFONT.BIN file. The problem wasn't it's presence or absence, but the fact that my tftp server looks like it had problems with the transfer (same for ntdetect.com).
So what I'm thinking is that something's wrong with my tftp server. I'm using Debian atftpd version 0.6.2. Can someone who has this setup working please tell me which particular tftp service you're using and it's version. I think that's the source of my problems.
Thanks in advance for any help.
Rick
Most of the files get transferred, and the client screen displayed: "Setup is inspecting your computer's hardware configuration...".
However, then it displayed "NTDETECT failed". Not so good.
I looked at the log file for my atftpd server, and there were some entries there that look like the below:
Jan 20 17:09:35 rct tftpd[8954]: received ACK <block: 515>
Jan 20 17:09:35 rct tftpd[8954]: sent DATA <block: 516, size 512>
Jan 20 17:09:35 rct tftpd[8954]: received ACK <block: 516>
Jan 20 17:09:35 rct tftpd[8954]: sent DATA <block: 517, size 0>
Jan 20 17:09:35 rct tftpd[8954]: received ACK <block: 517>
Jan 20 17:09:35 rct tftpd[8954]: End of transfer
Jan 20 17:09:35 rct tftpd[8954]: Server thread exiting
Jan 20 17:09:35 rct tftpd[8970]: Serving BOOTFONT.BIN to 10.100.191.1:60687
Jan 20 17:09:35 rct tftpd[8970]: received RRQ <filename: BOOTFONT.BIN, mode: octet, tsize: 0>
Jan 20 17:09:35 rct tftpd[8970]: tsize option -> 30
Jan 20 17:09:35 rct tftpd[8970]: sent OACK <tsize: 30>
Jan 20 17:09:35 rct tftpd[8970]: received ERROR <code: 8, msg: Bad TFTP options>
Jan 20 17:09:35 rct tftpd[8970]: Aborting transfer
Jan 20 17:09:35 rct tftpd[8970]: Server thread exiting
Jan 20 17:09:35 rct tftpd[8971]: Serving ntdetect.com to 10.100.191.1:60688
Jan 20 17:09:35 rct tftpd[8971]: received RRQ <filename: ntdetect.com, mode: octet, tsize: 0>
Jan 20 17:09:35 rct tftpd[8971]: tsize option -> 47548
Jan 20 17:09:35 rct tftpd[8971]: sent OACK <tsize: 47548>
Jan 20 17:09:35 rct tftpd[8971]: received ERROR <code: 8, msg: Bad TFTP options>
Jan 20 17:09:35 rct tftpd[8971]: Aborting transfer
Others have discussed the fact that BOOTFONT.BIN is being requested. Here too, BOOTFONT.BIN is being requested for download. However, I'm guessing that if it's not present, then the process will go on. I even put together a dummy BOOTFONT.BIN file. The problem wasn't it's presence or absence, but the fact that my tftp server looks like it had problems with the transfer (same for ntdetect.com).
So what I'm thinking is that something's wrong with my tftp server. I'm using Debian atftpd version 0.6.2. Can someone who has this setup working please tell me which particular tftp service you're using and it's version. I think that's the source of my problems.
Thanks in advance for any help.
Rick
At first glance, it maybe a pathing problem. Ie the DOS v's UNIX path delimiters. / or \
perhaps install ethereal or use tcpdump to capture the raw TFTP and have a look at the full paths requested. It will also likely show the real error that is occuring during the transfer.
Rob
perhaps install ethereal or use tcpdump to capture the raw TFTP and have a look at the full paths requested. It will also likely show the real error that is occuring during the transfer.
Rob
Seems like the same problem I was having... Unfortunately, I think I hit the limit of what I can do with my technical skills so I'm eager to know if you get over this obstacle. Keep us informed! thanks.
Alpay
Alpay
I created a specific topic regarding BartPe in RAM and all the tecniques avaible. ATM it does not cover PXE but I will integer in the weekend, please post there any other q and A.
I also have been experimenting with this method but under diffrent circumstances, and im wonderifn if any1 else has figured this out. Im using winpe 2k5 and I have it loading my winpe iso into ram using the /rdexportascd method. What I would like to do is 1 of 2 things, and dosent matter to me either way. Make the ISO that it loads to RAM Writable, thus flushing all changes on reboot, but being able to edit whats loaded, which I would prefer. I tried to change the method of boot in teh winnt.sif to /rdexportashd just for fun and it went but it got a blue screen so I think maybe it might be a valid command ? I dunno cause it went thru the loading to ramdisk part but blue screened after that I was thinking if I changed my winpe it might work. Or I need to be able to create a RAM drive inside of the RAM disk or in additon to the RAM disk to have as a writable partition for some minimum file editing. Before I would have my winpe load from cd to drive x: and then make a drive Z: that was a 64 or 32 er whatever ramdsrive for reading and writing files. I am wondering and I have only tried a little if I can just add that method to the ramdrive method or if im going to hafta figure out a way to make the iso it loads writable. Any Input on this ?
maybe BCDW can memdisk such image?
I was wondering, is it possible to create some sort of menu where I can select different iso images to boot from???
This network boot is great, but I would like to choose between ERD Commander, Ghost disk, WinPELab, WinPEDeploy, etcetc
Regards, Michiel
This network boot is great, but I would like to choose between ERD Commander, Ghost disk, WinPELab, WinPEDeploy, etcetc
Regards, Michiel
Hi all,
I have just tested booting my iso (builded from Win2003 SP1 RC1 / WinPE 2005) from PXE
I did all steps as written in the initial post. The ntdetect.com and startrom.com was taken from the RC1 CD (Beta 1289) STARTROM.CO_, NTLDR is a renamed SETUPLDR.EX_
And this is the winnt.sif
I am running a W2K Server SP4 with DHCP and DNS. The tftp service is running properly and I also tested PXE with our old Boot Loader and there is no error.
WinPE doesn't start, after i recived an IP, Mask and a Gateway there is only a blinking curser.
Anybody has an idea?
I have just tested booting my iso (builded from Win2003 SP1 RC1 / WinPE 2005) from PXE
I did all steps as written in the initial post. The ntdetect.com and startrom.com was taken from the RC1 CD (Beta 1289) STARTROM.CO_, NTLDR is a renamed SETUPLDR.EX_
And this is the winnt.sif
QUOTE
[SetupData]BootDevice="ramdisk(0)"
BootPath="\i386\System32\"
OsLoadOptions = "/noguiboot /fastdetect /minint /rdexportascd /rdpath=winpe.iso"
BootPath="\i386\System32\"
OsLoadOptions = "/noguiboot /fastdetect /minint /rdexportascd /rdpath=winpe.iso"
I am running a W2K Server SP4 with DHCP and DNS. The tftp service is running properly and I also tested PXE with our old Boot Loader and there is no error.
WinPE doesn't start, after i recived an IP, Mask and a Gateway there is only a blinking curser.
Anybody has an idea?
Has anyone successfully used pxelinux with memdisk to load pe2k5? It seems like it should be possible with the .com support, and I'd like to have all my boot options in the pxe menu.
@Macfox
I am newbie to this forum. In your first post, you mentioned that "It's
also possible to load the ISO images from CD/HD/USB also with the right
winnt.sif and ARC path options". Can you please describe the steps to
achieve this.
Do you mean boot from the CD and use the ISO file? I have a WinPE ISO
image from Win2003. I would like to boot through the CD and load the
WinPE ISO image into RAM. So that we could remove the CD and use the CD
drive for other purposes (like data backup, restore to and from the CD).
Any help would be appreciated! Thanks.
I am newbie to this forum. In your first post, you mentioned that "It's
also possible to load the ISO images from CD/HD/USB also with the right
winnt.sif and ARC path options". Can you please describe the steps to
achieve this.
Do you mean boot from the CD and use the ISO file? I have a WinPE ISO
image from Win2003. I would like to boot through the CD and load the
WinPE ISO image into RAM. So that we could remove the CD and use the CD
drive for other purposes (like data backup, restore to and from the CD).
Any help would be appreciated! Thanks.
Things are running smooth with our install -- now one last hurdle to get over. TFTP is working flawlessly and my only bump in the road now is getting the download to go faster. Is there a way to speed up the download from the TFTP server? The only hurdle that I want to have is the line speed -- the majority of the systems that we deploy come with a minimum of 512MB....normal systems have 1GB.
My winnt.sif looks like this:
[SetupData]
BootDevice = "ramdisk(0)"
BootPath = "\i386\System32\"
OsLoadOptions = "/fastdetect /minint /nogui /inram /rdexportascd /rdpath=winpe.iso"
Do I need to increase my ramdisk? I don't believe that is the issue here....is it something with the TFTP configuration that is limiting what/how much is being downloaded to the client? Anyone have any knowledge on this item? CD installs work without and issue and works very well, but we want to automate distribution of systems by using PXE and not having our engineers carry around CD's with them : deploying 3-4 systems a day at one given time.
Thanks for any input.
My winnt.sif looks like this:
[SetupData]
BootDevice = "ramdisk(0)"
BootPath = "\i386\System32\"
OsLoadOptions = "/fastdetect /minint /nogui /inram /rdexportascd /rdpath=winpe.iso"
Do I need to increase my ramdisk? I don't believe that is the issue here....is it something with the TFTP configuration that is limiting what/how much is being downloaded to the client? Anyone have any knowledge on this item? CD installs work without and issue and works very well, but we want to automate distribution of systems by using PXE and not having our engineers carry around CD's with them : deploying 3-4 systems a day at one given time.
Thanks for any input.
TFTP is not the most efficient protocol if it comes to thruput. It's a simple protocol without the transport features of FTP - the T stands for trivial. The only you can do is to optimize the network interface, means 100 or better 1000 MBit/s and Full-Duplex on both sides and on the way between them.
SAM
SAM
Well, I understand the TFTP server you choose has alot to do with speed. for instance, some french dude's homebrew tftp server app (forget the name, i think it's mentioned elsewhere in this thread) was way faster than the Intel one which seems to be of standard use. it takes very little effort to grab another tftp server, try and see if it improves your speed.
Sam : we are already configured at 100Full on our network so that isn't the issue. Throwing the coin at 1000MB dont' think will solve the problem sense we went from 10 to 100 and saw ZERO performance improvement with bringing the image down. I believe the problem is with the TFTP and image size. alpay : I will look at WinAgents and a few others for their TFTP servers and report back if I find a difference in their distribution vs. the standard that we speak of in this topic.
Does this method still work if my BartPE 3.12 ISO is 600MBs?
As I get an error when loading the ramdisk image ERROR CODE 16. tftp32 2.80 says something about a file being too big, thought it might be the fact that my ISO is 600MB.
MrXP
As I get an error when loading the ramdisk image ERROR CODE 16. tftp32 2.80 says something about a file being too big, thought it might be the fact that my ISO is 600MB.
MrXP
It looks like its a limit to the ramdisk driver and kernal from 2003 sp1. looks like its the block size. need to be able to change the size maybe, since tftp is so limited. Maybe we can use FTP with PXE to boot a WinE ISO image!
maybe its not posible.
mrxp
maybe its not posible.
mrxp
Uh, no. TFTP is a core component of PXE. You can't replace it with another protocol.
Is there a step-by-step or how to written on this?
Any one up for writing one?
Trying to piece all the details togehter from several pages of posts is a little frustrating.
I've never used RIS (although I'm vaguly familur with what it does) nor have I used PXE, however this sounds really cool and I'd love to try it out.
>Graxx
Any one up for writing one?
Trying to piece all the details togehter from several pages of posts is a little frustrating.
I've never used RIS (although I'm vaguly familur with what it does) nor have I used PXE, however this sounds really cool and I'd love to try it out.
>Graxx
The documentation that comes with WinPE fully explains how to do this. Consult your copy.
Hi Guys,
Anybody have tested to boot WinPE 2003 SP1 in RAMdisk with the Intel PXE server?
Because I can specified or create the boot file *.0 and *.1. Nothing start. I miss understand something, but I don't know what.
Regards
Lezuff
Anybody have tested to boot WinPE 2003 SP1 in RAMdisk with the Intel PXE server?
Because I can specified or create the boot file *.0 and *.1. Nothing start. I miss understand something, but I don't know what.
Regards
Lezuff
Hi All,
After much difficultly I've got this running from *nix servers.
What are the secrets?
1. ntldr needs to be NTLDR
2. the name of the iso has to be fully capitalised eg. WINPE.ISO
3. startrom.com needs to called startrom.0
An added tip is to use startrom.n12 instead of startrom.com as it doesn't ask for F12 to be pressed.
Cheers,
Richard
After much difficultly I've got this running from *nix servers.
What are the secrets? 1. ntldr needs to be NTLDR
2. the name of the iso has to be fully capitalised eg. WINPE.ISO
3. startrom.com needs to called startrom.0
An added tip is to use startrom.n12 instead of startrom.com as it doesn't ask for F12 to be pressed.
Cheers,
Richard
QUOTE (WinPE_bla @ Feb 4 2005, 04:11 PM)
Hi all,
I have just tested booting my iso (builded from Win2003 SP1 RC1 / WinPE 2005) from PXE
I did all steps as written in the initial post. The ntdetect.com and startrom.com was taken from the RC1 CD (Beta 1289) STARTROM.CO_, NTLDR is a renamed SETUPLDR.EX_
And this is the winnt.sif
[SetupData]
BootDevice="ramdisk(0)"
BootPath="\i386\System32\"
OsLoadOptions = "/noguiboot /fastdetect /minint /rdexportascd /rdpath=winpe.iso"
WinPE doesn't start, after i recived an IP, Mask and a Gateway there is only a blinking curser.
Anybody has an idea?
I have just tested booting my iso (builded from Win2003 SP1 RC1 / WinPE 2005) from PXE
I did all steps as written in the initial post. The ntdetect.com and startrom.com was taken from the RC1 CD (Beta 1289) STARTROM.CO_, NTLDR is a renamed SETUPLDR.EX_
And this is the winnt.sif
QUOTE
[SetupData]
BootDevice="ramdisk(0)"
BootPath="\i386\System32\"
OsLoadOptions = "/noguiboot /fastdetect /minint /rdexportascd /rdpath=winpe.iso"
WinPE doesn't start, after i recived an IP, Mask and a Gateway there is only a blinking curser.
Anybody has an idea?
I have the same problem as the quote, only on the server it says that it has successfully transfered the startrom.com and the NTLDR and then sits there doing nothing.
Is there anyone that can help me out, maybe it is my files I took them from W2k3 sever SP1.
I'm also running this on w2k sp1 server with tftp32.
Joe
Use the inbuilt TFTP Server that comes with windows.
This inf file show work for Win2003 as well
Please post the file sizes and the placement of the files if your still having issues.
Rob
This inf file show work for Win2003 as well
CODE
; TFTPD.INF
;
; Setup for the TFTP service of Windows 2000
;
; Copyright (c) 2000-2003, Stefan Kanthak <skanthak@nexgo.de>
[Version]
Class = System
InfVersion = "01.00.00"
LayoutFile = LAYOUT.INF
Provider = "Stefan Kanthak"
SetupClass = BASE
Signature = "$Windows NT$"
[DefaultInstall.NTx86]
AddReg = TFTPD.Install.AddReg
CopyFiles = TFTPD.Files.Inf,TFTPD.Files.Sys
DelFiles = TFTPD.Files.Pnf
Reboot
[DefaultInstall.NTx86.Services]
AddService =
"%TFTPD*Key%",%SPSVCINST_ASSOCSERVICE%,TFTPD.Service,TFTPD.EventLog
[DefaultUninstall.NTx86]
DelFiles = TFTPD.Files.Inf,TFTPD.Files.Pnf,TFTPD.Files.Sys
DelReg = TFTPD.Remove.DelReg
Reboot
[DefaultUninstall.NTx86.Services]
DelService = "%TFTPD*Key%",%SVCINST_DELETEEVENTLOGENTRY%
[TFTPD.Install.AddReg]
HKLM,"Software\Microsoft\Windows\CurrentVersion\Uninstall\%TFTPD*Key%","DisplayName",,"%TFTPD*Description%"
HKLM,"Software\Microsoft\Windows\CurrentVersion\Uninstall\%TFTPD*Key%","DisplayVersion",,"%TFTPD*Version%"
HKLM,"Software\Microsoft\Windows\CurrentVersion\Uninstall\%TFTPD*Key%","HelpLink",,""
HKLM,"Software\Microsoft\Windows\CurrentVersion\Uninstall\%TFTPD*Key%","InstallLocation",,"%11%"
HKLM,"Software\Microsoft\Windows\CurrentVersion\Uninstall\%TFTPD*Key%","InstallSource",,"%01%"
HKLM,"Software\Microsoft\Windows\CurrentVersion\Uninstall\%TFTPD*Key%","Publisher",,"%TFTPD*Author%"
HKLM,"Software\Microsoft\Windows\CurrentVersion\Uninstall\%TFTPD*Key%","UninstallString",,"%11%\RunDll32.Exe
%11%\SetupAPI.Dll,InstallHinfSection DefaultUninstall.NTx86 4
%17%\TFTPD.Inf"
HKLM,"Software\Microsoft\Windows\CurrentVersion\Uninstall\%TFTPD*Key%","URLInfoAbout",,"%TFTPD*URL%"
[TFTPD.Remove.DelReg]
HKLM,"Software\Microsoft\Windows\CurrentVersion\Uninstall\%TFTPD*Key%"
[TFTPD.Service]
AddReg = TFTPD.Parameters.Reg
DisplayName = "%TFTPD*Daemon%"
ErrorControl = %SERVICE_ERROR_NORMAL%
ServiceType = %SERVICE_WIN32_OWN_PROCESS%
StartName = "%TFTPD*Key%
StartType = %SERVICE_AUTO_START%
ServiceBinary = "%11%\TFTPD.EXE"
[TFTPD.EventLog]
AddReg = TFTPD.EventLog.Reg
[TFTPD.EventLog.Reg]
HKR,,"EventMessageFile",%REG_EXPAND_SZ%,"%%SystemRoot%%\System32\IoLogMsg.Dll"
HKR,,"TypesSupported",%REG_DWORD%,7
[TFTPD.Parameters.Reg]
HKR,"Parameters","Clients",%REG_SZ%,"*.*.*.*"
HKR,"Parameters","Directory",%REG_EXPAND_SZ%,"%%SystemRoot%%\System32\Drivers\Etc"
HKR,"Parameters","Masters",%REG_SZ%,""
HKR,"Parameters","Readable",%REG_SZ%,"*"
HKR,"Parameters","Writeable",%REG_SZ%,""
[SourceDiskNames]
; Cabinet file names and associated disks
; <disk or cabinet number> = <disk description>,[<cabinet
filename>],<identifier (unused, must be 0)>,[<relative source
path>]
99 = "%TFTPD*Description%",,0000-0000,"."
[SourceDiskFiles]
; <filename> = <disk or cabinet
number>,[<subdirectory>],[<filename>],[<size>],[<checksum>]
; Note: <filename> is neither on a disk nor in a cabinet if <disk
or cabinet number> is 0
TFTPD.INF = 99
[DestinationDirs]
TFTPD.Files.Sys = 11 ; %SystemRoot%\System32
TFTPD.Files.Inf = 17 ; %SystemRoot%\Inf
TFTPD.Files.Pnf = 17 ; %SystemRoot%\Pnf
[TFTPD.Files.Inf]
TFTPD.INF,,,%DELFLG_IN_USE1%
[TFTPD.Files.Pnf]
TFTPD.PNF,,,%DELFLG_IN_USE1%
[TFTPD.Files.Sys]
TFTPD.EXE,,,%DELFLG_IN_USE1%
[Strings]
TFTPD*Author = "Microsoft Corp."
TFTPD*Daemon = "TFTP Service"
TFTPD*Description = "Microsoft Windows 2000 TFTP Service"
TFTPD*Key = "TFTPD"
TFTPD*URL = "http://www.microsoft.com/"
TFTPD*Version = "5.0.2134.1"
; Non-Localizable Strings
DELFLG_IN_USE1 = 0x00010000
; Registry Data Types (usable with SETUPAPI.DLL only!)
REG_SZ = 0x00000000
REG_BINARY = 0x00000001
REG_SZ_NOCLOBBER = 0x00000002
REG_BINARY_NOCLOBBER = 0x00000003
REG_MULTI_SZ = 0x00010000
REG_DWORD = 0x00010001
REG_MULTI_SZ_NOCLOBBER = 0x00010002
REG_DWORD_NOCLOBBER = 0x00010003
REG_EXPAND_SZ = 0x00020000
REG_EXPAND_SZ_NOCLOBBER = 0x00020002
; Driver and Service Types
SERVICE_KERNEL_DRIVER = 0x00000001
SERVICE_KERNEL_FILESYSTEM_DRIVER = 0x00000002
SERVICE_NETWORK_ADAPTER_DRIVER = 0x00000004
SERVICE_WIN32_OWN_PROCESS = 0x00000010
SERVICE_WIN32_SHARED_PROCESS = 0x00000020
; Driver and Service Start Types
SERVICE_BOOT_START = 0
SERVICE_SYSTEM_START = 1
SERVICE_AUTO_START = 2
SERVICE_MANUAL_START = 3
SERVICE_NEVER_START = 4 ; (deactivated)
; Driver and Service Error Control
SERVICE_ERROR_IGNORE = 0
SERVICE_ERROR_NORMAL = 1
SERVICE_ERROR_SEVERE = 2
SERVICE_ERROR_CRITICAL = 3
SVCINST_TAGTOFRONT = 0x00000001
SVCINST_ASSOCSERVICE = 0x00000002
SVCINST_DELETEEVENTLOGENTRY = 0x00000004
;
; Setup for the TFTP service of Windows 2000
;
; Copyright (c) 2000-2003, Stefan Kanthak <skanthak@nexgo.de>
[Version]
Class = System
InfVersion = "01.00.00"
LayoutFile = LAYOUT.INF
Provider = "Stefan Kanthak"
SetupClass = BASE
Signature = "$Windows NT$"
[DefaultInstall.NTx86]
AddReg = TFTPD.Install.AddReg
CopyFiles = TFTPD.Files.Inf,TFTPD.Files.Sys
DelFiles = TFTPD.Files.Pnf
Reboot
[DefaultInstall.NTx86.Services]
AddService =
"%TFTPD*Key%",%SPSVCINST_ASSOCSERVICE%,TFTPD.Service,TFTPD.EventLog
[DefaultUninstall.NTx86]
DelFiles = TFTPD.Files.Inf,TFTPD.Files.Pnf,TFTPD.Files.Sys
DelReg = TFTPD.Remove.DelReg
Reboot
[DefaultUninstall.NTx86.Services]
DelService = "%TFTPD*Key%",%SVCINST_DELETEEVENTLOGENTRY%
[TFTPD.Install.AddReg]
HKLM,"Software\Microsoft\Windows\CurrentVersion\Uninstall\%TFTPD*Key%","DisplayName",,"%TFTPD*Description%"
HKLM,"Software\Microsoft\Windows\CurrentVersion\Uninstall\%TFTPD*Key%","DisplayVersion",,"%TFTPD*Version%"
HKLM,"Software\Microsoft\Windows\CurrentVersion\Uninstall\%TFTPD*Key%","HelpLink",,""
HKLM,"Software\Microsoft\Windows\CurrentVersion\Uninstall\%TFTPD*Key%","InstallLocation",,"%11%"
HKLM,"Software\Microsoft\Windows\CurrentVersion\Uninstall\%TFTPD*Key%","InstallSource",,"%01%"
HKLM,"Software\Microsoft\Windows\CurrentVersion\Uninstall\%TFTPD*Key%","Publisher",,"%TFTPD*Author%"
HKLM,"Software\Microsoft\Windows\CurrentVersion\Uninstall\%TFTPD*Key%","UninstallString",,"%11%\RunDll32.Exe
%11%\SetupAPI.Dll,InstallHinfSection DefaultUninstall.NTx86 4
%17%\TFTPD.Inf"
HKLM,"Software\Microsoft\Windows\CurrentVersion\Uninstall\%TFTPD*Key%","URLInfoAbout",,"%TFTPD*URL%"
[TFTPD.Remove.DelReg]
HKLM,"Software\Microsoft\Windows\CurrentVersion\Uninstall\%TFTPD*Key%"
[TFTPD.Service]
AddReg = TFTPD.Parameters.Reg
DisplayName = "%TFTPD*Daemon%"
ErrorControl = %SERVICE_ERROR_NORMAL%
ServiceType = %SERVICE_WIN32_OWN_PROCESS%
StartName = "%TFTPD*Key%
StartType = %SERVICE_AUTO_START%
ServiceBinary = "%11%\TFTPD.EXE"
[TFTPD.EventLog]
AddReg = TFTPD.EventLog.Reg
[TFTPD.EventLog.Reg]
HKR,,"EventMessageFile",%REG_EXPAND_SZ%,"%%SystemRoot%%\System32\IoLogMsg.Dll"
HKR,,"TypesSupported",%REG_DWORD%,7
[TFTPD.Parameters.Reg]
HKR,"Parameters","Clients",%REG_SZ%,"*.*.*.*"
HKR,"Parameters","Directory",%REG_EXPAND_SZ%,"%%SystemRoot%%\System32\Drivers\Etc"
HKR,"Parameters","Masters",%REG_SZ%,""
HKR,"Parameters","Readable",%REG_SZ%,"*"
HKR,"Parameters","Writeable",%REG_SZ%,""
[SourceDiskNames]
; Cabinet file names and associated disks
; <disk or cabinet number> = <disk description>,[<cabinet
filename>],<identifier (unused, must be 0)>,[<relative source
path>]
99 = "%TFTPD*Description%",,0000-0000,"."
[SourceDiskFiles]
; <filename> = <disk or cabinet
number>,[<subdirectory>],[<filename>],[<size>],[<checksum>]
; Note: <filename> is neither on a disk nor in a cabinet if <disk
or cabinet number> is 0
TFTPD.INF = 99
[DestinationDirs]
TFTPD.Files.Sys = 11 ; %SystemRoot%\System32
TFTPD.Files.Inf = 17 ; %SystemRoot%\Inf
TFTPD.Files.Pnf = 17 ; %SystemRoot%\Pnf
[TFTPD.Files.Inf]
TFTPD.INF,,,%DELFLG_IN_USE1%
[TFTPD.Files.Pnf]
TFTPD.PNF,,,%DELFLG_IN_USE1%
[TFTPD.Files.Sys]
TFTPD.EXE,,,%DELFLG_IN_USE1%
[Strings]
TFTPD*Author = "Microsoft Corp."
TFTPD*Daemon = "TFTP Service"
TFTPD*Description = "Microsoft Windows 2000 TFTP Service"
TFTPD*Key = "TFTPD"
TFTPD*URL = "http://www.microsoft.com/"
TFTPD*Version = "5.0.2134.1"
; Non-Localizable Strings
DELFLG_IN_USE1 = 0x00010000
; Registry Data Types (usable with SETUPAPI.DLL only!)
REG_SZ = 0x00000000
REG_BINARY = 0x00000001
REG_SZ_NOCLOBBER = 0x00000002
REG_BINARY_NOCLOBBER = 0x00000003
REG_MULTI_SZ = 0x00010000
REG_DWORD = 0x00010001
REG_MULTI_SZ_NOCLOBBER = 0x00010002
REG_DWORD_NOCLOBBER = 0x00010003
REG_EXPAND_SZ = 0x00020000
REG_EXPAND_SZ_NOCLOBBER = 0x00020002
; Driver and Service Types
SERVICE_KERNEL_DRIVER = 0x00000001
SERVICE_KERNEL_FILESYSTEM_DRIVER = 0x00000002
SERVICE_NETWORK_ADAPTER_DRIVER = 0x00000004
SERVICE_WIN32_OWN_PROCESS = 0x00000010
SERVICE_WIN32_SHARED_PROCESS = 0x00000020
; Driver and Service Start Types
SERVICE_BOOT_START = 0
SERVICE_SYSTEM_START = 1
SERVICE_AUTO_START = 2
SERVICE_MANUAL_START = 3
SERVICE_NEVER_START = 4 ; (deactivated)
; Driver and Service Error Control
SERVICE_ERROR_IGNORE = 0
SERVICE_ERROR_NORMAL = 1
SERVICE_ERROR_SEVERE = 2
SERVICE_ERROR_CRITICAL = 3
SVCINST_TAGTOFRONT = 0x00000001
SVCINST_ASSOCSERVICE = 0x00000002
SVCINST_DELETEEVENTLOGENTRY = 0x00000004
Please post the file sizes and the placement of the files if your still having issues.
Rob
QUOTE (Mohrbajo @ Apr 18 2005, 07:01 PM)
QUOTE (WinPE_bla @ Feb 4 2005, 04:11 PM)
Hi all,
I have just tested booting my iso (builded from Win2003 SP1 RC1 / WinPE 2005) from PXE
I did all steps as written in the initial post. The ntdetect.com and startrom.com was taken from the RC1 CD (Beta 1289) STARTROM.CO_, NTLDR is a renamed SETUPLDR.EX_
And this is the winnt.sif
[SetupData]
BootDevice="ramdisk(0)"
BootPath="\i386\System32\"
OsLoadOptions = "/noguiboot /fastdetect /minint /rdexportascd /rdpath=winpe.iso"
WinPE doesn't start, after i recived an IP, Mask and a Gateway there is only a blinking curser.
Anybody has an idea?
I have just tested booting my iso (builded from Win2003 SP1 RC1 / WinPE 2005) from PXE
I did all steps as written in the initial post. The ntdetect.com and startrom.com was taken from the RC1 CD (Beta 1289) STARTROM.CO_, NTLDR is a renamed SETUPLDR.EX_
And this is the winnt.sif
QUOTE
[SetupData]
BootDevice="ramdisk(0)"
BootPath="\i386\System32\"
OsLoadOptions = "/noguiboot /fastdetect /minint /rdexportascd /rdpath=winpe.iso"
WinPE doesn't start, after i recived an IP, Mask and a Gateway there is only a blinking curser.
Anybody has an idea?
I have the same problem as the quote, only on the server it says that it has successfully transfered the startrom.com and the NTLDR and then sits there doing nothing.
Is there anyone that can help me out, maybe it is my files I took them from W2k3 sever SP1.
I'm also running this on w2k sp1 server with tftp32.
Joe
If you are using TFTPD32 as your TFTP server, set the anticipation window size to 256 bytes for a faster download of the ISO. My download (a 480MB file) went from 226s (2.1MB/s) to 84s (5.7MB/s).
This is over a gigabit network so YMMV.
BTW, ensure in TFTPD32 the preference is set to "Use "/" as Virtual Root".
That resolved a similar problem for me.
QUOTE (MrXP @ Mar 22 2005, 08:35 AM)
Does this method still work if my BartPE 3.12 ISO is 600MBs?
Microsoft set a hardlimit of 512MB for the ISO.
My question was not relevant to this subject.
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
---
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
---
QUOTE (j.man @ Apr 27 2005, 09:02 PM)
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
---
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.
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...
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 ?
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 ?
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
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
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
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
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.
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.
This file loads the "menu" which is:
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
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"
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
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
QUOTE
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/
QUOTE
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...
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
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".
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
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
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
QUOTE (manouman @ May 2 2005, 10:24 AM)
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 ?
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.
QUOTE (Metzen @ Jul 6 2005, 04:48 AM)
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.
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
QUOTE (Turbo Donkey @ Jul 11 2005, 12:51 PM)
How exactly do you edit the registry hive before or after you've built the image?
John
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.
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
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
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
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
QUOTE (Macfox @ Aug 11 2005, 02:43 AM)
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
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
QUOTE (risky @ Aug 14 2005, 10:43 PM)
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
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.
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
we are using PE and PQIdeploy to PXE boot and deploy Xp images to about 19K Client boxes
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.