(sorry for my english, i m french)
here my purpose :
my server is bartpe (on harddisk) to launch another bartpe pxe (with more softs)
bartpe built is windows server 2003 standard SP1 (french)
I have set up tftpd32 to load startrom.0
set up the following:
The following files are in C:\tftp
NTDETECT.COM
NTLDR
startrom.0
winnt.sif
winpe (folder)
content of winnt.sif:
[SetupData]
OsLoadOptions = "/fastdetect /minint"
SetupSourceDevice = "\Device\LanmanRedirector\logatome\tftp\bartpe"
[UserData]
ComputerName = logatome
ps : i dont want to use ISO method
i use binlsrv from sherpya (moved binlsrv.py to binlsrv.exe with py2exe - it works fine)
well... my problem is :
mrxsmb.sys...
Windows XP bootscreen come up and the last file transferred using tftp is mrxsmb.sys, but the screen just sits there... Bartpe doesn't see share.
i have seen other threads about this... and more research...
have you an idea ?
Full Version: Pxe bartpe server Booting BartPe Using Tftpd32
QUOTE (bouh @ Jun 14 2006, 10:58 AM) 
(sorry for my english, i m french)
here my purpose :
my server is bartpe (on harddisk) to launch another bartpe pxe (with more softs)
bartpe built is windows server 2003 standard SP1 (french)
I have set up tftpd32 to load startrom.0
set up the following:
The following files are in C:\tftp
NTDETECT.COM
NTLDR
startrom.0
winnt.sif
winpe (folder)
content of winnt.sif:
[SetupData]
OsLoadOptions = "/fastdetect /minint"
SetupSourceDevice = "\Device\LanmanRedirector\logatome\tftp\bartpe"
[UserData]
ComputerName = logatome
ps : i dont want to use ISO method
i use binlsrv from sherpya (moved binlsrv.py to binlsrv.exe with py2exe - it works fine)
well... my problem is :
mrxsmb.sys...
Windows XP bootscreen come up and the last file transferred using tftp is mrxsmb.sys, but the screen just sits there... Bartpe doesn't see share.
i have seen other threads about this... and more research...
have you an idea ?
here my purpose :
my server is bartpe (on harddisk) to launch another bartpe pxe (with more softs)
bartpe built is windows server 2003 standard SP1 (french)
I have set up tftpd32 to load startrom.0
set up the following:
The following files are in C:\tftp
NTDETECT.COM
NTLDR
startrom.0
winnt.sif
winpe (folder)
content of winnt.sif:
[SetupData]
OsLoadOptions = "/fastdetect /minint"
SetupSourceDevice = "\Device\LanmanRedirector\logatome\tftp\bartpe"
[UserData]
ComputerName = logatome
ps : i dont want to use ISO method
i use binlsrv from sherpya (moved binlsrv.py to binlsrv.exe with py2exe - it works fine)
well... my problem is :
mrxsmb.sys...
Windows XP bootscreen come up and the last file transferred using tftp is mrxsmb.sys, but the screen just sits there... Bartpe doesn't see share.
i have seen other threads about this... and more research...
have you an idea ?
ramdisk.inf
ramdisk.sys
you have to extract these two files from the windows server 2003 sp3 . These files are newer.
my winnt.sif looks like this :
[SetupData]
BootDevice = "ramdisk(0)"
BootPath = "\i386\System32\"
OsLoadOptions = "/noguiboot /fastdetect /minint /rdexportascd /rdpath=\images\microsoft\test.iso"
[quote name='Vodken' date='Jun 14 2006, 02:56 PM' post='115292']
ramdisk.inf
ramdisk.sys
you have to extract these two files from the windows server 2003 sp3 . These files are newer.
my winnt.sif looks like this :
[SetupData]
BootDevice = "ramdisk(0)"
BootPath = "\i386\System32\"
OsLoadOptions = "/noguiboot /fastdetect /minint /rdexportascd /rdpath=\images\microsoft\test.iso"
[/quote]
thx for answer
well... it seems difficult to find these files...
windows server 2003 sp3 ? Can you send me these files ?
ramdisk.inf
ramdisk.sys
you have to extract these two files from the windows server 2003 sp3 . These files are newer.
my winnt.sif looks like this :
[SetupData]
BootDevice = "ramdisk(0)"
BootPath = "\i386\System32\"
OsLoadOptions = "/noguiboot /fastdetect /minint /rdexportascd /rdpath=\images\microsoft\test.iso"
[/quote]
thx for answer
well... it seems difficult to find these files...
windows server 2003 sp3 ? Can you send me these files ?
Well.
Vodken, i dont want to use iso image but shared folder...
(iso image works but for me it's not interesting)
always searching...
i you have another idea, thanks
Vodken, i dont want to use iso image but shared folder...
(iso image works but for me it's not interesting)
always searching...
i you have another idea, thanks
QUOTE (bouh @ Jun 15 2006, 10:43 AM)
Well.
Vodken, i dont want to use iso image but shared folder...
(iso image works but for me it's not interesting)
always searching...
i you have another idea, thanks
Vodken, i dont want to use iso image but shared folder...
(iso image works but for me it's not interesting)
always searching...
i you have another idea, thanks
I see this topic is age old, but i had the exact same problem, and its due to file permissions on your server. What you need to do is to enable the guest user, and set it to have permissions on the share. You also need to set the guest password to nothing (just set it without typing a password). You also need to set permissions in "local security policy" and "Accounts : Limit local account use of blank password to console only" to DISABLED.
Finish off with a gpupdate.
However, this is a highly unsecure method of doing it, but in a closed network it can at least be used as a tryout..
But.. now im stuch at the network card not being "usable" once bartpe starts up.. I guess its kinda logical, as the "os disk" is now really a networked disk, so if i try to load/unload the network driver, it looses connection with the os disk itself.. hehe..
So.. what then? i cant seem to mount network shares or similar by using "net use" command either, even tho my system drive is clearly mounted on the network..
Ideas?
thanks for reply... very much )
well... i have some questions :
how do you enable guest user under bartpe (server is bartpe)
how do you set guest password to nothing
and
how do you set permissions in local security policy and accounts
not so evident under bartpe...
Have you a document "how to" ?
)well... i have some questions :
how do you enable guest user under bartpe (server is bartpe)
how do you set guest password to nothing
and
how do you set permissions in local security policy and accounts
not so evident under bartpe...
Have you a document "how to" ?
I think CyberMax is talking about a normal windows server, not a bartpe one. Not heard of anyone doing this.
Have you tried sdi?
Have you tried sdi?
Yes it's normal server...
so...
i haven't tried with "sdi"... it's a good idea... i will try it
so...
i haven't tried with "sdi"... it's a good idea... i will try it
Hello bouh, we are in same boat.
I got stuck on exactly same place as you did, stuck GUI boot loading screen. and the last file tftp32 load is mrxsmb.sys.
I can't use ramdisk way because I want my PXE bartpe run under 128 RAM. (ramdisk way can't do that)
My bartpe is build with winxp sp2.....help plz
note: I already allow guest and enable blank password login by setting secpol.msc, but still stuck at mrxsmb.sys. Is SAMBA really a must to get it work??
I got stuck on exactly same place as you did, stuck GUI boot loading screen. and the last file tftp32 load is mrxsmb.sys.
I can't use ramdisk way because I want my PXE bartpe run under 128 RAM. (ramdisk way can't do that)
My bartpe is build with winxp sp2.....help plz
note: I already allow guest and enable blank password login by setting secpol.msc, but still stuck at mrxsmb.sys. Is SAMBA really a must to get it work??
I had a 64mb sdi that I think I managed to pxe boot on a 128mb pc... was a long time ago though
make sure that the needed nic driver is in i386\system32, it's not a default, you need to explicit place it there
QUOTE (sherpya @ Mar 21 2007, 10:51 AM)
make sure that the needed nic driver is in i386\system32, it's not a default, you need to explicit place it there
Yes, I dupe all my drivers to i386\system32 (and I also dupe all driver to i386\ too), same result.....stop at mrxsmb.sys
make your reminst share as write protected, btw how it freezes, just black screen or something different?
QUOTE (sherpya @ Mar 23 2007, 10:20 AM)
make your reminst share as write protected, btw how it freezes, just black screen or something different?
it end up the GUI windows xp loading screen, endless loading (and the loading bar is running and running) and tftp32 log stop at mrxsmb.sys
here is reference link who got same errors
http://www.911cd.net/forums/index.php?showtopic=11571
http://www.911cd.net/forums//index.php?sho...hl=pe+hang+with
YAHOO!!!!! Finally make a sucessful DIRECT PXE BOOT 2 BARTPE (no iso or ramdisk, run my 698mb bartpe fine under 128 ram) 
The result is secpol.msc need more setting tweaking ( MS makes more restrict on "guest" by default, not only just disable blank password login)
All right, DIRECT PXE BOOT 2 BARTPE is working under REAL WINXP as host pxe server....what I plan is make bartpe as pxe host server. And I belive "guest" will be a problem under bartpe. Btw still worth to try........will be continue
The result is secpol.msc need more setting tweaking ( MS makes more restrict on "guest" by default, not only just disable blank password login)
All right, DIRECT PXE BOOT 2 BARTPE is working under REAL WINXP as host pxe server....what I plan is make bartpe as pxe host server. And I belive "guest" will be a problem under bartpe. Btw still worth to try........will be continue
QUOTE (samplempg @ Mar 26 2007, 06:40 PM)
what I plan is make bartpe as pxe host server. And I belive "guest" will be a problem under bartpe. Btw still worth to try........will be continue
Hi samplempg,
I solved this problem and created a plugin that turns bartpe into a PXE Server to server another Bart (RIS-like). The plugin uses TFTPD32, Sherpya's BINL-Server, and Windows file sharing capabilities. I tested with a bare bone BartPE (Nu2 Menu) as well as with XPE plugin. It runs with WinXP and with Win2k3.
I'm searchin' for the 'Attach file' button here, but this seems not to be possible here. Are you still interested in this? Can I email you the zip file of the plugin (18KB)? I don't know where I can publish it?
Yours,
Keira
QUOTE (KeiraM @ Jun 24 2007, 07:31 PM)
I'm searchin' for the 'Attach file' button here, but this seems not to be possible here. Are you still interested in this? Can I email you the zip file of the plugin (18KB)? I don't know where I can publish it?
Yours,
Keira
Yours,
Keira
Scroll down
green button UPLOAD and Max single upload size: 2MB
or upload it to a free online file sharing like RapidShare
Hi everyone,
Thanks! It seems I was blind.
There is some info about the plugin in the zip-file-comment and also some info in the inf-file. There is no real help file inside.
Here is the zip-file-info:
The plugin is public domain (as far as I am allowed to declare this).
You're invited to send any comments or anything else here, but since writing plugins isn't my main business, I cannot guarantee any support.
You're also invited to share this plugin with others on your homepage or somewhere else.
Have fun!
Keira
Edit: Maybe I wasn't so blind at all. I just tried to post my OpenVPN plugin in the Anyone got OpenVPN plugin to work? thread in the Plugins forum but there is no "Attachments" section in the "Send post" site. Why am I allowed to post attachments only in certain fora?
Keira
QUOTE
Scroll down
green button UPLOAD
green button UPLOAD
Thanks! It seems I was blind.
There is some info about the plugin in the zip-file-comment and also some info in the inf-file. There is no real help file inside.
Here is the zip-file-info:
QUOTE
PXEBoot
Installs a kind of PXE-Boot-Server on BartPE that can serve Bart CDs (or maybe something else) to the network.
Can work as RIS server (files are accessed by the client via network on demand) or serve an ISO-image (is transfered as one big file/Win2k3-SP1 only!)
A little script is included that sets up everything needed.
Some files are needed for this plugin to work: Two from the internet (Junction.exe, TFTPD32.exe), one from another Bart build ('bootsect.bin').
See comments on top of inf-file for details!
Place this plugin as subfolder somewhere in the plugins folder, not deeper! This plugin reaches for mkisofs.exe by "..\..\mkisofs.exe".
Problems:
* Some writeable folder on an NTFS drive is needed (this can be provided by formating the RAMDisk accordingly, e.g. with "format /FS:NTFS"). Only about 1 MB space is needed in this folder for RIS boot.
* Serving an ISO image needs the iso image to be present, of course. MSISofs will be copied with this plugin, but creating the iso-image will need a lot space (on the NTFS folder mentioned above).
* The Bart system that hosts the server *cannot* be served (when the registry hives are read, they appear modified). This can be worked around by copying i386 to e.g. i386pxe prior to image creation. When creating the image with -duplicates-once, no additional space will be occupied by this folder. Then i386pxe can be served.
* On a RIS booted system the network configuration behaves strangely: Network capabilities are present, but it's hard to change settings for NICs. On the other hand, creating a TAP device (with OpenVPN) is still possible.
* ISO booted systems need a lot of RAM...
With this plugin the nice little BINL-Server created by sherpya is shipped, as well as a so-called InfParser that was coded in C and adapted from sherpyas InfParser.py. Sherpyas BINL-Server is GNU-GPL - see sherpyas homepage for the source. My C-InfParser is closed-source freeware. Do with it whatever you want to. BUT THERE IS NO WARRANTY FOR NOTHING!!!
And there is NO WARRANTY for the whole plugin.
sorry for my english
Installs a kind of PXE-Boot-Server on BartPE that can serve Bart CDs (or maybe something else) to the network.
Can work as RIS server (files are accessed by the client via network on demand) or serve an ISO-image (is transfered as one big file/Win2k3-SP1 only!)
A little script is included that sets up everything needed.
Some files are needed for this plugin to work: Two from the internet (Junction.exe, TFTPD32.exe), one from another Bart build ('bootsect.bin').
See comments on top of inf-file for details!
Place this plugin as subfolder somewhere in the plugins folder, not deeper! This plugin reaches for mkisofs.exe by "..\..\mkisofs.exe".
Problems:
* Some writeable folder on an NTFS drive is needed (this can be provided by formating the RAMDisk accordingly, e.g. with "format /FS:NTFS"). Only about 1 MB space is needed in this folder for RIS boot.
* Serving an ISO image needs the iso image to be present, of course. MSISofs will be copied with this plugin, but creating the iso-image will need a lot space (on the NTFS folder mentioned above).
* The Bart system that hosts the server *cannot* be served (when the registry hives are read, they appear modified). This can be worked around by copying i386 to e.g. i386pxe prior to image creation. When creating the image with -duplicates-once, no additional space will be occupied by this folder. Then i386pxe can be served.
* On a RIS booted system the network configuration behaves strangely: Network capabilities are present, but it's hard to change settings for NICs. On the other hand, creating a TAP device (with OpenVPN) is still possible.
* ISO booted systems need a lot of RAM...
With this plugin the nice little BINL-Server created by sherpya is shipped, as well as a so-called InfParser that was coded in C and adapted from sherpyas InfParser.py. Sherpyas BINL-Server is GNU-GPL - see sherpyas homepage for the source. My C-InfParser is closed-source freeware. Do with it whatever you want to. BUT THERE IS NO WARRANTY FOR NOTHING!!!
And there is NO WARRANTY for the whole plugin.
sorry for my english
The plugin is public domain (as far as I am allowed to declare this).
You're invited to send any comments or anything else here, but since writing plugins isn't my main business, I cannot guarantee any support.
You're also invited to share this plugin with others on your homepage or somewhere else.
Have fun!
Keira
Edit: Maybe I wasn't so blind at all. I just tried to post my OpenVPN plugin in the Anyone got OpenVPN plugin to work? thread in the Plugins forum but there is no "Attachments" section in the "Send post" site. Why am I allowed to post attachments only in certain fora?
Keira
QUOTE (KeiraM @ Jul 10 2007, 03:32 PM)
Edit: Maybe I wasn't so blind at all. I just tried to post my OpenVPN plugin in the Anyone got OpenVPN plugin to work? thread in the Plugins forum but there is no "Attachments" section in the "Send post" site. Why am I allowed to post attachments only in certain fora?
Keira
Keira
Had you clicked on the Add Reply button or the " Reply button when you looked for the Upload button?
@KeiraM
It seems like a nice piece of work!
I am posting a link to this thread on tftp32 forum, here:
http://www.boot-land.net/forums/Tftpd32-f58.html
Just to give your plugin some more visibility.
jaclaz
It seems like a nice piece of work!
I am posting a link to this thread on tftp32 forum, here:
http://www.boot-land.net/forums/Tftpd32-f58.html
Just to give your plugin some more visibility.
jaclaz
Hi Ed,
I just tried both, but the Attachments rectangle is always missing. When I click on " Reply here in this thread (what I did in order to write this text), the Attachments rectangle is there.
Keira
QUOTE (Ed_P @ Jul 10 2007, 05:58 PM)
Had you clicked on the Add Reply button or the " Reply button when you looked for the Upload button?
I just tried both, but the Attachments rectangle is always missing. When I click on " Reply here in this thread (what I did in order to write this text), the Attachments rectangle is there.
Keira
QUOTE (KeiraM @ Jul 11 2007, 02:27 PM)
Hi Ed,
I just tried both, but the Attachments rectangle is always missing. When I click on " Reply here in this thread (what I did in order to write this text), the Attachments rectangle is there.
Keira
QUOTE (Ed_P @ Jul 10 2007, 05:58 PM)
Had you clicked on the Add Reply button or the " Reply button when you looked for the Upload button?
I just tried both, but the Attachments rectangle is always missing. When I click on " Reply here in this thread (what I did in order to write this text), the Attachments rectangle is there.
Keira
We are talking about the posting here right? http://www.911cd.net/forums//index.php?s=&...st&p=132825
Hi Ed
Yours, Keira
QUOTE (Ed_P @ Jul 11 2007, 12:45 PM)
We are talking about the posting here right? http://www.911cd.net/forums//index.php?s=&...st&p=132825
Yes. I have no Attachments box in that thread.Yours, Keira
QUOTE (KeiraM @ Jul 21 2007, 04:56 PM)
Hi Ed
Yours, Keira
QUOTE (Ed_P @ Jul 11 2007, 12:45 PM)
We are talking about the posting here right? http://www.911cd.net/forums//index.php?s=&...st&p=132825
Yes. I have no Attachments box in that thread.Yours, Keira
Dang, every time I click on " Reply or Add Reply to that thread I see an Attachment box but it might be due to my ranking. Can anyone else report what they see when they try those two options?
QUOTE (Ed_P @ Jul 21 2007, 10:56 PM)
QUOTE (KeiraM @ Jul 21 2007, 04:56 PM)
Hi Ed
Yours, Keira
QUOTE (Ed_P @ Jul 11 2007, 12:45 PM)
We are talking about the posting here right? http://www.911cd.net/forums//index.php?s=&...st&p=132825
Yes. I have no Attachments box in that thread.Yours, Keira
Dang, every time I click on " Reply or Add Reply to that thread I see an Attachment box but it might be due to my ranking. Can anyone else report what they see when they try those two options?
I see no "Attachment" option with either of the Reply buttons on that thread also. As I post this here though I see a light green UPLOAD button in a section labeled Attachments located between this posting box and the Post Options box.
The only thing I see that is unique about that thread is it was started over a year ago. Maybe the Attachment function only applies to threads started after a specific update or version change.
Try this version of the thread: http://www.911cd.net/forums//index.php?sho...c=20099&hl=
If it doesn't work I'm out of ideas at the moment.
If it doesn't work I'm out of ideas at the moment.
@KeiraM
I'm trying to use your plugin on a real Windows XP Professional SP2 English box (running this script outside of BartPE).
All required files are present in %temp% folder: *.* unzipped from P_PXEBoot.zip + *.* unzipped from tftpd32.323.zip + *.* unzipped from Junction.zip
1st try
pxeserver -CD G: -Sys i386
ipconfig.tmp
script fails to parse data in :LabelMainArgIP1 section (before :: Process 'Range' and 'DHCP' argument). Is ipconfig.tmp well formated?
2nd try
pxeserver -CD G: -Sys i386 -IP 192.168.1.36 -Mask 255.255.255.0 -DHCP 192.168.1.100 -Range 100
I'm trying to use your plugin on a real Windows XP Professional SP2 English box (running this script outside of BartPE).
All required files are present in %temp% folder: *.* unzipped from P_PXEBoot.zip + *.* unzipped from tftpd32.323.zip + *.* unzipped from Junction.zip
1st try
pxeserver -CD G: -Sys i386
QUOTE
Invalid number. Numeric constants are either decimal (17),
hexadecimal (0x11), or octal (021).
9 was unexpected at this time.
hexadecimal (0x11), or octal (021).
9 was unexpected at this time.
ipconfig.tmp
QUOTE
ECHO is off.
Ethernet adapter Local Area Connection:
ECHO is off.
Connection-specific DNS Suffix . :
IP Address. . . . . . . . . . . . : 192.168.1.36
Subnet Mask . . . . . . . . . . . : 255.255.255.0
IP Address. . . . . . . . . . . . : fe80::230:5ff:fe81:a127%9
Default Gateway . . . . . . . . . : 192.168.1.1
ECHO is off.
Tunnel adapter Teredo Tunneling Pseudo-Interface:
ECHO is off.
Connection-specific DNS Suffix . :
IP Address. . . . . . . . . . . . : 3ffe:831f:4136:e37a:0:f917:a5f9:c817
IP Address. . . . . . . . . . . . : fe80::5445:5245:444f%6
Default Gateway . . . . . . . . . : ::
ECHO is off.
Tunnel adapter Automatic Tunneling Pseudo-Interface:
ECHO is off.
Connection-specific DNS Suffix . :
IP Address. . . . . . . . . . . . : fe80::5efe:192.168.1.36%2
Default Gateway . . . . . . . . . :
Ethernet adapter Local Area Connection:
ECHO is off.
Connection-specific DNS Suffix . :
IP Address. . . . . . . . . . . . : 192.168.1.36
Subnet Mask . . . . . . . . . . . : 255.255.255.0
IP Address. . . . . . . . . . . . : fe80::230:5ff:fe81:a127%9
Default Gateway . . . . . . . . . : 192.168.1.1
ECHO is off.
Tunnel adapter Teredo Tunneling Pseudo-Interface:
ECHO is off.
Connection-specific DNS Suffix . :
IP Address. . . . . . . . . . . . : 3ffe:831f:4136:e37a:0:f917:a5f9:c817
IP Address. . . . . . . . . . . . : fe80::5445:5245:444f%6
Default Gateway . . . . . . . . . : ::
ECHO is off.
Tunnel adapter Automatic Tunneling Pseudo-Interface:
ECHO is off.
Connection-specific DNS Suffix . :
IP Address. . . . . . . . . . . . : fe80::5efe:192.168.1.36%2
Default Gateway . . . . . . . . . :
script fails to parse data in :LabelMainArgIP1 section (before :: Process 'Range' and 'DHCP' argument). Is ipconfig.tmp well formated?
2nd try
pxeserver -CD G: -Sys i386 -IP 192.168.1.36 -Mask 255.255.255.0 -DHCP 192.168.1.100 -Range 100
QUOTE
255 was unexpected at this time.
QUOTE (KeiraM @ Jul 21 2007, 04:56 PM)
Hi Ed
Yours, Keira
QUOTE (Ed_P @ Jul 11 2007, 12:45 PM)
We are talking about the posting here right? http://www.911cd.net/forums//index.php?s=&...st&p=132825
Yes. I have no Attachments box in that thread.Yours, Keira
Finally an answer. It's not an option in that forum. You will have to upload your file to a file sharing system and attach a link to your posting.
Sorry for the inconvenience.
Hi everyone,
I.
I found an error in my plugin: RIS booting seems not to work when the -sys directory is named other than i386 (so the idea I wrote in the description with the rename the i386 to something else and use mkisofs with -duplicates-once is pretty worthless).
I have to investigate that further, but it might help if someone else observes the same thing. Maybe this problem also occurs when using the ISO boot option.
If the problem is what I think it is, I probably will add some code to the script that renames the -sys directory to i386. Let's see....
As workaround (if someone has trouble with this), you can copy your whole CD structure in a subdirectory on the CD and use -cd X:\CopyOfCD.
Sorry for that!
II. @bilou_gateux
Well, as far as I remember I once succesfully used the script on a Win2k system serving a Win2k3 Bart CD (but that was months ago).
But here it looks like the problem is not caued by the Non-Bart environment. The parsing of IP addresses seems to be broken. I don't exactly know who creates that error messages (### unexpected) - maybe Reg.exe ?
Since you use it outside of Bart, maybe you can do the following: Copy the PXEServer directory on a writeable drive and remove the Echo off at the beginning. Then post the output here. I need at least (with or without Echo) some lines above the error message so I know where in the script the error occurs.
I don't think IPConfig.tmp is wrong formated since it isn't (or shouldn't be) used at all when your 2nd try is invoked.
III. @Ed_P
Well ..... So one cannot upload plugins to the Plugins forum.
I'll think about it. (My internet connection is very slow, so I need some time for that). Thanks anyway for investigating - now we know it's not an error.
Yours,
Keira
Edit: Re III:
I just realized I received a personal message with a webspace offer. Wow!
Keira
I.
I found an error in my plugin: RIS booting seems not to work when the -sys directory is named other than i386 (so the idea I wrote in the description with the rename the i386 to something else and use mkisofs with -duplicates-once is pretty worthless).
I have to investigate that further, but it might help if someone else observes the same thing. Maybe this problem also occurs when using the ISO boot option.
If the problem is what I think it is, I probably will add some code to the script that renames the -sys directory to i386. Let's see....
As workaround (if someone has trouble with this), you can copy your whole CD structure in a subdirectory on the CD and use -cd X:\CopyOfCD.
Sorry for that!
II. @bilou_gateux
QUOTE
I'm trying to use your plugin on a real Windows XP Professional SP2 English box (running this script outside of BartPE). ........ Is ipconfig.tmp well formated?
Well, as far as I remember I once succesfully used the script on a Win2k system serving a Win2k3 Bart CD (but that was months ago).
But here it looks like the problem is not caued by the Non-Bart environment. The parsing of IP addresses seems to be broken. I don't exactly know who creates that error messages (### unexpected) - maybe Reg.exe ?
Since you use it outside of Bart, maybe you can do the following: Copy the PXEServer directory on a writeable drive and remove the Echo off at the beginning. Then post the output here. I need at least (with or without Echo) some lines above the error message so I know where in the script the error occurs.
I don't think IPConfig.tmp is wrong formated since it isn't (or shouldn't be) used at all when your 2nd try is invoked.
III. @Ed_P
QUOTE
It's not an option in that forum.
Well ..... So one cannot upload plugins to the Plugins forum.
QUOTE
You will have to upload your file to a file sharing system and attach a link to your posting.
I'll think about it. (My internet connection is very slow, so I need some time for that). Thanks anyway for investigating - now we know it's not an error.
Yours,
Keira
Edit: Re III:
I just realized I received a personal message with a webspace offer. Wow!
Keira
Hi everyone,
There is a new version of the PXEBoot plugin available! Nuno provided some webspace for me (what I appreciate very much), so the current plugin version (as well as some other plugins) can be found here: http://keira.boot-land.net.
I corrected a bug reported by Bilou which broke the DHCP address range calculation. I also removed the -sys command line parameter. It is now fixed to i386. You can find details in the zip file comment.
@bilou:
I successfully reproduced your problem and as stated above, it should be fixed with this update. Nevertheless, I expect problems when running PXEServer.cmd in a non-Bart-environment: You have to make sure the system is configured according to the registry settings in PXEBoot.inf (TFTPD32 as well as the Windows file sharing settings). And now I realized why PXEServer.cmd failed at detecting your IP configuration: There are a lot IPv6 adresses in your IPConfig.tmp, and IPv6 isn't supported, I'm afraid.
Yours,
Keira
There is a new version of the PXEBoot plugin available! Nuno provided some webspace for me (what I appreciate very much), so the current plugin version (as well as some other plugins) can be found here: http://keira.boot-land.net.
I corrected a bug reported by Bilou which broke the DHCP address range calculation. I also removed the -sys command line parameter. It is now fixed to i386. You can find details in the zip file comment.
@bilou:
I successfully reproduced your problem and as stated above, it should be fixed with this update. Nevertheless, I expect problems when running PXEServer.cmd in a non-Bart-environment: You have to make sure the system is configured according to the registry settings in PXEBoot.inf (TFTPD32 as well as the Windows file sharing settings). And now I realized why PXEServer.cmd failed at detecting your IP configuration: There are a lot IPv6 adresses in your IPConfig.tmp, and IPv6 isn't supported, I'm afraid.
Yours,
Keira
QUOTE (KeiraM @ Jul 28 2007, 01:30 PM)
@bilou:
I successfully reproduced your problem and as stated above, it should be fixed with this update. Nevertheless, I expect problems when running PXEServer.cmd in a non-Bart-environment: You have to make sure the system is configured according to the registry settings in PXEBoot.inf (TFTPD32 as well as the Windows file sharing settings). And now I realized why PXEServer.cmd failed at detecting your IP configuration: There are a lot IPv6 adresses in your IPConfig.tmp, and IPv6 isn't supported, I'm afraid.
Yours,
Keira
I successfully reproduced your problem and as stated above, it should be fixed with this update. Nevertheless, I expect problems when running PXEServer.cmd in a non-Bart-environment: You have to make sure the system is configured according to the registry settings in PXEBoot.inf (TFTPD32 as well as the Windows file sharing settings). And now I realized why PXEServer.cmd failed at detecting your IP configuration: There are a lot IPv6 adresses in your IPConfig.tmp, and IPv6 isn't supported, I'm afraid.
Yours,
Keira
Thanks,
I have disabled 'Microsoft TCP/IP version 6' on my Local Network Connection and stopped 'IPv6 Helper Service'. In fact, i don't use it although it's installed.
Previous command works for parsing IP address.
Now the issue i have is file sharing settings.
Running the script logged as Administrator, HKLM\SAM\SAM\Domains\Account\Users\Names is not accessible. As described in AutoIt forums here post#26, you can access this registry key under System account only.
I have to use a nice tool:
PowerPrompt: Run programs with System credentials to launch the script.
Hi bilou,
Why? When the RIS booted system mounts its X: drive, its access to the host system is subject to access restrictions given by the Guest account. But the name of this account varies on localized Windows systems and I couldn't find a way to determine the exact name. So I decided to remove access restrictions on all accounts.
You should change the For-loop that does the thing described above so it's only applied to Guest (or whatever your Guest account is called), i.e. replace this line (around line 365 according to Windows notepad)
Yours,
Keira
QUOTE
I have disabled 'Microsoft TCP/IP version 6' on my Local Network Connection and stopped 'IPv6 Helper Service'.
I'm not an IPv6 expert, but I think, you can maybe switch it back on in case you need it again as long as you manually supply IPv4 addresses and masks and so on with the -IP -DHCP.. switches. But this depends on how backward-compatible IPv6 is... (??)QUOTE
Running the script logged as Administrator, HKLM\SAM\SAM\Domains\Account\Users\Names is not accessible.
Uuhou this is a good point. I just realized that running the script on productive non-Bart systems is pretty dangerous as it tries to enable all user accounts and remove their passwords (somewhere near :: Clear all file access restrictions). For this it needs to find all user accounts available.Why? When the RIS booted system mounts its X: drive, its access to the host system is subject to access restrictions given by the Guest account. But the name of this account varies on localized Windows systems and I couldn't find a way to determine the exact name. So I decided to remove access restrictions on all accounts.
You should change the For-loop that does the thing described above so it's only applied to Guest (or whatever your Guest account is called), i.e. replace this line (around line 365 according to Windows notepad)
CODE
For /F "delims=\ tokens=8" %%a in ('reg.exe query HKLM\SAM\SAM\Domains\Account\Users\Names') do (
with thisCODE
For /F "delims=\ tokens=1" %%a in ("Guest") do (
I'm sorry, but I don't see any other solution at the moment. I hope this works for you.QUOTE
PowerPrompt: Run programs with System credentials to launch the script.
This is really nice, thanks for posting that information.Yours,
Keira
Thanks for the detailled explanation so far.
Although i use an ENU Windows OS, i don't like to have some data values hardcoded for portability reasons.
A lot of freeware can help us to find the friendly name of the guest account.
I'm sure that you can script parsing output of this command:
lg . -lu
to find it.
We can also CollectSID
SID Values For Default Windows NT Installations, especially guest account Relative Identifier (RID)=501
and then get the name with sid2name
Although i use an ENU Windows OS, i don't like to have some data values hardcoded for portability reasons.
A lot of freeware can help us to find the friendly name of the guest account.
I'm sure that you can script parsing output of this command:
lg . -lu
to find it.
We can also CollectSID
SID Values For Default Windows NT Installations, especially guest account Relative Identifier (RID)=501
and then get the name with sid2name
Hi Bilou,
Thanks for pointing this out. The output of lg . -lu seems to be not structured enough to extract the user account independently of the language used (at least on my Win2k machine). Unfortunatelly I couldn't download CollectSID, so I found a way that utilizes PsGetSID, which can be downloaded by everyone. Place PsGetSID.exe where also your PXEServer.cmd script is, and in PXEServer.cmd replace these lines
If it works, I consider updating my plugin with this, but I'm not sure right now (it would add the option of using it outside of Bart, but also would increase size, would need another file from the net, and booting from outside of Bart is not the main purpose of the plugin). ...???
Yours,
Keira
Edit: Corrected the typos reported by Bilou and Jaclaz, so it's easier for visitors to copy things out of here. Also added the Nul-redirection. Thanks for this! Keira
QUOTE (bilou_gateux @ Aug 3 2007, 08:05 AM)
Thanks for the detailled explanation so far.
Although i use an ENU Windows OS, i don't like to have some data values hardcoded for portability reasons.
Avec plaisir! Protability (especially concerning localizations) was also my main concern.Although i use an ENU Windows OS, i don't like to have some data values hardcoded for portability reasons.
QUOTE (bilou_gateux @ Aug 3 2007, 08:05 AM)
A lot of freeware can help us to find the friendly name of the guest account.
.....
.....
Thanks for pointing this out. The output of lg . -lu seems to be not structured enough to extract the user account independently of the language used (at least on my Win2k machine). Unfortunatelly I couldn't download CollectSID, so I found a way that utilizes PsGetSID, which can be downloaded by everyone. Place PsGetSID.exe where also your PXEServer.cmd script is, and in PXEServer.cmd replace these lines
CODE
Set PXES__Result0=
For /F "delims=\ tokens=8" %%a in ('reg.exe query HKLM\SAM\SAM\Domains\Account\Users\Names') do (
If not "%%a"=="" Net.exe User %%a /Active:Yes /PasswordReq:No > Nul
Cacls.exe "%PXES__PXEPath%" /T /E /C /G %%a:C > Nul 2> Nul
Cacls.exe "%PXES__PXEPath%" /T /E /C /P %%a:C > Nul 2> Nul
:: Raising security to 'Read' (instead of 'Change') would make XPE complain about some 'Registration' directory
Call "%~f0" PXES__StrCat " /Grant:%%a,Change"
)
:: WinXP's Net.exe doesn't know the '/Grant:...' command
Net.exe Share PXE="%PXES__PXEPath%" /Unlimited /Cache:None %PXES__Result0% > Nul 2> Nul
with theseFor /F "delims=\ tokens=8" %%a in ('reg.exe query HKLM\SAM\SAM\Domains\Account\Users\Names') do (
If not "%%a"=="" Net.exe User %%a /Active:Yes /PasswordReq:No > Nul
Cacls.exe "%PXES__PXEPath%" /T /E /C /G %%a:C > Nul 2> Nul
Cacls.exe "%PXES__PXEPath%" /T /E /C /P %%a:C > Nul 2> Nul
:: Raising security to 'Read' (instead of 'Change') would make XPE complain about some 'Registration' directory
Call "%~f0" PXES__StrCat " /Grant:%%a,Change"
)
:: WinXP's Net.exe doesn't know the '/Grant:...' command
Net.exe Share PXE="%PXES__PXEPath%" /Unlimited /Cache:None %PXES__Result0% > Nul 2> Nul
CODE
For /F %%a in ('"%~dp0PsGetSID.exe" ^2^> Nul') do Set PXES__Guest=%%a
For /F "delims=\ tokens=2" %%a in ('"%~dp0PsGetSID.exe" %PXES__Guest%-501 ^2^> Nul') do Set PXES__Guest=%%a
Cacls.exe "%PXES__PXEPath%" /T /E /C /G %PXES__Guest%:C > Nul 2> Nul
Cacls.exe "%PXES__PXEPath%" /T /E /C /P %PXES__Guest%:C > Nul 2> Nul
:: Raising security to 'Read' (instead of 'Change') would make XPE complain about some 'Registration' directory
Net.exe Share PXE="%PXES__PXEPath%" /Unlimited /Cache:None /Grant:%PXES__Guest%,Change > Nul 2> Nul
:: WinXP's Net.exe doesn't know the '/Grant:...' command
I tried the first two lines and it determined my Guest account correctly (on my Win2k machine). I cannot try in a Bart-environment right now so please report if it's working.For /F "delims=\ tokens=2" %%a in ('"%~dp0PsGetSID.exe" %PXES__Guest%-501 ^2^> Nul') do Set PXES__Guest=%%a
Cacls.exe "%PXES__PXEPath%" /T /E /C /G %PXES__Guest%:C > Nul 2> Nul
Cacls.exe "%PXES__PXEPath%" /T /E /C /P %PXES__Guest%:C > Nul 2> Nul
:: Raising security to 'Read' (instead of 'Change') would make XPE complain about some 'Registration' directory
Net.exe Share PXE="%PXES__PXEPath%" /Unlimited /Cache:None /Grant:%PXES__Guest%,Change > Nul 2> Nul
:: WinXP's Net.exe doesn't know the '/Grant:...' command
If it works, I consider updating my plugin with this, but I'm not sure right now (it would add the option of using it outside of Bart, but also would increase size, would need another file from the net, and booting from outside of Bart is not the main purpose of the plugin). ...???
Yours,
Keira
Edit: Corrected the typos reported by Bilou and Jaclaz, so it's easier for visitors to copy things out of here. Also added the Nul-redirection. Thanks for this! Keira
Small typo (quote in red need to be removed) in your modified 'real Windows' code make the script fail. Still learning scripting commands, i have also changed syntax with help of others posts:
stderr redir here
and here
Currently evaluating the script on real Windows XP box before building a new BartPE Boot CD, I can easily add supplemental tools (psgetsid.exe) to the plugin dir to check it. No need to publish a modified plugin which is primarily intended for use with BartPE Boot CD.
stderr redir here
and here
QUOTE (KeiraM @ Aug 4 2007, 12:36 PM)
for /F "usebackq delims== skip=1" %%a in ('"%~dp0PsGetSID.exe ^2^>nul')
If it works, I consider updating my plugin with this, but I'm not sure right now (it would add the option of using it outside of Bart, but also would increase size, would need another file from the net, and booting from outside of Bart is not the main purpose of the plugin). ...???
Yours,
Keira
If it works, I consider updating my plugin with this, but I'm not sure right now (it would add the option of using it outside of Bart, but also would increase size, would need another file from the net, and booting from outside of Bart is not the main purpose of the plugin). ...???
Yours,
Keira
Currently evaluating the script on real Windows XP box before building a new BartPE Boot CD, I can easily add supplemental tools (psgetsid.exe) to the plugin dir to check it. No need to publish a modified plugin which is primarily intended for use with BartPE Boot CD.
@bilou
if I am not mistaken, in that snippet, if %~dp0 expands to a name containing a space it might fail.
In other words, this:
will work if %~dp0 does NOT contain spaces
while this:
should work also in that case.
jaclaz
if I am not mistaken, in that snippet, if %~dp0 expands to a name containing a space it might fail.
In other words, this:
QUOTE
for /F "usebackq delims== skip=1" %%a in ('%~dp0PsGetSID.exe ^2^>nul')
will work if %~dp0 does NOT contain spaces
while this:
QUOTE
for /F "usebackq delims== skip=1" %%a in ('"%~dp0PsGetSID.exe" ^2^>nul')
should work also in that case.
jaclaz
QUOTE (samplempg @ Mar 27 2007, 04:40 AM)
YAHOO!!!!! Finally make a sucessful DIRECT PXE BOOT 2 BARTPE (no iso or ramdisk, run my 698mb bartpe fine under 128 ram)
The result is secpol.msc need more setting tweaking ( MS makes more restrict on "guest" by default, not only just disable blank password login)
All right, DIRECT PXE BOOT 2 BARTPE is working under REAL WINXP as host pxe server....what I plan is make bartpe as pxe host server. And I belive "guest" will be a problem under bartpe. Btw still worth to try........will be continue
The result is secpol.msc need more setting tweaking ( MS makes more restrict on "guest" by default, not only just disable blank password login)
All right, DIRECT PXE BOOT 2 BARTPE is working under REAL WINXP as host pxe server....what I plan is make bartpe as pxe host server. And I belive "guest" will be a problem under bartpe. Btw still worth to try........will be continue
It is unfortunate that the secpol.msc tweaking is not detailed, so there is no published complete solution to the hang after mrxsmb.sys problem.
Maybe somebody could give complete solution for this point?
Edit: finally the few modifications to secpol.msc mentioned from this thread are sufficient; My problem was due strangely with VMWare virtual machine test. On a real machine, there is no problem booting BartPE (UBCD4Win in my case).
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.