San Francisco Rush 2049 (Arcade)/Upgrading - Revision history

NeSneSgB at 08:57, 6 November 2023

2023-11-06T08:57:24Z

← Older revision		Revision as of 08:57, 6 November 2023
Line 3:		Line 3:
	* Program a PIC16F57 with the security data with oscillator type set to XT		* Program a PIC16F57 with the security data with oscillator type set to XT
	* Extract the CHD and write the HDD image to a IDE HDD or CF card		* Extract the CHD and write the HDD image to a IDE HDD or CF card
			* Confirm that the proper resolution DIP switches are set

	== Detailed Instructions ==		== Detailed Instructions ==
	To upgrade San Francisco Rush 2049 to Tournament Edition or Special Edition, the upgrade kit consists of the following parts:		To upgrade San Francisco Rush 2049 to Tournament Edition or Special Edition, the upgrade kit consists of the following parts:
	* Security PIC (PIC16C57/PIC16F57-I/P or equivalent PIC) [https://www.digikey.com/en/products/detail/microchip-technology/PIC16F57-I-P/613201 ~~Digikey~~ link]		* Security PIC (PIC16C57/PIC16F57-I/P or equivalent PIC) [https://www.digikey.com/en/products/detail/microchip-technology/PIC16F57-I-P/613201 DigiKey link]
	* Boot ROM (27C4001/27C040/27C401 or equivalent EPROM; Originals are 100ns, slower may not work)		* Boot ROM (27C4001/27C040/27C401 or equivalent EPROM; Originals are 100ns, slower may not work)
	* IDE Hard drive or CF card with IDE adapter (the SE image in MAME is almost 20GB, but the ~~original HDD~~ is smaller, so as small as 4GB will work)		* IDE Hard drive or CF card with IDE adapter (the SE image in MAME is almost 20GB, but the game image is smaller, so as small as 4GB will work)
	** SATA devices with an IDE adapter will not work. IDE DOMs should work, but I was unable to get one to boot. The test menu disk test saw it as a device, but the game did not mount the partitions.		** SATA devices with an IDE adapter will not work. IDE DOMs should work, but I was unable to get one to boot. The test menu disk test saw it as a device, but the game did not mount the partitions.
	**[[File:Sandisk_cf.png\|thumb\|upright=0.50\|One of the few CF cards that the game accepts]]		**[[File:Sandisk_cf.png\|thumb\|upright=0.50\|One of the few CF cards that the game accepts]]
Line 30:		Line 31:

	The proper command to run is <code>chdman extractraw -i sf2049se.chd -o sf2049se.raw</code>, where '''sf2049se.chd''' is the input file path to your CHD, and '''sf2049se.raw''' is the output file path for the new decompressed image. A program such as Win32DiskImager on Windows or dd for Linux can then write this file to your physical medium.		The proper command to run is <code>chdman extractraw -i sf2049se.chd -o sf2049se.raw</code>, where '''sf2049se.chd''' is the input file path to your CHD, and '''sf2049se.raw''' is the output file path for the new decompressed image. A program such as Win32DiskImager on Windows or dd for Linux can then write this file to your physical medium.

			=== Setting the resolution DIP switches ===
			The DIP switch definitions for the game's video resolution changes between original 2049 and TE/SE, so it is important to confirm that the resolution is set properly before starting the game for the first time. For example, the default setting of On, Off, is VGA resolution in original 2049, but becomes medium resolution for SE. Some of the stock CRTs in Rush 2049 machines are not tri-sync, and may cause damage to them with an out of bounds sync frequency. The game will run at the other resolutions, but it will look odd on some screens, such as the Phantom Photon and Team Rush static images.

			For most cases, set DIPs 1 and 2 to on. This will select VGA for all 3 versions of the game.

NeSneSgB at 08:44, 6 November 2023

2023-11-06T08:44:30Z

NeSneSgB: Rewrite

2023-11-06T08:43:27Z

Rewrite

← Older revision		Revision as of 08:43, 6 November 2023
Line 1:		Line 1:
	== ~~Overview~~ ==		== TL;DR ==
	To upgrade San Francisco Rush 2049 to Tournament Edition or Special Edition, the ~~bare minimum~~ upgrade kit consists of the following parts:		* Program a 27C4001 with the boot ROM
			* Program a PIC16F57 with the security data with oscillator type set to XT
			* Extract the CHD and write the HDD image to a IDE HDD or CF card

			== Detailed Instructions ==
			To upgrade San Francisco Rush 2049 to Tournament Edition or Special Edition, the upgrade kit consists of the following parts:
	* Security PIC (PIC16C57/PIC16F57-I/P or equivalent PIC) [https://www.digikey.com/en/products/detail/microchip-technology/PIC16F57-I-P/613201 Digikey link]		* Security PIC (PIC16C57/PIC16F57-I/P or equivalent PIC) [https://www.digikey.com/en/products/detail/microchip-technology/PIC16F57-I-P/613201 Digikey link]
	* Boot ROM (27C4001/27C040/27C401 or equivalent EPROM~~, originals~~ are 100ns, slower may not work)		* Boot ROM (27C4001/27C040/27C401 or equivalent EPROM; Originals are 100ns, slower may not work)
	* IDE Hard drive or CF card with IDE adapter (the SE image in MAME is almost 20GB, but the original HDD is smaller, so as small as 4GB will work)		* IDE Hard drive or CF card with IDE adapter (the SE image in MAME is almost 20GB, but the original HDD is smaller, so as small as 4GB will work)
	** SATA devices with an IDE adapter will not work~~, nor will~~ IDE DOMs.		** SATA devices with an IDE adapter will not work. IDE DOMs should work, but I was unable to get one to boot. The test menu disk test saw it as a device, but the game did not mount the partitions.
	**[[File:Sandisk_cf.png\|thumb\|upright=0.50\|One of the few CF cards found to work]] The Vegas hardware is very picky about what CF cards will work.		**[[File:Sandisk_cf.png\|thumb\|upright=0.50\|One of the few CF cards found to work]] The Vegas hardware is very picky about what CF cards will work.

	~~This data can be found elsewhere on the Internet. There are plenty of websites out there that host up-to-date versions of romsets from MAME, so they will not be provided here.~~

	~~There are more components included with the official kits, but these 3 parts are the minimum required for the game to work.~~

	The BRAM database will be wiped if a new version of the game is installed, so game settings, date and time, and play statistics should be recorded before upgrading.		The BRAM database will be wiped if a new version of the game is installed, so game settings, date and time, and play statistics should be recorded before upgrading.
Line 16:		Line 17:
	A universal programmer such as the TL866A can program both the security PIC and boot ROM. Other programmer support will vary, especially for the PIC. The GQ-4X and GQ-4X4 can write the boot ROM, but not the PIC.		A universal programmer such as the TL866A can program both the security PIC and boot ROM. Other programmer support will vary, especially for the PIC. The GQ-4X and GQ-4X4 can write the boot ROM, but not the PIC.

	~~Programming is mostly straightfoward, however there are some things to keep in mind:~~		* [[File:Pic16x57_bits.png\|thumb\|upright=0.75\|PIC16F57 config bits from the datasheet]] FOSC0 will need to be set to 01 (XT oscillator) in the programmer settings, otherwise the game will not work. Depending on the programmer, this may require setting bits, or just selecting XT in the configuration menu.
	* [[File:Pic16x57_bits.png\|thumb\|upright=0.75\|PIC16F57 config bits from the datasheet]] FOSC0 will need to be set to 01 (XT oscillator) in the programmer settings, otherwise the game will not work. Depending on the programmer, this may just ~~be setting~~ the ~~oscillator type to XT as opposed to setting bits~~.		* The USER ID0-3 may need to be shortened to only 4 digits, as having more may cause verification to fail. "0FFF" is a value that works for all of the IDs.
	* The USER ID0-3 may need to be shortened to only 4 digits, as having more may cause verification to fail. "0FFF" is a ~~tested~~ value that works for all of the IDs.
	* Programming the Special Edition security data may require an extra step of deleting the extraneous 7 bytes from the buffer. Otherwise, the device might not program correctly.		* Programming the Special Edition security data may require an extra step of deleting the extraneous 7 bytes from the buffer. Otherwise, the device might not program correctly.

	If the ~~game doesn't boot~~, ~~erase~~ the ~~device and recheck the configuration.~~		If the seven-segment LED flashes I O A S I C, then the security PIC needs to be programmed again.

	~~'''Make sure~~ to ~~not install the chips in backwards~~. ~~They can survive a short amount of time reversed, but they will quickly get hot and die!'''~~

	== Writing the boot ROM ==		== Writing the boot ROM ==
	This is ~~much more~~ straightforward~~, the U27 boot ROM just has~~ to ~~be programmed like any other EPROM~~. If it fails ~~verification~~, then it should be erased in a UV EPROM eraser for 15-20 minutes and ~~attempted~~ again. If it keeps failing, try another chip.		This is straightforward to program. If it fails to verify against the file data, then it should be erased in a UV EPROM eraser for 15-20 minutes and programmed again. If it keeps failing, then try another chip.

	== Writing the hard drive/CF card ==		== Writing the hard drive/CF card ==
	The CHD image cannot be written to a hard drive as-is; it must be decompressed first. The chdman tool included with MAME can do this.		The CHD image cannot be written to a hard drive as-is; it must be decompressed first. The chdman tool included with MAME can do this. It is possible to decompress the image directly to a physical device, but it is easier to do it in multiple steps.

	The proper command to run is <code>chdman extractraw -i sf2049se.chd -o sf2049se.raw</code>, where '''sf2049se.chd''' is the input file path to your CHD, and '''sf2049se.raw''' is the output file path for the new decompressed image.		The proper command to run is <code>chdman extractraw -i sf2049se.chd -o sf2049se.raw</code>, where '''sf2049se.chd''' is the input file path to your CHD, and '''sf2049se.raw''' is the output file path for the new decompressed image. A program such as Win32DiskImager on Windows or dd for Linux can then write this file to your physical medium.

NeSneSgB at 03:41, 24 February 2023

2023-02-24T03:41:02Z

← Older revision		Revision as of 03:41, 24 February 2023
Line 1:		Line 1:
	== ~~Upgrading~~ ==		== Overview ==
	To upgrade San Francisco Rush 2049 to Tournament Edition or Special Edition, the bare minimum upgrade kit consists of the following parts:		To upgrade San Francisco Rush 2049 to Tournament Edition or Special Edition, the bare minimum upgrade kit consists of the following parts:
	* Security PIC (PIC16C57/PIC16F57-I/P or equivalent PIC) [https://www.digikey.com/en/products/detail/microchip-technology/PIC16F57-I-P/613201 Digikey link]		* Security PIC (PIC16C57/PIC16F57-I/P or equivalent PIC) [https://www.digikey.com/en/products/detail/microchip-technology/PIC16F57-I-P/613201 Digikey link]

NeSneSgB at 03:37, 24 February 2023

2023-02-24T03:37:54Z

← Older revision		Revision as of 03:37, 24 February 2023
Line 1:		Line 1:
	== Upgrading ==		== Upgrading ==
	To upgrade San Francisco Rush 2049 to Tournament Edition or Special Edition, the bare minimum upgrade kit consists of the following parts:		To upgrade San Francisco Rush 2049 to Tournament Edition or Special Edition, the bare minimum upgrade kit consists of the following parts:
	* Security PIC (PIC16C57/PIC16F57-I/P or equivalent PIC)		* Security PIC (PIC16C57/PIC16F57-I/P or equivalent PIC) [https://www.digikey.com/en/products/detail/microchip-technology/PIC16F57-I-P/613201 Digikey link]
	* Boot ROM (27C4001/27C040/27C401 or equivalent EPROM, originals are 100ns, slower may not work)		* Boot ROM (27C4001/27C040/27C401 or equivalent EPROM, originals are 100ns, slower may not work)
	* IDE Hard drive or CF card with IDE adapter (the SE image in MAME is almost 20GB, but the original HDD is smaller, so as small as 4GB will work)		* IDE Hard drive or CF card with IDE adapter (the SE image in MAME is almost 20GB, but the original HDD is smaller, so as small as 4GB will work)

NeSneSgB at 03:25, 24 February 2023

2023-02-24T03:25:57Z

← Older revision		Revision as of 03:25, 24 February 2023
Line 29:		Line 29:

	== Writing the hard drive/CF card ==		== Writing the hard drive/CF card ==
	The CHD image cannot be written to a hard drive as-is; it must be decompressed first. The ~~CHDMan~~ tool included with MAME can do this.		The CHD image cannot be written to a hard drive as-is; it must be decompressed first. The chdman tool included with MAME can do this.

	The proper command to run is <code>chdman extractraw -i sf2049se.chd -o sf2049se.raw</code>, where '''sf2049se.chd''' is the input file path to your CHD, and '''sf2049se.raw''' is the output file path for the new decompressed image.		The proper command to run is <code>chdman extractraw -i sf2049se.chd -o sf2049se.raw</code>, where '''sf2049se.chd''' is the input file path to your CHD, and '''sf2049se.raw''' is the output file path for the new decompressed image.

NeSneSgB at 03:23, 24 February 2023

2023-02-24T03:23:33Z

← Older revision		Revision as of 03:23, 24 February 2023
Line 2:		Line 2:
	To upgrade San Francisco Rush 2049 to Tournament Edition or Special Edition, the bare minimum upgrade kit consists of the following parts:		To upgrade San Francisco Rush 2049 to Tournament Edition or Special Edition, the bare minimum upgrade kit consists of the following parts:
	* Security PIC (PIC16C57/PIC16F57-I/P or equivalent PIC)		* Security PIC (PIC16C57/PIC16F57-I/P or equivalent PIC)
	* Boot ROM (27C4001/27C040/27C401 or equivalent EPROM)		* Boot ROM (27C4001/27C040/27C401 or equivalent EPROM, originals are 100ns, slower may not work)
	* IDE Hard drive or CF card with IDE adapter (the SE image in MAME is almost 20GB, but the original HDD is smaller, so as small as 4GB will work)		* IDE Hard drive or CF card with IDE adapter (the SE image in MAME is almost 20GB, but the original HDD is smaller, so as small as 4GB will work)
	** SATA devices with an IDE adapter will not work, nor will IDE DOMs.		** SATA devices with an IDE adapter will not work, nor will IDE DOMs.
Line 17:		Line 17:

	Programming is mostly straightfoward, however there are some things to keep in mind:		Programming is mostly straightfoward, however there are some things to keep in mind:
	* [[File:Pic16x57_bits.png\|thumb\|PIC16F57 config bits from the datasheet]] FOSC0 will need to be set to 01 (XT oscillator) in the programmer settings, otherwise the game will not work. Depending on the programmer, this may just be setting the oscillator type to XT as opposed to setting bits.		* [[File:Pic16x57_bits.png\|thumb\|upright=0.75\|PIC16F57 config bits from the datasheet]] FOSC0 will need to be set to 01 (XT oscillator) in the programmer settings, otherwise the game will not work. Depending on the programmer, this may just be setting the oscillator type to XT as opposed to setting bits.
	* The USER ID0-3 may need to be shortened to only 4 digits, as having more may cause verification to fail. "0FFF" is a tested value that works for all of the IDs.		* The USER ID0-3 may need to be shortened to only 4 digits, as having more may cause verification to fail. "0FFF" is a tested value that works for all of the IDs.
	* Programming the Special Edition security data may require an extra step of deleting the extraneous 7 bytes from the buffer. Otherwise, the device might not program correctly.		* Programming the Special Edition security data may require an extra step of deleting the extraneous 7 bytes from the buffer. Otherwise, the device might not program correctly.
Line 24:		Line 24:

	'''Make sure to not install the chips in backwards. They can survive a short amount of time reversed, but they will quickly get hot and die!'''		'''Make sure to not install the chips in backwards. They can survive a short amount of time reversed, but they will quickly get hot and die!'''

			== Writing the boot ROM ==
			This is much more straightforward, the U27 boot ROM just has to be programmed like any other EPROM. If it fails verification, then it should be erased in a UV EPROM eraser for 15-20 minutes and attempted again. If it keeps failing, try another chip.

			== Writing the hard drive/CF card ==
			The CHD image cannot be written to a hard drive as-is; it must be decompressed first. The CHDMan tool included with MAME can do this.

			The proper command to run is <code>chdman extractraw -i sf2049se.chd -o sf2049se.raw</code>, where '''sf2049se.chd''' is the input file path to your CHD, and '''sf2049se.raw''' is the output file path for the new decompressed image.

NeSneSgB: Create page

2023-02-24T02:04:37Z

Create page

New page

== Upgrading ==
To upgrade San Francisco Rush 2049 to Tournament Edition or Special Edition, the bare minimum upgrade kit consists of the following parts:
* Security PIC (PIC16C57/PIC16F57-I/P or equivalent PIC)
* Boot ROM (27C4001/27C040/27C401 or equivalent EPROM)
* IDE Hard drive or CF card with IDE adapter (the SE image in MAME is almost 20GB, but the original HDD is smaller, so as small as 4GB will work)
** SATA devices with an IDE adapter will not work, nor will IDE DOMs.
**[[File:Sandisk_cf.png|thumb|upright=0.50|One of the few CF cards found to work]] The Vegas hardware is very picky about what CF cards will work.

This data can be found elsewhere on the Internet. There are plenty of websites out there that host up-to-date versions of romsets from MAME, so they will not be provided here.

There are more components included with the official kits, but these 3 parts are the minimum required for the game to work.

The BRAM database will be wiped if a new version of the game is installed, so game settings, date and time, and play statistics should be recorded before upgrading.

== Writing the security PIC ==
A universal programmer such as the TL866A can program both the security PIC and boot ROM. Other programmer support will vary, especially for the PIC. The GQ-4X and GQ-4X4 can write the boot ROM, but not the PIC.

Programming is mostly straightfoward, however there are some things to keep in mind:
* [[File:Pic16x57_bits.png|thumb|PIC16F57 config bits from the datasheet]] FOSC0 will need to be set to 01 (XT oscillator) in the programmer settings, otherwise the game will not work. Depending on the programmer, this may just be setting the oscillator type to XT as opposed to setting bits.
* The USER ID0-3 may need to be shortened to only 4 digits, as having more may cause verification to fail. "0FFF" is a tested value that works for all of the IDs.
* Programming the Special Edition security data may require an extra step of deleting the extraneous 7 bytes from the buffer. Otherwise, the device might not program correctly.

If the game doesn't boot, erase the device and recheck the configuration.

'''Make sure to not install the chips in backwards. They can survive a short amount of time reversed, but they will quickly get hot and die!'''

← Older revision		Revision as of 08:44, 6 November 2023
Line 10:		Line 10:
	* IDE Hard drive or CF card with IDE adapter (the SE image in MAME is almost 20GB, but the original HDD is smaller, so as small as 4GB will work)		* IDE Hard drive or CF card with IDE adapter (the SE image in MAME is almost 20GB, but the original HDD is smaller, so as small as 4GB will work)
	** SATA devices with an IDE adapter will not work. IDE DOMs should work, but I was unable to get one to boot. The test menu disk test saw it as a device, but the game did not mount the partitions.		** SATA devices with an IDE adapter will not work. IDE DOMs should work, but I was unable to get one to boot. The test menu disk test saw it as a device, but the game did not mount the partitions.
	**[[File:Sandisk_cf.png\|thumb\|upright=0.50\|One of the few CF cards ~~found to work~~]] ~~The Vegas hardware is very picky about what CF cards will work.~~		**[[File:Sandisk_cf.png\|thumb\|upright=0.50\|One of the few CF cards that the game accepts]]

	The BRAM database will be wiped if a new version of the game is installed, so game settings, date and time, and play statistics should be recorded before upgrading.		The BRAM database will be wiped if a new version of the game is installed, so game settings, date and time, and play statistics should be recorded before upgrading.

	== Writing the security PIC ==		=== Writing the security PIC ===
	A universal programmer such as the TL866A can program both the security PIC and boot ROM. Other programmer support will vary, especially for the PIC. The GQ-4X and GQ-4X4 can write the boot ROM, but not the PIC.		A universal programmer such as the TL866A can program both the security PIC and boot ROM. Other programmer support will vary, especially for the PIC. The GQ-4X and GQ-4X4 can write the boot ROM, but not the PIC.

Line 23:		Line 23:
	If the seven-segment LED flashes I O A S I C, then the security PIC needs to be programmed again.		If the seven-segment LED flashes I O A S I C, then the security PIC needs to be programmed again.

	== Writing the boot ROM ==		=== Writing the boot ROM ===
	This is straightforward to program. If it fails to verify against the file data, then it should be erased in a UV EPROM eraser for 15-20 minutes and programmed again. If it keeps failing, then try another chip.		This is straightforward to program. If it fails to verify against the file data, then it should be erased in a UV EPROM eraser for 15-20 minutes and programmed again. If it keeps failing, then try another chip.

	== Writing the hard drive/CF card ==		=== Writing the hard drive/CF card ===
	The CHD image cannot be written to a hard drive as-is; it must be decompressed first. The chdman tool included with MAME can do this. It is possible to decompress the image directly to a physical device, but it is easier to do it in multiple steps.		The CHD image cannot be written to a hard drive as-is; it must be decompressed first. The chdman tool included with MAME can do this. It is possible to decompress the image directly to a physical device, but it is easier to do it in multiple steps.

	The proper command to run is <code>chdman extractraw -i sf2049se.chd -o sf2049se.raw</code>, where '''sf2049se.chd''' is the input file path to your CHD, and '''sf2049se.raw''' is the output file path for the new decompressed image. A program such as Win32DiskImager on Windows or dd for Linux can then write this file to your physical medium.		The proper command to run is <code>chdman extractraw -i sf2049se.chd -o sf2049se.raw</code>, where '''sf2049se.chd''' is the input file path to your CHD, and '''sf2049se.raw''' is the output file path for the new decompressed image. A program such as Win32DiskImager on Windows or dd for Linux can then write this file to your physical medium.