News/A Spooky New Years - Revision history

Okeijidragon: Hope this wasn't presumptuous of me for editing a major HP article. When I found this page, it was hard to read paragraphs that were stretched across in a UW monitor. Not fun, so I added reasonable width length.

2025-01-04T08:26:02Z

Hope this wasn't presumptuous of me for editing a major HP article. When I found this page, it was hard to read paragraphs that were stretched across in a UW monitor. Not fun, so I added reasonable width length.

← Older revision		Revision as of 08:26, January 4, 2025
Line 4:		Line 4:
	medievil logo.png		medievil logo.png
	</gallery>		</gallery>

	[[MediEvil (Jun 22, 1998 prototype)]]<br>		[[MediEvil (Jun 22, 1998 prototype)]]<br>
	[[MediEvil (Jul 9, 1998 prototype)]]<br>		[[MediEvil (Jul 9, 1998 prototype)]]<br>
Line 11:		Line 10:
	[http://hiddenpalace.org/forums/viewtopic.php?f=22&t=3323 {{icon\|comments}} Discuss this release on the boards here!]<br>		[http://hiddenpalace.org/forums/viewtopic.php?f=22&t=3323 {{icon\|comments}} Discuss this release on the boards here!]<br>

	Happy New Years everyone!<br>		Happy New Years everyone!<br></center>
			<div style="max-width: 700px; margin: auto; font-size: 16px;">
	This year saw a lot of nice releases from all corners of the internet. From early prototypes of Pokemon Gold & Silver to unreleased games such as SegaSonic Bros and SimCity for the NES, it looks like 2018 was one of the best years for prototypes in a while! What will 2019 bring? ~~<br>~~		This year saw a lot of nice releases from all corners of the internet. From early prototypes of ''Pokemon Gold & Silver'' to unreleased games such as ''SegaSonic Bros'' and ''SimCity'' for the NES, it looks like 2018 was one of the best years for prototypes in a while! What will 2019 bring? <br>

	To start off the new year with something great, we decided to release four prototypes from the MediEvil series! Be sure to check out the articles for each prototype, as the articles will describe how to properly play them.<br>

			To start off the new year with something great, we decided to release four prototypes from the ''MediEvil'' series! Be sure to check out the articles for each prototype, as the articles will describe how to properly play them.<br>
			<center>
	{\| style="text-align: center"		{\| style="text-align: center"
	\|-		\|-
Line 23:		Line 22:
	\| [[MediEvil (Jun 22, 1998 prototype)\|MediEvil .31 prototype]] \|\| [[MediEvil (Jul 9, 1998 prototype)\|MediEvil .35 prototype]]		\| [[MediEvil (Jun 22, 1998 prototype)\|MediEvil .31 prototype]] \|\| [[MediEvil (Jul 9, 1998 prototype)\|MediEvil .35 prototype]]
	\|}		\|}
			</center>
	First up, we have two prototypes of the first MediEvil - one meant for review and another for preview. These prototypes are dated several months before the first retail release of the game. While the two prototypes are dated a few weeks apart, they both contain a considerable amount of differences. Unfinished levels, a programmers test level, different layouts, different textures, and more! <br>		<div style="max-width: 700px; margin: auto; font-size: 16px;">
			First up, we have two prototypes of the first ''MediEvil'' - one meant for review and another for preview. These prototypes are dated several months before the first retail release of the game. While the two prototypes are dated a few weeks apart, they both contain a considerable amount of differences. Unfinished levels, a programmers test level, different layouts, different textures, and more! <br>
			<center>
	{\| style="text-align: center"		{\| style="text-align: center"
	\|-		\|-
Line 32:		Line 32:
	\| [[MediEvil II (Dec 20, 1999 prototype)\|MediEvil II .19 prototype]] \|\| [[MediEvil II (Feb 29, 2000 prototype)\|MediEvil II .51 prototype]]		\| [[MediEvil II (Dec 20, 1999 prototype)\|MediEvil II .19 prototype]] \|\| [[MediEvil II (Feb 29, 2000 prototype)\|MediEvil II .51 prototype]]
	\|}		\|}
			</center>
			<div style="max-width: 700px; margin: auto; font-size: 16px;">
			Next, we have two prototypes of ''MediEvil II'' as well! Again, one “preview” prototype and one “review” prototype. The differences between the final version and the earliest prototype are extreme. For instance, most of the FMV sequences in the December prototype are unfinished (only a rough “layout” was rendered for most scenes). Many stages that would be used in the final version are different here in various ways. The prototype contains a level that was cut from the game called “Parliament” which is playable from the cheats menu. The earliest prototype also includes a few test levels as well, much like the first game. <br>

			<center>

	Next, we have two prototypes of MediEvil II as well! Again, one “preview” prototype and one “review” prototype. The differences between the final version and the earliest prototype are extreme. For instance, most of the FMV sequences in the December prototype are unfinished (only a rough “layout” was rendered for most scenes). Many stages that would be used in the final version are different here in various ways. The prototype contains a level that was cut from the game called “Parliament” which is playable from the cheats menu. The earliest prototype also includes a few test levels as well, much like the first game. <br>

	<gallery mode=nolines>		<gallery mode=nolines>
	medievildiscerror.png		medievildiscerror.png
	</gallery>		</gallery>

			<div style="max-width: 700px; margin: auto; font-size: 16px;">
	However, not everything went smoothly this time. <br>		However, not everything went smoothly this time. <br>
	</center>		</center>
			<div style="max-width: 700px; margin: auto; font-size: 16px;">
	Issues occurred when attempting to backup these prototypes which made us question the integrity of the dumps we created. Besides the typical bad dump that can be remedied through trial and error on different burners with different read speeds, we were constantly presented with an issue where each game would just stop functioning after a certain point (usually during a level change). With no PS1 developer hardware to test with, we were unsure if the games were physically at fault for causing these issues, or if it was a sign of some form of copy protection. <br>		Issues occurred when attempting to backup these prototypes which made us question the integrity of the dumps we created. Besides the typical bad dump that can be remedied through trial and error on different burners with different read speeds, we were constantly presented with an issue where each game would just stop functioning after a certain point (usually during a level change). With no PS1 developer hardware to test with, we were unsure if the games were physically at fault for causing these issues, or if it was a sign of some form of copy protection. <br>

Line 51:		Line 53:
	After we were sure that the data track (the .img) was being dumped consistently, we decided to debug the games with no$psx to figure out what was going on. To make a long story short, both of the MediEvil prototypes actually use a form of SCEx copy protection where the check is done at the software level rather than just at the BIOS level. This copy protection involves comparing the letters “SCEx” (where “x” is the region of the game or console) with what’s stored on the disc against what’s stored in the BIOS. This check occurs when loading into a new level or quitting the game. <br>		After we were sure that the data track (the .img) was being dumped consistently, we decided to debug the games with no$psx to figure out what was going on. To make a long story short, both of the MediEvil prototypes actually use a form of SCEx copy protection where the check is done at the software level rather than just at the BIOS level. This copy protection involves comparing the letters “SCEx” (where “x” is the region of the game or console) with what’s stored on the disc against what’s stored in the BIOS. This check occurs when loading into a new level or quitting the game. <br>

	MediEvil II on the other hand doesn’t seem to be using libcrypt. The February prototype seems to work fine and doesn’t seem to check between level changes. The December prototype seems to hang when loading levels even from the cheat menu. However, the prototype seems to work fine in PCSX while any other emulator hangs.<br>		MediEvil II, on the other hand, doesn’t seem to be using libcrypt. The February prototype seems to work fine and doesn’t seem to check between level changes. The December prototype seems to hang when loading levels even from the cheat menu. However, the prototype seems to work fine in PCSX while any other emulator hangs.<br>

	However, even with the correct conditions the game would still refuse to load into another level. Luckily, by disassembling the games, we found that each prototype can be unlocked to work as normal by inputting an “unlock” or “cheat” code combination while the game is paused, which you can see for yourself by checking out the articles for each prototype. While we still aren’t confident that we fully understand what’s going on, it’s possible that the developers intentionally “sabotaged” their builds of the game by disallowing anyone from playing the game on anything besides a developer console, which has the ability to mimic specific regions. It’s also possible that the copy protection is set to always hang to prevent people other than the intended parties from accessing the rest of the game’s contents without knowing how to activate the in game cheats.<br>		However, even with the correct conditions the game would still refuse to load into another level. Luckily, by disassembling the games, we found that each prototype can be unlocked to work as normal by inputting an “unlock” or “cheat” code combination while the game is paused, which you can see for yourself by checking out the articles for each prototype. While we still aren’t confident that we fully understand what’s going on, it’s possible that the developers intentionally “sabotaged” their builds of the game by disallowing anyone from playing the game on anything besides a developer console, which has the ability to mimic specific regions. It’s also possible that the copy protection is set to always hang to prevent people other than the intended parties from accessing the rest of the game’s contents without knowing how to activate the in game cheats.<br>

	Up until this point, we have dumped all CD/DVD based prototypes so far with CloneCD using both a Lite-On LH-20A1L and a HLDS GSA-U10N, drives that have historically low error rates. These particular dumps were created shortly before [[drx]] had to move overseas. The move has been a temporary set back since most of the stuff we intend to release is still in progress. The subchannel data will have to be redumped using different methods in order to ensure that the problems we were seeing aren’t caused by the dumps themselves. We consider the dumps okay for release, but we intend to redump everything in the future with a different standard so that we can ensure the best possible dumps. There is some promising software being developed, such as DiscImageCreator by the [http://redump.org.org Redump] project.<br>		Up until this point, we have dumped all CD/DVD based prototypes so far with CloneCD using both a Lite-On LH-20A1L and a HLDS GSA-U10N, drives that have historically low error rates. These particular dumps were created shortly before [[drx]] had to move overseas. The move has been a temporary set back since most of the stuff we intend to release is still in progress. The subchannel data will have to be redumped using different methods in order to ensure that the problems we were seeing aren’t caused by the dumps themselves. We consider the dumps okay for release, but we intend to redump everything in the future with a different standard so that we can ensure the best possible dumps. There is some promising software being developed, such as DiscImageCreator by the [http://redump.org.org Redump] project.<br>
			<div style="max-width: 700px; margin: auto; font-size: 16px;">

	~~<center>~~
	With that being said, we hope you enjoy this release and look forward to sharing more with you in the upcoming months.<br>		With that being said, we hope you enjoy this release and look forward to sharing more with you in the upcoming months.<br>

	Until next time! <br>		<center>Until next time! <br>
	<gallery mode=nolines>		<gallery mode=nolines>
	teaser2019_1.png		teaser2019_1.png
	</gallery>		</gallery>
	</center>		</center>

Hidden Palace at 02:20, January 2, 2019

2019-01-02T02:20:52Z

← Older revision		Revision as of 02:20, January 2, 2019
Line 9:		Line 9:
	[[MediEvil II (Dec 20, 1999 prototype)]]<br>		[[MediEvil II (Dec 20, 1999 prototype)]]<br>
	[[MediEvil II (Feb 29, 2000 prototype)]]<br>		[[MediEvil II (Feb 29, 2000 prototype)]]<br>
	[http://hiddenpalace.org/forums/viewtopic.php?f=22&t=~~3322~~ {{icon\|comments}} Discuss this release on the boards here!]<br>		[http://hiddenpalace.org/forums/viewtopic.php?f=22&t=3323 {{icon\|comments}} Discuss this release on the boards here!]<br>

	Happy New Years everyone!<br>		Happy New Years everyone!<br>

Hidden Palace at 01:57, January 2, 2019

2019-01-02T01:57:58Z

← Older revision		Revision as of 01:57, January 2, 2019
Line 62:		Line 62:
	Until next time! <br>		Until next time! <br>
	<gallery mode=nolines>		<gallery mode=nolines>
	~~teaser2019~~.~~jpg~~		teaser2019_1.png
	</gallery>		</gallery>
	</center>		</center>

Drx at 01:52, January 2, 2019

2019-01-02T01:52:35Z

← Older revision		Revision as of 01:52, January 2, 2019
Line 21:		Line 21:
	\| [[File:me 31 proto 1.png\|centre\|frameless\|link=MediEvil (Jun 22, 1998 prototype)]] \|\| [[File:me 35 proto 1.png\|centre\|frameless\|link=MediEvil (Jul 9, 1998 prototype)]]		\| [[File:me 31 proto 1.png\|centre\|frameless\|link=MediEvil (Jun 22, 1998 prototype)]] \|\| [[File:me 35 proto 1.png\|centre\|frameless\|link=MediEvil (Jul 9, 1998 prototype)]]
	\|-		\|-
	\| MediEvil .31 prototype \|\| MediEvil .35 prototype		\| [[MediEvil (Jun 22, 1998 prototype)\|MediEvil .31 prototype]] \|\| [[MediEvil (Jul 9, 1998 prototype)\|MediEvil .35 prototype]]
	\|}		\|}

Line 30:		Line 30:
	\| [[File:me2 19 proto 1.png\|centre\|frameless\|link=MediEvil II (Dec 20, 1999 prototype)]] \|\| [[File:me2 51 proto 1.png\|centre\|frameless\|link=MediEvil II (Feb 29, 2000 prototype)]]		\| [[File:me2 19 proto 1.png\|centre\|frameless\|link=MediEvil II (Dec 20, 1999 prototype)]] \|\| [[File:me2 51 proto 1.png\|centre\|frameless\|link=MediEvil II (Feb 29, 2000 prototype)]]
	\|-		\|-
	\| MediEvil II .19 prototype \|\| MediEvil II .51 prototype		\| [[MediEvil II (Dec 20, 1999 prototype)\|MediEvil II .19 prototype]] \|\| [[MediEvil II (Feb 29, 2000 prototype)\|MediEvil II .51 prototype]]
	\|}		\|}

Drx at 01:49, January 2, 2019

2019-01-02T01:49:35Z

← Older revision		Revision as of 01:49, January 2, 2019
Line 45:		Line 45:
	Issues occurred when attempting to backup these prototypes which made us question the integrity of the dumps we created. Besides the typical bad dump that can be remedied through trial and error on different burners with different read speeds, we were constantly presented with an issue where each game would just stop functioning after a certain point (usually during a level change). With no PS1 developer hardware to test with, we were unsure if the games were physically at fault for causing these issues, or if it was a sign of some form of copy protection. <br>		Issues occurred when attempting to backup these prototypes which made us question the integrity of the dumps we created. Besides the typical bad dump that can be remedied through trial and error on different burners with different read speeds, we were constantly presented with an issue where each game would just stop functioning after a certain point (usually during a level change). With no PS1 developer hardware to test with, we were unsure if the games were physically at fault for causing these issues, or if it was a sign of some form of copy protection. <br>

	MediEvil marked one of the earliest attempts to thwart pirates with the copy protection method known as “libcrypt”. With this method, unique non-Yellow Book data is stored in subchannels on the disc itself. Games with libcrypt issue special, undocumented firmware commands to perform reads from the subchannel data, and check if it contains the unique data. This was a relatively effective copy protection mechanism for its time, since most pirate releases (even today) do not include the subchannel data (which is not contained in a typical bin/cue).<br>		MediEvil marked one of the earliest attempts to thwart pirates with the copy protection method known as “libcrypt”. With this method, unique non-Yellow Book data is stored in subchannels on the disc itself. Games with libcrypt issue special, undocumented firmware commands to perform reads from the subchannel data, and check if it contains the unique data. This was a relatively effective copy protection mechanism for its time, since most pirate releases (even today) do not include the subchannel data, which is not contained in a typical "bin/cue" dump.<br>

	It’s also difficult to perfectly extract subchannel data with common CD/DVD readers. Unlike data channels, which use extensive error correction algorithms, most of the subchannels are not error corrected, resulting in pretty much every dump being different (without error correction, reading raw data on CDs with a laser is very error prone!). Most burners also have a difficult time burning subchannel data back to CD-Rs as well. As an effect, at the time, the only way to bypass this copy protection was to debug the game and physically alter the game’s code through a patch to avoid these checks. <br>		It’s also difficult to perfectly extract subchannel data with common CD/DVD readers. Unlike data channels, which use extensive error correction algorithms, most of the subchannels are not error corrected, resulting in pretty much every dump being different (without error correction, reading raw data on CDs with a laser is very error prone!). Most burners also have a difficult time burning subchannel data back to CD-Rs as well. As an effect, at the time, the only way to bypass this copy protection was to debug the game and physically alter the game’s code through a patch to avoid these checks. <br>

Drx at 01:47, January 2, 2019

2019-01-02T01:47:33Z

← Older revision		Revision as of 01:47, January 2, 2019
Line 57:		Line 57:
	Up until this point, we have dumped all CD/DVD based prototypes so far with CloneCD using both a Lite-On LH-20A1L and a HLDS GSA-U10N, drives that have historically low error rates. These particular dumps were created shortly before [[drx]] had to move overseas. The move has been a temporary set back since most of the stuff we intend to release is still in progress. The subchannel data will have to be redumped using different methods in order to ensure that the problems we were seeing aren’t caused by the dumps themselves. We consider the dumps okay for release, but we intend to redump everything in the future with a different standard so that we can ensure the best possible dumps. There is some promising software being developed, such as DiscImageCreator by the [http://redump.org.org Redump] project.<br>		Up until this point, we have dumped all CD/DVD based prototypes so far with CloneCD using both a Lite-On LH-20A1L and a HLDS GSA-U10N, drives that have historically low error rates. These particular dumps were created shortly before [[drx]] had to move overseas. The move has been a temporary set back since most of the stuff we intend to release is still in progress. The subchannel data will have to be redumped using different methods in order to ensure that the problems we were seeing aren’t caused by the dumps themselves. We consider the dumps okay for release, but we intend to redump everything in the future with a different standard so that we can ensure the best possible dumps. There is some promising software being developed, such as DiscImageCreator by the [http://redump.org.org Redump] project.<br>

			<center>
	With that being said, we hope you enjoy this release and look forward to sharing more with you in the upcoming months.<br>		With that being said, we hope you enjoy this release and look forward to sharing more with you in the upcoming months.<br>

Line 63:		Line 64:
	teaser2019.jpg		teaser2019.jpg
	</gallery>		</gallery>
			</center>

Drx at 01:47, January 2, 2019

2019-01-02T01:47:13Z

← Older revision		Revision as of 01:47, January 2, 2019
Line 41:		Line 41:
	</gallery>		</gallery>
	However, not everything went smoothly this time. <br>		However, not everything went smoothly this time. <br>
			</center>

	Issues occurred when attempting to backup these prototypes which made us question the integrity of the dumps we created. Besides the typical bad dump that can be remedied through trial and error on different burners with different read speeds, we were constantly presented with an issue where each game would just stop functioning after a certain point (usually during a level change). With no PS1 developer hardware to test with, we were unsure if the games were physically at fault for causing these issues, or if it was a sign of some form of copy protection. <br>		Issues occurred when attempting to backup these prototypes which made us question the integrity of the dumps we created. Besides the typical bad dump that can be remedied through trial and error on different burners with different read speeds, we were constantly presented with an issue where each game would just stop functioning after a certain point (usually during a level change). With no PS1 developer hardware to test with, we were unsure if the games were physically at fault for causing these issues, or if it was a sign of some form of copy protection. <br>
Line 62:		Line 63:
	teaser2019.jpg		teaser2019.jpg
	</gallery>		</gallery>
	~~</center>~~

Drx at 01:45, January 2, 2019

2019-01-02T01:45:30Z

← Older revision		Revision as of 01:45, January 2, 2019
Line 17:		Line 17:
	To start off the new year with something great, we decided to release four prototypes from the MediEvil series! Be sure to check out the articles for each prototype, as the articles will describe how to properly play them.<br>		To start off the new year with something great, we decided to release four prototypes from the MediEvil series! Be sure to check out the articles for each prototype, as the articles will describe how to properly play them.<br>

	[[File:me 31 proto 1.png\|centre\|frameless\|link=MediEvil (Jun 22, 1998 prototype)]]		{\| style="text-align: center"
	[[File:me 35 proto 1.png\|centre\|frameless\|link=MediEvil (Jul 9, 1998 prototype)]]		\|-
			\| [[File:me 31 proto 1.png\|centre\|frameless\|link=MediEvil (Jun 22, 1998 prototype)]] \|\| [[File:me 35 proto 1.png\|centre\|frameless\|link=MediEvil (Jul 9, 1998 prototype)]]
			\|-
			\| MediEvil .31 prototype \|\| MediEvil .35 prototype
			\|}

	First up, we have two prototypes of the first MediEvil - one meant for review and another for preview. These prototypes are dated several months before the first retail release of the game. While the two prototypes are dated a few weeks apart, they both contain a considerable amount of differences. Unfinished levels, a programmers test level, different layouts, different textures, and more! <br>		First up, we have two prototypes of the first MediEvil - one meant for review and another for preview. These prototypes are dated several months before the first retail release of the game. While the two prototypes are dated a few weeks apart, they both contain a considerable amount of differences. Unfinished levels, a programmers test level, different layouts, different textures, and more! <br>

	[[File:me2 19 proto 1.png\|centre\|frameless\|link=MediEvil II (Dec 20, 1999 prototype)]]		{\| style="text-align: center"
	[[File:me2 51 proto 1.png\|centre\|frameless\|link=MediEvil II (Feb 29, 2000 prototype)]]		\|-
			\| [[File:me2 19 proto 1.png\|centre\|frameless\|link=MediEvil II (Dec 20, 1999 prototype)]] \|\| [[File:me2 51 proto 1.png\|centre\|frameless\|link=MediEvil II (Feb 29, 2000 prototype)]]
			\|-
			\| MediEvil II .19 prototype \|\| MediEvil II .51 prototype
			\|}



	Next, we have two prototypes of MediEvil II as well! Again, one “preview” prototype and one “review” prototype. The differences between the final version and the earliest prototype are extreme. For instance, most of the FMV sequences in the December prototype are unfinished (only a rough “layout” was rendered for most scenes). Many stages that would be used in the final version are different here in various ways. The prototype contains a level that was cut from the game called “Parliament” which is playable from the cheats menu. The earliest prototype also includes a few test levels as well, much like the first game. <br>		Next, we have two prototypes of MediEvil II as well! Again, one “preview” prototype and one “review” prototype. The differences between the final version and the earliest prototype are extreme. For instance, most of the FMV sequences in the December prototype are unfinished (only a rough “layout” was rendered for most scenes). Many stages that would be used in the final version are different here in various ways. The prototype contains a level that was cut from the game called “Parliament” which is playable from the cheats menu. The earliest prototype also includes a few test levels as well, much like the first game. <br>

Hidden Palace: Evilhamwizard moved page News/A Spooky New Years! to News/A Spooky New Years

2019-01-02T01:33:42Z

Evilhamwizard moved page News/A Spooky New Years! to News/A Spooky New Years

← Older revision

Revision as of 01:33, January 2, 2019

Hidden Palace: Created page with "NOTOC medievil logo.png MediEvil (Jun 22, 1998 prototype)
MediEvil (Jul 9, 1998 prototype)
MediEvil II (Dec 2..."

2019-01-02T01:08:00Z

Created page with "__NOTOC__ <center> <gallery mode=nolines> medievil logo.png </gallery> MediEvil (Jun 22, 1998 prototype) MediEvil (Jul 9, 1998 prototype) MediEvil II (Dec 2..."

New page

__NOTOC__
<center>
<gallery mode=nolines>
medievil logo.png
</gallery>

[[MediEvil (Jun 22, 1998 prototype)]] 
[[MediEvil (Jul 9, 1998 prototype)]] 
[[MediEvil II (Dec 20, 1999 prototype)]] 
[[MediEvil II (Feb 29, 2000 prototype)]] 
[http://hiddenpalace.org/forums/viewtopic.php?f=22&t=3322 {{icon|comments}} Discuss this release on the boards here!] 

Happy New Years everyone! 

This year saw a lot of nice releases from all corners of the internet. From early prototypes of Pokemon Gold & Silver to unreleased games such as SegaSonic Bros and SimCity for the NES, it looks like 2018 was one of the best years for prototypes in a while! What will 2019 bring? 

To start off the new year with something great, we decided to release four prototypes from the MediEvil series! Be sure to check out the articles for each prototype, as the articles will describe how to properly play them. 

[[File:me 31 proto 1.png|centre|frameless|link=MediEvil (Jun 22, 1998 prototype)]]
[[File:me 35 proto 1.png|centre|frameless|link=MediEvil (Jul 9, 1998 prototype)]]
First up, we have two prototypes of the first MediEvil - one meant for review and another for preview. These prototypes are dated several months before the first retail release of the game. While the two prototypes are dated a few weeks apart, they both contain a considerable amount of differences. Unfinished levels, a programmers test level, different layouts, different textures, and more! 

[[File:me2 19 proto 1.png|centre|frameless|link=MediEvil II (Dec 20, 1999 prototype)]]
[[File:me2 51 proto 1.png|centre|frameless|link=MediEvil II (Feb 29, 2000 prototype)]]
Next, we have two prototypes of MediEvil II as well! Again, one “preview” prototype and one “review” prototype. The differences between the final version and the earliest prototype are extreme. For instance, most of the FMV sequences in the December prototype are unfinished (only a rough “layout” was rendered for most scenes). Many stages that would be used in the final version are different here in various ways. The prototype contains a level that was cut from the game called “Parliament” which is playable from the cheats menu. The earliest prototype also includes a few test levels as well, much like the first game. 

<gallery mode=nolines>
medievildiscerror.png
</gallery>
However, not everything went smoothly this time. 

Issues occurred when attempting to backup these prototypes which made us question the integrity of the dumps we created. Besides the typical bad dump that can be remedied through trial and error on different burners with different read speeds, we were constantly presented with an issue where each game would just stop functioning after a certain point (usually during a level change). With no PS1 developer hardware to test with, we were unsure if the games were physically at fault for causing these issues, or if it was a sign of some form of copy protection. 

MediEvil marked one of the earliest attempts to thwart pirates with the copy protection method known as “libcrypt”. With this method, unique non-Yellow Book data is stored in subchannels on the disc itself. Games with libcrypt issue special, undocumented firmware commands to perform reads from the subchannel data, and check if it contains the unique data. This was a relatively effective copy protection mechanism for its time, since most pirate releases (even today) do not include the subchannel data (which is not contained in a typical bin/cue). 

It’s also difficult to perfectly extract subchannel data with common CD/DVD readers. Unlike data channels, which use extensive error correction algorithms, most of the subchannels are not error corrected, resulting in pretty much every dump being different (without error correction, reading raw data on CDs with a laser is very error prone!). Most burners also have a difficult time burning subchannel data back to CD-Rs as well. As an effect, at the time, the only way to bypass this copy protection was to debug the game and physically alter the game’s code through a patch to avoid these checks. 

After we were sure that the data track (the .img) was being dumped consistently, we decided to debug the games with no$psx to figure out what was going on. To make a long story short, both of the MediEvil prototypes actually use a form of SCEx copy protection where the check is done at the software level rather than just at the BIOS level. This copy protection involves comparing the letters “SCEx” (where “x” is the region of the game or console) with what’s stored on the disc against what’s stored in the BIOS. This check occurs when loading into a new level or quitting the game. 

MediEvil II on the other hand doesn’t seem to be using libcrypt. The February prototype seems to work fine and doesn’t seem to check between level changes. The December prototype seems to hang when loading levels even from the cheat menu. However, the prototype seems to work fine in PCSX while any other emulator hangs. 

However, even with the correct conditions the game would still refuse to load into another level. Luckily, by disassembling the games, we found that each prototype can be unlocked to work as normal by inputting an “unlock” or “cheat” code combination while the game is paused, which you can see for yourself by checking out the articles for each prototype. While we still aren’t confident that we fully understand what’s going on, it’s possible that the developers intentionally “sabotaged” their builds of the game by disallowing anyone from playing the game on anything besides a developer console, which has the ability to mimic specific regions. It’s also possible that the copy protection is set to always hang to prevent people other than the intended parties from accessing the rest of the game’s contents without knowing how to activate the in game cheats. 

Up until this point, we have dumped all CD/DVD based prototypes so far with CloneCD using both a Lite-On LH-20A1L and a HLDS GSA-U10N, drives that have historically low error rates. These particular dumps were created shortly before [[drx]] had to move overseas. The move has been a temporary set back since most of the stuff we intend to release is still in progress. The subchannel data will have to be redumped using different methods in order to ensure that the problems we were seeing aren’t caused by the dumps themselves. We consider the dumps okay for release, but we intend to redump everything in the future with a different standard so that we can ensure the best possible dumps. There is some promising software being developed, such as DiscImageCreator by the [http://redump.org.org Redump] project. 

With that being said, we hope you enjoy this release and look forward to sharing more with you in the upcoming months. 

Until next time! 
<gallery mode=nolines>
teaser2019.jpg
</gallery>
</center>

News/A Spooky New Years - Revision history

Okeijidragon: Hope this wasn't presumptuous of me for editing a major HP article. When I found this page, it was hard to read paragraphs that were stretched across in a UW monitor. Not fun, so I added reasonable width length.

Hidden Palace at 02:20, January 2, 2019

Hidden Palace at 01:57, January 2, 2019

Drx at 01:52, January 2, 2019

Drx at 01:49, January 2, 2019

Drx at 01:47, January 2, 2019

Drx at 01:47, January 2, 2019

Drx at 01:45, January 2, 2019

Hidden Palace: Evilhamwizard moved page News/A Spooky New Years! to News/A Spooky New Years

Hidden Palace: Created page with "__NOTOC__ medievil logo.png MediEvil (Jun 22, 1998 prototype) MediEvil (Jul 9, 1998 prototype) MediEvil II (Dec 2..."

Hidden Palace: Created page with "NOTOC medievil logo.png MediEvil (Jun 22, 1998 prototype)
MediEvil (Jul 9, 1998 prototype)
MediEvil II (Dec 2..."