GRUB4DOS for UEFI

liuzhaoyzz

2011yaya2007777 发表于 2025-7-9 19:41
要在服务器查啥？find只能查找文件在哪个硬盘，哪个分区。服务器根目录不是某硬盘的根目录。这个命令只能查 ...

原来想着如果find命令可以用于pxe的话，可以用一个菜单通杀本地menu.lst和网络启动的menu.lst菜单，以前g4d好像就可以的。

wqsohu

谢谢分享

xiaoy

用HTTP启动PE失败，蓝屏， 用TFTP协议可以启动PE.

2011yaya2007777

set http
/efi/grub/ext/ntboot /boot/winpe.wim

maomaozrm

GRUB4DOS for UEFI 留印备查

xiaoy

2011yaya2007777 发表于 2025-8-9 11:57
set http
/efi/grub/ext/ntboot /boot/winpe.wim

还是不行呢

2011yaya2007777

你的服务器是什么，http驱动又是什么？

xiaoy

https://www.dhcpserver.de/cms/download/   DHCP Server V2.5.2

2011yaya2007777

没有用过这个。他内部包含http驱动吗？

xiaoy

http驱动?  http服务么，  带http服务

mygamexxx

2011yaya2007777 发表于 2025-8-9 18:05
没有用过这个。他内部包含http驱动吗？

DHCP Server for Windows v2.5.2(最新版为2.10.0，要捐款后才能下载。以服务启动，启动文件固定后比较方便，ipxe.bios要自行编译为默认脚本autoexec.ipxe。支持HTTP)在dnsmasq配置中用下面语句可实现不编译内置脚本，加载自定义菜单，菜单名自己定。
使用VMware，7月3日新版G4E，HTTP网启测试，进入菜单正常，选择网启菜单后，不正常，返回到菜单了。可能是软件本身或设置那里有问题。
同时打开EasyWebSvr作为HTTP服务器，网启正常。
配置文件如下一楼，IPXE.EFI是成功的，引导文件名改为BOOTG4E.EFI，能出菜单，选择网启菜单项后，返回菜单。

mygamexxx

[SETTINGS]
IPPOOL_1=192.168.220.1-254
IPBIND_1=192.168.220.1
AssociateBindsToPools=1
Trace=1
DeleteOnRelease=0
ExpiredLeaseTimeout=3600

[GENERAL]
LEASETIME=86400
NODETYPE=8
SUBNETMASK=255.255.255.0
BOOTFILE=IPXE.EFI
NEXTSERVER=192.168.220.1
DNS_0=8.8.8.8
ROUTER_0=192.168.220.1

[DNS-SETTINGS]
EnableDNS=1
FORWARD=8.8.8.8

[TFTP-SETTINGS]
EnableTFTP=1
ROOT=G:\
WritePermission=1

[HTTP-SETTINGS]
EnableHTTP=1
ROOT=G:\
[00-0C-29-5A-84-0D]
IPADDR=192.168.220.2
AutoConfig=02/11/2025 11:18:31
LeaseEnd=1740707767
Hostname=minint-nlgp8dn
[00-0C-29-FC-AB-28]
IPADDR=192.168.117.3
AutoConfig=02/12/2025 15:56:25
LeaseEnd=1739851945
Hostname=minint-0utk006
[00-0C-29-52-CE-C8]
IPADDR=192.168.220.3
AutoConfig=08/11/2025 08:10:28
LeaseEnd=1754959161
Hostname=minint-4cent86

2011yaya2007777

DHCP Server for Windows v2.5.2

你这个是中文界面，我怎么是英文的？
如何向TinyPXEServer一样，指定网起文件名？而不是网起虚拟机磁盘？

xiaoy

DHCP Server for Windows最新版2.10.0   也是同样
“7月3日新版G4E，HTTP网启测试，进入菜单正常，选择网启菜单后，不正常，返回到菜单了”

mygamexxx

2011yaya2007777 发表于 2025-8-11 10:06
你这个是中文界面，我怎么是英文的？
如何向TinyPXEServer一样，指定网起文件名？而不是网起虚拟机磁盘 ...

我自己汉化的，指定网启文件名要运行dhcpwiz.exe，直接在dhcpsrv.ini配置文件中修改也可以。

2011yaya2007777

使用VMware，7月3日新版G4E，HTTP网启测试，进入菜单正常，选择网启菜单后，不正常，返回到菜单了。可能是软件本身或设置那里有问题。

我使用DHCP Server for Windows v2.5.2，网起VMware成功。但是他是启动了VMware上的 /efi/boot/bootx64.efi。从网起意义上说是成功了。
但是他没有任何网络信息，只有本地磁盘信息。不能继续测试网起。

如何先加载服务器上的bootx64.efi？

mygamexxx

2011yaya2007777 发表于 2025-8-12 10:59
我使用DHCP Server for Windows v2.5.2，网起VMware成功。但是他是启动了VMware上的 /efi/boot/bootx64.e ...

只要加入EASYWEBSERVER，启动是成功的。可能软件的HTTP有问题？

mygamexxx

出错的服务器日志如下：

[08/12/2025 11:23:01] Adapter 1 has recognized an incoming DHCP request
[08/12/2025 11:23:01] DHCP message = DHCPDISCOVER
[08/12/2025 11:23:01]    requested options: 1 2 3 4 5 6 12 13 15 17 18 22 23 28 40 41 42 43 50 51 54 58 59 60 66 67 97 128 129 130 131 132 133 134 135
[08/12/2025 11:23:01] Lookup client data for physical address "00-0C-29-52-CE-C8" / client_id "00-0C-29-52-CE-C8"
[08/12/2025 11:23:01] Client 00-0C-29-52-CE-C8 is configured with the IP address 192.168.220.3
[08/12/2025 11:23:02] Response: offer the configured IP address (lease time = 86400)
[08/12/2025 11:23:02] Sending a broadcast response to the client
[08/12/2025 11:23:02] Connection 1: sending top queue packet
[08/12/2025 11:23:05] Adapter 1 has recognized an incoming DHCP request
[08/12/2025 11:23:05] DHCP message = DHCPREQUEST
[08/12/2025 11:23:05]    requested options: 1 2 3 4 5 6 12 13 15 17 18 22 23 28 40 41 42 43 50 51 54 58 59 60 66 67 97 128 129 130 131 132 133 134 135
[08/12/2025 11:23:05] Lookup client data for physical address "00-0C-29-52-CE-C8" / client_id "00-0C-29-52-CE-C8"
[08/12/2025 11:23:05] Client 00-0C-29-52-CE-C8 is configured with the IP address 192.168.220.3
[08/12/2025 11:23:06] Response: hand out the configured IP address (lease time = 86400)
[08/12/2025 11:23:06] Sending a broadcast response to the client
[08/12/2025 11:23:06] Connection 1: sending top queue packet
[08/12/2025 11:23:06] Adapter 3 has recognized an incoming TFTP request
[08/12/2025 11:23:06] TFTP RRQ started on port_index=53: G:\PXE\BOOTG4E.EFI
[08/12/2025 11:23:06] Adapter 3 has recognized an incoming TFTP request
[08/12/2025 11:23:06] TFTP RRQ started on port_index=54: G:\PXE\BOOTG4E.EFI
[08/12/2025 11:23:07] Adapter 3 has recognized an incoming TFTP request
[08/12/2025 11:23:07] TFTP RRQ started on port_index=55: G:\PXE\efi\grub\menu.lst
[08/12/2025 11:23:07] Adapter 3 has recognized an incoming TFTP request
[08/12/2025 11:23:07] TFTP RRQ started on port_index=56: G:\PXE\efi\grub\menu.lst
[08/12/2025 11:23:07] Adapter 3 has recognized an incoming TFTP request
[08/12/2025 11:23:07] TFTP RRQ started on port_index=57: G:\PXE\efi\grub\menu.lst
[08/12/2025 11:23:07] Adapter 3 has recognized an incoming TFTP request
[08/12/2025 11:23:07] TFTP RRQ started on port_index=58: G:\PXE\efi\grub\menu.lst
[08/12/2025 11:23:07] Adapter 3 has recognized an incoming TFTP request
[08/12/2025 11:23:07] TFTP RRQ started on port_index=59: G:\PXE\efi\grub\menu.lst
[08/12/2025 11:23:07] Adapter 3 has recognized an incoming TFTP request
[08/12/2025 11:23:07] TFTP RRQ started on port_index=60: G:\PXE\efi\grub\menu.lst
[08/12/2025 11:23:07] Adapter 3 has recognized an incoming TFTP request
[08/12/2025 11:23:07] TFTP RRQ started on port_index=61: G:\PXE\efi\grub\menu.lst
[08/12/2025 11:23:07] Adapter 3 has recognized an incoming TFTP request
[08/12/2025 11:23:07] TFTP RRQ started on port_index=62: G:\PXE\efi\grub\menu.lst
[08/12/2025 11:23:08] Adapter 3 has recognized an incoming TFTP request
[08/12/2025 11:23:08] TFTP RRQ started on port_index=63: G:\PXE\efi\grub\menu.lst
[08/12/2025 11:23:08] Adapter 3 has recognized an incoming TFTP request
[08/12/2025 11:23:08] TFTP RRQ started on port_index=64: G:\PXE\efi\grub\menu.lst
[08/12/2025 11:23:08] Adapter 3 has recognized an incoming TFTP request
[08/12/2025 11:23:08] TFTP RRQ started on port_index=65: G:\PXE\efi\grub\menu.lst
[08/12/2025 11:23:08] Adapter 3 has recognized an incoming TFTP request
[08/12/2025 11:23:08] TFTP RRQ started on port_index=66: G:\PXE\efi\grub\menu.lst
[08/12/2025 11:23:08] Adapter 3 has recognized an incoming TFTP request
[08/12/2025 11:23:08] TFTP RRQ started on port_index=67: G:\PXE\boot\background.jpg
[08/12/2025 11:23:08] Adapter 3 has recognized an incoming TFTP request
[08/12/2025 11:23:08] TFTP RRQ started on port_index=68: G:\PXE\boot\background.jpg
[08/12/2025 11:23:08] Adapter 3 has recognized an incoming TFTP request
[08/12/2025 11:23:08] TFTP RRQ started on port_index=69: G:\PXE\boot\hk22.hex
[08/12/2025 11:23:08] Adapter 3 has recognized an incoming TFTP request
[08/12/2025 11:23:08] TFTP RRQ started on port_index=70: G:\PXE\boot\hk22.hex
[08/12/2025 11:23:10] Adapter 3 has recognized an incoming TFTP request
[08/12/2025 11:23:10] TFTP RRQ started on port_index=71: G:\PXE\EFI\tool\CrScreenshotDxe.efi
[08/12/2025 11:23:10] Adapter 3 has recognized an incoming TFTP request
[08/12/2025 11:23:10] TFTP RRQ started on port_index=72: G:\PXE\EFI\tool\CrScreenshotDxe.efi
[08/12/2025 11:23:12] Adapter 3 has recognized an incoming TFTP request
[08/12/2025 11:23:12] TFTP RRQ started on port_index=73: G:\PXE\boot\hk22.hex
[08/12/2025 11:23:12] Adapter 3 has recognized an incoming TFTP request
[08/12/2025 11:23:12] TFTP RRQ started on port_index=74: G:\PXE\boot\hk22.hex
[08/12/2025 11:23:13] Adapter 3 has recognized an incoming TFTP request
[08/12/2025 11:23:13] TFTP RRQ started on port_index=75: G:\PXE\efi\ext\hotkey
[08/12/2025 11:23:13] Adapter 3 has recognized an incoming TFTP request
[08/12/2025 11:23:13] TFTP RRQ started on port_index=76: G:\PXE\efi\ext\hotkey
[08/12/2025 11:23:13] Adapter 3 has recognized an incoming TFTP request
[08/12/2025 11:23:13] TFTP RRQ started on port_index=77: G:\PXE\efi\ext\hotkey
[08/12/2025 11:23:13] Adapter 3 has recognized an incoming TFTP request
[08/12/2025 11:23:13] TFTP RRQ started on port_index=78: G:\PXE\efi\ext\hotkey
[08/12/2025 11:25:38] DHCP Server V2.5.2.3 started as Application
[08/12/2025 11:25:38] NetworkAdapter Initialization returns 0
[08/12/2025 11:25:38] Adapter 0 with IP address 192.168.220.1 found (pAdap=0x001fb798)
[08/12/2025 11:25:38] Adapter 1 with IP address 172.168.0.208 found but not used
[08/12/2025 11:25:58] DHCP Server is terminating (ignore error messages that follow)
[08/12/2025 11:25:58] recvfrom returns with error 10038
[08/12/2025 11:25:58] DHCP Server terminated

mygamexxx

感觉是HTTP服务不成功。服务器状态中没看到HTTP服务。

2011yaya2007777

可能吧。我这里网起文件成功后，才有资格能回答。

mygamexxx

2011yaya2007777 发表于 2025-8-12 12:12
可能吧。我这里网起文件成功后，才有资格能回答。

很奇怪的是IPXE.EFI作为启动文件时，显示好像是HTTP。能顺利启动到PE桌面，并且速度也快，感觉就是HTTP。


关闭软件的HTTP：
[HTTP-SETTINGS]
EnableHTTP=0
IPXE.EFI作为启动文件，HTTP连接不成功，说明这个软件的HTTP服务是成功的。

xiaoy

这个软件 HTTP服务肯定是很容易就启动成功的  IPXE能HTTP传输  打开网页也能很好下载文件。

2011yaya2007777

这个软件 HTTP服务肯定是很容易就启动成功的

问一下，如何指定首先加载根目录 ROOT=C:\usr\dhcpsrv2.5.2\wwwroo\bootx64.efi ?

2011yaya2007777

很奇怪的是IPXE.EFI作为启动文件时，显示好像是HTTP

问一下，如何指定首先加载根目录 ROOT=C:\usr\dhcpsrv2.5.2\wwwroo\bootx64.efi ?

mygamexxx

2011yaya2007777 发表于 2025-8-12 13:39
问一下，如何指定首先加载根目录 ROOT=C:%usr\dhcpsrv2.5.2\wwwroo\bootx64.efi ?

就在配置文件dhcpsrv.ini中，BOOTFILE=IPXE.EFI，直接修改配置文件，程序接收到连接申请时会重新读配置文件，修改配置文件后不需要重启软件。Is it necessary to restart the DHCP server after editing the INI file? | DHCP Server for Windows

[GENERAL]
LEASETIME=86400
NODETYPE=8
SUBNETMASK=255.255.255.0
BOOTFILE=IPXE.EFI
NEXTSERVER=192.168.220.1
DNS_0=8.8.8.8
ROUTER_0=192.168.220.1

[DNS-SETTINGS]
EnableDNS=1
FORWARD=8.8.8.8

[TFTP-SETTINGS]
EnableTFTP=1
ROOT=G:\
WritePermission=1

[HTTP-SETTINGS]
EnableHTTP=1
ROOT=G:\

2011yaya2007777

你这个IPXE.EFI放在何处？
ROOT=G:\  ？

xiaoy

启动文件就放在ROOT指定的目录下，如 ROOT=G:\   那IPXE.EFI就在g根目录下

2011yaya2007777

搞不定。不再费神了。
看来 dhcpsrv2.5.2 远没有 TinyPXEServer1.0.0.23 易用，好用！

xiaoy

它非常稳定，特别是机房很多电脑同时网启， tinypxe遇到多台同时就很容易崩溃，而这个不得，即使就用它的tftp来启动PE，速度也很好，我以前也常用tinypxe  现在用这个更多了。

freesoft00

xiaoy 发表于 2025-8-11 11:52
DHCP Server for Windows最新版2.10.0   也是同样
“7月3日新版G4E，HTTP网启测试，进入菜单正常，选择网 ...

哪里有下载