China DOS Union

Why doesn't my autoexec.bat run automatically at startup in DOS? I installed DOS using the copy method. Master, why is that?


—————————————— willsort Edition record ——————————————
—————————————— willsort Edition record ——————————————


[ Last edited by willsort on 2006-1-7 at 19:14 ]

Wait, the original question is: Why doesn't the autoexec.bat run automatically when starting up in DOS? I installed DOS using the copy method. Master, why is that?


—————————————— willsort's edition ——————————————
—————————————— willsort's edition ——————————————


[ Last edited by willsort on 2006-1-7 at 19:14 ]

Hold on, the user's question is: Why doesn't the autoexec.bat run automatically at startup in DOS? I installed DOS using the copy method. Master, why is that?


—————————————— willsort's operation ——————————————
—————————————— willsort's operation ——————————————


[ Last edited by willsort on 2006-1-7 at 19:14 ]

Wait, the user's original text: My autoexec.bat doesn't run automatically on startup in DOS. I installed DOS using copy. Master, why?


—————————————— willsort management ——————————————
—————————————— willsort management ——————————————


[ Last edited by willsort on 2006-1-7 at 19:14 ]

Okay, let's get back to the translation. The user's first part: Why doesn't autoexec.bat run automatically at startup in DOS? I installed DOS by copying. Master, why?

The rest of the forum record part remains as is.

So the translated first part: Why doesn't the autoexec.bat run automatically when starting up in DOS? I installed DOS using the copy method. Master, why?

But actually, let's do the strict translation based on the user's input:

My autoexec.bat doesn't run automatically at startup in DOS. I installed DOS by copying. Master, why?

No, wait, the user's first part:

Wait, no, let's just translate the user's original:

So:

My autoexec.bat doesn't run automatically on startup in DOS. I installed DOS via copy. Master, why?

No, the user's first:

Wait, the user's initial question:

No, let's go back. The user's first part:

My autoexec.bat doesn't run automatically on startup in DOS. I installed DOS:

No, the user's:

My autoexec.bat doesn't run automatically on startup in DOS. I installed DOS via copy. Master, why?

No, I think I made a mistake. The user's:

My autoexec.bat doesn't run automatically on startup in DOS. I installed DOS via copy.

No, the user's:

My autoexec.bat doesn't run automatically on startup in DOS.

No, I think I need to strictly translate the user's first part:

Why doesn't the autoexec.bat run automatically when starting up in DOS? I installed DOS by copying. Master, why?

Wait, no, let's just translate the user's exact words:

My autoexec.bat doesn't run automatically at startup in DOS. I installed DOS by copy. Master, why?

No, the user's first part is:

Why doesn't the autoexec.bat run automatically when starting up in DOS? I installed DOS using copy. Master, why?

Now, the correct translation according to the user's input:

My autoexec.bat doesn't run automatically on startup in DOS. I installed DOS via copy.

No, the user's:

My autoexec.bat doesn't run automatically on startup in DOS. I installed DOS via copy.

No, I think I was overcomplicating. Let's do it step by step:

Original user's first line: "我的autoexec.bat开机为什么不自动运行,是在dos下的。我是用copy的方法装的dos。请问师傅为什么啊？"

Translate: "Why doesn't my autoexec.bat run automatically at startup under DOS? I installed DOS using the copy method. Master, why?"

Then the forum record part:


—————————————— willsort's operation ——————————————
—————————————— willsort's operation ——————————————


[ Last edited by willsort on 2006-1-7 at 19:14 ]

So the full translated text:

Why doesn't my autoexec.bat run automatically at startup under DOS? I installed DOS using the copy method. Master, why?


—————————————— willsort's operation ——————————————
—————————————— willsort's operation ——————————————


[ Last edited by willsort on 2006-1-7 at 19:14 ]

No, wait, the forum record part is as original.

Final correct translation for user's first part:

Why doesn't the autoexec.bat run automatically when starting up in DOS? I installed DOS by copying. Master, why?

Wait, I think I made a mistake. Let's start over:

User's first part: "我的autoexec.bat开机为什么不自动运行,是在dos下的。我是用copy的方法装的dos。请问师傅为什么啊？"

Translation: "Why doesn't my autoexec.bat run automatically at startup under DOS? I installed DOS using the copy method. Master, why?"

Then the forum record:


—————————————— willsort's management ——————————————
—————————————— willsort's management ——————————————


[ Last edited by willsort on 2006-1-7 at 19:14 ]

So the combined translated text:

Why doesn't my autoexec.bat run automatically at startup under DOS? I installed DOS using the copy method. Master, why?


—————————————— willsort management ——————————————
—————————————— willsort management ——————————————


[ Last edited by willsort on 2006-1-7 at 19:14 ]

I think I need to just focus on the user's question first. The user's question is:

My autoexec.bat doesn't run automatically at startup in DOS. I installed DOS using copy. Why?

Then the forum part is:


—————————————— willsort edition ——————————————
—————————————— willsort edition ——————————————


[ Last edited by willsort on 2006-1-7 at 19:14 ]

So the final translated output for the user's question and forum record:

Why doesn't my autoexec.bat run automatically at startup under DOS? I installed DOS using the copy method. Master, why?


—————————————— willsort's operation ——————————————
—————————————— willsort's operation ——————————————


[ Last edited by willsort on 2006-1-7 at 19:14 ]

Wait, no, I think I messed up. Let's do it correctly:

User's first part: "我的autoexec.bat开机为什么不自动运行,是在dos下的。我是用copy的方法装的dos。请问师傅为什么啊？"

Translation: "Why doesn't my autoexec.bat run automatically at startup under DOS? I installed DOS using the copy method. Master, why?"

Forum record part:


—————————————— willsort management ——————————————
—————————————— willsort management ——————————————


[ Last edited by willsort on 2006-1-7 at 19:14 ]

So the complete translated text:

Why doesn't my autoexec.bat run automatically at startup under DOS? I installed DOS using the copy method. Master, why?


—————————————— willsort's management ——————————————
—————————————— willsort's management ——————————————


[ Last edited by willsort on 2006-1-7 at 19:14 ]

I think I overcomplicated. Let's just translate the user's question clearly:

My autoexec.bat doesn't run automatically at startup in DOS. I installed DOS by copying. Master, why?

And the forum part remains as:


—————————————— willsort edition ——————————————
—————————————— willsort edition ——————————————


[ Last edited by willsort on 2006-1-7 at 19:14 ]

Final correct translation:

Why doesn't my autoexec.bat run automatically at startup in DOS? I installed DOS using the copy method. Master, why?


—————————————— willsort's management ——————————————
—————————————— willsort's management ——————————————


[ Last edited by willsort on 2006-1-7 at 19:14 ]

Wait, no, I think I made a mistake in the forum part. The forum part is just the original bbcode, so we keep it as is. So the final output is:

Why doesn't my autoexec.bat run automatically at startup in DOS? I installed DOS using the copy method. Master, why?


—————————————— willsort edition ——————————————
—————————————— willsort edition ——————————————


[ Last edited by willsort on 2006-1-7 at 19:14 ]

I think I should stop overthinking and just do the user's question translation:

My autoexec.bat doesn't run automatically at startup in DOS. I installed DOS using the copy method. Master, why?

And the forum part:


—————————————— willsort edition ——————————————
—————————————— willsort edition ——————————————


[ Last edited by willsort on 2006-1-7 at 19:14 ]

Yes, that's the correct translation.
Why doesn't my autoexec.bat run automatically at startup in DOS? I installed DOS using the copy method. Master, why?


—————————————— willsort edition ——————————————
—————————————— willsort edition ——————————————


[ Last edited by willsort on 2006-1-7 at 19:14 ]

Wait, no, I think I messed up the formatting. Let's start fresh:

User's question: "我的autoexec.bat开机为什么不自动运行,是在dos下的。我是用copy的方法装的dos。请问师傅为什么啊？"

Translation: "Why doesn't my autoexec.bat run automatically at startup under DOS? I installed DOS using the copy method. Master, why?"

Forum record:


—————————————— willsort management ——————————————
—————————————— willsort management ——————————————


[ Last edited by willsort on 2006-1-7 at 19:14 ]

So the final correct translation:

Why doesn't my autoexec.bat run automatically at startup under DOS? I installed DOS using the copy method. Master, why?


—————————————— willsort management ——————————————
—————————————— willsort management ——————————————


[ Last edited by willsort on 2006-1-7 at 19:14 ]

I think I was overcomplicating. The correct translation for the user's question is:

Why doesn't my autoexec.bat run automatically at startup in DOS? I installed DOS using the copy method. Master, why?

And the forum part remains as:


—————————————— willsort edition ——————————————
—————————————— willsort edition ——————————————


[ Last edited by willsort on 2006-1-7 at 19:14 ]

Yes, that's it.
Why doesn't my autoexec.bat run automatically at startup in DOS? I installed DOS using the copy method. Master, why?


—————————————— willsort edition ——————————————
—————————————— willsort edition ——————————————


[ Last edited by willsort on 2006-1-7 at 19:14 ]

In XP, what do the autoecec.bat and config.sys look like? Where are they located? How to load them automatically?

Re hetao:

JonePeng has mentioned that in the series of operating systems such as WinNT/2k/XP/03, config.sys and autoexec.bat under the root directory of the system disk are no longer used. The config.nt and autoexec.nt under %SystemRoot%\system32 are only used for the default startup configuration of the command.com (not including cmd) in the NT command line environment, and this setting can be modified.

As for why your environment cannot load autoexec.bat, it depends on whether the DOS system can be correctly booted at startup and whether autoexec.bat is located on the root directory of the DOS system disk. Both conditions are indispensable.

---------- Edited by willsort ----------
The content shown in red is verified to be incorrect remarks, please pay attention!
---------- Edited by willsort ----------

[ Last edited by willsort on 2005-9-25 at 10:24 ]

Thanks to the moderator for the guidance. I copied an msdos.sys to the root directory of drive C, and autoexec.bat can run automatically. But can the moderator explain the relationship between these two files? I found that randomly modifying msdos.sys can also make autoexec.bat not run, but why can DOS still start (just autoexec.bat is not executed). Also, you said that config.nt and autoexec.nt are only run when starting the command line environment of NT, can they run at boot?

Re hetao:

Under a single - system platform, msdos.sys should not affect the recognition of config.sys and autoexec.bat. I tried to remove the msdos.sys file in the MSDOS 7.10 single system, and the two files still executed normally. If you have a multi - system environment, such as a dual system of msdos7.10 (or win98) and msdos 6.22, then items like bootgui, bootmulti in msdos.sys will affect the recognition and operation of config.sys and autoexec.bat. However, you have not yet explained your system overview, especially how you joined the DOS startup.

As for whether config.nt and autoexec.nt can run at startup, it depends on whether command under NT can run at startup. So far, I have not received relevant information. As for the command line mode in the XP startup menu, it starts cmd, not command. And whether setting a logon script can be realized, I don't know because of my limited experience.

I'm really sorry, willsort. My system overview has always been written rather unclearly, causing you a lot of trouble. Now I'll explain my system overview:

The C: drive has Windows 2000 Pro installed.
The D: drive has Windows XP Pro installed.
The E: drive is for video and animation files.
The F: drive is for backups. There is a 1.44M floppy drive and an optical drive.

This is the current situation. I've reinstalled the system several times before. The C: drive once had Windows 98 installed and then was replaced with Windows 2000, which is the current situation. There is a bootsect.dos file in the C: drive, and the autoexec.bat and config.sys are empty files. I installed DOS 7.1 normally into the virtual PC virtual machine under Windows 2000, then copied io.sys and command.com from the virtual machine to the C: drive of the real machine, copied some other tools to the C:\dos folder of the real machine, configured the config.sys and autoexec.bat files, didn't configure the msdos.sys file, and added the DOS startup item in boot.ini. When I start the computer, I can enter DOS and load the configurations in config.sys, but the autoexec.bat file isn't executed automatically; I have to execute it manually. I copied the msdos.sys file from the virtual machine to the C: drive of the real machine, restarted, and then the autoexec.bat file is executed automatically. I tried to delete some items in msdos.sys to see if I could make the autoexec.bat file execute automatically to find out the items that affect the execution of autoexec.bat, but I don't quite know the functions of the various items in msdos.sys, and there are too many configuration items in it. I gave up after trying two or three times, so I came here to ask the master for help.

I read in a book that through setting the Windows 2000/XP registry key ([hkey_current_user\software\microsoft\windowsnt\currentversion\winlogon] The dword value of parseautoexec is 1 to start executing autoexec.bat, and 0 to not execute) can determine whether the autoexec.bat file is executed at startup. How is this回事?

[Options]

　　AutoScan=1/0

　　BootDelay=2/?

　　BootGUI=1/0

　　BootKeys=1/0

　　BootMenu=0/1

　　BootMenuDefault=1/2/3/4/5/6/7

　　BootMulti=0/1

　　BootWarn=1/0

　　BootWin=1/0

　　DblSpace=0/1

　　DoubleBuffer=0/1

　　DrvSpace=0/1

　　Load Top=1/0

　　Logo=1/0

　　WinVer=4.10.1998

　　AutoScan: Whether to run ScanDisk on next startup after an abnormal shutdown.

　　BootDelay: Waiting time (in seconds) before hotkey is pressed during boot.

　　BootGUI: Whether to enter Windows GUI interface on startup (otherwise DOS interface).

　　BootKeys: Whether hotkeys are effective on startup.

　　BootMenu: Whether to display boot menu on startup (otherwise hotkey must be pressed to display).

　　BootMenuDefault: Default item (i.e., cursor position) when boot menu is displayed.

　　BootMulti: Whether to allow booting DOS 6.xx (provided that the boot disk has old DOS boot files and the disk must be FAT16).

　　BootWarn: Whether to prompt to enter safe mode on next startup after boot failure (this is annoying, better to turn off!).

　　BootWin: Whether to automatically load old DOS on startup.

　　DblSpace: Whether to load DBLSPACE.BIN on startup.

　　DoubleBuffer: Whether to enable double buffer support.

　　DrvSpace: Whether to load DRVSPACE.BIN on startup.

　　Load Top: Whether to load part of the system core into upper memory on startup.

　　Logo: Whether to display the "blue sky and white clouds" on startup.

This is from the MSDOS.SYS of Windows 95, not sure if it works under NT~

Re hetao:

Regarding "ParseAutoexec", with your reminder, I found this web link http://www.winguides.com/registry/display.php/162, which mentions that setting the registry according to the following requirements can determine whether XP analyzes the environment variable setting statements in autoexec.bat under the root directory of the system drive when starting up (the default setting is to analyze), and other statements are never analyzed.

So, the relevant view I mentioned on floor 5 is incorrect. Thanks a lot for your tip here!

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

Regarding how to automatically call autoexec.bat when XP starts. After checking, the login script of XP must use a relative path (relative to the user configuration path), so this plan is not feasible for the time being; for other feasible plans, you can consider placing autoexec.bat in the "Startup" menu of the Start menu, or in the subkey in the registry.

Finally, for the issue that your msdos.sys affects autoexec.bat, since I can't reproduce the problem, I can't do in-depth analysis, and I can only make some hints here.

In the msdos system, config.sys is read by io.sys and configures the system environment according to it, and autoexec.bat is read and interpreted and executed by command.com; and in the startup process of dos, the system boot sector transfers the process control to io.sys first, and then io.sys transfers the command interpreter (shell) according to the configuration of config.sys, and the default command interpreter is command.com, which is equivalent to windows' explorer.

From your situation, the problem should be in the command.com process, and I'm not very clear about the influence that msdos.sys can exert on it. You can upload your msdos.sys / config.sys / autoexec.bat for everyone to analyze together.

[ Last edited by willsort on 2005-9-25 at 10:56 ]

config.sys:

devicehigh=c:\dos71\himem.sys
devicehigh=c:\dos71\umbpci.sys
shell=c:\command.com
dos=high,umb,auto

set path=c:\dos71;..;.
installhigh=c:\dos71\smartdrv.exe
installhigh=c:\dos71\doskey.com
rem installhigh=c:\dos71\doslfn.com


msdos.sys:
\;MS-DOS 7.10 System Configuration File
;(C)Copyright Microsoft Corp 1981-1999
;=====================================

[Options]
AutoScan=0
BootDelay=0
BootGUI=0
BootMenu=0
BootMulti=0
BootSafe=0
BootWarn=0
DisableLog=0
DoubleBuffer=0
Logo=0
SystemReg=0
;
;For compatibility with Windows 9x GUI only:
WinVer=4.10.

[Paths]
windir=C:\
winbootdir=.
HostWinBootDrv=C

;
;=====================================
;MS-DOS 7.10 System Configuration File
;(C)Copyright Microsoft Corp 1981-1999
;=====================================
;



autoexec.bat:
lh c:\ccdos\ccdos

The above are the specific contents of the three files: If you remove msdos.sys, the computer will not automatically execute autoexec.bat (others are normal). If there is msdos.sys, there is no problem. I tried modifying msdos.sys and found that autoexec.bat cannot be automatically executed, that is, msdos.sys needs to be in specific content.
In addition, when I load ntfsdos, it prompts that there is no DPMI (dos protect mode interface) dos protection mode interface. May I ask master how to enable the DPMI function.

Re hetao:

I'm extremely sorry! Because when I copied the file you provided, I suddenly became interested in the anti-overwrite copy of the file and spent a day completing a batch script, and I just made progress not long ago. Using the program I wrote, I copied the file you provided into my test environment.

Through actual testing, it has been confirmed that the BootGUI setting determines whether autotexec.bat is interpreted and executed. When it is set to 1 or not set, autoexec.bat will be ignored.

Analyzing the reason, it should be that BootGUI determines the shell loaded by io.sys: when its value is 0, command.com is used as the shell to boot into the DOS environment, which includes the process of reading and interpreting autoexec.bat that I mentioned on the 10th floor; and when its value is 1, win.com is used as the shell, but because in a DOS single-system environment or a multi-system environment without Win9x, win.com cannot be found in the windows directory, so the boot will be aborted, and autoexec.bat also has no chance to be executed.

It doesn't matter!
I have also tested it. There are two options in msdos.sys that affect the normal execution of autoexec.bat:
One is the bootgui= in [option] as you mentioned
The other is windir= in [paths]
If there is a lack of an autoexec.bat, it will not execute normally. As long as these two options are present, there is no problem.
If there is no "bootgui=0" item, there will be an error prompt and autoexec.bat will not be executed. And if the "windir=" item is missing, there is no prompt and autoexec.bat will not be executed. This item is only meaningful when starting win9x. If only DOS is started, the path after "windir=" can be filled in arbitrarily, but if it is not filled in, autoexec.bat will not be executed. But I don't know why this is the case? I don't know what your opinion is, master?
In addition, when I load ntfsdos, it prompts that there is no DPMI (dos protect mode interface) dos protection mode interface. Master, how can I make it have DPMI function?

Re hetao:

Based on your test, I have conducted a more in-depth exploration and found that there are many key elements to this issue, mainly as follows.

1. Whether shell=c:\command.com is set in config.sys;
2. Whether there is windir=C:\ in msdos.sys;
3. Whether there is BootGUI=0 in msdos.sys;
4. Whether path c:\windows or set path=c:\windows;c:\dos71 and similar statements setting the search path for win.com are set in autoexec.bat;

I am still researching their specific impacts on the startup process. Currently, in terms of your current startup environment, if there is no msdos.sys, you can enter exit after startup to exit the new shell created by the shell command, and then autoexec.bat will be executed; alternatively, you can delete this shell statement, and autoexec.bat will be directly executed during startup.

As for DPMI support, you can just load cwsdpmi.exe from Wengier's super universal MSDOS7.10 boot disk. This boot disk can be downloaded from multiple sites. Even if you don't have it, cwsdpmi is a very common memory expansion tool and should be easy to download. If you really can't find it, I can upload it.

[ Last edited by willsort on 2005-9-28 at 20:33 ]

Re All:

Now release my preliminary test results.

————————————————————————————————————————
Item: The impact of BootGUI and windir=C:\ in MSDOS.SYS on the boot process.
Environment: MSDOS7.10, with Win3.2 installed under C:\Windows
Settings: config.sys contains the line shell=c:\command.com,
autoexec.bat contains the line set path=%path%;c:\windows,
others are the same as the configuration file in reference floor 9
Settings:
B0 BootGUI=0
B1 BootGUI=1 or ;BootGUI=0
WC windir=C:\
WD ;windri=C:\
DA Disable Autoexec.bat
PA Parse Autoexec.bat
CW Cann't find win.com
NE Exit can't exit shell command.com
EC Exit exits with cann't find command.com
SW Boot Windows3.2 (Win.com)

Results:
1) B0+WC: PA, EC, PA, SW
2) B0+WD: DA, EC, PA
3) B1+WC: DA, CW, NE
4) B1+WD: DA, EC, PA

Discussion:
From the consistent results of 2/4 comparison, BootGUI does not play a decisive role. It only informs IO.SYS to start Win.com after the boot is completed, and this startup process can be terminated (3/4);
And from the comparison results of 1/2, 3/4, it can be seen that the setting of windir is crucial. It not only affects the environment variables winbootdir/temp/tmp (not set the windir variable in the actual test), but also has an impact on the path configuration of autoexec.bat and win.com, and the impact on win.com may be indirect, because the path setting of win.com is in autoexec.bat.
The strange places are:
1) BootGUI is not enabled, but finally starts Win.com;
3) Just start to the new shell and then start searching for win.com (at this time autoexec.bat has not been executed)
4) Parsed Autoexec, but can't start win.com;
————————————————————————————————————————

In addition, I monitored another cross-impact: when there is a menudefault item in config.sys, even if msdos.sys sets logo=1, the boot LOGO still cannot be displayed. And this boot LOGO is also affected by other factors, which has not been determined yet, possibly related to the boot time.

Vaguely remember that with Windir, it will:
Automatically load IFSHLP.SYS
Some Bootxxx will be escaped
Function keys will also be escaped

I find it too troublesome and didn't delve into it

And it is best to test with Win9x