I still have the backup files. Is there another program I can use to restore my ipod with?

Not that I know of.

863: They now think you're crazy. Even crazier than before, when you were programming all class and somehow still managed to ace every test.

So basically what we all do. ;-)
865: You have only been a member since August 10,2010, and already have 752 posts.
866: You eagerly anticipate Axe/KOS by hounding Quigibo/SirCmpwn until they give demos. (Sorry guys )

Are there exceptions, though? I remember a year ago the Java applet for IRC on Omni website stopped working completly for many people. After a few java updates, it seemed to work fine, though.

Java doesn't work on everything.  It must have a JVM or Java Virtual Machine built inside to run the Java ByteCode.

So, I just checked out the svn.  The makeFile doesn't build the binary, and the binary that is included with the svn cannot be executed.

This was test on Mac OS X 10.5.8, btw.

I guess maybe they absolutely want the team to code it in Java. Is it for some sort of java classroom and the teacher decided that it would be in java? That said, in the end, if what is produced is great, I think that's what counts the most, not how it was made. Back in 2004 I remember cases where TI-83+ BASIC games were put down by elitist ASM fanboys just because they were written in BASIC, even if the ASM counterparts weren't even as great (except for speed).

True.  In this case, it's basically ease of coding vs. speed requirements.  I program in Java all the time, but usually won't release something in it unless it can afford to be slow, or doesn't do labor intensive things.

0] Java in a nutshell. (http://oreilly.com/)
1] Let's see.  There are a few things.  One is the Object Oriented nature of Java.  That isn't that hard to get used to, though.  Another thing is how everything is structured.  It's not really complicated and explained in said book.
2] Not going to explain classes as it's in that book.  As for the others:
* Private refers to a method or class that cannot be really accessed.  For example, a private method cannot be called outside that class.  Mostly used for internal class stuff.
* Public refers to a method that can be called inside the class, inside the package and outside the package.
* Protected refers to stuff that can only be called inside the package, but not outside.
* Static is slightly complicated, as it requires knowledge of something you don't already know, so here we go.  Say I have a class called MyClass.  Say all MyClass did was store a number.  Not really class worthy as there are "native" things like int to take care of that (Although there is the Integer class, but that's beside the point right now), but nevertheless, let's try it.  So, the "constructer" of MyClass takes one argument.  It can have more than one constructer, btw.  So anyway, to create an "instance" of the class, I do this:
MyClass variableName = new MyClass(5);
Which creates a variable called variableName which is an instance of the class MyClass.  Now then, any method not declared static applies to the object itself.  So, the static method variableName.toString() would really be MyClass.toString().  In other words, static references the class, whereas no static references the object.

Final words: Just read the book. ;-)

Yeah, as alberthrocks said, this isn't dead. I'll look into microUSB, though.

Hmm, is there a way to detect if a BSoD byte is sent? If it is, maybe KOS could cancel it as soon as it's detected...

Not really.  BSOD occurs when the screen is put into test mode.  This would require knowing what bytes were written to the port, which, IIRC, isn't possible.  I think that it could correct it, but it would wast time and space.