Site updates upcoming.

A few changes are impending.

For one, the blog will be getting a new set of clothes. Twentyeleven is great, but it makes me look lazy, like the blog isn’t that important.

For another, I’m working on a little project called “re/g/”.
It’s basically a technologically-centered imageboard with a more tolerable signal-to-noise ratio.

Also, now that there’s plans to make webOS open-source, I’m going to be experimenting and tinkering with it. Porting it to other devices is one thing I’d like to work on.

I’ll close with a link to the XDA thread for the Android-on-Veer effort.

sourced from /g/ volume 1: How to port Wii Ocarina codes between regions.

OP 12/30/11(Fri)07:05 No.21927857

    >>21927769
    >Ported a PAL Wii/Ocarina cheat code to an NTSC game.
    I've always wondered how one does this.

>> ARMv7 !gnXDAg2iL2 12/30/11(Fri)07:16 No.21927987

    >>21927857
    It's simple.

    Make a RAM dump of both the PAL and NTSC (hereafter "source" and "destination", respectively) versions of the game, virgin (no mods/cheats applied).
    I won't walk you through that, but it involves Gecko OS and a USBGecko adapter tool.
    You'll have two files from each dump - named [gameid]_DUMP80 and _DUMP90.bin.

    Now look up http://wiibrew.org/wiki/Memory_Map and find the offsets in the Source ocarina code. Match them to the right file (dump80 is MEM1; dump90 is MEM2. Most often the codes are loaded in MEM1 space.)

    Use the win32console program vbindiff (or your gnu/linux equivalent), load up the two dumps, and use the Go To command to visit the offset in the source dump. In the dump, the beginning of MEM0 will be based at 0, so compensate for this mathematically.
    Then use the Search/Find command, in Hex mode, to find the code at that offset. Try searching for eight bytes worth, if not four.

    If they now match up (all or most of the red is gone), look at the offset in the destination dump, and use that offset in the new (destination) code.

    Sometimes it might glitch, due to some resources being different between regions, but it works for the most part.

Touchpad get.

New development challenge: Plan 9 on the Touchpad/”Tenderloin”?
Maybe. We’ll have to wait and see. Internally, webOS is a very capable Linux (minus gnu) system as it is.

Hackin’ away~

Pictured: Veer, and two VZ Pixi+'s

Pictured: Veer, and two VZ Pixi+'s

It’s about time I got to doing something.
First hurdle: Android. It’s something of immediate use to the community, and isn’t as hard to port over as, say, like Plan9 or Haiku.

Veer4G get.

Just came in today. Awaiting the touchstone dock et. al., should be here soonish.
Trying to unlock it – got the USB passthrough done, but it won’t show the serial device to the unlocker script – because, as far as I know, it doesn’t exist. Damn ubuntu.

Next course of action, is getting a proper dev computer up and running, and researching more about its Linux kernel, drivers, and other miscellany.

UI-wise, I might have to implement gesture controls, for the “gesture pad”, but until then, I can deal with onscreen buttons.

This is why we can’t have nice things.

http://lists.freebsd.org/pipermail/freebsd-chat/2011-November/006642.html

Images of daemons strike fear into the hearts of many as The Devil hacks into the Internet. More at eleven.
Continue reading ‘This is why we can’t have nice things.’

So this is it.

I’ll be posting on this blog in the future to keep track of projects, development, and experiments.

If you’re from /g/, howdy!