Archive for the ‘firsts’ Category

This tutorial isn’t really aimed for anyone in particular, but I assume you already know the basics of object orientated programming. If you already use Eclipse for Java development and know your way around it then you can probably skip this one and wait for part two.

For part one you need to have Eclipse for Java developers (download) and the Slick graphics engine (download) that I will be teaching you how to use in the future.

This tutorial requires that you have at least Java 1.5 installed on your system.
To see if you have the correct version Java installed, open a Command Prompt or a Terminal window, type java --version and press enter. If your computer does not recognize the command, then you do not have Java installed. You can download Java here.

Note to Apple users: Mac OS X already has Java installed.

1. Creating a new project in Eclipse.

In Eclipse, click File > New > Java Project. A window like this should appear.

Enter a name (e.g. “Slick Tutorial” or “Clam Chowder Deluxe”). Then click Finish. You should now see your project in the list 🙂

Note: If you do not see a ‘src’ folder, you will have to add it: Right-click on your project, go to Build Path > New Source Folder… type in ‘src’ and click Finish.

2. Adding Slick to your Build Path

Right click on your project and select Build Path > Add Libraries. You should see this:
Select User Library and click Next


Click User Libraries…


Click New… and type in “Slick” and click ok. Now you will have a new entry in the list of User Libraries.


Click on the newly created Slick, click Add JARs… then navigate to where you extracted Slick, go into the ‘lib‘ directory and select lwjgl.jar and slick.jar then click ok.

You should see the jars added to the list:

Now double-click on Native library location under lwjgl.jar, click External Folder… and select the directory you extracted slick (the root, not ‘lib’) and click ok.

Note: By default the root of the Slick folder only contains Windows 32 and 64-bit dll’s. For other systems, look in Slick/lib and find a native jar that matches your system. Extract them into a folder and select that as your native library location.

Next double-click on Javadoc location under slick.jar, click Browse…, navigate to your Slick folder and select javadoc and click ok. Click validate, it should say the location is likely valid. If all is well click ok to go back to the User Libraries window.

Things should look similar to this:

Now click ok, and then make sure “Slick” is checked.

Click Finish. You should now see Slick in your project, like this:

All done !

In the next installment we’ll get started with the code 🙂

Advertisements

I’m still alive!

Posted: January 9, 2011 by jellymann in firsts

Hey everybody!

It has been a long time since I last posted. Something like a month… or more!

Since then nothing too exciting has happened. This isn’t going to be a long post, I’m just posting for now just to let everybody know that this blog is not dead, it was just hibernating over the summer holidays.

I’ll be blogging more often this year, providing studies and work don’t get in the way. I promise I will not make blogging too big of a priority, which means if I’m not blogging, it means I’m studying or working! Unless I take another holiday break, but I’ll let you know if that happens.

Soon (next few days probably) I’ll post about my project, Retrostyle Arcade. I’ve just recently dug it up and started re-vamping it with a new particle system. Also, this week sometime I’ll take another crack at the Inception project, remember that one? Plus I’ve been meaning to share with you guys my Ubuntu look.

Lekker Kieff 🙂

Overclock a Dinosaur

Posted: October 2, 2010 by jellymann in computers, CPU, firsts, GPU, motherboards, overclocking, tech

Since I messed up my computer with the whole cpu cooler fiasco, I’ve had to go back to my old PC. The specs are as follows:

Processor: AMD Sempron 2500+ @1.5GHz (166MHz * 9.0)
Motherboard: ASRock K7VM3, Rated FSB: 333MHz
Memory: 2x 1GB DDR @200MHz
Graphics: Inno3D GeForce 6600 @300MHz, 256MB @500MHz
Hard Drives (2): Seagate Barracuda 7200rpm 200GB + 80GB (P-ATA IDE)
Optical Drive: LG Super Multi DVD re-writer
PSU:
ISO 300WSwitching Power Supply
Operating System: Windows XP Service Pack 3

For the technologically challenged: it’s crap. These days you can get a fridge with more processing power than this thing. (ok I’m over exaggerating, I’m actually writing this blog post on it within Firefox 3.6.8 while playing music through iTunes 10)

Being used to my “reasonable” Core 2 Duo and HD4870 I was extremely dissatisfied with the above setup. Tests showed a very sad eight frames per second (average) on lowest graphics settings in Crysis @800×600, and less than one frame per second when blowing up buildings with the rocket launcher, physics set at medium. Enabling shadows halved the average frame rate to around four frames per second. Dropping screen size below 800×600 did not make much of a difference, the issue of pixel count giving way to other factors such as shaders and polygon count that may not rely on screen resolution (as far as I know, just speculating here).

Since this old brontosaurus of a pc isn’t really of much value to me (besides sentimental value. I wouldn’t sell it to anyone, although I doubt I’ll get anything for it if I did) I thought I might take a stab at this whole overclocking thing. I’ve overclocked my HD4870 before, but this is the first time I’ll be overclocking a processor.

WARNING!
To all you folks out there who think overclocking is a fun experience (actually it isn’t very fun) and a quick way to get more power without buying new hardware, make sure know what you’re doing before you do it, or just don’t do it. Don’t say I didn’t warn you…

Since this old rig (oil rig?) is old, none of it’s components really output an impressive amount of heat, giving me good headroom for bumping the hertz up a little bit. Even with really lame stock coolers, the processor usually didn’t go higher than forty under load, and the GPU stuck around the sixties, also not changing much under load. I didn’t burn my fingers on the GPU like I always did with my 4870 every time I stuck my hand in the case.
(Temperatures are in degrees Celsius, for all you Americans reading this, convert!)

the Overclock:

The ASRock K7VM3 has a feature they call Hybrid Booster “safe” overclocking. This allows for easy changing of the bus speed within BIOS. Over-enthusiastically I took a huge leap from a bus speed of 166MHz to 233MHz. NOTE: This is a stupid thing to do! Always overclock in small increments, like 5MHz, and every time rebooting and checking up on how the computer does under the new speed. Thankfully ASRock’s “safe” overclocking did not allow my idiotic jump, and promptly reset the bus speed.

I still didn’t quite take the 5MHz advise very well (and by no means am I encouraging this behavior) and increased it in 10MHz steps. And I don’t know if the Crysis CPU Benchmark constitutes as a CPU stability test, but it definitely allowed me to see that the overclocking was working.

The K7VM3 uses jumpers to set the CPU multiplier. The manual shows, in a rather confusing way, where to put the jumpers to get the desired multiplier. By default (with no jumpers) the multiplier is at 9.0, and can be increased (or decreased) in steps of 0.5, up to a whopping 24. I set it to 10.0 and very excitedly switched it on and… It didn’t work…. it still showed 9.0 no matter what I did. Sadly, this specific processor is locked to 9.0 and cannot be changed without possible mutilation. I’m not going to try that!

I stopped at a bus speed of 200MHz, resulting in a substantial CPU clock speed increase of 300MHz to 1.8GHz. Very happy I tested it on Crysis and saw an increase of one frame per second in the CPU benchmark! w00t! 🙂


To overclock the GPU was much easier, but unfortunately not as fantastic. Using RivaTuner, I was able to push the core clock speed by 17MHz (yippee….) and the memory frequency by 14MHz (wow….). Not all that great of an overclock but an overclock nonetheless.



However, I am a little concerned about the current stability of the system. Since the overclock, Firefox has randomly quit (which it never does) twice and earlier the computer reset without warning, Windows later telling me that there was a serious error and had no explanation as to what happened. I’m glad nothing has happened while writing this blog…

I will do some tests with Prime95 soon and will post the results. I don’t know if I want to see the results…

Other tools used: CPU-Z and GPU-Z

Jailbreak! :)

Posted: September 7, 2010 by jellymann in firsts, hacking, iphone, jailbreak, tech

I jailbroke an iPhone the other day.

A friend of mine just got his iPhone 3G fixed, and he wanted to me to jailbreak it for him. I’ve never done it before but I was confident I could do it. After many hours of reading discouraging reviews about people’s iPhones going blank and never switching on, I decided to do it anyway.

Redsn0w seemed a good choice, it seemed relatively simple: plug in your iPhone, click a few buttons, wait a while, and viola! I downloaded redsn0w 0.9.2 because I think that was the most stable version. I wanted to use 0.9.5 and install iOS 4.1 beta but I thought I’d rather stick with something simpler. Besides, I couldn’t find a place to download the exact iOS I needed. So I decided to go with downloading plain ol’ 3.1.2 ipsw.

I thought I had to use iTunes 9 to do all of this but it turns out iTunes 10 still does the trick, despite it’s disgusting new icon (bleh!). I was afraid that Apple disabled shift-clicking on the update button but I was relieved to see I could still load a downloaded ipsw.

Redsn0w is quite simple really. Load the ipsw, then it processes it. Plug in the iPhone, switch it off, click a button, hold down some buttons to get into some DFU mode or something, let it do it’s thing, then after a painstaking length of time the jailbroken iPhone will now be ready to play around with 🙂

On the topic of Cydia, the little app that comes with jailbreaking an iPhone, we didn’t seem to get it going correctly. Damn thing couldn’t download half the stuff. I guess the repositories are down? Deprecated? On strike? Eaten? I don’t know. Too lazy to find out at the moment but maybe some day I’ll check it out.

Note to all people new to jailbreaking: be patient, and try not to throw your iPhone at your computer screen.

I should be studying now, but thanks for reading. Happy jailbreaking! 🙂