Forums before death by AOL, social media and spammers... "We can't have nice things"
|    comp.lang.asm.x86    |    Ahh, the lost art of x86 assembly    |    4,675 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 2,830 of 4,675    |
|    James Harris to wolfgang kern    |
|    Re: Look back to "just for the H@ck"    |
|    18 Jul 17 09:11:11    |
      From: james.harris.1@nospicedham.gmail.com              On 18/07/2017 07:26, wolfgang kern wrote:       > Martin Str|mberg wrote:       > ...       >> So you decide the rules and tell and show us (if you want).       >       > Thanks, I thought real needs caused this restrictions.              As someone who has seen the various attempts at writing a decoder I am       not sure what the goal is. I get it that you have been producing code       which uses bytes in the ASCII printable character set but there are lots       of questions.              What is the basic requirement?              What are the initial conditions, i.e. what do you know about registers       at entry?              What's the minimum number of bytes you can count on before you might get       to a CR or CR/LF?              Can you overwrite the original text with the decoded version? If not,       what options can be used to get memory to decode into?              In addition, I could guess there might be problems with the location of       the decoded code. So I guess it is meant to be started at CS:0 or       CS:100. Am I anywhere close?                     > So my rules for such an Base64 decoder would allow ASCII 33..127 and       > nothing less than 386 code.              You know you want to use 8086 code really.... :-)                     --       James Harris              --- SoupGate-Win32 v1.05        * Origin: you cannot sedate... all the things you hate (1:229/2)    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca