Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>So I was doing some more digging, I stumbled across the following resource:</p> <p><a href="http://books.google.com/books?id=veMTOpapeZkC&amp;pg=PT327&amp;lpg=PT327&amp;dq=how+to+far+jump+to+label+assembly&amp;source=bl&amp;ots=_jHSgrwdfG&amp;sig=C63QURL0FlVhDv_FFrDm1oevBfs&amp;hl=en&amp;sa=X&amp;ei=zOWSUbWxGcWDyAH77ICoCA&amp;ved=0CDwQ6AEwAjgK" rel="nofollow">http://books.google.com/books?id=veMTOpapeZkC&amp;pg=PT327&amp;lpg=PT327&amp;dq=how+to+far+jump+to+label+assembly&amp;source=bl&amp;ots=_jHSgrwdfG&amp;sig=C63QURL0FlVhDv_FFrDm1oevBfs&amp;hl=en&amp;sa=X&amp;ei=zOWSUbWxGcWDyAH77ICoCA&amp;ved=0CDwQ6AEwAjgK</a></p> <p>To which I saw there was something called a near jump...<code>jmp near</code> in the code. I don't know how I missed that in my previous hours of looking. When I entered it into my code it resolved my issue...</p> <p>short jumps are +- 127 relative bytes. Near jumps are up to 2GB within a segment. Far jumps or outside of the segment; I think I may have been trying to use the far jump incorrectly.</p> <p>The following fixed my code;</p> <pre><code>org 0x500 jmp near main %include "smallFile1.inc" ;couple bytes assembled and linked in %include "smallFile2.inc" ;couple bytes assembled and linked in %include "smallFile3.inc" ;couple bytes assembled and linked in %include "LargeFile.inc" ;couple hundred bytes assembled and linked in %include "LargeFile2.inc" ;couple hundred bytes assembled and linked in main: ;start instructions, these instructions are now reached. </code></pre> <p>Thank you to everyone who looked at this in attempts to resolve my issue. Hope this helps somebody someday.</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload