Hacker News Reader

Comment by Sir_Cmpwn | Hacker News Reader

Wow - only supports Windows XP, and a MediaFire link full of questionable executables? I hope fixing this is part of your "WIP"...

View on HN

These files are necessary to setup the dev environment if you want to compile. I use the link myself when setting up a new build machine.

If you don't trust the files that's perfectly fine. You could pretty easily, I believe, find them all from repositories you trust.

Also yep Win XP only! Keeping it authentic lol. :)

To clarify: The N64 SDK runs on XP.

Yep! Thanks for the clarification.

I wonder if it'd be possible to get it running on Wine for a safer experience.

I've tried but it doesn't seem possible. Wine and even DOS Box can't run the 16 bit SDK executables. I'd love to be able to run just the ROM build process in Wine. :)

What's so special about the ROM process that it can't be ported or rewritten in a more portable way?

Because the 16 bit executables are closed source. :/ The special linker MILD.exe that organizes all of the RSP(Reality Signal Processor) microcodes and game data is the piece that needs to be reverse-engineered which is possible but currently beyond me. :)

I don't think it's beyond you, I just think you lack confidence. You can do it! I've been in your shoes before and it worked out.

Aww thanks much! :D Yeah I just lack confidence I guess since reversing binaries has always seemed a bit intense. I need to finally buy a really good code reversal tool and then start my quest to reproduce! :) It would be great if me or someone else was successful since then the N64 could be more easily developed for on any OS!!

You probably don't even need to reverse anything. Just learn how other (open source) toolchains work, read N64 manuals and information from other reverse engineers, and work incrementally. It's probably not necessary to reverse this proprietary ROM you're stuck with.

Reply on news.ycombinator.com