China DOS Union

I put the programs that need to run at startup in autoexec.bat, but there is no response when XP starts. Where should I make changes? I'm sorry, I'm a newbie. Please give me some advice!!!

xp starts without running autoexec.bat!win2000 runs autoexec.bat

Is there a way to make XP run autoexec.bat at startup?

Just put autoexec.bat directly in the startup of XP. Hehe..

In the XP windows\system32\ has AUTOEXEC.NT, but it doesn't seem to run automatically at boot. However, it runs automatically when running 16-bit DOS programs.

Oh, is that so? Thanks

Starting from Windows 2000, subsequent systems ignore the Autoexec.bat in the system root directory. To make the system automatically execute a batch file, you can place it in the "Startup" item in the Start menu. If you want the batch file to run in hidden mode, you can create its shortcut and then modify the running method, or make a VBS script program.

Re JonePeng & others:

Regarding the handling of autoexec.bat by NT series, there has been a discussion in the following post:

http://www.cn-dos.net/forum/viewthread.php?tid=17107#pid100219

Originally posted by willsort at 2005-10-6 23:10:
Re JonePeng & others:

There has been a discussion on the handling of autoexec.bat in NT series in the following post:

http://www.cn-dos.net/forum/viewthread.php?tid=17107#pid100219

Re willsort:

When will your self-enclosed training plan end? Come out and get some fresh air!!

I have read the post you provided above three times, but it doesn't seem to have a complete explanation of the reasons for the failure of autoexec.bat/autoexec.nt startup under NT-based environments like 2000/XP/2003?

I guess what more people want to know is how to control the startup of the system in the NT environment through autoexec.nt, such as setting passwords or interference items in autoexec.nt to prevent the system from completing the loading. If JONGPENG's method is used to add a batch file in the "Startup" item, the system has already been started by then.

Re 220110:

I'm very sorry that I've neglected this thread for a long time. Also, my closed training is intermittent, not meaning to be isolated from the world.

Regarding config/autoexec, the information mentioned in the link is relatively scattered. Now I'll sort it out.

In NT series operating systems such as 2000/XP/2003, the boot process basically doesn't rely on the two files config.sys / autoexec.bat. Among them, config.sys is completely no longer used. For autoexec.bat, only when the ParseAutoexec value in the registry (see the quote) is 1 (the default is this value), will it analyze the environment variable setting statements such as set / path in it, and other statements will be ignored in any case.

config.nt / autoexec.nt are the default configuration files for the command line environment of the NT series. They have nothing to do with the system boot process. The command line window opened by entering command in Run uses these two files for environment configuration.

If you intend to set passwords or interference items before the NT series system is loaded, using autoexec.bat or autoexec.nt can't be done. Maybe only using special boot management software or customizing a special ntloader can be done. I don't have the technology and experience in this regard.

User Key:
Value Name: ParseAutoexec
Data Type: REG_SZ (String Value)
Value Data: (0 = disabled, 1 = enabled)

Isn't it just solving it by directly modifying the registry???

Is it related to "boot script"?

Willsort is really my mentor!