No one has voted on any posts yet. Votes from other community members are used to determine a member's reputation amongst their peers.
6 Posted Topics
Re: if you want to actually understand how assembly works, you shouldn't use all those pre-defined macros! there isn't one single CPU instruction in all of the code you pasted. understanding assembly means understanding the instructions and what they do. and in the future please just use the CODE tags instead … | |
Re: no reason to restrict yourself to looking for TASM source code, it's all the same minus some syntax differences. in any case you must have not looked very hard, just doing a google search for "tasm multiplication" turns up tons of relevant results. what have you tried so far in … | |
Re: in addition to simply knowing what opcodes translate to what values, it is essential that you understand the so-called mode/reg/RM byte. there are quite a few addressing modes understood by the 8086 CPU. this byte is placed directly after the opcode byte if the opcode requires operand(s) that aren't immediate. … | |
Re: as schoil pointed out, it sounds like you're not really clear on exactly how disk access works. there isn't some special CPU instruction that magically creates A:\ or anything like that. the easiest way to go about actually reading data off the disk is to use the BIOS routines for … | |
let me preface this by explaining the reason i'm writing this code.. i've been writing an x86 PC emulator in FreeBASIC, and this program is designed to test it's handling of video mode 13h, including palette manipulation. i thought in addition to being fun (at least for a nerd like … | |
Re: in addition to that, you also have to have routines in between each byte you send that polls the serial controller's status port to know when the other system has received the data, and it's safe to send the next byte. if you neglect to do this, the data coming … |
The End.