中国DOS联盟

Support you, this thing is really good, I like it!!!

1、I used it in an internet cafe before. At that time, all the computers in the internet cafe were SATA hard drives. When doing network cloning, the speed was only a few M/s. Later, after frequent research, it was because of the problem of the SATA driver. Then, using mousedos for cloning, the speed could reach hundreds of M/s. I want to ask if this problem has been solved in the new version.

2、I want to boot the winpe.iso image in the boot menu. I would like to ask how to set it up. I used to read the article "PXE Server Setup Guide and PXE Boot WinPE Solution Summary" on Wuyou and made a direct PXE boot to PE according to it. Now the directory structure I set is:

1. Previously, I used tftpboot to boot for network cloning in internet cafes, but the speed was only a few MB per minute. Later, after searching various materials, I found that it was because of the problem with the SATA hard drive driver. Then I used mouseDOS for network cloning, and the speed could reach hundreds of MB/s. Does the new version solve the problem of slow network cloning for SATA hard drives?

2. I want to add an option to boot from winpe.iso in the pxe menu. I would like to know what needs to be changed. Currently, I achieve this by switching the configuration of hanewin. It would be more convenient if there could be options in the tftpboot menu.

My current directory structure

I've seen it, but I don't understand it. There are some parts.

If grub4dos supports booting ISO files on the hard disk, then for PXE booting ISO files, you can try changing the boot file to grldr. Then edit the Pxeboot\menu.lst file.

Learn it, it feels very complicated.

@xugaohui

Have you ever tried gpxelinux.0, which supports HTTP

Thanks for sharing.

There is an issue when setting the boot file to gpxelinux.0 in syslinux 3.7. The DOS image file under tftp is extremely slow. It is almost impossible to use normally. The HTTP usage is not very useful for the time being, and it has not been tried. It should be that in the root path of the hanewin DHCP server, specify an HTTP URL + file name. The remote installation of Linux is best done with NFS shared installation.

There is a problem when setting the boot file to gpxelinux.0 in syslinux 3.7.
The DOS image file under tftp is very slow. It is almost impossible to use normally.
The HTTP usage is not very useful for the time being, and it has not been tried. It should be that a HTTP URL + file name is specified in the root path of the hanewin DHCP server.
The remote installation of Linux is best NFS shared installation.

TFTPboot update:
Updated to syslinux 3.70
gpxe + 0.93
grub4dos 06-Jul-2008
HDAT2 4.6b2
Re-added 8.3, the file name is ghost83.exe, which can solve the problem of slow network cloning. ghost.exe is ghost 11.5
Reduced ghconfig to 11.2 to solve the problem that some cannot change IP, gateway, NDS.
Three versions of awdflash are now provided:
8.92 8.87 8.67
ctmouse is replaced with version 1.94

There is a problem with the forum, and there is an error when replying, and refreshing has replied again.

Last edited by xugaohui on 2008-7-8 at 01:09 AM ]

gpxelinux.0 should also be good when used with HFS in a local area network. I haven't had an environment to test recently.

example:
kernel http://192.168.1.100/vmlinuz
append initrd=http://192.168.1.100/initrd.gz


gpxelinux currently only supports HTTP 1.1

Is NetSet a program written by xugaohui? Can a Chinese version be released?

thanks

Poster:

I'm sorry, I'm a Taiwanese netizen. I'm honored to read the owner's article and also downloaded the owner's DOS boot disk. But I encountered some problems and would like to ask for advice (I'm sorry I can only write traditional Chinese, I hope the owner can understand).

1. DHCP is using (haneWIN DHCP), and the boot file is: pxelinux.0
2. Successfully booted with PXE, saw the boot menu, entered: Normal boot,
3. Want to use network functions. Executed: runnet
4. Entered the net folder: executed: net use v: \\192.168.1.254\img (the shared path on the server)

But when executing net use, the following error message appears:
NET3658: The DLSHELP.SYS driver is not installed.
For more information, type NET HELP 3658
Typing NET HELP 3658 finds
Cause: Either the DEVICE=DLSHELP.SYS statement does not exist in CONFIG.SYS or an error occurred while attempting to load DLSHELP.SYS.

Originally, I hoped to connect to the network disk, and then I could run ghost to restore the image on the server or back up the image on the server. But the above problem has been appearing all the time, so I can't connect to the disk. Can the owner please give me some advice?

Poster:

I'm sorry, I'm a Taiwanese netizen. I'm honored to read the owner's article and also downloaded the owner's DOS boot disk. But I encountered some problems and want to ask for advice (I'm sorry I can only write traditional Chinese, I hope the owner can understand).

1. DHCP is using (haneWIN DHCP), the boot file is: pxelinux.0
2. Successfully booted via PXE, saw the boot menu, entered: Normal boot,
3. Want to use network functions. Executed: runnet
4. Entered the net folder: executed: net use v: \\192.168.1.254\img (the shared path on the server)

But when executing net use, the following error message appears
NET3658: The DLSHELP.SYS driver is not installed.
For more information, type NET HELP 3658
Typing NET HELP 3658 finds
Cause: Either the DEVICE=DLSHELP.SYS statement does not exist in CONFIG.SYS or an error occurred while attempting to load DLSHELP.SYS.

Originally, I hoped to connect to the network disk, and then I could run ghost to restore or backup the image on the server.