China DOS Union

Hehe, there aren't many people making universal network boot disk images. Using this thing, you can connect to Windows shared resources under DOS. Let's talk about the features:

The batch files inside are not encrypted and have Chinese annotations. Those who want to understand the workflow can look at them themselves. The netboot.txt in wbat.rar inside is for interface configuration, and you can modify it yourself.

Other universal network cloning tools or network boot disks use DETPCI.SYS from Ghost Enterprise Edition to detect network cards, so the number of network cards recognized is limited by DETPCI.SYS and cannot be expanded or added. Our network card detection module is written by ourselves. Because in terms of the number of network cards recognized, it can be said to be infinitely expandable. As long as you report the Vendor ID and Device ID of the network card, as long as the manufacturer has an NDIS2 driver, it can be added. It also supports nVidia network cards very well, and there's no need to specify it in the Config.sys menu.

The interface is all in Chinese, which is of course more convenient than all in English.

NetBeui and IPX are outdated protocols, so they are no longer supported, only TCP/IP protocol is supported. Also, it saves some memory.

Usage method:
After the network enters the DOS prompt after setting, you can use net use drive letter \\computer name\shared resource name to map the network shared resource. For example, net use z: \\server\d

Solution for not being able to connect to XP shared resources:
Because XP doesn't enable network sharing by default, sometimes you may need to set it:
1. First set sharing, which is the things in "Share and Security" by right-clicking on the drive letter or folder.

2. Right-click on "My Computer", select "Computer Management" - "Local Users and Groups" - "Users" in the menu, double-click the GUEST account, and uncheck "Account is disabled".
3. Run the Group Policy Editor gpedit.msc, open "Computer Configuration" - "Windows Settings" - "Security Settings" - "Local Policies" - "User Rights Assignment", and if there is a GUEST user in "Deny access to this computer from the network", delete the GUEST.

4. Open "Computer Configuration" - "Windows Settings" - "Security Settings" - "Local Policies" - "Security Options", and set both "Don't allow anonymous enumeration of SAM accounts" and "Don't allow anonymous enumeration of SAM accounts and shares" to "Disabled".

Download address: http://www.mousedos.com/temp/netboot1.img

[ Last edited by zqlcch on 2007-8-28 at 04:05 PM ]

Such a good thing no one wants?

I downloaded it, took a quick look, the owner's style is a bit like mine...

It should be a good thing. I used to feel that the ones making network card drivers from MaxDOS are quite complete, just not convenient to port.

Thank you,楼主. I'll study it when I have time.

Already used it, this is a great thing!

Other universal network cloning tools or network boot disks use the DETPCI.SYS that comes with Ghost Enterprise Edition to implement network card detection. Therefore, the number of network card identifications is limited by DETPCI.SYS and cannot be expanded or added. Our network card detection module is written by ourselves. Because in terms of the number of network card identifications, it can be said to be infinitely expandable. As long as you report the Vendor ID and Device ID of the network card, as long as the manufacturer has an NDIS2 driver, it can be added. It also supports nVidia network cards very well, and there is no need to specify it in the Config.sys menu.

Wrong, DETPCI.SYS can also be infinitely expanded

Can detpci also achieve this? Please inform. Currently, the network card of the P35 motherboard cannot be detected by detpci. Do I just need to copy the new e1000.dos in?

Oh, need to take a look

I'm a newbie, wanting to make a bootable disk. Now I've solved a difficult problem of DOS networking. ^_^ It's still in Chinese, thanks!

How does Windows XP access DOS?

The network function is not as strong as http://netbootdisk.com/screens.htm.

IPX is still needed by many programs under DOS. For example, Yugu Tianqing network clone, netop, netcopy for netop. Most network programs under DOS need packet driver support. Using ms ipx + dis_pkt is completely the same in efficiency as ms ip + dis_pkt. The former uses less memory and starts faster.

Other universal network clone tools or network boot disks use DETPCI.SYS provided by Ghost Enterprise Edition to realize network card detection. Currently, only maxdos uses this method. Unless it is the IBM IP protocol, it can only be used when loading in config.sys.

The network card detection module is written by ourselves. Because in terms of the number of network card recognition, it can be said to be infinitely expandable. As long as the Vendor ID and Device ID of the network card are reported, as long as the manufacturer has an NDIS2 driver, it can be added.

Can the slot number be checked? If it only checks the Vendor ID and Device ID, there are a lot of such source programs online, and there is no need to write it ourselves.

The dialog box to solve the shared error 53 problem is not seen in the picture. Is there no such function. Or?

Is the nVidia driver the latest?

nVidia's official side updates several times a month.

Originally posted by zqlcch at 2007-9-8 12:38 PM:
Can detpci also be implemented? Please inform. Currently, the network card of the P35 motherboard cannot be detected by detpci. Just copy the new e1000.dos in?

Completely dismiss detpci, the detpci.sys that comes with ghost is for generating and selecting the IBM TCP/IP boot disk. Many P35 motherboards integrate 8169, 8111b(c), Marvell gigabit network cards, have you all tried them?
The network card integrated on the P35 motherboard is also based on the PCI or PCI-E bus. I don't have a P35 motherboard to verify. I saw many people using detpci.sys for P35 motherboards on the MaxDOS forum. And no one said it couldn't be detected.

Thanks for the great share, I'll download and try it out...

Support

Bump