It would be amazing to see the Gameboy/N64 emulator hacker community expand, and NEW games begin to be developed based on these docs. Maybe Nintendo could double-down on this and turn it into good publicity
The article mentions that this would be unwise due to these documents being released illegally. Reverse engineering some existing system for the purpose of interoperability (as is common among homebrew enthusiasts) is legal; hacking into a Nintendo subcontractor's IT and leaking internal documentation obviously isn't.
Nintendo has reportedly suffered a significant legacy console leak
41–50 of 220 posts
Re: Nintendo has reportedly suffered a significant legacy console leak
#42> The PC emulation community could also theoretically use the data to improve their software so that it imitates the original systems perfectly. However, since the leaked documentation has been illegally obtained this would put them in murky territory. I'd love to hear opinions about this whole thing from folks who work on emulators.
I don't work on emulators, but I do work on Wine. We explicitly forbid any contributions from anyone who has seen any Microsoft source code. The risk of introducing work derived from code owned by Microsoft is too high. I don't know how strict emulator authors are about this--they're non-commercial and so have less at stake than we do--but if I were an emulator author, I would cut ties with anyone known to have looke…
Except that people need ROMs to test emulators with.
Just like the old saying that it's impossible to actually start "from scratch", at some point everything is a derivative work of everything else; it just has to be far enough away to not attract legal attention.
Re: Nintendo has reportedly suffered a significant legacy console leak
#43Earlier quoted context omitted.
Actually I am gonna remove this google "download nintendo leak routefree" and you'll find what you need somewhere in the results.
The Pokemon source code link is still up, but the "mgnet.xyz" link that presumably contains the N64 source no longer works :( I'm a huge N64 enthusiast and wanted to see the Verilog source.
Re: Nintendo has reportedly suffered a significant legacy console leak
#44Earlier quoted context omitted.
Nah, Dolphin is 100% open source and above board, they're going to avoid this stuff like the plague.
True I don't think they would take the risk, it's just not worth it. Through I'm wondering if Nintendo will try to use that as a excuse just claiming they used that material.
I'd be doubly surprised if they ever open sourced anything.
Re: Nintendo has reportedly suffered a significant legacy console leak
#45Re: Nintendo has reportedly suffered a significant legacy console leak
#46To be clear, this doesn't just contain the source code of the software. It also contains the Verilog for the N64 GPU and other important hardware component, which is hugely important. From what I gather, it also contains full version history from their VCS. While it is very interesting, it's worth noting that anybody hoping to use this for anything "serious" risks getting the Nintendo lawyers on their ass. Emulators…
Re: Nintendo has reportedly suffered a significant legacy console leak
#47Earlier quoted context omitted.
Chances are Nintendo licensed these designs from a third party and isn’t in a position to give them away.
Yes. Silicon Graphics was heavily involved in the hardware design of the N64. Even if Nintendo wanted to allow everything in the leaks to be public, they don't have the rights to.
Re: Nintendo has reportedly suffered a significant legacy console leak
#48Earlier quoted context omitted.
The article mentions that this would be unwise due to these documents being released illegally. Reverse engineering some existing system for the purpose of interoperability (as is common among homebrew enthusiasts) is legal; hacking into a Nintendo subcontractor's IT and leaking internal documentation obviously isn't.
A developer can use the leak as a reference without being the one responsible for the leak. It sounds like it would be hugely beneficial.
There's a reason why people go to these lengths:
Re: Nintendo has reportedly suffered a significant legacy console leak
#49Earlier quoted context omitted.
> emulator and hardware developers [...] now have to screen new contributors to ensure they have not been exposed to this material. You cannot prove a negative. The most a project can do is to have people signing waivers that state they have not been exposed and/or will not copy stuff, effectively discharging responsibility on the individual.
This isn't a hypothetical concern. https://en.wikipedia.org/wiki/ReactOS#Internal_audit >> "On 27 January 2006, the developers responsible for maintaining the ReactOS code repository disabled access after a meeting was held to discuss the allegations. When approached by NewsForge, Microsoft declined to comment on the incident. Since ReactOS is a free and open-source software development project, the claim triggered a…
>> all developers were made to sign an agreement committing them to comply with the project's policies on reverse engineering. Contributors to its development were not affected by these events, and all access to the software development tools was restored
Also relevant:
>> the 2004 leaked Windows source code[38] was not seen as legal risk for ReactOS, as the trade secret was considered indefensible in court due to broad spread.[39]
Re: Nintendo has reportedly suffered a significant legacy console leak
#50Earlier quoted context omitted.
Well, they'll always oversell the damage, but realistically, not much impact to their bottom line. They do release remasters and ports, but I'd be hard pressed to see it being a significant loss in the grand scheme of things for a company that doesn't need to subsidize hardware with software. Like: people would buy a hypothetical N64 mini regardless of 3rd party emulators available. Or buy old games on the Virtual Co…
> From enthusiast perspective - it's a boon for preservation purposes. Sort of. It's obviously illegal to distribute, and arguably using it as a reference for re-implementation in emulators or in hardware would be a derivative work, and so also illegal. This could make things harder for emulator and hardware developers who now have to screen new contributors to ensure they have not been exposed to this material. It w…