assembly - "Safety net" utilities (or tricks) for developing ASM under DOS? -
In Windows, when programming in assembly - says, one in Visual Studio. Inline assembly in CPP file - Development environment prevents my own mistakes If a substrate is released, then I stop the ESP register, it lets me know that something special happened, but it otherwise remains in the sun. When I'm not paying attention and writing my code in an invalid memory location, the only thing that gets crashed is my own program, which I can immediately return to editing in seconds. In DOS, these errors always require a reboot.
I understand that due to windows of different memory models, compared to the dose of windows (vs real-mode vs. virtual / protected mode) crashes- for the most part, windows cells prone , Rarely do damage outside the field of their own execution.
But I was still wondering whether there existed, past or present, a DOS utility which is a type of executor-in-progress security deterrent which reduces the possibility of complete DOS environment (Read: at least developer DOS), computer with free-level error on low-level developer error? >
You can write your program in mind with a 32-bit dos extension, such as DOS / 4G, DOS / 32 etc. A protected mode cover is started around the DOS, it will catch at least invalid instructions and most memory errors, print an exception handler report and will dump you back to the DOS shell.
You can still use many dos / bios interrupt functions, but you can effectively write 32-bit programs instead of a 16-bit.
Comments
Post a Comment