中国DOS联盟

Which expert can introduce the function of UNDI (Universal Network Driver Interface) in PXE! Using UNDI to drive the network card under DOS can use one driver program to drive most network cards.

What I know is that if your machine's network card has the function of PXE boot, then no matter what model the network card is, it can be driven by a general driver under DOS.

First run INSTUNDI.EXE in GHOST 8.3 to load the PXE UNDI driver, and then run UNDIPD.COM 0X60 in GHOST8.3 to load the Packet driver under DOS.

And the NDIS driver is Intel's NDIS.DOS.

These three files can be downloaded at "DOS Boot Disk & LOGO Technology (Boot Disk Room)" - " PXE Network Boot Virtual Floppy Disk Image".

http://www.cn-dos.net/forum/viewthread.php?tid=19003&fpage=1

The integrated network card of the motherboard generally supports the PXE function. As long as the option of network card boot is turned on in the BIOS, and some more network card boot information can be seen after the power-on self-test, it means it is okay. If there are "Options ROM", "PXE", "UNDI" options in the BIOS, they should also be set to be effective.

And for independent PCI network cards, good ones like Intel, 3Com, etc., also have the PXE function. For the 8139 network card, a PXE boot chip needs to be added.

However, my machine is an ASRock 865G motherboard, with an 8139 network card, which supports the PXE boot function, but somehow, running INSTUNDI.EXE will make an error, maybe it is the problem of the motherboard BIOS.

Last edited by LanCat on 2006-6-3 at 00:16 ]

I also don't understand, I can only say the general meaning.

UNDI is short for Universal Network Driver Interface, translated into Chinese is Universal Network Driver Interface. It can be regarded as a driver program interface library data, which is a data segment retained in the DOS conventional memory of 640K.

date code, usually use Intel's ndis.dos, 3com's UNDIS3C.DOS to call this data segment. Loading and booting the image will clear UNDI. In order to use UNDI, the image file format must retain this UNDI data segment, and the conventional memory will also be reduced.

The real PXE boot also needs PXE service. The port of PXE service is 4000. General applications only use DHCP service and TFTP. One of the main functions of PXE service is to provide the client with a boot selection menu. If only startup is needed, emboot menu.pxelinux can be used instead. I rarely install the PXE server. If it is DHCP + PXE + TFTP + ordinary floppy disk image file, I don't know if the conventional memory will be reduced. There is no test for the time being. Some PXE diskless can make DOS, 98, Linux, ME, 2K, XP boot selection menus to enter different systems. PXE service is much more powerful than PXELINUX, 3com menu functions, but there are not many separate easy-to-use PXE server ends. Intel PDK 2.1 is free. DeployCenter 6.0, Phoenix PXE Server v4.6.1 are all PXE server ends.

Last edited by xugaohui on 2006-6-4 at 23:16 ]