Quote: "
ok, you just said to call DLLs i wanna know how i would include a function that loaded DLLs into the application.
"
Well, it'll be a little much to explain all that here. Sorry. But you might want to read
this and also download the zip "LUEVELSMEYER's description about PE file format" (bottom of page).
Quote: "
I heard the pointer is how the program knows where in the code the program is at and there is some sort of code that says to move the pointer according to the situations in the programs...
"
Ah, in x86 CPUs that would be a special register that is called PC (Program Counter). You can 'move' it by increasing, decreasing, overwriting the PC or using commands like JUMP, CALL etc. then it's automatically changed by the CPU.
Quote: "
Do you know where i can get a HEX list of the OPCODES and a tutorial or something on how to write the OPCODES and stuff...
"
The link to the opcode I gave show the opcodes in binary code because a lot bits change according to the registers it affects. If you want you can convert that to hexadecimal with the Windows calculator.
Quote: "
By parse table i mean how would i know what OPCODES to write in HEX for the commands...like a list of OPCODES for the commands and theyre HEX equivalent...
"
Well not every Basic command has an equivalent opcode. The whole trick is to convert a high-level language like Basic to machine code.
Quote: "
And about the HEX, so where does the hex go...i have a dword and i want to push it on a stack(whatever that is) where does the hex code for pushing it onto the stack go?
"
It's in the memory. And it stays there. The Program Counter points at that opcode, the opcode is "sent" to the CPU, the CPU now waits for the value to push and increases the PC by 1 (Byte 'cause the size of this opcode is 1 Byte), the value the PC points at is sent to the CPU, the CPU pushes the value onto the stack.
I awoke in a fever. The bedclothes were all soaked in sweat.
She said "You've been having a nightmare and it's not over yet"