China DOS Union

Ask, I used mousedos to drive the network card, and then wanted to run netset.exe (from the network deployment tools of xugaohui, which can change the computer name and get the IP addresses of TFTP and DHCP), but it didn't work, and it prompted that a file was needed. May I ask: what specific other files does it need?

This question is clearer to xugaohui. I haven't used the netset.exe tool you mentioned..

Mousedos is a network card driver? Strange.. It seems like it should be a mouse driver by name..

mousedos is the mousedos toolbox, a universal network card driver toolbox for network cloning
The following is the website
http://www.mousedos.com/

In pure DOS, is there a good way to obtain the DHCP or TFTP IP address and SET it into a variable

Bump again, seeking methods to obtain DHCP and TFTP service IPs under DOS and assign them to variables

The missing file is that netset.exe cannot be used with mousedos. This needs to call other programs to detect the network card model.
Of course you can't use it alone.
You can try downloading again to see if it works. In order to reduce the size of tftpboot, netset.exe was modified. It has only been tested on the virtual machine for the time being. If it still has an error, report the online model.
Under DOS, you can obtain all the data passed by the DHCP server to the client.
I get the DHCP packet by searching the data in memory. It's the software called query.exe. Written with qbasic. When executed, it displays most of the information of the DHCP server. Currently only common information is obtained. Then a batch program is generated to set the tftpip environment variable. This method is crude, but this is an effective way. It can perfectly obtain all the data passed from the DHCP server (which can be a router) to the client.
Originally, a network program was written with qbasic. But qbasic can only write programs based on the packet driver. The DHCP data obtained by this method is inaccurate. It's okay for routers or old versions of hanewin DHCP. It's easy to make mistakes. When using the ndis2 driver network card, it can't be used. Finally, an idea came up. Search in memory.
It can be used for both the packet driver and the ndisk2 driver. The data can be accurately obtained each time.
This kind of problem has been mentioned by many people on the forum. The answers on the Internet are all writing WATTCP programs, which can't be used for the ndis2 driver. And I don't know C language at all.

[ Last edited by xugaohui on 2008-11-10 at 23:03 ]

Write your own QB network program pf
I tried ipconfig, but there are only local IP and gateway IP, and there is no server ID ip at all
After running query, it shows out of range, is it because of insufficient memory or what parameters are needed

It can only display the IP when the network is started and no other programs are executed. It is best to use it together with batch processing. It is suggested that you take a look at the netd.bat batch processing.

I took a look at your batch script. The netset batch script is encrypted. It seems that if you run a certain part within this program, the query can work normally?

I still can't do it before executing quickgho.bat under MOUSEDOS, and it shows "out of range".

I use query and sometimes can query the siaddr, which can be specified as the router's address, not my TFTP and DHCP address.
Using xugaohui's TFTPBOOT image, sometimes it's the router's address, sometimes it's the correct TFTP IP address.
Why is mine always not working? Super depressed

Why not just use my software package? The IP obtained by query is definitely correct. Both MS TCP and IBM TCP may obtain the IP assigned by DHCP service or the router's DHCP. IBM usually obtains the information of DHCP service. If you are using MS IPX NetBEUI and Packet driver, most of the obtained IP is assigned by the router. Query is to find the IP in the local memory. It has nothing to do with the network. At least my tftpboot has not encountered the "out of range" error prompt. If I encounter this prompt, I need to modify the program.

mousedos has stopped updating, and it itself supports few network cards. tftpboot is the most perfect one.

There is no need to reinvent the wheel.

The batch file is not encrypted, but it is just edited under DOS. You can edit it with edit in the cmd window.

In order to make the program applicable to both NDIS2 driver and Packet driver situations, it is more reasonable to use the method of finding DHCP data in the memory.

[ Last edited by xugaohui on 2008-11-12 at 17:02 ]

Your TFTPBOOT is indeed convenient, but I don't need the functions like changing the computer name at boot. I just need some functions that are applicable to me. Moreover, in my network environment, most of the time your TFTPBOOT gets the IP address of the router. My network is an environment where two wireless bridges of WDDRTt are used, and the host uses Windows 2008 Ent edition. While asking for advice, I can also improve myself. Maybe I didn't express clearly. I just need to be able to be well compatible with PXE boot packages in different network environments. Just as it's better to teach a man to fish than to give him fish, please give me some advice,楼主.

All are using msclient, we can't control whether it is looking for DHCP or the router's DHCP. In the environment I tested, 98% get the IP from the DHCP server. If it gets the router's DHCP, there's no way. Now the acquisition method is from memory. You can compare the client's IP information with the IP for entering Ghost network cloning. They are definitely the same. The function to change the computer name is a program running under DOS, completely independent from the network part.