China DOS Union

I'm sorry, I made a mistake. It's more than 300 megabytes per minute. Here, we all clone machines alone, usually installing one or two machines of the same model. If using GHOST multicast, one more machine is needed to run the GHOST server program. I think it's more troublesome, so we all directly GHOST the GHOST file on the server.

Ask the original poster, is there a download of the full version of the LANtastic program?

Then ask another question. If I don't install DHCP and TFTP services, directly burn the 8M file in tftpboot onto a CD-ROM to make it bootable, and boot from the CD-ROM, can it map network shares?

This 8M image file is not in a standard format and cannot be modified with winimage, but winimage can open it. Currently, it is not directly supported to burn it to a CD. The main problem now is that when making an ISO file for testing, it doesn't pass in VMware and Virtual PC. When tested on a real computer, the network card can be normally driven and the shared directory can be connected.

[ Last edited by xugaohui on 2006-6-2 at 19:54 ]

I just tried it on VMWARE and can map the shared directory for internet connection. But there is another problem. If my network card doesn't have PXE boot function and I don't want to install PXE server program, how to achieve the mapping of UNDI driver's shared directory?

In ghost8.3, there are instundi.exe and undi_drv.exe. In an environment without PXE boot, the universal network card driver can also be used. It has poor support for some very old network cards, while relatively new gigabit network cards are all okay.

I downloaded GHOST 8.3 CE and tried it. The specific situation is as follows:

There are three files related to PXE UNDI in GHOST 8.3, namely: InstUndi.exe, Undi_Drv.exe, UndiPd.com.

The functions of InstUndi.exe and Undi_Drv.exe are the same, both are drivers for PXE UNDI. The only difference is that Undi_Drv.exe can also be loaded in the Config.sys file.

The UndiPd.com file is the Packet UNDI driver.

If the network card does not have the function of PXE boot, running InstUndi.exe and Undi_Drv.exe will both report the error "UNDI Option ROM not detected!".

My meaning is that in the case where this network card does not have the PXE boot function and I don't want to install the PXE server program, is there a way to combine with the PXE boot code floppy disk so that the network card without the PXE boot function can use the universal PXE UNDI driver.

Thank you!

[ Last edited by LanCat on 2006-6-3 at 01:30 ]

InstUndi.exe and Undi_Drv.exe are used without PXE booting. If it's PXE, it can't be used. "UNDI Option ROM not detected!" means it doesn't support your network card. Network cards like 8029, 8139, 8169, sis 900, intel, 3com are okay. The DEC 21140A 10/100 in virtual pc doesn't support it. You can try adding the parameter device vendor later.

[ Last edited by xugaohui on 2006-6-3 at 09:33 ]

楼主 Xugaohui, your new pxe.img can't be edited with the 3COM Boot Image Editor. Could you provide an editing tool? Thanks...

Originally posted by xugaohui at 2006-6-3 09:29 AM:
InstUndi.exe and Undi_Drv.exe are used when there is no PXE boot. If it is PXE, then it cannot be used. "UNDI Option ROM not detected!" indicates that it does not support your network card, such as 8029, 8139, 8169, sis 900, inte...

I don't think so. My motherboard is ASRock, and the on-board network card is 8139. If I disable the function of booting from the network card in the BIOS and directly boot to DOS, when running InstUndi.exe, it will prompt "UNDI Option ROM not detected!". If I enable the function of booting from the network card in the BIOS and then do not boot from PXE, but directly boot from the hard disk to DOS, running InstUndi.exe will be fine.

In the Ghost 8.3 boot disk making wizard, if you choose "Universal Packet Driver", Ghost will prompt you to turn on the "Option ROM", "PXE" and "UNDI" options in the BIOS.

Therefore, this is my understanding: If your network card supports PXE boot and the PXE boot function is turned on. Even if you do not boot the machine from the PXE of the network card, but directly enter DOS, you can also drive your network card under DOS by loading the UNDI driver (InstUndi.exe) and using the universal Packet UNDI driver (UndiPd.com) and the universal Ndis UNDI driver (NDIS.DOS).

The prompt "UNDI Option ROM not detected!" has nothing to do with whether the network card boot function is enabled. It may be a bug in instundi.exe itself. A more reliable method is to load Undi_Drv.exe in config.sys. The line "device=undi_drv.exe" should be placed before himem.sys, that is, load undi_drv.exe first.

Can xugaohui provide the download again?

L楼 main:
Can you provide the download for Network Boot Tools 1.2?

I extracted the downloaded file to C:\TFTP, then set the ROOT directory of the TFTP service to c:\TFTP and in DHCP set the boot file name to PXELINUX.0

Isn't it said that the file is 16MB? Why do I have 20MB when downloading? Also, how are H, C, S calculated