Max Azoury CoolOppo

[Source][1]

Pointers

In earlier chapters, variables have been explained as locations in the computer's memory which can be accessed by their identifier (their name). This way, the program does not need to care about the physical address of the data in memory; it simply uses the identifier whenever it needs to refer to the variable. For a C++ program, the memory of a computer is like a succession of memory cells, each one byte in size, and each with a unique address. These single-byte memory cells are ordered in a way that allows data representations larger than one byte to occupy memory cells that have consecutive addresses. This way, each cell can be easily located in the memory by means of its unique address. For example, the memory cell with the address 1776 always follows immediately after the cell with address 1775 and precedes the one with 1777, and is exactly one thousand cells after 776 and exactly one thousand cells before 2776. When a variable is declared, the memory needed

Source

Linker Enhancements in Visual Studio 2013 Update 2

For developer scenarios, linking takes the lion's share of the application's build time. From our investigation we know that the Visual C++ linker spends a large fraction of its time in preparing, merging and finally writing out debug information. This is especially true for non-Whole Program Optimization scenarios.

In Visual Studio 2013 Update 2 CTP2, a set of features were added which help improve link time significantly as measured by products we build here in our labs (AAA Games and Open source projects such as Chromium):

Remove unreferenced data and functions (/Zc:inline). This can help all of your projects.
Reduce time spent generating PDB files. This applies mostly to binaries with medium to large amounts of debug information.
Parallelize code-generation and optimization build phase (*

Use (setsid yourcommand &), it detaches from the tty and works equally in interactive and script modes.

( spawns a subshell, which handles job control differently.

Or use nohup yourcommand > /dev/null 2>&1 &


	Step one � find address in cheat engine
	step two � find what rights to that address
	step three � go on olly search for address the writes that
	Step 3.5 � by setting hardware breakpoints find where
	the beginning and end of the code is regarding the function you were looking for
	e.g. firing gun, this way we know where to stop searching
	step four � reverse through all the jumps jmp e.g. JNZ becomes JE
	step five � write comments and test a command at a time
	step six �if the game crashes then simply return to that address leaving a comment

	echo type now
	set /p test=
	echo %test%