Assembly language programming problem in dos system initialization
I have a little problem in understanding that why we are storing ES and AX values in STACK. This is mentioned in lines "line1" and "line2", respectively.
EXTERN RE_INIT:FAR
ASSUME ES:SYSINITSEG
PUSH ES
MOV AX, OFFSET SYSIN
PUSH AX
RE_INIT PROC FAR
RET
RE_INIT ENDP
;
;MOV THE DOS TO IT'S PROPER LOCATION
;
SYSIN:
.........code continues.........
assembly dos masm x86-16
add a comment |
I have a little problem in understanding that why we are storing ES and AX values in STACK. This is mentioned in lines "line1" and "line2", respectively.
EXTERN RE_INIT:FAR
ASSUME ES:SYSINITSEG
PUSH ES
MOV AX, OFFSET SYSIN
PUSH AX
RE_INIT PROC FAR
RET
RE_INIT ENDP
;
;MOV THE DOS TO IT'S PROPER LOCATION
;
SYSIN:
.........code continues.........
assembly dos masm x86-16
1
Because the value of ES is not known until runtime. One way around this is to push the segment you want to jump to, followed by the offset and then issuing a FAR RETURN. The effect is doing a runtime FAR JMP to SYSIN. It sets CS to what ES was and the IP (offset) of SYSIN. It is jumping to a piece of relocated code in a different segment but the same offset (SYSIN).
– Michael Petch
Dec 30 '18 at 5:31
Thanks Michael, now I have understood the complete logic. Thank
– Vstbutwhy
Dec 30 '18 at 6:48
add a comment |
I have a little problem in understanding that why we are storing ES and AX values in STACK. This is mentioned in lines "line1" and "line2", respectively.
EXTERN RE_INIT:FAR
ASSUME ES:SYSINITSEG
PUSH ES
MOV AX, OFFSET SYSIN
PUSH AX
RE_INIT PROC FAR
RET
RE_INIT ENDP
;
;MOV THE DOS TO IT'S PROPER LOCATION
;
SYSIN:
.........code continues.........
assembly dos masm x86-16
I have a little problem in understanding that why we are storing ES and AX values in STACK. This is mentioned in lines "line1" and "line2", respectively.
EXTERN RE_INIT:FAR
ASSUME ES:SYSINITSEG
PUSH ES
MOV AX, OFFSET SYSIN
PUSH AX
RE_INIT PROC FAR
RET
RE_INIT ENDP
;
;MOV THE DOS TO IT'S PROPER LOCATION
;
SYSIN:
.........code continues.........
assembly dos masm x86-16
assembly dos masm x86-16
edited Dec 30 '18 at 5:33
Michael Petch
25.3k556101
25.3k556101
asked Dec 30 '18 at 5:17
VstbutwhyVstbutwhy
173
173
1
Because the value of ES is not known until runtime. One way around this is to push the segment you want to jump to, followed by the offset and then issuing a FAR RETURN. The effect is doing a runtime FAR JMP to SYSIN. It sets CS to what ES was and the IP (offset) of SYSIN. It is jumping to a piece of relocated code in a different segment but the same offset (SYSIN).
– Michael Petch
Dec 30 '18 at 5:31
Thanks Michael, now I have understood the complete logic. Thank
– Vstbutwhy
Dec 30 '18 at 6:48
add a comment |
1
Because the value of ES is not known until runtime. One way around this is to push the segment you want to jump to, followed by the offset and then issuing a FAR RETURN. The effect is doing a runtime FAR JMP to SYSIN. It sets CS to what ES was and the IP (offset) of SYSIN. It is jumping to a piece of relocated code in a different segment but the same offset (SYSIN).
– Michael Petch
Dec 30 '18 at 5:31
Thanks Michael, now I have understood the complete logic. Thank
– Vstbutwhy
Dec 30 '18 at 6:48
1
1
Because the value of ES is not known until runtime. One way around this is to push the segment you want to jump to, followed by the offset and then issuing a FAR RETURN. The effect is doing a runtime FAR JMP to SYSIN. It sets CS to what ES was and the IP (offset) of SYSIN. It is jumping to a piece of relocated code in a different segment but the same offset (SYSIN).
– Michael Petch
Dec 30 '18 at 5:31
Because the value of ES is not known until runtime. One way around this is to push the segment you want to jump to, followed by the offset and then issuing a FAR RETURN. The effect is doing a runtime FAR JMP to SYSIN. It sets CS to what ES was and the IP (offset) of SYSIN. It is jumping to a piece of relocated code in a different segment but the same offset (SYSIN).
– Michael Petch
Dec 30 '18 at 5:31
Thanks Michael, now I have understood the complete logic. Thank
– Vstbutwhy
Dec 30 '18 at 6:48
Thanks Michael, now I have understood the complete logic. Thank
– Vstbutwhy
Dec 30 '18 at 6:48
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53975440%2fassembly-language-programming-problem-in-dos-system-initialization%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53975440%2fassembly-language-programming-problem-in-dos-system-initialization%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
Because the value of ES is not known until runtime. One way around this is to push the segment you want to jump to, followed by the offset and then issuing a FAR RETURN. The effect is doing a runtime FAR JMP to SYSIN. It sets CS to what ES was and the IP (offset) of SYSIN. It is jumping to a piece of relocated code in a different segment but the same offset (SYSIN).
– Michael Petch
Dec 30 '18 at 5:31
Thanks Michael, now I have understood the complete logic. Thank
– Vstbutwhy
Dec 30 '18 at 6:48