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

I personally think it looks ugly like that i.e unbalanced.

And it then "throws" too much informations at the user as some of these informations are not needed to boot : I want optional fields to remain hidden.

 

What I could do is rather than expand vertically (and therefore beyond 600 pixels) is to expand horizontally.

Expanding vertically was probably a bad idea to start with.

You can do it balanced :-)

Yes, expanding vertically was probably a bad idea. It is better to do horizontally but to a whole does not exceed 800 pix

I have modified Tiny PXE Server to detect multiple monitors and add a veritical scrollbar if the active monitor resolution has a height <=600.

Hopefully, as a temp solution it was address Glendo00's request.

 

In parallel, I will consider redesigning the GUI to expand horizontally instead of vertically.

 

New code under the "other" button.

procedure TfrmDHCPServer.btnshowpxeoptClick(Sender: TObject);
var
monitor:TMonitor ;
height:integer;
begin
try
monitor:=Screen.MonitorFromPoint(Mouse.CursorPos);
height:=screen.Monitors[monitor.MonitorNum].Height;
except
height:=screen.Height;
end;
if btnshowpxeopt.Tag =0 then
  begin
  if height<=600 then
    begin
    VertScrollBar.Visible :=true; //need for scrollbar
    VertScrollBar.range :=800;
    self.ClientWidth :=504+4;
    end;
  self.clientHeight :=698;
  btnshowpxeopt.Tag :=1;
  exit;
  end;
if btnshowpxeopt.Tag =1 then
  begin
  if height<=600 then
    begin
    VertScrollBar.Visible :=false; //no need for scrollbar
    VertScrollBar.range :=0;
    self.ClientWidth :=504;
    end;
  self.clientHeight :=514;
  btnshowpxeopt.Tag :=0;
  exit;
  end
end;

You should not be grumpy on a sunday

I wasn't before , my common sense alarm got triggered by the "resolution autodetection" ...


 

The philosophy of Tiny PXE Server is that all fits in one screen while remaining as simple as possible : "click and play".
One should normally not have to expand the lower part of the screen to pxe boot unless one has specific needs.

Which is a definite improvement  from the "dancing tabs" that *some other* tool used to sport .

 

Wonko

...Me not changing the zip file name (i.e including the build/version and/or datetime) is a PITA.
 
But as many web sites point to my hosting place, i cannot change the zip file or else all remote sites would have a broken link.
I could use reboot.pro to host these files and update the meta informations there but I had many issues in the past : could not upload anymore, etc ...
 
I will add a meta file to the zip package to mitigate that versioning issue....

Completely understand the difficulties when other sites link to the download. The addition of a meta file with version info seems the most simple answer - thanks erwan.l.

The forum resident grumpy b@5t@rd has also made some useful suggestions - cheers wonko

I'll look at updating the guide soon to reflect the gui changes once you decide on a layout.

Regards,

Misty

P.s. @erwan.l - just out of curiosity, have you updated or added any other files in the new download?

P.s. @erwan.l - just out of curiosity, have you updated or added any other files in the new download?

 

I have updated the executable today.

Not a big change : a vertical scrollbar will appear when pushing the "other" button when using a monitor with resolution <= 600.

 

Which is a definite improvement  from the "dancing tabs" that *some other* tool used to sport .

 

Wonko

 

 

"Touché"

And this "other tool" got so much better thanks to the feedback provided.

 

Lesson leanred : after today's discussion, TPS will most probably have a reviewed GUI in a next version.

Hi Erwan.l,
 
Shouldn't the version number be update?
 
I have an older download of version 1.0.0.20 and from the pxesrv.txt file

1.0.0.20
added : new option wsMinimized in config.ini to start the app minimized
fixed : @mac,@ip,@arch added to dhcp_offer (was only dhcp_ack before)
fixed : pool start correct when opt54 set in ini file
todo : send arch in dhcp offer
added : @opt54 variable next to @mac,@ip,@arch -> similar to ${next-server} in ipxe
fixed : next server passed to send_dhcpoffer and send_dhcpac

Using the same version 1.0.0.20 when you did changes and released a new version is confusing!

 

Thanks for you hard work on TPS

The fact that we are complaining about the resolution / gui and version numbering speaks volumes about just how great and stable Tiny PXE Server actually is.

Thanks erwan.l

To paraphrase Wayne and Garth - "we are not worthy"

Misty

Hi,

 

 

OK, now I understand.  I like it!  Would you mind sharing how you do that?  I'd like to give it a try.

 

Currently I have my Tiny PXE Server system booting Windows XP Pro from a USB flash drive.  It starts Easy2Boot with a 3 second delay and then starts XP if no keypress.  If I choose, I can boot any of a number of ISO's or other utility programs, etc.  For that machine it should be easy to modify the menu to launch iPXE.  But on my Win8/10 machines it would be handy to have the menu option set up they way you have yours.

Thanks,

Glen

 

 

This  Grub4Dos NetBoot Win7.rar   417.03KB   6 downloads is the install script I use run Install.cmd as Administrator.

 

I forgot to mention that I use Grub4Dos to load gPXE.

Hi Misty,
 
By the way did you know that several links in your webpages don't work!
 
Some links have inverted slashes like this:

http://www.mistyrebo...files/bcd_files\_boot.wim_bios\cmd.txt

 

the correct link is http://www.mistyrebo...files/bcd_files/_boot.wim_bios/cmd.txt

 

About the Wimboot problem when using grub4dos did you use grub4dos from chenall? I don't think it works on the "normal" grub4dos.

 

Sorry for the out of topic post.

...By the way did you know that several links in your webpages don't work!
 
Some links have inverted slashes like this:

http://www.mistyrebo...files/bcd_files\_boot.wim_bios\cmd.txt
 
the correct link is http://www.mistyrebo...files/bcd_files/_boot.wim_bios/cmd.txt

I haven't noticed any problems myself - may be browser related. Can you please be a bit more specific (which pages/links)?

...About the Wimboot problem when using grub4dos did you use grub4dos from chenall? I don't think it works on the "normal" grub4dos...

I honestly don't remember which version. Unless specified it was likely to be the one included in the Tiny PXE Server I was using at the time of the tests.

Regards

Misty

I haven't noticed any problems myself - may be browser related. Can you please be a bit more specific (which pages/links)?

 

The example I post above is from http://www.mistyrebo...e_bcd.htm#speed

Wow! I hardly know where to start! My inbox was flooded with Reboot messages when I signed in today. I thought, Oh no, I must have opened a hornets nest or something. And man, did I ever!

 

@errwan.l:

I had no idea I would be the cause of starting such a ruckus. I have to tell you that I am impressed with your self-possessed calm, quiet, gentle manner of responding to everyone. Remarkable.

 

@Everyone:

I read your posts on this topic to my wife and we loved them all. I appreciate the way that you guys can be open and straight forward in dealing with each other and yet remain kind and not get upset with each other. Nothing unkind and always respectful. Way cool.

 

@Wonko:

Maybe I put the wrong inflection on your words when I read them to my wife, but we were howling with laughter! Erwan was right, you shouldn't be grumpy on Sunday. <grin>

 

 

Have a great day!

 

Glen

Hi Glendon00,

 

You should see something like the below.

 

If detect a screen height inferior or equal to 600, when you push the "other" button TPS will add a toolbar to the right allowing you to scroll in the main form.

 

If it does not work at your side it could be :

-my code does not detect correctly your screen height

-you may have multiple screens and my code does not detect

-the download is not working.

 

I will now add a text file to the zip with the datetime of the latest compilation.

 

For reference, below the modified code

procedure TfrmDHCPServer.btnshowpxeoptClick(Sender: TObject);
begin
if btnshowpxeopt.Tag =0 then
  begin
  if screen.Height<=600 then
    begin
    VertScrollBar.Visible :=true;
    VertScrollBar.range :=800;
    self.ClientWidth :=504+4;
    end;
  self.clientHeight :=698;
  btnshowpxeopt.Tag :=1;
  exit;
  end;
if btnshowpxeopt.Tag =1 then
  begin
  if screen.Height<=600 then
    begin
    VertScrollBar.Visible :=false;
    VertScrollBar.range :=0;
    self.ClientWidth :=504;
    end;
  self.clientHeight :=514;
  btnshowpxeopt.Tag :=0;
  exit;
  end
end;

Regards,

Erwan

 

 

 

Hi erwan,

 

You were correct in your prognosis, the systems I tested the new TPS on were dual monitor capable.

 

I ran another test on a system with only one video output and your change worked beautifully! I saw things I had never seen before, even at 1024x768! And toggling the extra option s area on and off does not truncate the upper display area like it does normally. But it only works on that single port system.

 

Here is the strange part; on the system where TPS normally resides, the secondary monitor defaults to 640x480 (since it has not been enabled or configured). I would expect that the code should either ignore the disabled secondary, or recognize it as <=600.

 

In any case, I added a second monitor to the system and configured it for 800x600 but there was no change. Somehow having a secondary monitor messes with the code, regardless of configuration.

 

Somehow I expect that you will make some small change and all will be as it ought.

 

Thank you very much,

 

Glen

@erwan.l:

 

I like the idea of a config line in the .ini file. I love having the computer do things automatically, but over the years I have come to resign myself to the fact that computers are dumb and the brunt of automating anything on them falls to the programmers. And even the best programmers can't anticipate all the variables in the real world.

 

Therefore, sigh, it is oft times necessary to resort to manual methods like config files. Big sigh…

 

I like your idea about expanding horizontally. Seems like a good solution. And keeping rarely needed fields hidden but easily accessible also makes good esthetic sense to me.

 

Have a great day!

 

Glen

@erwan.l:

 

I just downloaded the latest TPS, and it works! To a point.

 

Remember my previous comment about real world variables and that the best programmers can't anticipate them all? Well…

 

It never occurred to me that it might be an issue, and it should have.

 

On my primary TPS system I am not only running at 800x600 resolution, but I have also set the system font to 120%. So I don't even see the 'Other' options button.

 

As a temporary workaround I have reduced the system font back to the normal setting and now I can see everything and the scroll bar works. This will have to do until such time as you may decide to change the GUI.

 

If and when you make any further changes, would you mind testing them at 120% font size when running at 800x600? I know it is a pain to change that as a reboot is required, but it would make it so much better if I could use the larger font size.

 

I have to say again how much I appreciate what you have done to help me make better use of TPS.

 

Have a great day!

 

Glen

Is it possible to use a variable to set the boot url in PXE menus as it is in iPXE?

 

Thanks,

 

Glen

 

Hi all,

 

I have searched and searched but have not found a good answer to my next question.  What method(s) do you all use to edit the BCD in PE images?

 

Thanks,

 

Glen

Hi all,

 

I have searched and searched but have not found a good answer to my next question.  What method(s) do you all use to edit the BCD in PE images?

 

Thanks,

 

Glen

 

Hi Glen,

 

You can use bootice : nice proggie, nice GUI.

You can use bcdedit or offlinereg from the command line (if you want to automate, etc).

 

Regards,

Erwan

Is it possible to use a variable to set the boot url in PXE menus as it is in iPXE?

 

Thanks,

 

Glen

 

You mean the below line in an iPxe script?

If so, this custom variable in ipxe is independant of TPS : you can set it to whatever variable coming from either the system itself or the dhcp lease.

set boot-url http://${next-server}

@erwan.l:

 

On my primary TPS system I am not only running at 800x600 resolution, but I have also set the system font to 120%. So I don't even see the 'Other' options button.

 

If and when you make any further changes, would you mind testing them at 120% font size when running at 800x600? I know it is a pain to change that as a reboot is required, but it would make it so much better if I could use the larger font size.

 

 

 

Hi Glen,

 

Just tried it at 125% and I see what you mean.

I should be able to implement a quick workaround to mitigate that until I come with a more permanent solution.

 

Regards,

Erwan

...What method(s) do you all use to edit the BCD in PE images?...

My preference is the command-line bcdedit - shameless plug - check out my guide - http://www.mistyrebo...uments/BCDEdit/

Misty

Since it is monday and I am allowed to be grumpy by definition...
... I won't give you this satisfaction and post a plain comment instead ....
 
Expected:
version.txt <- this upon double click will open in most systems in Notepad or Wordpad

Tiny PXE Server version 1.0.0.20
jan 22, 2017 - 14:24:15
CRC32: 3304D444
MD5: 53416A419324AD154A77BEB75724F79C
SHA-1: 3032029CF01C6439149774F1094F0EDD74CBB31B

 
What I got instead:
pxesrv.nfo <- this upon double click will open on many systems in Microsoft System Information and throw an error

pxesrv.exe version 1.0.0.20
?jan 22, ?2017 - ??14:24:15
CRC32: 3304D444
MD5: 53416A419324AD154A77BEB75724F79C
SHA-1: 3032029CF01C6439149774F1094F0EDD74CBB31B

 
Anyway, better than nothing.
 
More seriously (but not much) why the question marks? Your compiler (or whatever) is not too sure about its date and time?
 
Now, hopefully, some constructive critique.
 
The thingy - as is - is unusable, in the sense that noone would normally be able to understand what to do in the interface and the FAQ document doesn't give much information (please read as none).
 
In a perfect world, since we already have a nice help document/manual by Misty, simple, clear and rather detailed, it would be included in the download, either as a set of html files or "compiled" into a .chm etc., or at least you could add a web link to it in the FAQ.
 
As a side-side note I would make the right pointing arrow (that enlarges the interface below) a down pointing arrow and label it "More" instead of "Other" (but of course this has a near zero relevance).
 

Wonko

All good feedback as always, thanks Wonko !

 

-pxesrv.nfo will be renamed to version.txt (dont mind the '?', my nas/filesystem is mixing unicode characters these days which is a bit worrying...).

-Misty excellent documentation should definitely be more visible : it will be on the intiial post AND possibly in the zip file

-The "other" will be renamed to "more" with a down pointing arrow - this until I rework the interface to expand horizontally

 

Erwan

@erwan.l:

 

I just downloaded the latest TPS, and it works! To a point.

 

Remember my previous comment about real world variables and that the best programmers can't anticipate them all? Well…

 

It never occurred to me that it might be an issue, and it should have.

 

On my primary TPS system I am not only running at 800x600 resolution, but I have also set the system font to 120%. So I don't even see the 'Other' options button.

 

As a temporary workaround I have reduced the system font back to the normal setting and now I can see everything and the scroll bar works. This will have to do until such time as you may decide to change the GUI.

 

If and when you make any further changes, would you mind testing them at 120% font size when running at 800x600? I know it is a pain to change that as a reboot is required, but it would make it so much better if I could use the larger font size.

 

I have to say again how much I appreciate what you have done to help me make better use of TPS.

 

Have a great day!

 

Glen

 

Hi Glen,

 

If you add vscroll=1 in config.ini under [dhcp] section, you should now have a permanent vertical scrollbar allowing you to display the whole form on any screen resolution and dpi.

 

Let me know how it works for you.

 

Regards,

Erwan