RogueSpear's Runtime Collection

[RogueSpear]

20100403

• Updated the .NET 3.5 Lite installer and addon
• Updated Java Runtime Environment to 6.0 Update 19
• Removed the DirectX installer
• Removed the Silverlight installer
• More updates and announcements to come soon

[lindiro]

When I install the Java update 19 it says it's update 18 while it's installing. Is this something you can check?

[RogueSpear]

I suppose it would have helped had I uploaded the new file. Fixed.

[lindiro]

Thanks for the quick response.

[GrowBigTrees]

Hi Roguespear,

Both with 7zip and winrar, I get errors when extracting the msi for J2SE: (version 6.19 as well as 6.18)

7-zip v4.65: Unsupported compression method for 'Data1.cab', 'J2SE.msi', 'java.reg'
Winrar v3.61: Unknown method in 'Data1.cab', 'J2SE.msi', 'java.reg'

Thanks for your work!

[user_hidden]

Hi Roguespear,

Both with 7zip and winrar, I get errors when extracting the msi for J2SE: (version 6.19 as well as 6.18)

7-zip v4.65: Unsupported compression method for 'Data1.cab', 'J2SE.msi', 'java.reg'
Winrar v3.61: Unknown method in 'Data1.cab', 'J2SE.msi', 'java.reg'

Thanks for your work!

update your winrar to 3.93 and/or your 7zip to latest beta 9.13.
reason is the new archives are compressed with lzma2 compression which is not compatible with your older versions.

[dumpydooby]

I know you have Java Update Scheduler (jusched.exe) disabled, but do you disable Java Quick Start (jqs.exe) in your release of JRE?


I have my own build that I maintain, and I do disable JQS on it, but I noticed that you don't indicate in your post that it has been disabled, so I'm wondering if there's any merit to keeping it enabled.

[RogueSpear]

I leave it enabled by default in the installer. I had found a way to actually remove it from the installation package completely and did so with Update 15. The problem I discovered later is that it would not properly uninstall. Subsequent fiddling around with the .msi didn't prove useful either. JQS seems to hide everywhere in that installer.

So at work I just disable the service via GPO. For non-domain members, like out patrol cars, I disable the service somewhere in the RunOnceEx with the ScriptPack (I think with a simple reg entry but I don't even remember right now).

What's nice about disabling it with group policy is that if a user with local admin rights to his/her particular workstation decides to enable it for some reason, it will again be disabled on the next GPO refresh which I think is a 20(ish) minute interval.

[RogueSpear]

It seems that .NET 4.0 can be installed without .NET 3.0 or 3.5, but applications that depend on .NET 3.x will not run with only 4.0 installed. It also seems that you cannot install the .NET 3.0/3.5 Lite package I made and then install .NET 4.0 without a reboot in between. So what this all boils down to is that I'm not going to be making a .NET 4.0 installer since user_hidden's works rather well for me. What I do is just insert it into one of the RunOnceEx slots for the second run in the ScriptPack.

[newsposter]

I actually like JQS to be installed and running on my machines. JQS is relatively lightweight in terms of disk footprint and system resources and makes quite a bit of difference on how 'snappy' a web browser appears to be when downloading and running java applets.

[dumpydooby]

I leave it enabled by default in the installer. I had found a way to actually remove it from the installation package completely and did so with Update 15. The problem I discovered later is that it would not properly uninstall. Subsequent fiddling around with the .msi didn't prove useful either. JQS seems to hide everywhere in that installer.

So at work I just disable the service via GPO. For non-domain members, like out patrol cars, I disable the service somewhere in the RunOnceEx with the ScriptPack (I think with a simple reg entry but I don't even remember right now).

What's nice about disabling it with group policy is that if a user with local admin rights to his/her particular workstation decides to enable it for some reason, it will again be disabled on the next GPO refresh which I think is a 20(ish) minute interval.

When you remove it completely, you have to instantiate the MSI with a switch to get it to uninstall properly. You can find a list of all of the switches for Updates 12-19 on AppDeploy. Add these as a custom action to your installation routine and old versions will automatically be uninstalled when you install with the MSI containing those CAs.

But to disable it is super simple. Just execute:

Code: Select all

%ProgramFiles%\Java\bin\jqs.exe -unregister

I might have the path wrong, but that's it.


Anyway, yeah, I was mainly wondering why you keep it enabled, and I got the answer I was looking for. Thanks pal.

[dumpydooby]

It seems that .NET 4.0 can be installed without .NET 3.0 or 3.5, but applications that depend on .NET 3.x will not run with only 4.0 installed. It also seems that you cannot install the .NET 3.0/3.5 Lite package I made and then install .NET 4.0 without a reboot in between. So what this all boils down to is that I'm not going to be making a .NET 4.0 installer since user_hidden's works rather well for me. What I do is just insert it into one of the RunOnceEx slots for the second run in the ScriptPack.

That's not entirely correct. 3x applications should USUALLY (emphasis there, because according to Microsoft, 4x doesn't quite do everything 3x does, but it can do most of it) run *IF* the programmer checks for functionality rather than availability of hardcoded files. The problem is that MOST programmers do it the wrong way.

In the web world, that's similar to checking "user agent" and forbidding, say, IE because it doesn't support "getElementByClassName," whereas proper coding would simply check for the availability of the function rather than checking for browser version. (I only speak web languages, so sorry if you can't relate to my example. lol)


As for .NET Framework 4.0, I've decided not to install it yet. I may not ever deploy XP with it.

[RogueSpear]

That's not entirely correct. 3x applications should USUALLY (emphasis there, because according to Microsoft, 4x doesn't quite do everything 3x does, but it can do most of it) run *IF* the programmer checks for functionality rather than availability of hardcoded files. The problem is that MOST programmers do it the wrong way.

Yep, same old song and dance that I was going through with .NET 1.1 and 2.0 until quite recently. Luckily the offending software vendor just recently updated their product and now compile it against 2.0 so I don't have to worry about it. But for years I had to keep .NET 1.1 maintained on about four workstations just for one really crappy application.

[dumpydooby]

The crappy ones usually don't think to obfuscate their code. They should be pretty easy to decompile and compile again on your own. It's generally pretty easy to decompile .NET stuff. I did it when I was trying to learn how to write a "real" programming language; trying to migrate out of the PHP/web world.

[kane3162]

meh, me myself and for anyone who asks/ i help, I always install the latest .NET 1.1/2/3.5/(and soon to be)4

a simple task scheduler task automates this process for me, and after the 4th restart it removes the tasks from task scheduler... so i start it, walk away and then come back and they are all installed! goodiez!

but all my packages are outdated... I should update them sometime