Shulou(Shulou.com)06/01 Report--

This article mainly introduces how to build assembly language DOSBox and debug.exe environment under Windows64, which has a certain reference value, interested friends can refer to, I hope you can learn a lot after reading this article, the following let the editor take you to understand it.

This paper is also the answer to the similar question "how to enter debug under Windows 64-bit system".

When you need to learn assembly language in debug debug mode for other reasons, there will be an error similar to the following

This is because they are using 64-bit Windows systems (Win 7 Magi win 8 and Win 10, etc.), while 64-bit Windows systems no longer support entering debug debug mode at the command prompt.

So for users using 64-bit Windows systems, how can they successfully enter debug mode? There are three solutions:

Install a dual system with an additional 32-bit Windows operating system

Install a 32-bit Windows operating system in a virtual machine

Install and configure DOSBox and debug.exe on a 64-bit system

32-bit Windows systems can choose Win XP or Win 7, but whether it is a dual system or a virtual machine, it is too troublesome.

Here's the third way. By installing and configuring DOSBox and debug.exe, we can easily and quickly enter debug debug mode on a 64-bit Windows system.

First, prepare the materials DOSBox.exe and debug.exe (download link is provided at the end of the article).

Then install DOSBox, which is installed by default in the C:\ Program Files (x86) directory, or we can choose to install to another custom directory, here I choose to install to disk F.

After the installation is complete, we find debug.exe and put it in a location we like. For ease of management, I put debug.exe in the root directory of the DOSBox installation, and noticed that the root directory of the installation of DOSBox is: F:\ DOSBox-0.74.

Then we open DOSBox, and the initial interface is as follows:

It is not possible to enter the debug command directly at this time, and we still have to do some configuration work. So what do we do? The answer can be found in the DOSBox 0.74 Manual.txt file under the root of the DOSBox installation. We open the file and find the following help text

This help text means that we must use a command like the example "mount C D:\ GAMES" to mount one of our local directories as a drive of DOSBox before we can use DOSBox properly. In the example command "mount C D:\ GAMES", C indicates the drive we need to create in DOSBox, which can be defined at will, and D:\ GAMES indicates that we need to be mounted as the local directory of the drive. After the mount is successful, we enter the drive letter customized in the command, such as C:, to enter the partition in DOSBox.

Because we need to enter debug debugging mode, and debug.exe is placed in the F:\ DOSBox-0.74 directory at this time, we need to enter the following instruction: MOUNT F F:\ DOSBox-0.74 (, my custom drive letter is also F), as shown in the following figure:

Enter will indicate that drive F has been successfully mounted to the local directory F:\ DOSBox-0.74. At this point, we need to enter the F disk. We need to understand that this F disk is the F disk created in DOSBox after the MOUNT command. It maps to our local F:\ DOSBox-0.74 directory, but it is not the local F disk of our computer. Enter the command F: and enter, as shown below

After entering disk F, you can enter the debug command and enter debug mode normally.

It is true that you can enter debug mode through the above method, but it is very inconvenient to re-enter the above command every time you re-open DOSBox. We can change the configuration file to let DOSBox automatically enter the above command when it is opened. So how do I modify the configuration file? The answer can also be found in the DOSBox 0.74 Manual.txt file. We open the file and find the following help text

The above two help words mean that there is a [autoexec] section in the configuration file of DOSBox, and the commands in this section will run automatically every time DOSBox starts, and we can write MOUNT commands here. It also indicates the path of the configuration file on different systems, but we can find the configuration file more easily. Under the root of the DOSBos installation, there is a script file named DOSBox 0.74 Options.bat, which we can double-click to open the configuration file.

After opening the configuration file, pull it to the bottom and you can see the [autoexec] section.

We enter the above command here, as follows:

After saving, reopen DOSBox, which has been automatically mounted and entered the F disk, waiting for us to enter the debug command.

It is important to note that if we double-click the DOSBox 0.74 Options.bat file and do not open the configuration file, we can manually find the configuration file and open it. Opening DOSBox opens two windows at the same time, one of which is a black console window that indicates the absolute path to the configuration file:

After you find the configuration file through this path, open it in notepad.

Thank you for reading this article carefully. I hope the article "how to build an assembly language DOSBox and debug.exe environment under Windows64" shared by the editor will be helpful to you. At the same time, I also hope you will support us and pay attention to the industry information channel. More related knowledge is waiting for you to learn!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.