Portal:Syringe - Revision history

MarkJFox: 2 revisions imported

2025-03-31T20:00:54Z

2 revisions imported

← Older revision	Revision as of 22:00, 31 March 2025
(No difference)

en>Marshall: added note on Launch Base

2008-07-12T21:01:19Z

added note on Launch Base

← Older revision		Revision as of 23:01, 12 July 2008
Line 22:		Line 22:

	DCoder is also using ''Syringe'' for a modification for a different game (''Urban Chaos''), but it is not yet intended for public use.		DCoder is also using ''Syringe'' for a modification for a different game (''Urban Chaos''), but it is not yet intended for public use.

	\|-		\|-
	\| <h3 style="text-align: center;">Developer Information </h3>		\| <h3 style="text-align: center;">Developer Information </h3>
Line 40:		Line 41:
	<h4 style="text-align: center;">How ''does'' it work, really?</h4>		<h4 style="text-align: center;">How ''does'' it work, really?</h4>
	''Syringe'' uses a variant of the infamous ''DLL Injection'' technique - a small chunk of ASM code is inserted at executable startup, forcing the executable to search for and load suitable DLLs into its context. An ''injection control file'' dictates the functions to call at certain addresses, Syringe overwrites code at those addresses with 0xCC ({{Tt\|int 3}}), and those interrupts are trapped using Debug API and the executable is redirected to invoke said functions.		''Syringe'' uses a variant of the infamous ''DLL Injection'' technique - a small chunk of ASM code is inserted at executable startup, forcing the executable to search for and load suitable DLLs into its context. An ''injection control file'' dictates the functions to call at certain addresses, Syringe overwrites code at those addresses with 0xCC ({{Tt\|int 3}}), and those interrupts are trapped using Debug API and the executable is redirected to invoke said functions.

			<h4 style="text-align: center;">Does it work with Launch Base?</h4>
			Yes. [[LaunchBase\|Launch Base]] includes the latest version of Syringe and automatically knows when to execute it - your mod just needs to include any DLL files it requires in it's own "syringe" directory.

	\|}		\|}

en>DCoder: Creating, TODO: needs to be stylificated or something

2008-07-11T19:18:52Z

Creating, TODO: needs to be stylificated or something

New page

__NOTOC__

{| width="100%" class="table_parted"
| width="80%" style="text-align: center;" |
<h2>Syringe</h2>
<h3>'''Witty subtitle here'''</h3>
| rowspan="3" | {{ToolBar|name=Syringe|width=20%|dev=pd|version=0.1? (taken down, update in progress)|site=http://rp2.strategy-x.com}}
|-
| <h3 style="text-align: center;">End User Information</h3>
<h4 style="text-align: center;">What is Syringe?</h4>
'''Syringe''' is an application developed by ''pd'' primarily to simplify modification of {{yr}}. It can inject code into any other executable as well, so it is a general-purpose code injector tool.

<h4 style="text-align: center;">How does it work?</h4>
In simple terms, a patch developer creates a small DLL file and an "injection control file". When ''Syringe'' is run, it loads all recognized DLLs into the target program, and instructs the program to call certain functions from the DLL file under certain circumstances.

<h4 style="text-align: center;">How does this benefit the end user, compared to the old RockPatch patching method?</h4>
;No patching required:The end user no longer needs to apply patches to the executable. Instead, when he/she wants to use the added functionality, they simply need to run ''Syringe'' instead of the target executable. Running the executable itself will run the application without any modifications.
;Third-party contributions:''Syringe'' makes proper third-party patches possible, since multiple DLLs can be loaded and perform different tasks, whereas RockPatch was incompatible with any third-party changes.

<h4 style="text-align: center;">Are there any released patches which use ''Syringe''?</h4>
So far, the only publicly released project using ''Syringe'' is a [http://forums.renegadeprojects.com/showthread.php?tid=987 demonstration] of ''pd'''s new project '''[[Portal:Ares|Ares]]''', also known as '''RockPatch 2'''.

DCoder is also using ''Syringe'' for a modification for a different game (''Urban Chaos''), but it is not yet intended for public use.
|-
| <h3 style="text-align: center;">Developer Information </h3>
<h4 style="text-align: center;">What skills do I need to use ''Syringe''?</h4>
DLLs are written using C++, but naturally the executable you are targeting needs to be reverse-engineered for any meaningful changes.

For example, if you have reverse engineered a game and could possibly write some patches for it in assembler, you will be able to do the same in Syringe with no difficulty. If you don't know reverse-engineering, don't panic just yet - if the [[Syringe wrappers]] have been written for that executable, you can use them and write normal C++ code with some guidance from the reverse-engineers. For more info, check the [[Getting Started with Syringe]] page.

<h4 style="text-align: center;">I want to contribute something to the ''[[Portal:Ares|Ares]]/RockPatch 2'' project</h4>
Please see the [[Portal:Ares|Ares project page]].

<h4 style="text-align: center;">I want to create another DLL for YR</h4>
Please see the [[Writing A DLL for Syringe]] page.

<h4 style="text-align: center;">I want to create DLLs for a different application</h4>
Please see the [[Injecting Syringe DLLs Into An Application]] page.

<h4 style="text-align: center;">How ''does'' it work, really?</h4>
''Syringe'' uses a variant of the infamous ''DLL Injection'' technique - a small chunk of ASM code is inserted at executable startup, forcing the executable to search for and load suitable DLLs into its context. An ''injection control file'' dictates the functions to call at certain addresses, Syringe overwrites code at those addresses with 0xCC ({{Tt|int 3}}), and those interrupts are trapped using Debug API and the executable is redirected to invoke said functions.

|}