中国DOS联盟

I used TFTPBOOT.ZIP from December 17th, and there was a black screen.

The log of haneWIN dhcp server is as follows:

2006-12-17 16:07:11 DHCP Start Server on 192.168.18.3
2006-12-17 16:07:11 TFTP ready on port 69
2006-12-17 16:08:30 DHCP Request 00:50:eb:04:f2:08 ACK 192.168.18.10 36000 vc "PXEClient:Arch:00000:UNDI:002001" if 192.168.18.3
2006-12-17 16:08:30 TFTP Abort 192.168.18.10 Get/octet 0 TFTP Aborted E:\tftpboot\pxelinux.0
2006-12-17 16:08:30 TFTP 0s 192.168.18.10 Get/octet E:\tftpboot\pxelinux.0
2006-12-17 16:08:30 TFTP Error 192.168.18.10 Get 1 File not found E:\tftpboot\pxelinux.cfg\01-00-50-eb-04-f2-08
2006-12-17 16:08:30 TFTP Error 192.168.18.10 Get 1 File not found E:\tftpboot\pxelinux.cfg\C0A8120A
2006-12-17 16:08:30 TFTP Error 192.168.18.10 Get 1 File not found E:\tftpboot\pxelinux.cfg\C0A8120
2006-12-17 16:08:30 TFTP Error 192.168.18.10 Get 1 File not found E:\tftpboot\pxelinux.cfg\C0A812
2006-12-17 16:08:30 TFTP Error 192.168.18.10 Get 1 File not found E:\tftpboot\pxelinux.cfg\C0A81
2006-12-17 16:08:30 TFTP Error 192.168.18.10 Get 1 File not found E:\tftpboot\pxelinux.cfg\C0A8
2006-12-17 16:08:30 TFTP Error 192.168.18.10 Get 1 File not found E:\tftpboot\pxelinux.cfg\C0A
2006-12-17 16:08:30 TFTP Error 192.168.18.10 Get 1 File not found E:\tftpboot\pxelinux.cfg\C0
2006-12-17 16:08:30 TFTP Error 192.168.18.10 Get 1 File not found E:\tftpboot\pxelinux.cfg\C
2006-12-17 16:08:30 TFTP 0s 192.168.18.10 Get/octet E:\tftpboot\pxelinux.cfg\default
2006-12-17 16:08:30 TFTP 0s 192.168.18.10 Get/octet E:\tftpboot\vesamenu.c32
2006-12-17 16:08:36 TFTP 1s 192.168.18.10 Get/octet E:\tftpboot\vesamenu.c32
2006-12-17 16:08:41 TFTP 0s 192.168.18.10 Get/octet E:\tftpboot\vesamenu.c32
2006-12-17 16:08:47 TFTP 0s 192.168.18.10 Get/octet E:\tftpboot\vesamenu.c32
2006-12-17 16:08:53 TFTP 0s 192.168.18.10 Get/octet E:\tftpboot\vesamenu.c32
2006-12-17 16:08:59 TFTP 0s 192.168.18.10 Get/octet E:\tftpboot\vesamenu.c32
2006-12-17 16:09:04 TFTP 0s 192.168.18.10 Get/octet E:\tftpboot\vesamenu.c32
2006-12-17 16:09:10 TFTP 0s 192.168.18.10 Get/octet E:\tftpboot\vesamenu.c32
2006-12-17 16:09:16 TFTP 0s 192.168.18.10 Get/octet E:\tftpboot\vesamenu.c32
2006-12-17 16:09:22 TFTP 0s 192.168.18.10 Get/octet E:\tftpboot\vesamenu.c32
2006-12-17 16:09:28 TFTP 1s 192.168.18.10 Get/octet E:\tftpboot\vesamenu.c32
2006-12-17 16:09:33 TFTP 0s 192.168.18.10 Get/octet E:\tftpboot\vesamenu.c32
2006-12-17 16:09:39 TFTP 0s 192.168.18.10 Get/octet E:\tftpboot\vesamenu.c32

Bump it up by myself
And provide a temporary download address
The second sub - menu of the config menu is specific to the IBM TCPIP protocol. Automatically enable the network function. The network cloning speed is very fast.
To enable the network, still execute `runnet` in any path.
For network function customization, please modify `runnet.bat` by yourself, and add the required content to the end of the file.

Last edited by xugaohui on 2007 - 1 - 1 at 11:17 AM ]

Great stuff!

I have changed the original network boot disk to PXE. By the way, I wrote an instruction:

Original text (pictures, software)
http://zxdz.8800.org/htmldata/2/2007_01/%C0%FB%D3%C3PXE%CD%F8%C2%E7%C6%F4%B6%AF%CE%AC%BB%A4%CF%B5%CD%B31134_1.html

I. Introduction to PXE Network Boot

The PXE technology uses the network card to read the boot file from the PXE server to boot the computer, realizing diskless boot. Integrated network cards are the trend in the development of motherboards. Many motherboards integrate network cards and provide PXE network boot code in the BIOS at the same time, which allows us to widely use the PXE technology in the network. In the past, using PXE was very troublesome. The main problems were that the installation and configuration of the PXE server was cumbersome, making PXE boot image files was difficult, and all were paid software. Now, using PXELINUX + MEMDISK for PXE boot solves these problems easily. The server side can use the small but powerful Hanewin DHCP Server, and its installation and configuration is very simple. The boot image file can be made with Wimage, and unconventional floppy disk image files can be booted.

Using PXE boot to repair and maintain the system can avoid using the optical drive, floppy drive, or removing the hard disk and installing it on other machines for system maintenance. It realizes that without opening the case, the faulty machine is booted by reading the image file through the network cable via PXE network boot, the memory is virtualized into a disk, and the tools in the virtual disk or other tools shared on normal computers are used to repair the faulty machine. For example, boot to the DOS system with a DOS image file, run tools such as DM, GHOST, etc. Boot to the WINXP environment with a small WINPE image file to safely read, write, and modify the system password for the NTFS partition, etc. We can make various tool disks (CD-ROMs, floppy disks) into image files and store them centrally in a laptop. From then on, we don't have to worry about not finding the tool disk, and we don't have to carry a large number of tool disks to go to the door for maintenance.

II. Introduction to yzz163 PXE Network Recovery Image File

This boot disk uses the PXELINUX boot method of the DOS Union Forum. Based on my previously made network recovery disk V1.0, it is simply modified to become a network recovery disk based on PXE boot. The functions remain unchanged (loading three protocols: NETBEUI + TCP/IP + IPX respectively). Currently, it supports more than 100 kinds of network cards. As long as there are network card drivers, everyone can also add corresponding network cards. This recovery disk focuses on realizing file sharing under DOS using the NETBEUI protocol, and using the GHOST tool on the file sharing server to back up and restore the system. The main reason for using the NETBEUI protocol is my working environment. There are various types of PCs in my local area network, 8 types of network cards, and various business systems are installed on the machines. The M$ file sharing service is widely used in the network. After practicing with this boot disk on more than 10 kinds of machines, it is found that some motherboards will crash when using EMM386. Only conservative parameters are adopted, and the final parameters for EMM386 are determined as.

Practical experience tells me that using the NETBEUI protocol under DOS saves the most conventional memory (640K) and runs stably on various motherboards; using TCP/IP consumes the most memory, and some tools cannot be used. This disk has a Chinese interface, which is convenient for ordinary users to use. The client can choose the backup/restore function and store/read GHO files on the shared server according to the machine name.

For Internet cafes and other places where the motherboard models are single and only use PXE to realize the network multicast cloning function, using TCP/IP is more appropriate (can be in multiple subnets). There are special boot disks on the Internet, such as MAXDOS. For maintenance, under DOS in the local area network, using TCP/IP occupies more basic memory, making other tools unable to run, and the practical value based on TCP/IP is not great.

In the current local area network, the IPX protocol has basically disappeared. To cooperate with the hard disk copying of San Nuo, IPX network support is also added to my disk. This function is suitable for copying the entire hard disk between machines with the same hardware.

III. Production Method of Boot Disk Image File

The boot disk image file is made with Winimage and is a non-standard image file. GHOST83.EXE and DM tools are placed on the disk, and you can define the size of the image file according to your needs. Some problems are encountered during the production process. To make everyone take fewer detours, taking the 8M image file as an example, the problems to pay attention to during production are explained below.

1. Create a new image and define its format.
Image - Change Format - Select Custom Image Format, and enter as follows: (8M)

File system FAT16
Sectors per cluster 512 bytes
Total sectors 16384 = 8*1024*1024/512
Sectors per track 18
Heads 2
Hidden sectors 0
Physical drive 0

2. Set the value of the memory size for loading the image file
Click Options - Settings - Image, and fill in the size of the image file you made in "Limit of size of image loaded into memory", the unit is KB. In this example, it is 8192. Otherwise, the booted image file cannot perform read/write operations and an INT24 error occurs.

3. Save the image file as an img format
File - Save As, select "All Files" for the save type, the suffix is img, and save it as an img file. Winimage defaults to the compressed IMA format, and this kind of image file cannot be booted.

4. Change the properties of the boot sector
Image - Boot Sector Properties - Win95/98

IV. Server Side Setup

1. The PXE server side uses Hanewin DHCP or tftp32. It is recommended to use Hanewin DHCP, and only the boot file needs to be configured. The specific steps are shown in the figure:

DHCP configuration

TFTP configuration

If you want to share files, it is recommended to add the NETBEUI protocol. The shared file directory is as follows:

\tools--|
----gho
|
----winpe
|
----dos
|
----win

The gho stores GHOST files, and directories are built according to the machine name to store GHO backups of each user. The winpe stores tools, various drivers, etc. running under PE.


2. Modify the pxelinux configuration file
Add the following lines (boot menu) in the pxelinux.cfg\default file

LABEL yzznet (The label cannot be the same as others)
MENU DEFAULT (Default boot)
MENU LABEL ^9----yzz163 Network Boot (Display the menu, 9 is the menu key)
kernel memdisk c=455 h=2 s=18 floppy (Load memory disk parameters, c=total sectors 16384/2/18 rounded down)
append initrd=yzz163-8m.img (The image file name is yzz163-8m.img, placed in the TFTP root directory)

After configuring the server side, start the PXE client, press F8 to select to boot from the network, or set to boot from the PXE network in the CMOS, and the pxelinux menu will appear. If there is a boot error, you can look at the log of Hanewin DHCP, and the reason can be found quickly.

Finally, thanks to xugaohui from the DOS Union for providing TFTPBOOT.ZIP, thanks to chenall from the Wuyou Forum for providing WinPE.iso, and thanks to all those who helped me.

Reference articles:
1. Download of PXE network maintenance software package
http://www.cn-dos.net/forum/viewthread.php?tid=19003&fpage=2
2. PE suitable for using PXE boot
http://bbs.wuyou.com/viewthread.php?tid=87190
3. PXELINUX＋memdisk
http://syslinux.zytor.com/index.php
4. Network recovery disk V1.0
http://zxdz.8800.org/htmldata/2/19/2006_05/%CD%F8%C2%E7%C6%F4%B6%AF%BB%D6%B8%B4%B9%E2%C5%CCV1-049_1.html
Related software downloads:
1. hanewin dhcp server 3.04 + Chinese package
2. Winimage 8.00
3. yzz163-8m.img

Last edited by yzz163 on 2007-1-7 at 12:46 PM ]

Good stuff, thanks for sharing, I'll take it.

The fastest way to access the local area network under DOS is to use: IBM TCP/IP Protocol. The three protocols of MS are all much slower than this.

The client of NetWare 4.11 that occupies the least memory when accessing the local area network under DOS. For relevant information, please see http://www.veder.com/nwdsk/
This client can also start file and print sharing services, and can be unloaded from memory after enabling the network function.


Last edited by xugaohui on 2007-1-8 at 01:31 AM ]

With the help of xugaohui:
Found a way to add "password" protection to the PXE boot menu!
http://bbs.wwwfox.net/viewthread.php?tid=89112&extra=page%3D1

Give it a thumbs up,各位 experts continue!!!

Hui:
netcopy doesn't work. No matter how I adjust EMM386, it reports that there is not enough memory.
What's the difference between it and NC2002 (from Sannuo)?

After multiple tests, it is found that netcopy can work normally with 4 different network protocols. It can run on VMware, VPC, and real computers. nc2002 uses the IPX protocol. Netcopy uses the packet interface. The function of netcopy is much more powerful than that of nc2002, and the network cloning speed is also faster than that of nc2002.

The fastest way to access the local area network under DOS is to use: IBM TCP/IP Protocol.
The three protocols of MS are all much slower than this.
------------------------------------------
Now in the local area networks of units or internet cafes, the majority of users (>90%) may all be using M$'s WIN series and all "like" Network Neighborhood.
There's no way! Even M$ has to issue a NETBEUI patch for XP and WIN2k3.
Using its own one, there is guarantee of stability (I have 2 years of experience on more than 100 various models of WIN95, 98, 2K, XP client machines in 4 subnets).
The speed is not slow either. I map the shared disk with NETBEUI, and in a 100Mbps network, it also has 300 - 350MB/min. I think it's fast enough.
If it's multicast cloning, using the TCP/IP recommended by GHOST is appropriate, with guarantee of compatibility and reliability.

I used your pxeboot.img to boot, and I tried several options, but it couldn't run. It reported that there was not enough memory.
I have used two machines, the 845G and SIS650 motherboards. Are they too old?

As long as it is a graphical interface program running under DOS, or the host has more than or equal to 3G memory, if it cannot run, you can choose the option to start DOS without emm386.

When using MS's IP, IPX protocols under DOS to access the local area network, there is always only a little more than 300 Mbps. Some network cards can reach more than 400 Mbps. NETBEUIi has not been tried. In a pure gigabit environment, it is generally only 700 Mbps.

However, using IBM TCP/IP Protocol to access the local area network has a very fast speed. In a 100Mbps environment, it is generally 580 Mbps, and occasionally 600 Mbps. In a gigabit environment, it directly reaches more than 1800 Mbps. The compatibility is very good, and it is also very fast when finding the DHCP service.

Ghost multicast has no direct relationship with these protocols. It uses the packet interface. When was it recommended to use TCP/IP? As long as the enabled packet driver option is selected, any protocol can be used for multicast. Practice has proved that multicast will be faster when selecting IBM TCP/IP Protocol.

Last edited by xugaohui on 2007-1-11 at 05:13 AM ]

Originally posted by xugaohui at 2006-12-10 11:39 PM:
PXE boots Vista PE 2.0 successfully. There's nothing worth researching about PE 1.0.

Can you introduce in detail how to boot Vista PE?

The building owner's img is well done.