Register - Login
Views: 99863580
Main - Memberlist - Active users - Calendar - Wiki - IRC Chat - Online users
Ranks - Rules/FAQ - Stats - Latest Posts - Color Chart - Smilies
05-04-22 04:38:34 PM
Jul - The Cutting Room Floor - NES and SMS Roms New poll - New thread - New reply
Next newer thread | Next older thread
NSSFan
Random nobody
Level: 2


Posts: 1/1
EXP: 30
For next: 16

Since: 10-01-19


Since last post: 2.6 years
Last activity: 2.6 years

Posted on 10-01-19 07:45:40 AM Link | Quote
Hi Guys,

Im new here and i have an important question i have a complete library of NES and SMS Roms and many of these games have multiple revisions like Rev 1 or Rev 2 and there are also games that have separate versions for different regions like Japan, North America and Europe.

I found this website The Cutting Room Floor by accident because i was looking for revision changes betweens roms and it is very helpful but how did you guys find out about all these information changes between roms?

My question is simply how can i find or see what they exactly changed between the revisions of a particular game or what is different between regional versions of a game?
2Tie

Rumours of my death have been greatly exaggerated.
Level: 70


Posts: 1154/1230
EXP: 2878838
For next: 136973

Since: 02-22-10

Pronouns: anything works
From: here

Since last post: 7 days
Last activity: 1 day

Posted on 10-01-19 02:01:35 PM Link | Quote
UESCTerm 802.11 (remote override)
044 05.10.2337

It's pretty much a game-by-game basis. Some changes are noticed and documented just by playing the game (graphical changes, for example), while others might be figured out after comparing the bytecode in the roms against each other, for mechanics tweaks or debug menu codes and such. For the people who contribute to TCRF, the articles are made after they look into the revisions and prototypes themselves and document it. If an article for a game hasn't been made, and revisions do exist, it just means nobody's looked into it yet, or at least haven't uploaded their findings.

____________________
Press B to Cancel
Press A to Acknowledge
Mr.Tickles
Member
Level: 14


Posts: 35/35
EXP: 12745
For next: 326

Since: 12-19-11


Since last post: 2.6 years
Last activity: 4.7 years

Posted on 10-01-19 05:54:22 PM Link | Quote
Originally posted by NSSFan
Hi Guys,

Im new here and i have an important question i have a complete library of NES and SMS Roms and many of these games have multiple revisions like Rev 1 or Rev 2 and there are also games that have separate versions for different regions like Japan, North America and Europe.

I found this website The Cutting Room Floor by accident because i was looking for revision changes betweens roms and it is very helpful but how did you guys find out about all these information changes between roms?

My question is simply how can i find or see what they exactly changed between the revisions of a particular game or what is different between regional versions of a game?


If you have the GoodRoms archive of every NES/SNES rom that ever existed then the naming is not very consistent in that archive.

Generally v1.01 type stuff or revision 1 or 2 is some kind of bug fix that went out with a second printing of cartridges. Since these were read-only memory the companies could only recall and destroy, they couldn't issue 50 gigabyte release-day patches like Fallout 76.
rabidabid
Member
Level: 27


Posts: 131/135
EXP: 102494
For next: 13665

Since: 08-25-10


Since last post: 34 days
Last activity: 1 day

Posted on 10-10-19 03:18:14 AM Link | Quote
You can use something like WinMerge to open two ROMs side by side and compare the raw data.
KingMike
Member
Level: 16


Posts: 40/50
EXP: 20254
For next: 2

Since: 05-09-13


Since last post: 47 days
Last activity: 6 days

Posted on 10-10-19 02:43:52 PM Link | Quote
Originally posted by Mr.Tickles

Generally v1.01 type stuff or revision 1 or 2 is some kind of bug fix that went out with a second printing of cartridges. Since these were read-only memory the companies could only recall and destroy, they couldn't issue 50 gigabyte release-day patches like Fallout 76.


I think if they recall a game, it would have to be a REAL serious issue.

I know Howard Philips has responded to the rumor Nintendo destroyed most copies of Stadium Events by saying that doesn't sound very economical? realistic?. Something along those lines.

Something along the lines of the WTC version of Spiderman... uh, 2, was? for the PS1? That was scheduled to release like a week after 9/11 but had to be recalled to print a less timing-sensitive version. That is how extreme a situation a recall would have to be.
Rena
I had one (1) message in Discord deleted and proceeded to make a huge, huge mess about how it was a violation of free speech and how moderators are supposed to be spam janitors and nobody should have the right to tell me not to talk about school shootings
Level: 135


Posts: 5293/5390
EXP: 29079323
For next: 255682

Since: 07-22-07

Pronouns: he/him/whatever
From: RSP Segment 6

Since last post: 343 days
Last activity: 343 days

Posted on 11-03-19 05:05:31 PM Link | Quote
Usually they don't recall unless it's a serious bug; they'll just quietly start manufacturing a new version. Eg Ocarina of Time had 3 versions on cartridge; the earliest is still perfectly playable, but the revisions fix some bugs and change some graphics/music that people were offended by.

Comparing the raw binary can tell you what to look at for changes, but usually that's only a starting point. Unless it's immediately obvious (the changed data is some text or graphic that you can immediately recognize), you'd have to examine the code to find what those changes actually do. Sometimes they don't even do anything!

____________________
Next newer thread | Next older thread
Jul - The Cutting Room Floor - NES and SMS Roms New poll - New thread - New reply


Rusted Logic

Acmlmboard - commit 47be4dc [2021-08-23]
©2000-2022 Acmlm, Xkeeper, Kaito Sinclaire, et al.

32 database queries.
Query execution time: 0.107610 seconds
Script execution time: 0.009557 seconds
Total render time: 0.117167 seconds