User talk:Zzo38/Mapper 768: Difference between revisions
From NESdev Wiki
Jump to navigationJump to search
(→Extra Data: new section) |
No edit summary |
||
| (One intermediate revision by one other user not shown) | |||
| Line 1: | Line 1: | ||
== Extra Data == | == Extra Data == | ||
The [[NES 2.0]] format doesn't have any provisions for additional data beyond what the original [[iNES]] format mentions (where the PC10 PROM is often missing and the 128-byte/127-byte "title" is completely optional), so how would emulators know to load the "extra data for mapper 768" without having to hardcode mapper-specific behavior into their file loading logic? Perhaps it might be worth updating the standard to include a means of specifying additional mapper-specific data (since many emulators close the .NES file before ever initializing the mapper)... --[[User:Quietust|Quietust]] ([[User talk:Quietust|talk]]) 19:58, 19 March 2013 (MDT) | The [[NES 2.0]] format doesn't have any provisions for additional data beyond what the original [[iNES]] format mentions (where the PC10 PROM is often missing and the 128-byte/127-byte "title" is completely optional), so how would emulators know to load the "extra data for mapper 768" without having to hardcode mapper-specific behavior into their file loading logic? Perhaps it might be worth updating the NES 2.0 standard (maybe NES 2.1?) to include a means of specifying additional mapper-specific data (since many emulators close the .NES file before ever initializing the mapper)... --[[User:Quietust|Quietust]] ([[User talk:Quietust|talk]]) 19:58, 19 March 2013 (MDT) | ||
:It is probably not a bad idea; you can do this if you want to. Nevertheless, the extra data is always at the end, after everything else. It will probably be ignored otherwise anyways, such as if you are converting a private mapper (3840 and higher) to mapper 768 or vice versa, or into a standard mapper number (such conversions like this might be useful for testing; for actual conversion into standard mapper numbers you will probably truncate the file, too). --[[User:Zzo38|Zzo38]] ([[User talk:Zzo38|talk]]) 21:15, 19 March 2013 (MDT) | |||
Latest revision as of 03:15, 20 March 2013
Extra Data
The NES 2.0 format doesn't have any provisions for additional data beyond what the original iNES format mentions (where the PC10 PROM is often missing and the 128-byte/127-byte "title" is completely optional), so how would emulators know to load the "extra data for mapper 768" without having to hardcode mapper-specific behavior into their file loading logic? Perhaps it might be worth updating the NES 2.0 standard (maybe NES 2.1?) to include a means of specifying additional mapper-specific data (since many emulators close the .NES file before ever initializing the mapper)... --Quietust (talk) 19:58, 19 March 2013 (MDT)
- It is probably not a bad idea; you can do this if you want to. Nevertheless, the extra data is always at the end, after everything else. It will probably be ignored otherwise anyways, such as if you are converting a private mapper (3840 and higher) to mapper 768 or vice versa, or into a standard mapper number (such conversions like this might be useful for testing; for actual conversion into standard mapper numbers you will probably truncate the file, too). --Zzo38 (talk) 21:15, 19 March 2013 (MDT)
