https://www.retroreversing.com/atom.xml doesn't work?

Hi! I'm the creator of splat, a tool that's commonly used nowadays to handle rom splitting and linker script generation for N64 decomp projects. I made it a few years ago after learning how n64split works and realizing that what I wanted in a tool kind of went a bit beyond what n64split is capable of. I've spoken to queueRAM, creator of n64split, about this, and he was supportive of my aspirations. The community tries to steer people away from using n64split at this point, because it's not really suitable for arbitrary projects and was designed with a specific game (sm64) in mind.

However, your site has a guide which pushes people to try creating new projects with n64split. This has sent numerous people to n64 decomp communities on Discord, asking for help with what is essentially a deprecated piece of software. We have to continuously tell them that your website is outdated and to use splat instead. I realize that it's work to keep this kind of thing up-to-date, so if you're not interested in maintaining the information here, I think it would be best if the outdated info was marked as such or removed.

Similarly, there's some info on the site about a mupen RE version, but I've tried and failed to build it, and I've seen many others try and fail to build it as well. There's also no guide on how to use it or indication that any of these RE features actually exist. I've had to explain to several people that they won't be able to use this thing on your site. I think mentions of this should be removed, as it seems unusable and is causing many people to waste their time.

I don't mean to sound unappreciative of the service you provide, but the outdated info here has been more of a hindrance than a help to both the people looking to start new projects and those of us trying to help them. If we were to make a PR replacing n64split references with a pointer to the splat repo and removing the mupen RE stuff, would that be accepted?

Also, if you'd like to discuss this in a more casual setting, feel free to reach out to me on discord. I'm ethteck there.

All the xds.xbox.com links in pages/xbox/OfficialXboxSDK.md are dead

These links are
xds.xbox.com
https://xds.xbox.com/BPProgInfo.asp?page=content/wp_index.htm

After playing with some SYM files from the listing on your site, I realized that some are just garbage, they don't match at all with the EXE on CD. I wrote that little utility in a hope I'd get symbols for Wipeout XL, but I was wrong, the NTSC.SYM is for another build of the game!

But for Destruction Derby, Twisted Metal, Hi Octane, the SYMs are great, you just have to split some tail bytes to make IDA happy!

What I'm trying to say is that, maybe you could add a small section on your website saying that it might be a false positive and not to celebrate too early because it might just be garbage.

Using split_tad_console (from TwlToolsRED) one can extract the SRL file from a TAD file. I tested with 4 Swords a while back.
Someone on 4chan was distributing this Python code, also. Not sure if there's a difference.

One can then use ninfs to mount the SRL to a directory and view its contents, e.g. via mount_srl swords.srl ~/mnt_srl.
From the sounds of it on a 3DS you can use GodMode9 to convert the SRL to a CIA, or also install the SRL directly.
NO$GBA should be able to launch it too once it's in SRL format.

In the link https://www.retroreversing.com/ps1-debug-symbols , section "Demos and Betas with Linker Map file", Syphon Filter (USA) (Demo) is missing. The map file (SIPHON.MAP) can be found on the root directory.

I took a look in ghidra and it seems it doesn't quite match the binary (MainLoop is at 0x800144a4 in ghdira but is at 0x800144C0 in the map file).

I could be wrong about the memory address since I'm quite new to reverse engineering, but I think it can be explained with the date of the .map file versus the binary (.map is dated 1998-12-20 15:01 while SCUS_943.62 is 1998-12-16 03:54).

Still, hopefully someone with more knowledge can use this info to reverse the game I hope! (And if you do, let me know!)

When cloning the repo, I get this error

$ git clone https://github.com/RetroReversing/retroReversing.git
Cloning into 'retroReversing'...
remote: Enumerating objects: 20422, done.
remote: Counting objects: 100% (2921/2921), done.
remote: Compressing objects: 100% (1088/1088), done.
remote: Total 20422 (delta 1936), reused 2763 (delta 1807), pack-reused 17501
Receiving objects: 100% (20422/20422), 191.81 MiB | 1.13 MiB/s, done.
Resolving deltas: 100% (13234/13234), done.
error: invalid path 'public/images/xbox/Xbox Development kit DVT3:4 PCI Raptor DVD Emulator Card - Developer Jeff.jpeg'
fatal: unable to checkout working tree
warning: Clone succeeded, but checkout failed.
You can inspect what was checked out with 'git status'
and retry with 'git restore --source=HEAD :/'

I am using Windows 10 x64, never had such an issue when cloning a repo.
Trying again, from scratch, yields the same result.
Any idea why this happened?

$ git --version
git version 2.36.0.windows.1

The file that's currently at https://github.com/RetroReversing/retroReversing/blob/master/pages/xbox/OfficialXboxSDK.md is clearly promoting piracy.

What's the intention behind this, and wouldn't it put any other (possibly useful) infomation on this site in jeopardy?

If there's any other content which might be illegal, I'd strongly recommend to avoid it.
Such content will certainly lead to many other websites not using your content.
It prevents referring to you at all.

This is especially important for the emulation scene where preservation is at stake. So anything that could make the project attackable is usually avoided. If it refers to this website / project / ... it will certainly be a risk (that many won't be willing to take).

I just blogged about:

How I built my own Sega Mega Drive hardware dev kit from scratch
https://nestenius.se/2022/01/18/how-i-built-my-own-sega-mega-drive-hardware-dev-kit-from-scratch/

Perhaps something to add to your dev kit page?

I think this website duplicates a lot of information that's already present elsewhere, such as TCRF (although some of these platforms might be operated with conflicting politics).

Is this really necessary, and are there possibly better ways to handle this?

What's the motivation behind RetroReversing?

• Education
• Commercial
• ...

I would like to request the addition of a section on Sega Saturn save game files/formats.

Tools to reference:
Copy Saves from Saturn to PC:

• SS-Save-Parser: QT-based parser for Sega Saturn RAM Backup (aka Power Memory), Internal RAM, and possibly other media images. It can load/save/show image's content and extract/insert/delete single saves in a customizable way. Virtually any sector size (64,256,512,whatever) is suppoted, and conversion is available. Importing of a Datel's compressed images is supported.
• Save Game Extractor: Transmit Sega Saturn save game files as audio to backup on a PC. Based on the amazing minimodem.

Copy Saves from PC to Saturn:

• Save Game Manager: Most useful utility for gamers on SEGA Saturn. manage files. Supports:

  • copy, delete, format,
  • compress / decompress file archives (BZip2)
  • update Action Replay firmware (using arflash from ExCyber)
  • split / join files (since v2)
  • dump memory (AR firmware) to file (since v2)
  • export / import files using button commands (since v2)
  • export / import files using human readable base64 text (since v3) (Save Game eXchange over internet)

• Save Game Copier: Allows you to burn saves to a CD, boot on a real Saturn, and copy them to the internal memory of the Saturn. Archived project.

Greetings,

I am interested in learning how more about reverse engineering psx ROMs for the purpose of modding Front Mission 3.

PSX ROMs are typically distributed as .BIN files (along with .CUE files),
however, this file format is not mentioned on the PS1FileFormats Page.

This is also the case for the .85 files mentioned on the PS1_Radare2 Page.

I really have no idea on how and if it's worth adding a section for PowerPC games but here's a first one:

Wipeout XL for PowerPC Mac:

The hash on the right is SHA1, original file name is WipeOut 2097:

WipeOut 2097 Version 1.0 October 8, 2001	778284c41ca70989ce0c8e7decb7608fc7cadb22
WipeOut 2097 Version 1.2.1 August 23, 2002	b88986b89a391dd697552a72f93f456b7de1f76e
WipeOut 2097 Version 1.3 August 22, 2003	59b31107562fa3da69a358a8167eae784537d21a

Curiously, WipeOut 2097 Version 1.1 March 28, 2002 doesn't have any...

I don't know that platform at all, but the symbols are baked in the executable, IDA will find them but sadly not Ghidra:

followRaceLine(VECTOR *,ShipData *,Face *,int)
lookForWayPast(VECTOR *,ShipData *,short,short)	
calcMyXPos(ShipData *,short,short *,short *)
...