中国DOS联盟

I got this so-called latest version of the remote boot manager from the "Naked Man" of a certain technology development group yesterday and experienced it; it's been a long time since I wrote a software usage note. I remember that in Microsoft's WINNT4 many years ago, there was a "Remote Boot Manager" that used RPL. The Hunan-based diskless win98se back then used Microsoft's RPL; it was quite prosperous at that time. People who came into contact with diskless at that time all knew about this "Remote Boot Manager". Unexpectedly, this tool launched by deepin this time is directly named after this--quite bold. RPL has long been replaced by PXE, and it has its own support for virtual disks. I just don't understand why Microsoft hasn't updated the Remote Boot Manager yet, and many friends are very unfamiliar with this. After trying it, I feel it's very powerful. Now it's also available for download on major download sites. (Huajun download address: http://www.newhua.com/soft/14024.htm)

The main program is only one file, and it's completely blank when opened; from the interface, the author is intentionally imitating the MMC interface, looking a bit like an enterprise software, not as Q as before; the reasonable call of grub4dos is amazing. I didn't get the installation tutorial, and the whole operation I followed my feeling. As shown in Figure 1


First, I created a new node under the boot group in the left classification tree. Because according to the boot principle of PXE, it is necessary to configure an NBP file, as shown in Figure 2.


Now there are relatively many friends researching startup. The ones everyone uses more are probably grub4dos (grldr) and syslinux (pxelinux.0). I also like them, and I happened to have collected a few, so I directly took them and specified them; after the group was set up, I directly turned on a machine (VM) and booted from PXE network. The DHCP of PXE flashed by in an instant--it's fast enough, it seems to have used the so-called "Twenty-six Styles of狂龙掌"; but at this moment, what started later by TFTP was not PXELINUX.0, but GRLDR. Why is this. As shown in Figure 3


I observed the information in the machine list on the right to understand that it was booting from the default group, as shown in Figure 4


The default startup file can be specified in "Option Configuration", and the DHCP can also be set here. (The default startup file can be specified in "Option Configuration", and the DHCP can also be set here) This newly started machine hasn't been added to the startup group I just created, so it defaults to booting from GRLDR. It seems that DEEPIN still loves GRUB4DOS more and sets it as the default; as shown in Figure 5


So I habitually selected this machine and dragged it under the left boot group, and it really could be dragged (used to using diskless software); as shown in Figure 6


Actually, according to the orthodox operation, the right-click context menu can be used to specify the group. The machine finally booted normally from PXELINUX.0; as shown in Figure 7 (The writing of the menus for PXELINX.0 and grldr is not within the scope of discussion in this article. I'll communicate with you together next time if there's a chance)


The startup was normal, and the menu came out as shown in Figures 8 and 9




This "Remote Boot Manager" is claimed to support the simultaneous group startup of multiple NBP. So I created another group and then looked at the effect, as shown in Figures 10 and 11



Two different versions of GRLDR and an extracted PXELINUX.0 were started at the same time, and all could boot WINPE and DOS normally; simulating ISO and IMG were all normal as shown in Figures 12, 13, and 14



The effect is visible. If there are any problems, suggestions are welcome. Please put forward.

Last edited by pxeBOOT99 on 2010-7-9 at 14:35 ]

The thinking and methods are both very good. Worth learning!

Can't see the picture ah!!!!!!!!!!!!!!!!!!!!!!!!!!!11