China DOS Union

-- Unite DOS · Advance DOS · Grow DOS --

Union site: www.cn-dos.net Forum site: www.cn-dos.net/forum
DOS stands for freedom, openness and progress. Let us work hard, learn from the openness and GNU spirit of FreeDOS and Linux, and together build and grow a free GNU GPL world!

中国DOS联盟论坛
The time now is 2026-08-12 21:17
中国DOS联盟论坛 » DOS媒体世界 & 网络技术 (多媒体室) » When installing msclient3.0 to the final step, it prompts that SYSTEM.INI is incorrect View 1,665 Replies 1
Original Poster Posted 2008-02-22 15:34 ·  中国 辽宁 大连 联通
新手上路
Credits 6
Posts 2
Joined 2007-11-04 16:32
18-year member
UID 101676
Gender Male
Status Offline
When installing msclient 3.0 to the last step, it prompts that SYSTEM.INI has an error. It prompts that the SYSTEM.INI file in the installation disk is not writable or is missing. Press Enter to continue. After clicking Enter, it returns to DOS. After restarting, the network is not loaded. Check the SYSTEM.INI in the c:/net folder and find that some parameters such as username, lanroot, groupname, etc., have no set values. Under normal circumstances, they are there. The machine I am working on is an industrial steel material analysis equipment controlled by the DOS system. The customer requires DOS to connect to XP. On XP, we used VB to make a program for checking the data after DOS analysis. So we need to share the data under DOS over the network. The following are my operation steps: Boot into the virtual XP system with PE. Insert the USB flash drive to copy the MSCLIENT installation program NETSETUP, DEF-530 network card driver, and WG1049 patch. Restart and enter DOS. Install NETSETUP, the network card is successfully recognized, but it fails at the last step due to the error of SYSTEM.INI. I don't know why. Note: It has been successfully done to connect DOS with XP. Ask the expert. Why is this,!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Floor 2 Posted 2008-05-18 11:28 ·  中国 广东 珠海 电信
初级用户
Credits 58
Posts 26
Joined 2008-05-12 09:06
18-year member
UID 118462
Gender Male
Status Offline
Delete C:\NET\DHCP.PRM, first remove the "Hidden" and "Read-only" attributes! If you find it troublesome, when setting up, select PATH as C:\NET2 or other paths
Forum Jump: