CB JRE Platform update/exe modifications (Java 7u25/ .exe LAA)

So, after testing for a few weeks, I've concluded that updating the java from 6u11 to 7u25 and flagging the cosmic.exe application to large address aware (LAA) for memory seems to be relatively stable, so I'm releasing what I've done so far.  There's been a previous posting on updating java, but the links are dead and go through some ad site so I figure I might as well repost.

Contents:
-Java v7u25 - Same copy you get from oracle, upgrades the v6 gc to the new v7 version with more aggressive handling, various performance fixes (Note, may make cb worse or better depending on your computer), jvm.dll has been CRC modded to match the original version
-CRC modded jvm.dll - The only changed part of the fix, it has a edit in part of the commented portion of the dll to match the old CRC to prevent the launcher from erroring
-LAA flagged exe - Only thing changed is that the LAA on the exe is now flagged - May help in memory management - (Note:  This is more likely to be outdated quicker so use at your own risk)


DLs:
7u25 JRE with client jvm CRC patched:
http://www.mediafire.com/download/8f89p958y4j6o2c/CB_jre.zip

Just the 7u25 client jvm.dll:
http://www.mediafire.com/download/919fhy5p7yr197b/jvm-dll.zip

LAA flagged .exe:
http://www.mediafire.com/download/6w6tg411t12v0fn/cosmic.exe


Installation directions:

Standard cheesy disclaimer:
!!Backup your copy of CB before using.
!!USE AT YOUR OWN RISK (I am not responsible for your computer exploding, however unlikely it may be, nor c$ complaining about your version of java/exe)

JRE Installation:
1)  Rename your old JRE folder in the /cosmicbreak/ folder to something else like "jre-old" to create a backup to revert to in case it blows up
2)  Drag and drop the new JRE folder into the /cosmicbreak/ folder

JRE jvm.dll installation:
1) Download java 7u25 from the oracle website
2) Backup jvm.dll (In the /jre/bin/client/ file)
3) Replace jvm.dll with provided jvm.dll

LAA fix: (Current as of 8/27)
1)  Backup cosmic.exe (In the /cosmicbreak/programs/ folder)
2)  Replace cosmic.exe with provided cosmic.exe

Credit to:
Whoever thought of it in the last post
Macro for bringing it up that I should update said fix for people who aren't programmers




Known effects:
GC doesn't hit as hard and freeze you for 3-4 seconds
Faster garage times
Faster stage loading times
(Potentially more responsive action handling)

Known problems:
GC may trigger more often, cause more freezing in lower end pcs
???

I might try it but "might freeze more" doesn't sound so pleasant. I'll check tomorrow.

Well, it removes non-lag based freezes completely if your hardware is up to spec. So it's not all bad.

I'll test it when I wake up.

What program did you use to decompile/recompile the jvm.dll? Resource Editor, PE Explorer, Reflector or something else?

What program did you use to open and edit the Cosmic.exe file to turn on LAA? Would you, please, elaborate on the process of how one would accomplish this?

I want to give this a shot, but, I'm the, "trust no one," type, and would rather do it myself. Also, having the ability to reproduce this every Thursday would add a great deal of longevity to this improvement.

AnTi90d wrote:

What program did you use to decompile/recompile the jvm.dll? Resource Editor, PE Explorer, Reflector or something else?

What program did you use to open and edit the Cosmic.exe file to turn on LAA? Would you, please, elaborate on the process of how one would accomplish this?

I want to give this a shot, but, I'm the, "trust no one," type, and would rather do it myself. Also, having the ability to reproduce this every Thursday would add a great deal of longevity to this improvement.

I simply used a hex editor to look at the files to find a safe point to insert, then I modified them by directly changing bits in the file by writing a python script (although you can pretty much pick whatever programming language you want).  I think that dev random guy on the other post has the right base plan.  The past projects simply modified the last two hexes, so I assume that might be safe as well, but I don't see it as safe as a comment mod.

As for redoing the project, CB typically does not touch/overwrite the files, as the JRE has not been touched since the start of CB, so it is rather stable.  All you have to do is change the dll CRC every time java itself updates if you wish.

The LAA flag is something you can check with other programs and is a common .exe feature that quite a few programs should allow you to automatically find/change, although I don't use them.  Otherwise, just find the setting inside the EXE and make a script in whatever language you feel like to write to them.

Thank you, very much.

I did some more reading on the LAA switch. To benefit 32 bit operation systems, you have to set a switch in your boot.ini file. (Some people have had issues with this in XP 32 bit.) The LAA switch basically tells your OS to use more than 2GB of ram for the program. 32 bit operating systems are set, by default, to only use 2GB for programs and the rest for system use, hence why you have to alter both your boot.ini file and the .exe file. Since the max amount of RAM a 32 bit operating system can even recognize is just under 4MB, any benefits will be marginal, at best.

The page that had the most pertinent information also had a script that someone created to modify exe files and turn on the LAA switch with a nice GUI. http://www.techpowerup.com/forums/showthread.php?t=112556

I'll try this out, sometime tomorrow.

Tested it, didn't notice any real difference.