Final PSX Hacking FAQ - Revision history

Dlevere: /* Section 3 - Code Types */Added image in place of text

2015-04-10T08:16:02Z

Section 3 - Code Types: Added image in place of text

← Older revision		Revision as of 08:16, 10 April 2015
Line 79:		Line 79:
	Most codes will have a structure like this:		Most codes will have a structure like this:

	~~TTXXXXXX YYYY~~		[[File:PSX Hacking FAQ structure.PNG]]
	~~^ ^ ^~~
	~~\| \| \|~~
	~~\| \| Value~~
	~~\| Address~~
	~~Code Type~~

	The "TT" is where the code type is defined, "XXXXXX" is the address that the code does something with, and "YYYY" is where the value the code uses is. Besides a few types, there are some exceptions to this. On an Xploder or Code Breaker, the second "T" is used to tell if a code is default on or off. If the first line in a code has a 0 there, it's a default on code (so, if you select that game, all the codes with a 0 there will be activated). If that's an 8, instead of a 0, the code will be default off. As far as I know, there are no other exceptions, besides some types (that will be explained, in some sort of detail below).		The "TT" is where the code type is defined, "XXXXXX" is the address that the code does something with, and "YYYY" is where the value the code uses is. Besides a few types, there are some exceptions to this. On an Xploder or Code Breaker, the second "T" is used to tell if a code is default on or off. If the first line in a code has a 0 there, it's a default on code (so, if you select that game, all the codes with a 0 there will be activated). If that's an 8, instead of a 0, the code will be default off. As far as I know, there are no other exceptions, besides some types (that will be explained, in some sort of detail below).
Line 91:		Line 86:

	Speaking of hacked versions... Some codes may cause very annoying side effects when used with a hacked cart. Final Fantasy VII is probably the worst about it, as using some codes and saving (even with the codes off) may near permanently corrupt a card.		Speaking of hacked versions... Some codes may cause very annoying side effects when used with a hacked cart. Final Fantasy VII is probably the worst about it, as using some codes and saving (even with the codes off) may near permanently corrupt a card.


	===General Types===		===General Types===

Dlevere: /* Could you just do the FAQ without me asking questions? */

2013-05-14T09:09:13Z

Could you just do the FAQ without me asking questions?

← Older revision		Revision as of 09:09, 14 May 2013
Line 13:		Line 13:
	When you're searching for something, or browsing with the Memory Editor for that matter, the GS displays all addresses as 80 codes, but "80" is not really part of the address; it's just the most commonly used code type. This isn't really vital information to an average hacker, but for those seeking to reach a higher level of skill, it's definitely a bit of knowledge to have.		When you're searching for something, or browsing with the Memory Editor for that matter, the GS displays all addresses as 80 codes, but "80" is not really part of the address; it's just the most commonly used code type. This isn't really vital information to an average hacker, but for those seeking to reach a higher level of skill, it's definitely a bit of knowledge to have.

	[ Actually, the "80" is really part of the address. I'm not really sure why exactly, but the proof is (from [http://www.psxdev.net/forum/download/file.php?id=85~~&sid=a6bb8fe17a29b20d8f6d772fd5454800~~ PlayStation Developer's Guide, v2.5c]) :		[ Actually, the "80" is really part of the address. I'm not really sure why exactly, but the proof is (from [http://www.psxdev.net/forum/download/file.php?id=85 PlayStation Developer's Guide, v2.5c]) :

	Most PlayStation applications will run using the address ranges 0x80000000 to 0x80200000 (2 Mb RAM).		Most PlayStation applications will run using the address ranges 0x80000000 to 0x80200000 (2 Mb RAM).

Dlevere: /* Could you just do the FAQ without me asking questions? */

2013-05-14T09:04:17Z

Could you just do the FAQ without me asking questions?

← Older revision		Revision as of 09:04, 14 May 2013
Line 13:		Line 13:
	When you're searching for something, or browsing with the Memory Editor for that matter, the GS displays all addresses as 80 codes, but "80" is not really part of the address; it's just the most commonly used code type. This isn't really vital information to an average hacker, but for those seeking to reach a higher level of skill, it's definitely a bit of knowledge to have.		When you're searching for something, or browsing with the Memory Editor for that matter, the GS displays all addresses as 80 codes, but "80" is not really part of the address; it's just the most commonly used code type. This isn't really vital information to an average hacker, but for those seeking to reach a higher level of skill, it's definitely a bit of knowledge to have.

	[ Actually, the "80" is really part of the address. I'm not really sure why exactly, but the proof is (from PlayStation Developer's Guide, v2.5c) :		[ Actually, the "80" is really part of the address. I'm not really sure why exactly, but the proof is (from [http://www.psxdev.net/forum/download/file.php?id=85&sid=a6bb8fe17a29b20d8f6d772fd5454800 PlayStation Developer's Guide, v2.5c]) :

	Most PlayStation applications will run using the address ranges 0x80000000 to 0x80200000 (2 Mb RAM).		Most PlayStation applications will run using the address ranges 0x80000000 to 0x80200000 (2 Mb RAM).

	Also, this is probably why all psx "cheat devices" use the 80 type.]		Also, this is probably why all psx "cheat devices" use the 80 type.]


	===An explanation of GS searches===		===An explanation of GS searches===

Ace: Fixed a shit-ton of spelling errors.

2008-12-04T08:49:18Z

Fixed a shit-ton of spelling errors.

LiquidManZero at 07:37, 26 November 2008

2008-11-26T07:37:03Z

← Older revision		Revision as of 07:37, 26 November 2008
Line 80:		Line 80:
	Most codes will have a structure like this:		Most codes will have a structure like this:

	~~[[Image:PSX_Hacking_FAQ_structure.PNG~~\|~~noframe]]~~		TTXXXXXX YYYY
			^ ^ ^
			\| \| \|
			\| \| Value
			\| Address
			Code Type

	The "TT" is where the code type is defined, "XXXXXX" is the address that the code does something with, and "YYYY" is where the value the code uses is. Besides a few types, there are some exceptions to this. On an Xploder or Code Breaker, the second "T" is used to tell if a code is default on or off. If the first line in a code has a 0 there, it's a default on code (so, if you select that game, all the codes with a 0 there will be activated). If that's an 8, instead of a 0, the code will be default off. As far as I know, there are no other exceptions, besides some types (that will be explained, in some sort of detail below).		The "TT" is where the code type is defined, "XXXXXX" is the address that the code does something with, and "YYYY" is where the value the code uses is. Besides a few types, there are some exceptions to this. On an Xploder or Code Breaker, the second "T" is used to tell if a code is default on or off. If the first line in a code has a 0 there, it's a default on code (so, if you select that game, all the codes with a 0 there will be activated). If that's an 8, instead of a 0, the code will be default off. As far as I know, there are no other exceptions, besides some types (that will be explained, in some sort of detail below).

LiquidManZero at 07:34, 26 November 2008

2008-11-26T07:34:53Z

Show changes

MathUser: /* Section 3 - Code Types */

2008-11-23T14:57:07Z

Section 3 - Code Types

← Older revision		Revision as of 14:57, 23 November 2008
Line 74:		Line 74:

	==Section 3 - Code Types==		==Section 3 - Code Types==
	What I intend to do, is explain what code types exist, and if I can, how they work. At the very least, there is a full list of all GameShark (Action Replay, GameBuster, depending on where the device is from) types, and possibly some of the Caetla (most likely, also clones of it) and Xploder (Xplorer, X-Terminator, Code Breaker, depending also on where the thing came from) types as well. If all goes well, this will be less confusing than say... CM's FAQ, or if nothing else, more detailed. s		What I intend to do, is explain what code types exist, and if I can, how they work. At the very least, there is a full list of all GameShark (Action Replay, [[Game Buster\|GameBuster]], depending on where the device is from) types, and possibly some of the Caetla (most likely, also clones of it) and Xploder (Xplorer, X-Terminator, Code Breaker, depending also on where the thing came from) types as well. If all goes well, this will be less confusing than say... CM's FAQ, or if nothing else, more detailed. s

	Something that may be of use to some people, is, that GS and Xploder style carts can use nonexistent RAM addresses. So, you can use just about anything between 80000000 and 807FFFFF, if you want. Though, some addresses above 80200000 will cause problems, most won't, but some will. I have not tested this on a GS v1.x, or a Caetla, as I have neither one. This might not work on whatever you're using, but it's likely that it will.		Something that may be of use to some people, is, that GS and Xploder style carts can use nonexistent RAM addresses. So, you can use just about anything between 80000000 and 807FFFFF, if you want. Though, some addresses above 80200000 will cause problems, most won't, but some will. I have not tested this on a GS v1.x, or a Caetla, as I have neither one. This might not work on whatever you're using, but it's likely that it will.

MathUser: /* Section 3 - Code Types */

2008-11-22T14:03:41Z

Section 3 - Code Types

← Older revision		Revision as of 14:03, 22 November 2008
Line 80:		Line 80:
	Most codes will have a structure like this:		Most codes will have a structure like this:

	~~TTXXXXXX YYYY~~		[[Image:PSX_Hacking_FAQ_structure.PNG\|noframe]]
	~~^ ^ ^~~
	\| ~~\| \|~~
	~~\| \| Value~~
	~~\| Address~~
	~~Code Type~~

	The "TT" is where the code type is defined, "XXXXXX" is the address that the code does something with, and "YYYY" is where the value the code uses is. Besides a few types, there are some exceptions to this. On an Xploder or Code Breaker, the second "T" is used to tell if a code is default on or off. If the first line in a code has a 0 there, it's a default on code (so, if you select that game, all the codes with a 0 there will be activated). If that's an 8, instead of a 0, the code will be default off. As far as I know, there are no other exceptions, besides some types (that will be explained, in some sort of detail below).		The "TT" is where the code type is defined, "XXXXXX" is the address that the code does something with, and "YYYY" is where the value the code uses is. Besides a few types, there are some exceptions to this. On an Xploder or Code Breaker, the second "T" is used to tell if a code is default on or off. If the first line in a code has a 0 there, it's a default on code (so, if you select that game, all the codes with a 0 there will be activated). If that's an 8, instead of a 0, the code will be default off. As far as I know, there are no other exceptions, besides some types (that will be explained, in some sort of detail below).
Line 261:		Line 256:
	Originally, I wasn't going to do this part, but something someone had posted made me realize that this is really needed.		Originally, I wasn't going to do this part, but something someone had posted made me realize that this is really needed.

	80 - Has no effect past it's own line. Works with all other code types, except C1.		80 - Has no effect past it's own line. Works with all other code types, except C1.<br>
	30 - Same as 80.		30 - Same as 80.<br>
	D0 - Effects the line after it, works only with 80, 30, D0, D1, D2, D3, E0, E1, E2, E3, 50, C0, and C2. You can't use a 50 or C1 line after it under any circumstance.		D0 - Effects the line after it, works only with 80, 30, D0, D1, D2, D3, E0, E1, E2, E3, 50, C0, and C2. You can't use a 50 or C1 line after it under any circumstance.<br>
	D1 - Same as D0.		D1 - Same as D0.<br>
	D2 - Same as D0, and D1.		D2 - Same as D0, and D1.<br>
	D3 - Same as D0, D1, and D2.		D3 - Same as D0, D1, and D2.<br>
	D4 - Same as D0, D1, D2, and D3.		D4 - Same as D0, D1, D2, and D3.<br>
	D5 - Other lines above or below it have no effects on it. Functions in any place.		D5 - Other lines above or below it have no effects on it. Functions in any place.<br>
	D6 - Same as D5.		D6 - Same as D5.<br>
	E0 - Same as D0, D1, D2, D3, and D4.		E0 - Same as D0, D1, D2, D3, and D4.<br>
	E1 - Same as E0.		E1 - Same as E0.<br>
	E2 - Same as E0 and E1.		E2 - Same as E0 and E1.<br>
	E3 - Same as E0, E1, and E2.		E3 - Same as E0, E1, and E2.<br>
	50 - Requires an 80, 30, 10, 11, 20, or 21 line after it. Will have no effect if any D, E, or C0 line is above it.		50 - Requires an 80, 30, 10, 11, 20, or 21 line after it. Will have no effect if any D, E, or C0 line is above it.<br>
	10 - Needs a D0, D1, D2, D3, D4, E0, E1, E2, or E3 line above it. Lines below do not affect it.		10 - Needs a D0, D1, D2, D3, D4, E0, E1, E2, or E3 line above it. Lines below do not affect it.<br>
	11 - Same as 10.		11 - Same as 10.<br>
	20 - Same as 10 and 11.		20 - Same as 10 and 11.<br>
	21 - Same as 10, 11, and 20.		21 - Same as 10, 11, and 20.<br>
	C0 - Has no effect if there's not a line below it.		C0 - Has no effect if there's not a line below it.<br>
	C1 - Effects no other lines, can be placed anywhere.		C1 - Effects no other lines, can be placed anywhere.<br>
	C2 - Lines above can affect it. Valid lines above are: 80, 30, D0, D1, D2, D3, E0, E1, E2, E3, and C0. Needs a 80, 30, 10, 11, 20, or 21 line below it.		C2 - Lines above can affect it. Valid lines above are: 80, 30, D0, D1, D2, D3, E0, E1, E2, E3, and C0. Needs a 80, 30, 10, 11, 20, or 21 line below it.


	==Section 4 - Mathematics==		==Section 4 - Mathematics==

MathUser at 13:56, 22 November 2008

2008-11-22T13:56:11Z

← Older revision		Revision as of 13:56, 22 November 2008
Line 1:		Line 1:
	This is the '''Final PSX Hacking FAQ''', as written by [[Lazy Bastard]], [[KingEdgar0\|King Edgar 0]], and [[LiquidManZero\|Liquid Man Zero]]'' Hopefully, this FAQ should rid the scene of most PSX hacking questions, and clear the way for a few more good hackers.		This is the '''Final PSX Hacking FAQ''', as written by [[Lazy Bastard]], [[KingEdgar0\|King Edgar 0]], and [[LiquidManZero\|Liquid Man Zero]] Hopefully, this FAQ should rid the scene of most PSX hacking questions, and clear the way for a few more good hackers.

MathUser at 13:55, 22 November 2008

2008-11-22T13:55:47Z

← Older revision		Revision as of 13:55, 22 November 2008
Line 1:		Line 1:
	This is the '''Final PSX Hacking FAQ''', as written by [[Lazy Bastard]], [[King Edgar 0]], and [[Liquid Man Zero]]'' Hopefully, this FAQ should rid the scene of most PSX hacking questions, and clear the way for a few more good hackers.		This is the '''Final PSX Hacking FAQ''', as written by [[Lazy Bastard]], [[KingEdgar0\|King Edgar 0]], and [[LiquidManZero\|Liquid Man Zero]]'' Hopefully, this FAQ should rid the scene of most PSX hacking questions, and clear the way for a few more good hackers.

← Older revision		Revision as of 08:49, 4 December 2008
Line 50:		Line 50:
	==Section 2 - Ultimate Method==		==Section 2 - Ultimate Method==
	===A brief history of the ultimate method===		===A brief history of the ultimate method===
	Let us take a journey back to the later half of 1999. The PSX Hacking scene was at it's peak. Many different people from many different places were coming together to create original and interesting codes to extend the playability of the games we loved. As the number of hackers increased, so did the number of new people. In order to teach the new people how to hack, many websites and ~~faqs~~ were started to give them information on how to hack various types of codes. This seemed to work for a short time, but a major problem would became apparent ~~shorly~~.		Let us take a journey back to the later half of 1999. The PSX Hacking scene was at it's peak. Many different people from many different places were coming together to create original and interesting codes to extend the playability of the games we loved. As the number of hackers increased, so did the number of new people. In order to teach the new people how to hack, many websites and FAQs were started to give them information on how to hack various types of codes. This seemed to work for a short time, but a major problem would became apparent shortly.


	===Method hackers and abaxialism===		===Method hackers and abaxialism===
	The problem was a simple one to understand. As more people learned to hack using different single methods to hack different types of codes, they shifted away from the old method of hacking. That is, they shifted away from the old center of hacking knowledge, and altered the axis of the hacking world itself. These "Method hackers" were good at what they did, but that was the end of their abilities. To hack a new kind of code they had to be ~~tought~~ the "method" for that particular type of code. This greatly restricted their hacking ability, and in time helped bring about the so called dark ages of console hacking.		The problem was a simple one to understand. As more people learned to hack using different single methods to hack different types of codes, they shifted away from the old method of hacking. That is, they shifted away from the old center of hacking knowledge, and altered the axis of the hacking world itself. These "Method hackers" were good at what they did, but that was the end of their abilities. To hack a new kind of code they had to be taught the "method" for that particular type of code. This greatly restricted their hacking ability, and in time helped bring about the so called dark ages of console hacking.

	===Nachos, egg roll bandits, and the ultimate method===		===Nachos, egg roll bandits, and the ultimate method===
	Now we have entered the very early days of the year 2000. Method hackers run rampant, the golden age of the gameshark.com ubb is drawing to a close, and old style hackers are searching for a way to teach method hackers how to let go of their restraints and hack without methods. The older hackers had been doing it since the beginning of the scene, it seemed natural to them. However it was not so with the newer hackers (with a few ~~exeptions~~). The new hackers needed a method for everything. Without methods they couldn't do anything. It was an understanding of this that made the answer simple. Disguise the lack of methods as a method itself. On January 16th 2000 I took the next logical step and gave the new "method" a name, while adding it to the "Dope RPG hacking faq" that Heh[]Heh and I were working on at the time.		Now we have entered the very early days of the year 2000. Method hackers run rampant, the golden age of the gameshark.com ubb is drawing to a close, and old style hackers are searching for a way to teach method hackers how to let go of their restraints and hack without methods. The older hackers had been doing it since the beginning of the scene, it seemed natural to them. However it was not so with the newer hackers (with a few exceptions). The new hackers needed a method for everything. Without methods they couldn't do anything. It was an understanding of this that made the answer simple. Disguise the lack of methods as a method itself. On January 16th 2000 I took the next logical step and gave the new "method" a name, while adding it to the "Dope RPG hacking faq" that Heh[]Heh and I were working on at the time.

	(That faq was well known for it's lighthearted approach at hacking, using a good deal of the space to talk about the best hacking snacks, and how to "steal" egg rolls from ~~chinese~~ buffets).		(That faq was well known for it's lighthearted approach at hacking, using a good deal of the space to talk about the best hacking snacks, and how to "steal" egg rolls from Chinese buffets).

	===Naming and birth of the ultimate method===		===Naming and birth of the ultimate method===
	There I sat, pondering what name would be proper for a method/non-method of this sort. It would be 2 plates of nachos and 4 IM discussions later before I would arrive at the decision name it the "ultimate method". I used this name for a few reasons. First and foremost, it would attract the attention of method hackers. ~~Afterall~~, how could someone who relies on methods pass up the ultimate method? Secondly, it was quite true. Because the ultimate method is a lack of methods it is nothing.. but the name implies that it is everything. Look at it this way... The ultimate method replaces all other methods, it takes up every ounce of space in the "hacking universe". Therefore there are no other "methods" left to compare it with. Since there is no way to compare or measure this ultimate method, it can be seen as either everything or nothing. Which works out perfectly. Even though ~~thte~~ ultimate method DOES cover everything, it is a complete lack of methods. Everything and nothing at the same time.		There I sat, pondering what name would be proper for a method/non-method of this sort. It would be 2 plates of nachos and 4 IM discussions later before I would arrive at the decision name it the "ultimate method". I used this name for a few reasons. First and foremost, it would attract the attention of method hackers. After all, how could someone who relies on methods pass up the ultimate method? Secondly, it was quite true. Because the ultimate method is a lack of methods it is nothing.. but the name implies that it is everything. Look at it this way... The ultimate method replaces all other methods, it takes up every ounce of space in the "hacking universe". Therefore there are no other "methods" left to compare it with. Since there is no way to compare or measure this ultimate method, it can be seen as either everything or nothing. Which works out perfectly. Even though the ultimate method DOES cover everything, it is a complete lack of methods. Everything and nothing at the same time.

	Now that I look back upon that day I wish I would have had the insight to call it the Zero method. It carries the same implications as the ultimate method (although reversed), and because the last character in my nickname is "0" it is even more interesting.		Now that I look back upon that day I wish I would have had the insight to call it the Zero method. It carries the same implications as the ultimate method (although reversed), and because the last character in my nickname is "0" it is even more interesting.
Line 68:		Line 68:

	===The dark ages and incompleteness===		===The dark ages and incompleteness===
	Now the ultimate method was out in the open. Although many hackers had used it for years, it lacked a name until the first release of the Dope RPG hacking ~~faq~~. ~~Unfortunatly~~ all that the faq included was an introduction to the ultimate method. If a method hacker wanted to walk down the road of the ultimate method, he or she only had a very general sense of where that road was, and no directions when it came to what turns to make. Even to this day the ultimate method hasn't been fully explained. One possible reason is that perhaps it can't really be explained. Everyone learns differently, so is it that strange to assume that the road to the ultimate method is different depending on who you are? ~~Unfortunatly~~ the sand had run from the hourglass, and console hacking was about to enter it's dark ages.		Now the ultimate method was out in the open. Although many hackers had used it for years, it lacked a name until the first release of the Dope RPG hacking FAQ. Unfortunately all that the faq included was an introduction to the ultimate method. If a method hacker wanted to walk down the road of the ultimate method, he or she only had a very general sense of where that road was, and no directions when it came to what turns to make. Even to this day the ultimate method hasn't been fully explained. One possible reason is that perhaps it can't really be explained. Everyone learns differently, so is it that strange to assume that the road to the ultimate method is different depending on who you are? Unfortunately the sand had run from the hourglass, and console hacking was about to enter it's dark ages.

	They came quick, and they hit hard. The gameshark.com ~~ubb~~ was merged with the ~~dexdrive ubb~~ and the resulting mess drove most of the hackers away from gameshark.com for good. Most of those that didn't quit hacking migrated to the ~~gsccc~~. It seemed that the method hacker problem was worse than ever. It was hard to find people that used the ultimate method, most seemed to cling to method hacking because it was easy for them. During this time the mindset of the entire hacking community seemed to change. There were less and less group projects. Interesting codes were becoming a rarity. Many bad things came together to become 1 horrible thing: The dark ages of console hacking. When you compare the dark ages of console hacking to the ~~wonderfull~~ days of late 1999, you can see a drastic decrease in the ~~ammount~~ of interesting non-cheat codes being produced by the community. In the golden days of late 1999 you could see many interesting codes produced in 1 day, and from only one hacker. Sometimes a hacker would hack for 5 hours straight and each hour head over to the ~~ubb~~ to report his or her progress and post codes. Perhaps even seek a little help or turn the work into a group project so even more could be discovered from his or her initial discovery. However in the dark ages of console hacking it was not uncommon to see 2 or 3 weeks go by without an interesting code being made available to the public. With that simple comparison it is easy to see why the thought of the golden days of late 1999 brings up a lot of nostalgia in older hackers.		They came quick, and they hit hard. The gameshark.com UBB was merged with the DexDrive UBB and the resulting mess drove most of the hackers away from gameshark.com for good. Most of those that didn't quit hacking migrated to the GSCCC. It seemed that the method hacker problem was worse than ever. It was hard to find people that used the ultimate method, most seemed to cling to method hacking because it was easy for them. During this time the mindset of the entire hacking community seemed to change. There were less and less group projects. Interesting codes were becoming a rarity. Many bad things came together to become 1 horrible thing: The dark ages of console hacking. When you compare the dark ages of console hacking to the wonderful days of late 1999, you can see a drastic decrease in the amount of interesting non-cheat codes being produced by the community. In the golden days of late 1999 you could see many interesting codes produced in 1 day, and from only one hacker. Sometimes a hacker would hack for 5 hours straight and each hour head over to the UBB to report his or her progress and post codes. Perhaps even seek a little help or turn the work into a group project so even more could be discovered from his or her initial discovery. However in the dark ages of console hacking it was not uncommon to see 2 or 3 weeks go by without an interesting code being made available to the public. With that simple comparison it is easy to see why the thought of the golden days of late 1999 brings up a lot of nostalgia in older hackers.


Line 91:		Line 91:
	Something you should know, is that not all codes work. Some codes that should work (i.e, they are in a valid memory area, and are overall correct codes that have no reason to not work) just won't. This is most common on a GS Pro (v3.0 to v3.2), especially hacked versions of the cart.		Something you should know, is that not all codes work. Some codes that should work (i.e, they are in a valid memory area, and are overall correct codes that have no reason to not work) just won't. This is most common on a GS Pro (v3.0 to v3.2), especially hacked versions of the cart.

	Speaking of hacked versions... Some codes may cause very annoying side effects when used with a hacked cart. Final Fantasy VII is probably the worst about it, as using some codes and saving (even with the codes off) may near ~~permently~~ corrupt a card.		Speaking of hacked versions... Some codes may cause very annoying side effects when used with a hacked cart. Final Fantasy VII is probably the worst about it, as using some codes and saving (even with the codes off) may near permanently corrupt a card.


Line 238:		Line 238:

	'''C1:'''		'''C1:'''
	C1. Delays turning on all codes ~~untill~~ a certain amount of "time" has passed. The exact length of time this may be depends on the digits entered and the game being loaded. 1000 (hex) could be anything from 2 seconds to an entire minute... [I have a feeling it's based on something stupid, such as frames, or something. But now I'm thinking it's got something to do with the setting of VSync (this being always set to either 0, 1, 2, 3, or 4). VSync if I'm remembering right, is how the ~~psx~~ keeps the frame rate locked (or tries to at least).]		C1. Delays turning on all codes until a certain amount of "time" has passed. The exact length of time this may be depends on the digits entered and the game being loaded. 1000 (hex) could be anything from 2 seconds to an entire minute... [I have a feeling it's based on something stupid, such as frames, or something. But now I'm thinking it's got something to do with the setting of VSync (this being always set to either 0, 1, 2, 3, or 4). VSync if I'm remembering right, is how the PSX keeps the frame rate locked (or tries to at least).]

	An example:		An example:
Line 244:		Line 244:
	C1000000 1000		C1000000 1000

	This would leave all codes off ~~untill~~ "1000" something has passed. This could be anything from a few seconds to quite a number of minutes. This would probably be long enough for most games to load if they have problems with codes.		This would leave all codes off until "1000" something has passed. This could be anything from a few seconds to quite a number of minutes. This would probably be long enough for most games to load if they have problems with codes.

	'''C2:'''		'''C2:'''