Leaderboard

Java Runtime Environment 8 Update 25 Description Java allows you to play online games, chat with people around the world, calculate your mortgage interest, and view images in 3D, just to name a few. It's also integral to the intranet applications and other e-business solutions that are the foundation of corporate computing. Version: 8.0.250.18 Addon Release Date: October 31, 2014 Java Console created in: Control Panel Uninstallable: Yes Credit: *Reaper* NOTE: Due to the download server limitations, we can no longer upload .exe files. So after you download these just unzip the downloaded file to get your silent installer. Note: Add these as silent installers... No Switches needed! x64 - 58.1 MB - 7e7361c74c670d5b1d6b7c994d28925a x86 - 27.0 MB - cd11c905cde4fdf7671f7413c5d6128b Enjoy!

Anybody please create a unattended answer file for windows 8.1 (32bit and 64bit) for my following requirements: 1. during installation windows 8.1 should always ask me to set time zone and time. 2. secondly set screen refresh rate =75Hz so that i can insert this file into image.

In addition, and as a final remark on my behalf (it is time to get back to my real studies, though it was fun and reminded me to the time of 2005 where I was one of the minorities who bought xp x64 and where often forced to get used to modify .msi's with Orca) - I tried it again with the (official technet) sysprep way... the reason why WinToolkit recognized my first preped image as being corrupt was that I have chosen a custom name for the image.... still now, and after I've named it right, and though simply building a .iso via WT from the syspreped .wim worked like a charm (the get-package information afterwards was the same as for a real sp1 install-media), it failed when I tried to integrate IE11 and its prerequisites. That doesn't worked out well - WT integrated fine, the install resulted in failures which may well be searched in this forum for the early times of IE11 and its integration. So i am not sure if I missed some KB or if it ain't be possible to use WT on a syspreped .wim (which makes no sense IMHO, so my guess would still be a fault in my procedures - and that one may include that I where using a WinPE.iso handed over to the VM that where build with the current ADK release for Win8+; I used that because it is much easier to apply the dism commands (/capture-image) to build the .wim then using the old variant with imageX). As said, I still think that it is possible (else all technet sysprep how to build an oem/multilingual media, how to deploy sp1, etc. descriptions wouldn't make sense; At least for the sysprep way). In the meantime where the vm(s) where occupied with their install I checked the MD5 sums of the KB976902 files with their corresponding parts of KB976932 (SP1) and there where no differences to be found (haven't checked all of the files), so it should - in theory be possible - to get along that way to a working (and future proof) image... But as the OPs question (OEM based Win 7) and my curiosity about Dreamsparks PreSP1 Server 2008 R2 .img are just a minority in cases that may be neglected in the development of WT (or the Foolproof assignments/modules therein (which in my experiences make up 3/4 the time in the development of a GUI based project)) I just give up with trying any further (and will continue with my real work/study again ).

And keep in mind, that the OEM key from the sticker may be a "one-time only" key - as in using it, the activation will be bound to the hardware it is used on (I am mostly using SystemBuilder Variants(*1) for my system (as I build 'em myself or buy 'em without OS) and there thats not a problem (in short: I simply lack the Win7 OEM experience)), but as far as my knowledge has grown on the subject a vital change in hardware may or may not be activatable via phone or strictly license termin speaking may simply be rejected - so I see a reason to the "why someone will stick to autoactivation as long as possible", because then the OEM key could def. be used on changed hardware (if it is the first time this key is used - so why waste it on the OEM Hardware where its not needed) with just using the online activation. I am really not sure on this one, the MS specific sides (technet, etc.) are AFAIK strict on this one-time bound between key and hardware, other sides claim that an activation via phone is still possible. P.S.: with Win8 this whole OEM/Preactivation Discussion is Void - the new scheme where the "to be activated" key for OEM Systems is kept in the BIOS is a total different matter *1: Ok, from a German Point of view and an old Sentence about the resale of OEM licenses, MS SB variants where (AFAIK) the result of that verdict (as a different model to pure OEM license (like from Dell or such); SB (OEM) license is nowadays what is nearly 100% of the time sold to the customer here in germany (and I know only a few (real minority) shops who are actually offering the real retail)... And I am not sure what that means for reactivation on different hardware or such, but according to magazines like the C't (not talking Win8+ here) SB licenses under our law should be reactivatable under new hardware (but that may well be just an urban legend).

Luckily the release dates are stored in the update files themselves from Microsoft so was easy to implement. Done.

Man! it made it just in time, I see!

Just my thought... Try running inf in RunOnce which support REG_EXPAND_SZ and you can use variable instead of hardcode path like C:\PROGRAM FILES. E.g In case of dual boot OS, something the OS might not install to C: drive. It could be D or E drive. In Everything Search Engine, post 11, I have a simple batch to create RunOnce key using REG_EXPAND_SZ variable.