中国DOS联盟

Thanks.!.! Then I added multiple network cards.! In winnt4.0, there is a program.! It automatically detects what type of network card my local machine is to import the corresponding network card driver? I remember someone used pci.exe, these programs detect the type of the local network card.! But it has an interface prompt whether to detect automatically or manually.
I am also currently doing PXE DOS diskless. I am using Intel PDK2.0 but the DOS image file of my server currently only supports one type of network card.

By the way, I don't seem to understand very clearly the PXE set of software you made. Can you explain in detail about your server configuration and the configuration of the image file? Thank you!

http://www.nu2.nu/bootdisk/network/
There are two detection methods: automatic and manual.
The image of pdk 2.0 only supports the currently PXE-booted network card.

http://www.nu2.nu/bootdisk/network/
Inside this, it's detected using pci.exe.! Indeed, there are two types of detection: automatic and manual.
I don't know if there can be parameters in it to automatically select automatic detection without the prompt screen where I need to choose. I'll try again later.! Hehe.!

By the way, I seem not to have understood your PXE software set very clearly. Could you explain in detail your server configuration and the configuration of the image file. Thanks.!

After booting with this image, the mapping of the directory using `net use y: \\computer\tools` is not possible, and it prompts that the computer is not found. Is it because DNR is not loaded? It is suggested to still use Ghost 8.2, so that the computer can be installed in broadcast mode. Ghost 8.3 did not find the multicast server.

I once used Memdisk to load an image truncated by WINimage, and there would be some file reading errors. Just uncheck the "Trim unused image parts" in Winimage's settings and save the file. If you think the file is too large, you can compress the IMG file into GZ format with 7Zip, and it can still be loaded by Memdisk. Also, I have found the multicast server of Ghost 8.3 and GhoExplore.

Originally posted by liudh at 2006-4-19 02:43 PM:
I once used Memdisk to load an image truncated by WINimage, and there would be cases of partial file reading errors.
Just uncheck the "Truncate unused image portion" in Winimage's settings and save the file. ..

After testing, your method doesn't work. You mean the standard format. For non-standard formats, your method still doesn't work.

Last edited by xugaohui on 2006-4-19 at 23:13 ]

I successfully booted an image file larger than 2.88M with PXELINUX. Your problem is that the CHS value was not added in the next line. The menu configuration is as follows:
kernel memdisk c=300 h=2 s=48 floppy
append initrd=pxeboot.img c=300 h=2 s=48 floppy　keeppxe

Also, I have another question to ask. After I used the Default menu you made to boot, it couldn't be displayed, and it prompted that the Menu.c32 file was not found. I don't know why.

The Pxe.img you provided is very good, but it can only boot the server side for Argon CMS and cannot work on other PXE servers. I don't know where to find the registration code of CMS.

The attached file is the PXE server software package I made. Using the convenient and small TFTPD32 as the server side, it can boot WINPE, PXE images, and ordinary floppy disk IMG images.

Those who need MSNET, DOS - based Ftp, and graphical menu GHOST functions can download from HTTP://liudh70.cech.com.cn, and directly put the SUPBOOT.IMG file in the liudh directory into the TFTPBOOT. GRUBNET.img can be made into a floppy disk for GBUBNET to boot and download the boot image from the Tftp server, but the IP address configuration in the Menu.net file in the Boot directory needs to be edited, and it can also boot many tools such as RIS, PXE, DOS, etc.

Last edited by liudh on 2006 - 12 - 21 at 11:34 PM ]

menu.c32 is in the root directory of tftp.

Last edited by xugaohui on 2006-4-29 at 14:29 ]

I quite admire everyone above!
The LZ is using EMBOOT's PXE1.2, right? I've tried Intel, 3COM, PXEGRUB, PXELINUX, and I think PXELINUX suits my requirements better. 3COM and EMBOOT seem to be from the same company, and the BPPATCH inside is really a good thing, it's great for making DOS boot disks, but I didn't make an ACRONIS boot disk (LINUX) on it. PXEGRUB is similar to PXELINUX, but it seems that only a few network card drivers can be integrated during compilation in PXEGRUB, and it can't boot ACRONIS either. I'm using PXELINUX now, it can boot DOS disks (including a MINI98 hard disk image), and ACRONIS can also be booted. After using KEEPPXE, the network card drivers in the LZ's PXE environment also work.
I'm using the haneWIN DHCP Server recommended by the LZ, and this one is really fast.

Last edited by TurboY on 2006-5-8 at 17:54 ]

Using emboot to create an image reduces conventional memory by about 30K, leaving approximately 610K. PXELINUX has good compatibility. It can also install Linux remotely, and can run memtest, http://www.memtest86.com/, and many images can be booted with PXELINUX. Adding KEEPPXE uses 90K of conventional memory, but due to the appearance of ghost 8.3, the KEEPPXE parameter is no longer needed. Just run instundi.exe or undi_drv.exe under DOS, and you can use the universal undi driver or universal packet program. After booting with PXELINUX, BPPATCH and pboot are not usable. BPPATCH can read DHCP parameters, and the universal environment variable is modified in a text file. pboot can shut down, restart, or immediately change to booting from the hard disk. Of course, there are programs to replace pboot in PXELINUX. Testing PXELINUX + instundi on a virtual machine is unsuccessful. When virtualizing a hard disk, instundi can run normally, and it also works successfully on a real computer. If this method is useful, emboot is no longer needed.

PXELINUX menu


Run memtest


DOS boot menu


Last edited by xugaohui on 2006-5-8 at 22:32 ]

Who downloaded PXE.img? Can you provide it again? The link of the owner is unavailable for download.

LZ, when will the new version of the PXE network boot virtual floppy disk image be available for download?

My previous approach was to install the NETBEUI protocol on the server, boot the machine with a CD, run the network boot disk of NU, then connect to the shared directory of the server, and run GHOST for cloning. Generally, the speed is about 300M per second. I also made a PXE boot with 3COM for devices with PXE boot. I wonder how the speed of running GHOST is with the landlord's method. Has anyone tested it?

The NETBEUI protocol is rarely used nowadays. The GHO file placed in or read from a shared directory has at best a speed of over 300 MB per minute. You said about 300 MB per second refers to 300 Mbps. According to your speed calculation, it's about 40 M * 60 = 2400 MB per minute when network ghosting. It's difficult for a hard disk to hard disk clone to reach a speed of 2400 MB per minute. I don't know how your boot image is made.

It is suggested that everyone don't place GHO files on shared directories. Use the packet driver and apply the ghost multicast function. Generally, there is 500 - 600 MB per minute. Someone in this forum mentioned before that there is a 2 GB size limit when using the ms net client to connect to shared directories. The latest PXE boot image no longer uses the ms net client but uses LANtastic. It's very difficult for the ms net client to access 2003/xp systems, and in many cases, it can't map network drives. Connecting to shared directories with LANtastic is simpler and has a higher success rate. The new version of the image is very likely not using the emboot solution but using pxelinux. It also supports starting the hard disk repair program Efficiency Source 3.0 from PXE, and you can choose to start from the first hard disk or the second hard disk.

Last edited by xugaohui on 2006-6-1 at 20:14 ]