Register - Login
Views: 99384299
 Main - Memberlist - Active users - Calendar - Wiki - IRC Chat - Online users
Ranks - Rules/FAQ - Stats - Latest Posts - Color Chart - Smilies		 04-24-22 02:57:58 AM
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/1229
EXP: 2871914
For next: 143897

Since: 02-22-10

Pronouns: anything works
From: here

Since last post: 49 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: 12727
For next: 344

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: 102367
For next: 13792

Since: 08-25-10


Since last post: 24 days
Last activity: 6 days
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: 20222
For next: 34

Since: 05-09-13


Since last post: 37 days
Last activity: 4 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: 29050850
For next: 284155

Since: 07-22-07

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

Since last post: 333 days
Last activity: 333 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!

____________________
I make furry arts and dumb tweets.
Renamon is best pony.
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.

31 database queries.
Query execution time:  0.100128 seconds
Script execution time:  0.009378 seconds
Total render time:  0.109506 seconds


TidyHTML vomit below
line 1 column 1 - Warning: missing <!DOCTYPE> declaration
line 119 column 11 - Warning: <form> isn't allowed in <table> elements
line 118 column 10 - Info: <table> previously mentioned
line 120 column 11 - Warning: missing <tr>
line 120 column 119 - Warning: missing </font> before </td>
line 124 column 16 - Warning: plain text isn't allowed in <tr> elements
line 120 column 11 - Info: <tr> previously mentioned
line 125 column 68 - Warning: missing </nobr> before </td>
line 141 column 68 - Warning: missing </nobr> before <tr>
line 147 column 35 - Warning: missing <tr>
line 147 column 50 - Warning: missing </font> before </td>
line 148 column 37 - Warning: unescaped & or unknown entity "&id"
line 147 column 187 - Warning: missing </font> before </table>
line 149 column 35 - Warning: missing <tr>
line 149 column 50 - Warning: missing </font> before </td>
line 149 column 91 - Warning: missing </font> before </table>
line 156 column 9 - Warning: <div> isn't allowed in <table> elements
line 152 column 17 - Info: <table> previously mentioned
line 158 column 9 - Warning: missing <tr>
line 176 column 13 - Warning: missing <tr>
line 177 column 102 - Warning: unescaped & or unknown entity "&postid"
line 188 column 9 - Warning: <div> isn't allowed in <table> elements
line 152 column 17 - Info: <table> previously mentioned
line 190 column 9 - Warning: missing <tr>
line 208 column 13 - Warning: missing <tr>
line 209 column 102 - Warning: unescaped & or unknown entity "&postid"
line 211 column 74 - Warning: <style> isn't allowed in <td> elements
line 211 column 9 - Info: <td> previously mentioned
line 214 column 9 - Warning: <div> isn't allowed in <table> elements
line 152 column 17 - Info: <table> previously mentioned
line 216 column 9 - Warning: missing <tr>
line 234 column 13 - Warning: missing <tr>
line 235 column 102 - Warning: unescaped & or unknown entity "&postid"
line 250 column 9 - Warning: <div> isn't allowed in <table> elements
line 152 column 17 - Info: <table> previously mentioned
line 252 column 9 - Warning: missing <tr>
line 270 column 13 - Warning: missing <tr>
line 271 column 102 - Warning: unescaped & or unknown entity "&postid"
line 276 column 9 - Warning: <div> isn't allowed in <table> elements
line 152 column 17 - Info: <table> previously mentioned
line 278 column 9 - Warning: missing <tr>
line 296 column 13 - Warning: missing <tr>
line 297 column 102 - Warning: unescaped & or unknown entity "&postid"
line 309 column 9 - Warning: <div> isn't allowed in <table> elements
line 152 column 17 - Info: <table> previously mentioned
line 311 column 9 - Warning: missing <tr>
line 329 column 13 - Warning: missing <tr>
line 330 column 102 - Warning: unescaped & or unknown entity "&postid"
line 332 column 74 - Warning: <style> isn't allowed in <td> elements
line 332 column 9 - Info: <td> previously mentioned
line 338 column 17 - Warning: missing <tr>
line 338 column 17 - Warning: discarding unexpected <table>
line 341 column 35 - Warning: missing <tr>
line 341 column 50 - Warning: missing </font> before </td>
line 341 column 91 - Warning: missing </font> before </table>
line 343 column 35 - Warning: missing <tr>
line 343 column 50 - Warning: missing </font> before </td>
line 344 column 37 - Warning: unescaped & or unknown entity "&id"
line 343 column 187 - Warning: missing </font> before </table>
line 345 column 17 - Warning: discarding unexpected </textarea>
line 345 column 28 - Warning: discarding unexpected </form>
line 345 column 35 - Warning: discarding unexpected </embed>
line 345 column 43 - Warning: discarding unexpected </noembed>
line 345 column 53 - Warning: discarding unexpected </noscript>
line 345 column 64 - Warning: discarding unexpected </noembed>
line 345 column 74 - Warning: discarding unexpected </embed>
line 345 column 82 - Warning: discarding unexpected </table>
line 345 column 90 - Warning: discarding unexpected </table>
line 347 column 9 - Warning: missing </font> before <table>
line 359 column 25 - Warning: discarding unexpected </font>
line 368 column 37 - Warning: discarding unexpected </font>
line 346 column 1 - Warning: missing </center>
line 120 column 63 - Warning: <img> lacks "alt" attribute
line 125 column 19 - Warning: <td> attribute "width" has invalid value "120px"
line 125 column 93 - Warning: <img> lacks "alt" attribute
line 141 column 19 - Warning: <td> attribute "width" has invalid value "120px"
line 141 column 98 - Warning: <img> lacks "alt" attribute
line 148 column 44 - Warning: <img> proprietary attribute value "absmiddle"
line 148 column 142 - Warning: <img> proprietary attribute value "absmiddle"
line 148 column 246 - Warning: <img> proprietary attribute value "absmiddle"
line 161 column 21 - Warning: <img> lacks "alt" attribute
line 161 column 62 - Warning: <img> lacks "alt" attribute
line 161 column 111 - Warning: <img> lacks "alt" attribute
line 161 column 161 - Warning: <img> lacks "alt" attribute
line 172 column 15 - Warning: <img> lacks "alt" attribute
line 192 column 11 - Warning: <img> lacks "alt" attribute
line 193 column 22 - Warning: <img> lacks "alt" attribute
line 193 column 63 - Warning: <img> lacks "alt" attribute
line 193 column 111 - Warning: <img> lacks "alt" attribute
line 193 column 161 - Warning: <img> lacks "alt" attribute
line 194 column 11 - Warning: <img> lacks "alt" attribute
line 204 column 15 - Warning: <img> lacks "alt" attribute
line 211 column 566 - Warning: <img> lacks "alt" attribute
line 211 column 1271 - Warning: <div> anchor "joyeuse" already defined
line 219 column 22 - Warning: <img> lacks "alt" attribute
line 219 column 63 - Warning: <img> lacks "alt" attribute
line 219 column 112 - Warning: <img> lacks "alt" attribute
line 219 column 162 - Warning: <img> lacks "alt" attribute
line 230 column 15 - Warning: <img> lacks "alt" attribute
line 255 column 22 - Warning: <img> lacks "alt" attribute
line 255 column 63 - Warning: <img> lacks "alt" attribute
line 255 column 111 - Warning: <img> lacks "alt" attribute
line 255 column 161 - Warning: <img> lacks "alt" attribute
line 256 column 11 - Warning: <img> lacks "alt" attribute
line 266 column 15 - Warning: <img> lacks "alt" attribute
line 281 column 22 - Warning: <img> lacks "alt" attribute
line 281 column 63 - Warning: <img> lacks "alt" attribute
line 281 column 112 - Warning: <img> lacks "alt" attribute
line 281 column 161 - Warning: <img> lacks "alt" attribute
line 292 column 15 - Warning: <img> lacks "alt" attribute
line 314 column 23 - Warning: <img> lacks "alt" attribute
line 314 column 64 - Warning: <img> lacks "alt" attribute
line 314 column 113 - Warning: <img> lacks "alt" attribute
line 314 column 163 - Warning: <img> lacks "alt" attribute
line 325 column 15 - Warning: <img> lacks "alt" attribute
line 344 column 44 - Warning: <img> proprietary attribute value "absmiddle"
line 344 column 142 - Warning: <img> proprietary attribute value "absmiddle"
line 344 column 246 - Warning: <img> proprietary attribute value "absmiddle"
line 353 column 25 - Warning: <img> lacks "alt" attribute
line 358 column 267 - Warning: <img> lacks "alt" attribute
line 149 column 50 - Warning: trimming empty <font>
line 338 column 17 - Warning: trimming empty <tr>
line 341 column 50 - Warning: trimming empty <font>
line 125 column 68 - Warning: <nobr> is not approved by W3C
line 141 column 68 - Warning: <nobr> is not approved by W3C
line 177 column 27 - Warning: <nobr> is not approved by W3C
line 209 column 27 - Warning: <nobr> is not approved by W3C
line 235 column 27 - Warning: <nobr> is not approved by W3C
line 271 column 27 - Warning: <nobr> is not approved by W3C
line 297 column 27 - Warning: <nobr> is not approved by W3C
line 330 column 27 - Warning: <nobr> is not approved by W3C
Info: Document content looks like HTML5
Info: No system identifier in emitted doctype
Tidy found 121 warnings and 0 errors!


The alt attribute should be used to give a short description
of an image; longer descriptions should be given with the
longdesc attribute which takes a URL linked to the description.
These measures are needed for people using non-graphical browsers.

For further advice on how to make your pages accessible
see http://www.w3.org/WAI/GL.
You are recommended to use CSS to specify the font and
properties such as its size and color. This will reduce
the size of HTML files and make them easier to maintain
compared with using <FONT> elements.

You are recommended to use CSS to control line wrapping.
Use "white-space: nowrap" to inhibit wrapping in place
of inserting <NOBR>...</NOBR> into the markup.

About HTML Tidy: https://github.com/htacg/tidy-html5
Bug reports and comments: https://github.com/htacg/tidy-html5/issues
Official mailing list: https://lists.w3.org/Archives/Public/public-htacg/
Latest HTML specification: http://dev.w3.org/html5/spec-author-view/
Validate your HTML documents: http://validator.w3.org/nu/
Lobby your company to join the W3C: http://www.w3.org/Consortium

Do you speak a language other than English, or a different variant of
English? Consider helping us to localize HTML Tidy. For details please see
https://github.com/htacg/tidy-html5/blob/master/README/LOCALIZE.md