Sonic and Sega Retro Message Board: Armada - Viewing Profile - Sonic and Sega Retro Message Board

Jump to content

Hey there, Guest!  (Log In · Register) Help

Member: Members
Active Posts:
338 (0.09 per day)
Most Active In:
Engineering & Reverse Engineering (104 posts)
05-January 07
Profile Views:
Last Active:
User is offline Aug 29 2017 03:51 PM

My Information

Member Title:
Sometimes I do things
24 years old
February 11, 1993
Male Male

Contact Information

Click here to e-mail me
Website  http://

Previous Fields

National Flag:
Wiki edits:

Latest Visitors

Topics I've Started

  1. Troubleshoot Your Builds

    20 June 2009 - 04:09 PM

    So, I got pissed about how batch files close on resolution in XP (does it do it on Vista too). Finally, I was bothered to modify build.bat to log all the builds for troubleshooting at a later date. Since it has a bit of finicky code, it's worth the guide.

    First, add this after all the comments (REM) that recompress all the data:

    REM Troubleshooting log
    REM Stores date and output

    @FOR /F "tokens=*" %%A IN ('DATE/T') DO FOR %%B IN (%%A) DO SET Today=%%B
    @FOR /F %%A IN ('TIME/T') DO SET Now=%%A

    ECHO ====================================================== >>output.txt
    ECHO Built on %Today% at %Now% >> output.txt

    That bit parses the time and date and logs it in a file called "output.txt". Rename it as you like.

    This code is specific to your build tools, so here's the general form, place it after the date and time snippet and before your build command lines:
    rompad.exe s1built.bin 255 0 >>output.txt

    fixheadr.exe s1built.bin >>output.txt

    Finally add "PAUSE" to the end of your batch if you wish to see the output before closing. If all is successful, you should get the contents of the build in "output.txt". The batch is also up for download here if you're using ASM68K.
  2. Release Sofia as a generic pastebin?

    27 May 2009 - 08:40 PM

    I was considering this sometime in the future. I would highly improve and comment the code I'm currently using. I'd also make up a skin system to use as well. Just wondering what you guys think.

    10 May 2009 - 02:13 PM

    (If this needs to be moved, please do so.)

    It's finally ready! For those who have seen my signature, this explains the logo. Sofia stands for the Sonic Online Free Information Archive. I decided to create it when I noticed that I couldn't find any guides easily. Sofia was born to organize everything easily, in one place. I'd like to explain some finer points of what Sofia is about. For those who want to skip, it's basically "Sonic Pastebin".

    1. Sofia is free to use, for anyone.

    The "F" in the acronym clearly explains this. Any guide you want to share, or any existing guide that was allowed to be posted anywhere. You can access this information any time, easily, with no charge involved. You also keep any ownership of your guides. However, if you do post a guide on Sofia, you are implying it is allowed anywhere. If a guide (whether you wrote it or not) is for a specific site, please do not post it here as it goes against the site philosophy.

    2. Sofia gets you the best code based on public opinion

    With everyone being able to post code, there's bound to be duplicates? How are you supposed to know which is the best? How are you supposed to know it even works? Sofia covers this with promotion points. When you view a piece a code on the site, there a two options on the bottom. One you can select if the code is bug-free and one if the code does what it says. There is also a third option when coming from the search that adds another point if it is the best code from your search. These opinions can add or subtract promotion points from a piece of code. The search and code browser organize code by promotion points, so the better the opinion, the more likely that code is to get to you. This helps you get the best code faster.

    3. You can edit code on the site

    Found a bug in someone's code? Think you can do it better? Then fix it! Anyone has the ability to edit a guide that is already on the site. This also allows you to collaborate on personal projects, or just make good code better. Editing broken code will also improve the chances of it getting more promotion points and improving the overall serving of code.

    4. ASM and plain text guides in one post.

    When I was writing the code for this site, I had initially planned for only ASM to be posted. Then I realized that there are more than just ASM guides to be posted. Thanks to Qjimbo, it was possible for use to put in tags to highlight the code and have normal text be unchanged.

    Well, those are pretty much the major features of the site. I hope this becomes pretty useful. If you find any bugs, please PM me or post them in this topic until I get a bug report system running. Thanks for reading.
  4. The Earthbound Split Disassembly Project

    18 November 2008 - 03:31 PM

    Hello everyone, it's time for one of my fabulous topics again. You see, I enjoy Earthbound and the mother series. I've been a member at for a good while now, and I looked in their hacking forums. They have a nifty tool called "PK Hack", but I was surprised to see the lack of a decent split disassembly. The ROM has been disassembled, and the source code is out there, but it hasn't be investigated at all (with the exception of maybe using it to create a ROM map and decompress art for PK Hack).

    I guess it's because I was so used to split disassemblies that I decided to begin this motion. I understand good hacks can be done without them, but the benefits to having them are great. I can also see this will lead to more interest in analyzing the source code, and creating more useful tools (like an art decompression tool).

    Anyway here is the link to the project topic on If you're willing to help, drop in and see what you can do.

    I may have over glorified disams too much. :U
  5. Your Programming Language of Choice?

    23 July 2008 - 06:24 PM

    ASM/HEX doesn't really count in this topic, since a mojority of this community can understand it. So knock that one right off you list.

    I like to do small apps in C++, like a HEX to ASM converter I'm tinkering with. For large-scale apps (such as Mozart), I'm not confident enough with a C language, so I usually go with VB or C#. When it comes to web applications/sites, I stick to the standard combo of PHP and MySQL. I'm currently hand coding a browser-bassed MMORPG and a site managment system for my friend. I'd like to become a coder for a big community such as Retro sometime (I'm learning IPB's organization for modding when Team Hedgehog returns in a few weeks), so let me know if there's ever an opening. ;)


Armada hasn't added any friends yet.