, witch is set to 0 i guess.but as i said in my previous post - i probably solved this problem. but rather keep this topic open...
loader
Re: loader
thanks for the answer. yes - the kernel image should be loaded to to 0xa000. so for int13 must be es set to 0xa00. that has nothing to do with the stack segment , witch is set to 0 i guess.
but as i said in my previous post - i probably solved this problem. but rather keep this topic open...
, witch is set to 0 i guess.but as i said in my previous post - i probably solved this problem. but rather keep this topic open...
-
Firestryke31
- Member
- Posts: 550
- Joined: Sat Nov 29, 2008 1:07 pm
- Location: Throw a dart at central Texas
- Contact:
Re: loader
WRONG! These segments overlap. If SS is 0x0000 the only ES values that will not overlap are >= 0x1000. This has to do with the way real mode addressing works, in which an address = segment * 16 + offset, so with your setup SS:0xA000 == ES:0x0000 and data will be overwritten.lama wrote:es set to 0xa00. that has nothing to do with the stack segment.
Owner of Fawkes Software.
Wierd Al wrote: You think your Commodore 64 is really neato,
What kind of chip you got in there, a Dorito?