China DOS Union

Little brother has recently encountered many problems when using TFTP for PXE network cloning. For example, the PXE boot will display a timeout, and sometimes the TFTP server pops up many send boxes and never starts transmitting. I have searched a lot of information online, but it is just touching the surface and not getting to the key points.

@echo off
SET TZ=GHO-08:00
prompt $p$g
\net\Undipd.com 0x60
MOUSE.COM
echo Loading...
GHOST.EXE -clone,mode=prestore,src=@mcchenglong,dst=1:1 -sure -rb

What does the line "SET TZ=GHO-08:00" mean? I tried removing this line and a box will appear.

If you use tftpd32, remember to use version 2.8. The v3.x version often has such problems, and I don't know the specific reason.

As for this SET TZ=GHO-08:00, it seems to be similar to the concept of time zone. It seems to take effect when you store the backed-up image on an NTFS partition, and FAT32 seems to be unaffected. I don't know if adding this parameter makes it Beijing time.

I don't know. I tried in VPC and after removing this part, it didn't work. There would be a partition selection box appearing, but here I can't select. Does VPC 5.2 version not have the PXE module? Is there no setting for network card boot in the bios?

I used the one downloaded from the host's network disk recommended by the moderator, which is Connectix Virtual PC 5.2

wuyou.com originally had a post discussing SET TZ=GHO-08:00, but it's a pity it can't be found in the search. I think removing it shouldn't cause the error you mentioned.

Connectix Virtual PC 5.2 and later virtual pc2007 support PXE boot, but when cooperating with tftpd32, it still has the result of a large number of failed image sending as you described. You can use haneWINDHCPServer, and I feel this is more stable when testing with virtual pc.

In addition, you can change this sentence
GHOST.EXE -clone,mode=prestore,src=@mcchenglong,dst=1:1 -sure -rb
to
GHOST.EXE -ja=@mcchenglong -sure -rb
so that all your parameter settings can be adjusted in the client options of GhostSrv.

Still not working. I tried using PDK and NDIS2 drivers respectively. It seems that the network card can be activated, but when booting to GHost, it can't find the server. My ghostsrv.exe is in the same directory as TFTP.

May I ask what are the differences in effect and function between DOS network card drivers PDK and NDIS?

Methods to find Packet Driver drivers for any network card

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

I don't have the knowledge to explain the standard differences between Packet Driver and NDIS drivers, but there's no need to get bogged down in such details.

For finding official documentation, besides the UNDI driver used by PXE in Ghost, there's another way to directly use Packet Driver, which is NDIS loaded in the form of Packet Driver.

You can now try changing the virtual machine software. Maybe trying the lean version of VMware is also a good option. If you're sure that the driver under your DOS matches your virtual machine, you can try single-point transmission with GhostSrv or increase the timeout period