中国DOS联盟

As the title says~~~Has anyone done it?? I did it with Grub4dos, and when testing in VM, the following appears:
inf file XXX corrupt or missing status 21.;xxx is garbled;

title xp
pxe keep
chianloader --force /tftp/starrom.0

Is it a direct installation or a clone arrangement... Cloning is easy, but direct installation is more troublesome...

Originally posted by ad1234sl at 2009-4-9 06:40:
Direct installation or cloning arrangement... Cloning is easy, but direct installation is more troublesome.......

It's direct installation~~~~;
I have no problem with pxelinux.0, and it may install all the time~~~ but it doesn't work with GRUB4DOS, and there is no request information for the binlsrv service appearing; I think there must be a problem before this; -- I still don't know where the problem is, you big shots, how should I solve it, can you give a train of thought???

Have a chance to try.

I googled several articles and all felt extremely, extremely complicated. Microsoft's stuff is still Microsoft's. Personally, I feel the simplest way is to directly convert Bart's NetworkBootDisk, a DOS boot disk based on the Microsoft Network Client, into a PXE image using 3com's imedit.exe, then load it to the local machine to drive the local NIC NDIS2 NIC driver, and then map to the local disk through Windows file sharing to install. The PXELINUX solution on the internet feels like the steps are complicated.

Do you use tftp32? If yes, use a higher version of tftp32.

Using Hanewin DHCP~~~~

I encountered this problem not long ago. If you directly use startrom.0 or pxelinux.0, there is no problem. But there are some versions of grldr that have this phenomenon. Just update to the latest version of GRUB4DOS 0.4.4.