Chinpokomon, if I didn't know you weren't me, I would've sworn I wrote these lines. Like a program I wasn't even interested in. Once done, wouldn't even use it

Chinpokomon, if I didn't know you weren't me, I would've sworn I wrote these lines. Like a program I wasn't even interested in. Once done, wouldn't even use it. Years I was 14-15 were spent looking at disassembly listings(I used Win32DASM) getting drowned in patching versions (HexDecChar Editor), changing things. Sometimes not keeping track, wait, what did I change ? Learning to organize, even on paper. Offsets. Then writing small programs in Assembly, Pascal and C to do that. EB, 74, 75, 76, 90 etc.. Had a special meaning to me. Test calls, bogus functions and bloated DLLs getting called from a gazillion places(some of these on purpose). This has been invaluable to me. When I went to college, some courses have people struggling with debugging a program, but as you said, when you've been so close to the machine and didn't get lost, following an index is fairly easier. Also undeniably, when we had uP architecture course, I already knew that 5 years before, so it just was a refresher (bear in mind that they didn't even scratch the surface of what I was doing on my own as a kid. The most interrupt they toid with was printing (09h/21h) whilst I played with TSR and some neat things. It was also very useful with microcontroller class. PIC micros had only 35 instructions (didn't like MikroC). A lot of what I did as a kid or a bit later, turned to come in handy, always, at a later time.. So it became a sort of rule .. Whenever I'm doing something, I trust my gut instinct that some time, I'll use it. I'm yet to be proven wrong. Thanks for sharing, man.