How to Increase the Memory Limit for 32-bit Applications in Windows 64-bit OS

Most of us are now probably using a 64-bit Microsoft Operating System like Windows 7 x64 or Windows Vista x64, which allows the computer to address more than 3GB of RAM. Did you know, however, that any 32-bit applications you run are still limited to making use of only 2GB of RAM? This includes many games and probably the version of Microsoft Office you have installed, unless you specifically opted to install the 64-bit version.

You might wonder why this is a problem. Well, obviously if your system has more than 2GB of RAM, it’d be great to allow your applications or games to make use of it. Furthermore, some applications actually crash when they hit this limit, or start popping up boxes with out of memory errors. If you work on large excel files (500,000 rows+) then you’ll know what I’m talking about.

The Solution

Thankfully, there’s a solution! A great coder by the name of Daniel Pistelli has written a little patching application that will modify your 32-bit programs, and allow them to address up to 4GB of RAM. It’s important to remember that this utility is only useful if you are running a 64-bit OS. If you don’t know what I’m talking about, then here’s an easy way to check:

1. Go to Control Panel, and click view by “small icons” in the top right hand corner
2. Click System
3. As per the image below, next to System Type, it should say 64-bit operating system. If it doesn’t then this utility is of no use to you.

The second thing to remember is that this utility can only be used on 32-bit applications. If you are unsure if an application you are running is 32-bit, run task manager by pressing CTRL-SHIFT-ESCAPE. Click the tab for processes. A list of currently running programs will load. Find your application in the list, and look to see if it has *32 next to it. The example image below illustrates what I mean.

Using the patch

Assuming that you’ve followed the previous two points and now wish to patch your 32-bit application, first backup the executable file of the program you wish to patch. If the patching process fails, or if you need to download an update for the program you are patching, you may need to revert to the original file. Remember, you only need to backup the executable file for the program (i.e. the file with a .exe extension), not the entire program folder itself. Once you’ve done this, download the patching utility from here. Run it, and it will ask you to select your program. Simply select the executable file you wish to patch and the utility will work its magic. Upon completion, it will ask you if you wish to patch another file. If you do, go ahead, if not, quit!

Conclusion

If all goes well, your application should now be able to make use of up to 4GB of RAM. Obviously this will be most useful for resource-intensive applications, and you’ll probably see the greatest benefits with games. Some productivity software will also benefit, assuming you aren’t utilising the 64-bit versions of these (e.g. Excel, Photoshop, 3D Studio Max, and so on.)

Tq so much.  http://maketecheasier.com

Programming for Android, Part 1, Installing everything you need.

How to using the WorldWind Java 0.2 SDK in Netbeans IDE 7.2.1

• Visit http://goworldwind.org/ and do some research about what WW really is and why you should use it.
• Follow the getting started tutorial to get familiar with the examples.
• Open NetBeans and create a New Project using the "Java Application" template. Fill in the required details but uncheck the 'Create Main class' box. Your new project should reside in a clean directory.

• In the src you downloaded from the release site and extracted, rename WorldWind's'build.xml' to something else (build_ww.xml) and copy all the WorldWind's unzipped content to your NetBeans project folder so that the src folders overlap. You should end up with a folder structure very similar to the WorldWind unzipped folder, plus a'nbproject' and a 'test' folders. The 'build.xml' file is the one created by NetBeans, not the one that came with the zip (which is why we renamed it earlier).
• From NetBeans, you will notice that some folders/classes are marked with a red exclamation mark. We now need to tell the project about the required libraries. Right-click your project's node and select 'Properties' (typically the last menu item). Select the 'Libraries' node from the Categories tree and press the 'Add JAR/folder' button on the right. Keeping CTRL down, select the 'gluegen-rt.jar','jogl.jar', 'gdal.jar' and 'plugin.jar' that are now inside your project folder. Click 'ok'.
• 
  

                                             

• You can now run any of the examples by right-clicking them and selecting 'Run File' from the contextual menu.

Thanks. ;) http://forum.worldwindcentral.com/showthread.php?t=32347

Extrude in TatukGIS Editor 3

How to using the WorldWind Java 0.2 SDK in Eclipse

Step 1: Download and unzip

Grab the code from sourceforge, it's a zip. Unzip it someplace. I unzipped it to c:\software\dev\worldwind.release You'll see that path later.

[edit]Step 2: Start Eclipse and create a New Java Project

Start Eclipse and to to File -> New -> Project. Choose a Java Project.

[edit]Step 3: Point to the existing source code

In the new project wizard, make sure to select "Create project from existing source" and point to the unzipped directory. Then press "Finish."

Done! That was easy. Not like the steps needed for the 0.1 code! Major kudos to the NASA Java team for including JOGL and having a nice directory structure that allows Eclipse to interpret where things are.

Checking the project's settings, we see the libraries have been included:

Here's a shot of Eclipse, running the two demo apps that come with it, worldwinddemo.AWT1Up in the foreground, worldwinddemo.BasicDemo in the background.

To run one of these apps, navigate to src/worldwinddemo/ on the right hand Package Explorer and right click on one of the java classes. In the context menu that appears, go to Run As... and choose Java Application.

There're some interesting things here, first there's a floating placemark (neat), second there's a GML line (also neat) in AWT1Up, and third zooming is all shaky and wierd (bad).

Here's the snippet that produces the icons along the equator, with a 2m meter ones at every 90.

private IconLayer buildIconLayer()
{
   IconLayer layer = new IconLayer();

   for (double lat = 0; lat < 10; lat += 10)
   {
       for (double lon = -180; lon < 180; lon += 10)
       {
           double alt = 0;
           if (lon % 90 == 0)
               alt = 2000000;
           WWIcon icon = new UserFacingIcon("images/32x32-icon-nasa.png",
               new Position(Angle.fromDegrees(lat), Angle.fromDegrees(lon), alt));
           icon.setHighlightScale(1.5);
           icon.setToolTipFont(this.makeToolTipFont());
           icon.setToolTipText(icon.getPath());
           icon.setToolTipTextColor(java.awt.Color.YELLOW);
           layer.addIcon(icon);
       }
   }

   return layer;
}

Thanks http://www.worldwindcentral.com/wiki/WWJava_in_Eclipse