Jump to content











Photo

Bug Reports, Requests, HowTo's about Tiny PXE Server

pxe network boot

  • Please log in to reply
805 replies to this topic

#276 venerence

venerence

    Newbie

  • Members
  • 18 posts
  •  
    Australia

Posted 17 May 2015 - 03:30 AM

I have been trying to boot winpe via wimboot for a diagnostic environment I run, and I have encountered a limitation that was brought up over two years ago in ipxe.

 

http://forum.ipxe.or...ad.php?tid=6061

 

Apparently ipxe doesn't pass the wim file correctly into ram if it is over 330mb (my particular wim is ~450mb). I've tried swapping out the boot.wim for a smaller one and it works fine.

 

Is there a workaround for this aside from loading it all into memdisk? I'd prefer to avoid this since it basically doubles the memory requirement of the boot.



#277 erwan.l

erwan.l

    Gold Member

  • Developer
  • 2346 posts
  • Location:Nantes - France
  •  
    France

Posted 17 May 2015 - 10:02 AM

I have been trying to boot winpe via wimboot for a diagnostic environment I run, and I have encountered a limitation that was brought up over two years ago in ipxe.

 

http://forum.ipxe.or...ad.php?tid=6061

 

Apparently ipxe doesn't pass the wim file correctly into ram if it is over 330mb (my particular wim is ~450mb). I've tried swapping out the boot.wim for a smaller one and it works fine.

 

Is there a workaround for this aside from loading it all into memdisk? I'd prefer to avoid this since it basically doubles the memory requirement of the boot.

 

Hi,

 

Have you tried latest wimboot releases? see here : https://git.ipxe.org/release/wimboot/.

If memdisk or wimboot dont give you satisfaction, you may try sanboot+http, or sanboot+iscsi/aoe.

 

Regards,

Erwan



#278 venerence

venerence

    Newbie

  • Members
  • 18 posts
  •  
    Australia

Posted 19 May 2015 - 12:20 AM

Hi,

 

Have you tried latest wimboot releases? see here : https://git.ipxe.org/release/wimboot/.

If memdisk or wimboot dont give you satisfaction, you may try sanboot+http, or sanboot+iscsi/aoe.

 

Regards,

Erwan

 

Latest wimboot does the same thing, unfortunately.

 

That being said, sanboot seems to work fine, I'll stick with that. Cheers.



#279 misty

misty

    Silver Member

  • Developer
  • 928 posts
  •  
    United Kingdom

Posted 14 June 2015 - 11:05 PM

Dear Erwan.l,

You are a genius. :worship:

I'm no stranger to PXE booting and have used tftpd32 and Serva in the past - both are excellent pieces of software. I haven't set up a PXE server for 2-3 years as I've just not needed to and haven't had the time for playing around due to other commitments - needless to say I was pretty much starting from scratch having forgotten most of the steps involved.

I still don't need to PXE boot, however ipxe + wimboot over http seemed like fun. It actually proved quite a challenge as information is scattered across several threads and it's taken me a while (most of my free time over this weekend) and lots of experimentation to get things working.

I decided to try a standard WinPE boot by chainloading Boot/pxeboot.0 from pxelinux.0 - I just wanted to see if I could get a simple setup that I'm familiar with working first. It seemed so much slower than I remembered - until I had a lightbulb moment and realised that I was actually running Tiny PXE Server over a wireless connection! Once I managed to get it working via ethernet it was significantly faster.

My home network has a DHCP server built into my internet router and switching this off is not an option. It was nice to see that your Proxy DHCP implementation worked flawlessy :worship:

On to wimboot - once the pxelinux setup was working this proved relatively straightforward.

I figured now was the time to try a RIS install of Windows XP - just for old times sake - after all, this was my main reason for experimenting with PXE booting in the past. This took a little more effort on my part, however it's working. My initial efforts failed on two systems with a BSOD (*** STOP: 0x000000BB) error. I downloaded a much more recent driver pack and tried again using a different system - it worked. The BINL intergration is a real time saver. :worship:

I'll retest the two systems that gave the STOP: 0x000000BB error over the next few days just to see if the undated drivers make a difference - the systems were both old thinkpads - a T61 and an X61 respectively. The errors may be due to other factors - Proxy DHCP was used for these tests. The working test was completed using a crossover cable and the Proxy DHCP wasn't used.

Seeing the Windows XP setup was like seeing a long lost friend! Almost bought a tear to my eye.

Many thanks for all of the hard work and time you have clearly put into developing Tiny PXE Server. My only regret is that it's taken me so long to get around to testing this fantastic software.

Regards,

Misty

EDIT - Just completed a quick test with the Thinkpad X61. I used a similar setup to yesterday (with Proxy DHCP). Only difference was using a Windows 7 system on the Server side (I was using XP when it BSOD'd with the STOP: 0x000000BB error) with the most recent LAN Driver Pack. RIS install did not crash this time. I didn't complete the install - just tested to check if it completed as far as selecting the drive to install XP to. I'm not in a position to test with a Windows XP server again until later (maybe tomorrow) - I'll report back. It will be interesting to isolate whether the crash was due to the drivers or the OS running Tiny PXE Server.

#280 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 14404 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted 15 June 2015 - 09:56 AM

The BINL intergration is a real time saver. :worship:

Yep :), guess who exactly managed to trick erwan.l into adding it? ;)
 

You are a genius.
...
It actually proved quite a challenge as information is scattered across several threads and it's taken me a while (most of my free time over this weekend) and lots of experimentation to get things working.

So, someone who is very good at writing manuals/guides/howto's finds something  that he likes and it is missing a proper, structured, guide, what may come out of this?  :dubbio:

I guess that someone just got himself his next assignment....  :whistling:

 

:duff:

Wonko



#281 misty

misty

    Silver Member

  • Developer
  • 928 posts
  •  
    United Kingdom

Posted 16 June 2015 - 08:58 PM

The BINL intergration is a real time saver. :worship:

Yep :), guess who exactly managed to trick erwan.l into adding it? ;)

Up to your old tricks then Wonky?
 

You are a genius.
...
It actually proved quite a challenge as information is scattered across several threads and it's taken me a while (most of my free time over this weekend) and lots of experimentation to get things working.

So, someone who is very good at writing manuals/guides/howto's finds something that he likes and it is missing a proper, structured, guide, what may come out of this? :dubbio:

I guess that someone just got himself his next assignment.... :whistling:

Thanks for the compliment - I think! Are you flattering me in order to manipulate me by any chance? It worked!! Assignment kind of accepted. I'm still waiting on he who should not be named to proof read the last guide I put together :whistling:

I've got a lot on at the moment. I'd love to put something together to try and do justice to erwan.l's great work, however I won't be able to do much over the next few weeks due to other commitments. Also the scope of any guide will be pretty extensive as erwan.l appears to have crammed pretty much every available PXE boot manager/loader into the download - have you seen the latest Syslinux package - it's frightening!!!

Regards,

Misty

#282 erwan.l

erwan.l

    Gold Member

  • Developer
  • 2346 posts
  • Location:Nantes - France
  •  
    France

Posted 17 June 2015 - 08:06 PM

Dear Erwan.l,

You are a genius. :worship:

 

 

 

Hi Misty,

 

Such nice warm message makes me a good day, if not my week :)

 

Thanks a lot for this very positive feedback : much appreciated !

 

This forum was actually a great source of inspiration and Wonko definitely was key into driving me into specific directions (like BINL).

The only thing he could managed me to do was a documentation :)

You can however find some tutorials here and some dry tips here.

 

Regards,

Erwan



#283 erwan.l

erwan.l

    Gold Member

  • Developer
  • 2346 posts
  • Location:Nantes - France
  •  
    France

Posted 17 June 2015 - 08:08 PM

have you seen the latest Syslinux package - it's frightening!!!

 

 

Indeed.

And it breaks compatibility with chailoading from one boot loader to the other.

Hence me sticking to 4.x for now.



#284 misty

misty

    Silver Member

  • Developer
  • 928 posts
  •  
    United Kingdom

Posted 18 June 2015 - 09:04 PM

EDIT - Just completed a quick test with the Thinkpad X61. I used a similar setup to yesterday (with Proxy DHCP). Only difference was using a Windows 7 system on the Server side (I was using XP when it BSOD'd with the STOP: 0x000000BB error) with the most recent LAN Driver Pack. RIS install did not crash this time. I didn't complete the install - just tested to check if it completed as far as selecting the drive to install XP to. I'm not in a position to test with a Windows XP server again until later (maybe tomorrow) - I'll report back. It will be interesting to isolate whether the crash was due to the drivers or the OS running Tiny PXE Server.


Forgot to report back - I retested using Windows XP on the server side with the most recent version of the LAN driver pack - RIS install completed successfully.

:thumbsup:

Also just tested booting MistyPE (WinPE 3.1 base) through WDS as per section 7 of the FAQ in the pxesrv.zip download -

7.how to pxe boot winpe3 (wim) thru WDS
enter wdsnbp.com as boot filename
enter pxeboot.com as proxydhcp boot filename
enter boot\bcd as proxydhcp option 252
note : put bootmgr.exe in root folder, boot.wim in sources folder and boot.sdi in boot folder
note: wds files can be found in boot.wim of windows7/2008 installation files (\windows\boot\pxe)
note: see here how to customize a winpe http://ipxe.org/howto/winpe

Following is the config I used on my system (it might help others - took me a while to figure out the settings) -
[dhcp]
;needed to tell TFTPd where is the root folder
root=files
httpd=0
binl=1
start=1
dnsd=1
proxydhcp=0
tftpd=1
bind=1
opt54=192.168.2.1
poolstart=192.168.2.10
poolsize=5
; opt3 and opt6 should be same as server IP (opt54)
opt3=192.168.2.1
opt6=192.168.2.1
opt28=0.0.0.0
; opt66 should be set as servers Computer Name
opt66=MY-PC
opt67=wdsnbp.com
; opt252 can be used to change path to BCD store
opt252=BOOT\BCD
;alternative bootp filename if request comes thru proxydhcp (udp:4011)
proxybootfilename=pxeboot.com
log=1
I tested this using two laptops linked with a crossover cable so I didn't need to use the Proxy DHCP option.

I renamed pxeboot.n12 (extracted from \Windows\Boot\PXE\ directory in my boot.wim file) as pxeboot.com to avoid the need to press F12.

I found the following useful (from http://www.msfn.org/...up-wds-for-pxe/) as it helped me identify which settings to add to my config file (see above) -
 

4. Setting up PXE on the DHCP Server
- in the DHCP cpl, expand your scope and right Click on Scope Options and select Configure Options.
- select option 66 and type in the computer name of the WDS (ie: unclesocks)
- select option 67 and type in '\boot\x86\wdsnbp.com'
- select option 6 (DNS Servers) and type in the IP for the WDS server.
- select option 3 (Router) and type in the IP for the WDS server.


Main advantage of this method is the ability to specify a BCD store in the none default \BOOT\BCD path.

Great work Erwan.

Now what do I play around with next - it's great fun!

Regards,

Misty

#285 misty

misty

    Silver Member

  • Developer
  • 928 posts
  •  
    United Kingdom

Posted 24 June 2015 - 04:15 PM

Approximately five years ago I remember watching a recording of a gPXE presentation which seriously impressed me - presentation included Michael Brown (I think!) PXE booting and loading a disk image via HTTP over the internet - wirelessly if memory serves. Being inspired by the presentation I played around with this myself - fun stuff!!! The other bit of the presentation that seemed even more incredible (to me!) was SANBooting a full Windows XP system - sadly I had neither the time, hardware, knowledge or information to attempt this.

Five years is a long time and now, thanks to erwan.l and the respective teams/individuals behind iPXE, AoE and VBlade (used with Erwan'l's GUI :thumbsup:) I too was able to boot Windows XP from a network drive. A very sincere thanks to you Erwan for making this possible - it's been fun.

Windows 7 has been less fun and very bloody frustrating!!! :frusty:

I've spent a considerable amount of my free time and followed all the instructions I can find and it still hangs on the bloody splash screen. Any hints/tips? A confirmed to be working config file might help.


My Windows XP SANBoot AoE Experiment

My plan was to install Windows XP on an old laptop (a Thinkpad X61), then copy it to a 2GB disk image and transfer it to my home server so that I could SANBoot it - note Home Server is a grand term for an old desktop system that runs headless and sits in a cupboard - I lost the use of the room it used to live in when my youngest daughter was born! Here's my rough notes -


Client
Installed XP on the X61 laptop (RIS install using Tiny PXE Server) - the X61 BIOS was in AHCI mode - driverpacks were slipstreamed into the Windows XP source on the SERVER prior to the RIS installation - not sure this makes any difference, but I thought I'd mention it anyway!

Booted Windows XP on the X61 and installed the LAN driver and then set the pagefile as 128MB (fixed size) on drive C: - system rebooted - reboot following change to pagefile was probably not required. Reason for reducing the size of the pagefile was to ensure that the 2GB disk image didn't get quickly filled with a huge pagefile.

Following reboot - installed AoE Driver using the instructions here - http://etherboot.org...nboot/winnt_aoe (Windows AoE driver downloaded from http://winaoe.org/).

Checked the Service name for the Network Card on the X61 (identified it in under the Network adapters listed in device manager > right click > properties > Details (tab) - selected service in the Property drop box - in my case e1express)

Opened regedit and navigated to HKLM\System\CurrentControlSet\services\e1express - changed the start value to 0.

A number of instructions also mention installing CCBoot client - this wasn't required on my system.

Turned off the Windows XP firewall just to ensure that this didn't create any problems. Thats it in terms of configuring Windows XP on the client side.


Disk Image
Rebooted the X61 and booted into WinPE - PXE boot using Tiny PXE Server.

Checked the drive letter of my local Windows XP installation - it was C: (remember I'm running WinPE - systemdrive is X:) - this is the path to my source files.

Mounted my 2GB disk image via ImDisk as drive R: - note that the disk image was already partitioned and formatted - in this case using compressed NTFS.
Mounted the only partition/volume in my 2GB disk image via ImDisk as drive R: - note that the disk image was already partitioned. The existing partition spanned the whole disk and was formatted using compressed NTFS.

Copied the contents of drive C: to drive R: using the batch file below -
@echo off
setlocal
SET SOURCE=C
SET DEST=R

echo copying files
xcopy %SOURCE%:\ %DEST%:\ /exclude:%~dp0exclude.txt /e /c /i /h /k /x /y /w

echo.
echo.
endlocal
pause
exit
Contents of exclude.txt -
:\RECYCLER
:\$Recycle.Bin
:\bootstat.dat
:\hiberfil.sys
:\pagefile.sys
:\PerfLogs
:\System Volume Information
\Temp\
\Temporary Internet Files\
Now in the mounted disk image (drive R:) that now contains the copied Windows XP installation.
Now in the ImDisk mounted partition (drive letter R:) within my disk image that now contains the copied Windows XP installation -

Due to my system setup I needed to edit the path in R:\boot.ini from -


[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(2)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Microsoft Windows XP Professional (hd0,1)" /noexecute=optin /fastdetect
to -
[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional (hd0,0)" /noexecute=optin /fastdetect
Mounted the system registry hive R:\Windows\system32\config\system as _WinAoE

Edited HKLM\System\_WinAoE\System\MountedDevices key and deleted all of the entries to ensure that the physical disk in the X61 was reallocated drive letters when the disk image was booted from the server later.

EDIT - forgot to mention earlier that the disk initially failed to boot as ntldr (and possibly ntdetect.com) were compressed - uncompress them now if following these steps.

Unmounted the disk image and copied it to the SERVER.
Unmounted Drive R: (the partition within my disk image) and then copied the disk image to the SERVER.



Server

Installed WinPcap_4_1_3.exe

Installed Vblade - basically I used 7-zip to extract vblade.exe and cygwin1.dll from winaoe.msi to the same directory as Erwan's vGui.exe - I didn't need to run the .msi file.

Started VBlade via the GUI and pointed it to my disk image containing the Windows XP files copied earlier.

Started Tiny PXE Server - I'll double check my config file later as I don't have access to it at the moment - the following entries were certainly in it -
[dhcp]
root=files
filename=ipxe.pxe
altfilename=aoe.ipxe
httpd=1
binl=0
start=1
dnsd=1
proxydhcp=0
tftpd=1
bind=1 
aoe.ipxe script -
#!ipxe
dhcp net0
set keep-san 1
sanboot aoe:e0.0
boot
Notes

Despite using a disk with a different disk signature it worked without any issues.

Copying XP in this way to a disk image is well documented in the firadisk thread elsewhere on this forum.

This method allowed me to keep my laptop intact - I didn't have to worry about removing the hard disk or changing the disk signature to avoid conflicts before SANBooting XP.

I hope this information helps others.

Regards,

Misty

P.s. Post edited to stop Wonko moaning :whistling:

#286 erwan.l

erwan.l

    Gold Member

  • Developer
  • 2346 posts
  • Location:Nantes - France
  •  
    France

Posted 24 June 2015 - 04:48 PM

Hi Misty,

 

Very nice post and surely every helpful for the other guys who want to pxe boot their windows xp using AOE.  :clap:

Note that the same approach could be used with iSCSI (in place of AOE).

 

AOE on Win7 has always be a PITA for me : I kinda remember that i had to install CCBoot client on Win7 but could never explain why (is it a registry detail, an extra component, ...).

Hence my preference going to iSCSI (native component) when dealing with Win7.

 

About the disk image, you used this specific approach (copy files to a new image) to get a 2gb disk image as your original disk was bigger right?

 

Last but not least, what is fun as well : install win7 directly to an Iscsi drive. Here (ipxe) and Here (gpxe).

 

Well done,

Erwan



#287 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 14404 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted 24 June 2015 - 04:52 PM

Mounted my 2GB disk image via ImDisk as drive R: - note that the disk image was already partitioned and formatted - in this case using compressed NTFS.

No, you did not. :(

 

Remember that I am picky (and particularly sensible to this long time mixup of terms), what you did was to access a volume inside the partitioned disk image by mounting it (the volume) to a drive letter, and while what was partitioned was the disk (image) what was formatted was just the partition or volume.

 

IMDISK can mount volumes (and NOT disk images).

A drive letter is assigned to a volume (and NOT to a disk image).

 

Very nice and interesting report :thumbup: however. :)

 

 

:duff:

Wonko



#288 misty

misty

    Silver Member

  • Developer
  • 928 posts
  •  
    United Kingdom

Posted 24 June 2015 - 09:44 PM

@erwan.l

About the disk image, you used this specific approach (copy files to a new image) to get a 2gb disk image as your original disk was bigger right?

Correct. Original disk is a 60GB SSD - I could have cloned the whole disk if I'd had the patience. I was away from home and would have lost the will to live cloning 60GB to a USB 2.0 external drive so I though I'd give the Firadisk file copy method a go - I knew that I could easily get away with a 2GB disk image for testing purposes.
 

Last but not least, what is fun as well : install win7 directly to an Iscsi drive. Here (ipxe) and Here (gpxe).


I've checked out the links for installing iPXE or gPXE to an ISCSI drive - looks interesting. Unfortunately I can't test it at the moment as Starwind registration won't allow me to use my live.com email address :frusty:


@wonko
Sorry - I was feeling lazy.

Regards,

Misty

#289 reboot12

reboot12

    Frequent Member

  • Advanced user
  • 228 posts
  • Interests:WinXP, Debian, OpenWrt, gPXE, iPXE, BIOS, EFI, Coreboot, MS VirtualPC, VMware
  •  
    European Union

Posted 06 July 2015 - 05:17 AM

I test new version 1.0.0.19 but i need run other tools while TPS is running. I have config.ini like this:
start=1
cmd=FreeNFS.exe
but this works only if click Online button. I use this for boot Debian Live over PXE with NFS file system:
LABEL live
MENU LABEL Debian Live 486
kernel images/debian-live/vmlinuz
append initrd=images/debian-live/initrd.img boot=live config netboot=nfs ip=dhcp nfsroot=/debian-live
Please fix this to possible run while TPS running. Thx

P.S. I think that the NFSd server should be integrated into the TPS such as HTTPd, TFTPd, DHCPd

to misty: To install WinXP with iSCSI please read my posts from this: iSCSI

WinXP possible install to iSCSI, from iSCSI and another way :-)

#290 erwan.l

erwan.l

    Gold Member

  • Developer
  • 2346 posts
  • Location:Nantes - France
  •  
    France

Posted 06 July 2015 - 08:19 AM

I test new version 1.0.0.19 but i need run other tools while TPS is running. I have config.ini like this:

start=1
cmd=FreeNFS.exe
but this works only if click Online button. I use this for boot Debian Live over PXE with NFS file system:
LABEL live
MENU LABEL Debian Live 486
kernel images/debian-live/vmlinuz
append initrd=images/debian-live/initrd.img boot=live config netboot=nfs ip=dhcp nfsroot=/debian-live
Please fix this to possible run while TPS running. Thx

P.S. I think that the NFSd server should be integrated into the TPS such as HTTPd, TFTPd, DHCPd

 

 

You mean you want freenfs.exe to be starting as soon as you launch TPS if start=1?

I can fix that.

 

About implementing a NFSd in TPS is too much work for now for me.



#291 reboot12

reboot12

    Frequent Member

  • Advanced user
  • 228 posts
  • Interests:WinXP, Debian, OpenWrt, gPXE, iPXE, BIOS, EFI, Coreboot, MS VirtualPC, VMware
  •  
    European Union

Posted 06 July 2015 - 08:58 AM

I think that you need delete run 'cmd=' after clik Online button to prevent run cmd tool twice if click Offline and Online button

cmd= need only work while TPS autostart (start=1)

#292 erwan.l

erwan.l

    Gold Member

  • Developer
  • 2346 posts
  • Location:Nantes - France
  •  
    France

Posted 06 July 2015 - 05:41 PM

I think that you need delete run 'cmd=' after clik Online button to prevent run cmd tool twice if click Offline and Online button

cmd= need only work while TPS autostart (start=1)

 

Actually it was a bug : i was launching the external command even before I completed parsing the ini file...

 

Download again : latest version should work as you expect, i.e it will autostart then launch the external command.



#293 reboot12

reboot12

    Frequent Member

  • Advanced user
  • 228 posts
  • Interests:WinXP, Debian, OpenWrt, gPXE, iPXE, BIOS, EFI, Coreboot, MS VirtualPC, VMware
  •  
    European Union

Posted 06 July 2015 - 06:29 PM

Fix work but if click Offline and Online have error:

Attached File  twice_cmd.png   9.33KB   0 downloads

 

Because the tool is already running. It could so to be but better solution is remove the possibility of launching cmd after click Online. Only while start TPS with start=1



#294 erwan.l

erwan.l

    Gold Member

  • Developer
  • 2346 posts
  • Location:Nantes - France
  •  
    France

Posted 06 July 2015 - 06:43 PM

Fix work but if click Offline and Online have error:

attachicon.giftwice_cmd.png

 

Because the tool is already running. It could so to be but better solution is remove the possibility of launching cmd after click Online. Only while start TPS with start=1

 

start=1 will actually simply simulate the button click.

 

The error you get is because freenfs is already running.

Indeed, offline will not stop/kill the external command and clicking online will not check if the external command is already running.

 

I was thinking thus of killing the external command on clicking on offline.



#295 reboot12

reboot12

    Frequent Member

  • Advanced user
  • 228 posts
  • Interests:WinXP, Debian, OpenWrt, gPXE, iPXE, BIOS, EFI, Coreboot, MS VirtualPC, VMware
  •  
    European Union

Posted 06 July 2015 - 06:55 PM

Truthfully Online and Offline buttons are useful only during testing TPS. During normal usage, run the TPS only with option start=1 and close the program when it is no longer needed :-)
 
P.S. If you want add close external program to Offline button then need check PID while this program is running with cmd=
tasklist /fi "imagename eq FreeNFS.exe"

Image Name                     PID Session Name        Session#    Mem Usage
========================= ======== ================ =========== ============
FreeNFS.exe                   2068 Console                    0      6 048 K
and add function to close program by PID e.g. in WinXP is taskkill:
taskkill /pid 2068 /t
SUCCESS: Sent termination signal to process with PID 2068, child of PID 932.
PID 932 is Tiny PXE Server at this moment.

#296 Sfor

Sfor

    Newbie

  • Members
  • 24 posts
  •  
    Poland

Posted 06 July 2015 - 07:14 PM

Well, I use both Online and Offline buttons quite often during normal operations. I can remotely switch between installed OS and rescue and backup PXE OS just by turning the TPS online or offline and then to reboot. So, these buttons are very useful to me.

 

The ability to quickly and simply switch the PXE serwer on and off was exactly what I needed. That's why TPS is a perfect tool for me.



#297 reboot12

reboot12

    Frequent Member

  • Advanced user
  • 228 posts
  • Interests:WinXP, Debian, OpenWrt, gPXE, iPXE, BIOS, EFI, Coreboot, MS VirtualPC, VMware
  •  
    European Union

Posted 06 July 2015 - 07:32 PM

The ability to quickly and simply switch the PXE serwer on and off was exactly what I needed. That's why TPS is a perfect tool for me.

No cóż, każdy używa serwera TPS w inny sposób :-). Ja używam go tylko sporadycznie, mam wszystko na nim ustawione i jak mi trzeba to sobie włączam TPS, robię co trzeba i wyłączam.

Dobrze by było mieć na stałe taki serwer np. na routerze z OpenWRT tylko, że wtedy to już nie ma nic wspólnego z Tiny PXE Server

Najlepszą funkcją w TPS jest to iż ma zintegrowany daemon HTTPd. Protokół HTTP znacznie przyspiesza proces bootowania z serwera PXE :-)

#298 erwan.l

erwan.l

    Gold Member

  • Developer
  • 2346 posts
  • Location:Nantes - France
  •  
    France

Posted 06 July 2015 - 07:32 PM

Truthfully Online and Offline buttons are useful only during testing TPS. During normal usage, run the TPS only with option start=1 and close the program when it is no longer needed :-)
 
P.S. If you want add close external program to Offline button then need check PID while this program is running with cmd=

tasklist /fi "imagename eq FreeNFS.exe"

Image Name                     PID Session Name        Session#    Mem Usage
========================= ======== ================ =========== ============
FreeNFS.exe                   2068 Console                    0      6 048 K
and add function to close program by PID e.g. in WinXP is taskkill:
taskkill /pid 2068 /t
SUCCESS: Sent termination signal to process with PID 2068, child of PID 932.
PID 932 is Tiny PXE Server at this moment.

 

 

what i could do is an external command when going online, an external command when going offline.

then, the user might script whatever he wants.

 

offline script could be : taskkill /IM freenfs.exe /F /T



#299 erwan.l

erwan.l

    Gold Member

  • Developer
  • 2346 posts
  • Location:Nantes - France
  •  
    France

Posted 06 July 2015 - 07:45 PM

Added an offline option in config.ini that will launch a script when pressing the offline button.

 

cmd=_online.bat
offline=_offline.bat
note that the below will work the same
 
online=_online.bat
offline=_offline.bat

my _offline.bat

taskkill /IM winnfsd.exe /F /T


#300 reboot12

reboot12

    Frequent Member

  • Advanced user
  • 228 posts
  • Interests:WinXP, Debian, OpenWrt, gPXE, iPXE, BIOS, EFI, Coreboot, MS VirtualPC, VMware
  •  
    European Union

Posted 06 July 2015 - 07:58 PM

Me config.ini:
cmd=FreeNFS.exe
offline=_offline.bat
and _offline.bat
taskkill /IM FreeNFS.exe /F /T
Thx. This working :clap:
https://www.youtube....h?v=IxmyllUF2FA

Also working without /T switch. In help taskkill wrote:

/T Terminates the specified process and any
child processes which were started by it.

Child process is TPS and probably try close it.

P.S. I noticed that version 1.0.0.19 is unstable and sometimes I have to restart the program because pxelinux something crashes. In version 1.0.0.11 I have not noticed such problems.





Also tagged with one or more of these keywords: pxe, network boot

1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users