ViperX

Stop posting before you at least try solving your problems -.-

BitmapClass::BitmapCount

Putting it in the class would be cleaner. Just do 'static short BitmapCount;'

BitmapCount++; Where the fuck is BitmapCount declared?

You're setting dword to the size of a pointer. A pointer on a 32 bit architecture is ALWAYS 4 bytes. So no matter what, you're setting dword to 4.

Well, look at the idea as communism. It's a great idea, but it doesn't just work that way.

Yes. You really think noone else thought about that before? I'm pretty sure someone did. And it doesn't just work like that.

org 100h mean's that the offset of the program in memory is 100h. A .com program is loaded into one sector of memory (512kb). The instruction org 100h, simply tells the assembler that it has to add 100h to all addresses.

Hahahahahahaha get us the video fast please :P

Because in the batch you're deleting batchname.bat, while you're creating the batch with the name winuser.bat.

Sorry for a little late answer, but yes it's real mode code. You can't use BIOS interrupts in pmode (PE's). So you have to assemble that code to 16-bit (.com).

Every processor family has it's own assembly. MCS-51, DSP56000, x86, z80 are just a few. Good luck on writing an assembler, I promise you, you won't be done the next year. I have a little parser written in assembly (it's able to parse itself ;) and it's 1000 lines. The thing that actually assembles is 2000 lines long. And then we have a little 64 bit assembler (the thing that assembles alone, again), it's 8000 lines of assembly.

Assembly is used mostly for operating systems. But it can be used for anything.

Well.. if you use filenames over like 5 characters, yes :P

The only way i can think of real quick is bruteforcing through all filenames. I know how to do it in assembly (.com file only, since it requires interrupts).

Get FASM or GAS. Recommended books: All the x86 books from Intel.

In assembly it is: invoke mciSendString,_cmd_open,0,0,0 invoke mciSendString,_cmd_eject,0,0,0 invoke mciSendString,_cmd_close,0,0,0 So I guess in C, it would be something like: mciSendString(cmd_open, 0, 0, 0); mciSendString(cmd_eject, 0, 0, 0); mciSendString(cmd_close, 0, 0, 0);

Omg yes.

Ban azn plz.

1) Dev-C++ is not a compiler, just a GUI. 2) Don't use malloc, use new and delete (In case of using C++, and NOT C that is). 3) The way to assign a void* to char* goes like this (This is a copy/paste of a memcpy, me and some other guys have made for an OS project): void* memcpy(void* dest, const void* src, size_t count) { void* ret = dest; unsigned char* csrc = (unsigned char*)src; unsigned char* cdest = (unsigned char*)dest; while (count--) { *cdest++ = *csrc++; } return cdest; } Note: This code is C, and I have not tried compiling it in C++.

You have no idea how easy it actually is to become one....

Registry changes are just read at startup (except for program registry settings that gets read at, you guessed it, program startup).

Injection won't show the code inside the DLL....

No.

Yes, that's why it's called 'signed' and 'unsigned'. Since a whole bit is used to show if it's negative or not, the size available for numbers will be one bit less, which is quite a lot. For example, an 'unsigned short' can store between 0 and 2^16 (65536) because a short is 16 bits. A 'signed short' tho, can store between -(2^16/2) and 2^16/2. There ARE actually uses for 'signed char', but in this case there is no need for them. Char's default to unsigned, and they are one byte (8 bits) in size, which gives them a max value of 255 (unsigned).