Legolash2o

The Language Pack Converter tool converts your langauge packs from the .EXE form to the .CAB form so you can use them to integrate into your Windows image, using either the All-In-One Tool or another program from a different developer.

Step 1: Add the Langauge Pack(s)
Click the Add button, browse for your language packs.exe
Step 2: Starting the process
Press the Start button and select the folder you want the .cab to go
Step 3: Wait
Items that go Green mean they have converted successfully, that's pretty much it.

If i am correct, you you can use virtualbox, to install windows 7, once reached the place where you enter a username,
You use shift+ctrl+f3 to enter admin account and skip everything else,
Install everything + do the updates you want, after you have done this make sure you enable geniralize or what it was called.
And restart, you will get the language option if you got multiple languages installed + the ability to choose username and what not.
 
But do not continue just shutdown, mount the image and commit it to the install.wim
 
This is not a complete guide, have not used it myself fully. but i think he means this.
You will end up with a iso with everything you added to the install in virtual box.
 
Though i do not know how it go's about with system specific updates as drivers etc.

haha thanks. It's programming so I'm definitely confident about that exam. Even if it is C++

express cab contains only the update manifest files + xml file.. those are used by WU to identify the original package contents and to determine what components of it are needed for the system so it download them only
 
i.e.
if the update are multilingual, it will download only lang resources matching your system
 
only WU knows how to handle this mechanism
so, express cab are useless and cannot be used for integration

Bad News
My coursework is nearly done, just need to compare it with peers to see if I have missed anything. Once done my first task will be to update the Exclusive ISOs. I will be spending about 3/4 of my time revising whilst fixing bugs in Win Toolkit with the other 1/4
 
Good News
From 1st June 2014 to May 2015 I won't be going home to work during the summer like I did last summer so I will be working 9am-5pm pretty much every day on Win Toolkit for my Final Year Project. This won't be just coding though, The initial month or so will be research and taking advantage of all the new features such as multi-threading and .NET 4.5
 
Since I won't be working, all donations will DEFINITELY be appreciated.

Introduction
So as you may or may not be aware. Win Toolkit v2.0 has been accepted to be my final year project. That means a year and a half of researching, re-designing, re-coding and re-testing). It will require me to start the project from scratch taking in lots of researching, coding practices and everything I've learnt in the first four years into one beautiful final product.
 
At the moment the current Win Toolkit code is a big mess. It has a mixture of old rubbish code, sorta ok code and new code. Unfortunately that means adding your requests is really hard because as you know, it leads to quite a few bugs from just forcing it in there. Some of the big tools such as the All-In-One Integrator, has become so hard to manage that it scares me just thinking about adding stuff to it. So, saying all that. A complete rewrite is required.
 
The main effort will be focusing on the design and planning, focusing on efficiency, maintainability and taking advantage of the latest tools such as .NET Framework v4.5. This is crucial for making a high end product. Planning is key!
 
Feel free to post any questions. Anything which isn't on topic will be deleted.
 
Research
I hell of a lot of research is required, as I still have a lot to learn. In two hours alone, I learned so much about multi-threading. I even took the time to recover subjects in more detail such as abstract classes, constructors and best of all LINQ/Lambda. The potential of LINQ alone is huge but unfortunately, it's not implement much in the current release at all.
 
I also have to relearn Windows Presentation Foundation (WPF), as I plan on moving to that instead of Windows Forms to create an even better GUI. So far on my list of research material is:
.NET 4.5 features Threading (Tasks & Paralellism) WPF - Windows Presentation Foundation WIMGAPI - Remove the need for imagex Extraction - Remove the need for 7z Automated Testing Languages List will most likely grow. Maintainability and Efficiency
At the moment, the code is one big heap of mess with a low maintainability score and very high Cyclomatic Complexity rate. Adding new features and request, has become such as hard task that most of the time it's not even worth bothering, which is why not many requests get done.
 
Don't get me wrong, I know all my code of by heart pretty much and understands what it does, even without a single line of comments but it's still hard to add features. I absolutely need to focus on making the code as easily read as possible AND also efficient. Both of these together will create one hell of a program. Before I start on a feature or any code at all really. I need to sit back and look at it from a different perspective. Heck, even get a pencil and some paper out if I have to!
 
At the minute Visual Studio rates my Maintainability Score and Cyclomatic Complexity rating for the All-In-One Integrator as 31 (higher better) and 2,508 (lower better) respectively. However, with the new error logging system. It gets a rating of 80%+ and a cyclomatic rating of 4, which I think is impressive. If I took a step back and look at it again, I'm pretty sure I can get it to 90%+. The point is, the new system is so much easier to read and understand. I can add anything to it so easily, I could do it in my sleep. With the All-In-One Integrator on the other hand, just scares me thinking about changing even a tiny change.
 
Error Logging Experiment
Believe it or not error logging is an absolute critical feature that needs to work 99% of the time. Before the experiment, error logging worked about 10% of the time, with the other 90% of error logs being completely unreadable and therefore pointless. Using the latest code and practices I've learnt. I made Error Logging v2.0 which works 99% of the time, producing nice readable and detailed reports which you can view at your discretion. Also as more and more logs get moved onto the new system, you will see more details about the issues you are seeing. Better yet, they are in YOUR language! The new error logs system was a huge success and I'm proud of that.
 
The new EL2.0 system only took 5-6 hours of planning but it was done with minimal code and it worked like a dream from day 1. This just shows what happens when I sit back and think about things rather than just the usual hack and patch method to just get it working. Imagine the potential if the rest of the program had the same make-over!
 
.NET Framework 4.5
I've always been behind on the releases. Originally I used v2.5 when 3.5 was available. Currently I'm on v3.5 when v4.5 is available. I am eagerly wanting to jump to the latest release and take use of all the new features. v4.5 has a lot more features compared to 3.5, the biggest one of all is threading. I can't even begin to list them all.
 
Win Toolkit v1.4.xx will remain available on .NET Framework v3.5 for XP users. It will only have bug fixes.
 
Languages
Having a version of Win Toolkit has been requested for years. Since the program will be written from scratch, I will definitely explore the idea of having this in from the beginning. So hopefully the first version you test will have this feature. This will definitely make a lot of people happy.
 
Multi-Threading
Another focus will be on taking advantage, in a positive way, your computer’s hardware. Since computers these days are having more processing cores, I thought it’s about time Win Toolkit took advantage of that. Win Toolkit at the moment only uses a maximum of two threads. For example, in the All-In-One Integrator it uses a Background Workers to do the actual tasks whilst the GUI thread sits there doing nothing apart from keeping the GUI responsive. So in actual fact, Win Toolkit isn’t really multi-threaded at all. Even worse still, I’ve been told Background Workers are actually really bad for performance.
 
Imagine the potential if Win Toolkit used all of your cores instead of just the one. Integrating difference things at the same time. Reducing the amount of total time required. So this is where ‘Tasks’ and ‘Parallel’ come in. Tasks are a completely new feature of .NET 4.0 with huge enhancements in .NET 4.5. Tasks are absolutely powerful. Tasks will be used to do the split up each individual task whilst Parallel will be used within the tasks themselves to work on more than one file at a time.
 
If you have have a multi-core processor. The advantages you will gain are huge. Lets say, for example, you have an 8 core processor. Thats x8 the performance. In reality, it will be more like 6-7 times the performance but I won't complain about that at all and I doubt you will either. Check out the results of my multi-threaded experiments here.
 
Win Toolkit v1.4.xx.x All-In-One Integrator
At the moment with just one thread, the tasks are queued.
Mount > Updates > Drivers > Removal > Tweaks > Silents > Themes > Wallpapers > etc.. > UnmountAs you can see, it can take a while to get to the last task especially since most of the work is with Drivers.
 
Win Toolkit v2.x.x.x All-In-One Integrator
The new task method will give each one of those their own thread so all of them will be done at the same time. The image will be mounted, and then once mounted a task will be assigned to add Updates, Drivers and Component Removals. AT THE SAME TIME, your wallpapers, custom files, gadgets, theme packs
 
Stage 1:
Whilst Updates, Drivers and Components are queued under one task due to the fact they can't be done at the same time. Every other task will be given their own thread and will be done in the background.
MountMain Task: Updates > Drivers > Component RemovalTask 2: WallpapersTask 3: ThemesTask 4: GadgetsTask 5: Copy Silent Installersetc..Stage 2: These are things which require the registry but are locked during the DISM tasks.
Task 1: TweaksTask 2: Add Silent Installer entries.Task 3: ServicesUnmount
 
Windows Presentation Foundation, WPF
At the moment Win Toolkit uses Windows Forms which is very dated with controls which look they are made for Windows 98. WPF is the latest in GUI design, with all new controls, features, options and so on. ListViews for example, are sort-able by column built-in. It will made the app look more modern and give me much more control over the design. The bad news is, it's completely alien to me but I'm going to enjoy the learning experience so it isn't really bad news at all.
 

Rate of WPF adoption 2005-2007
 
As you can see, the rate of adoption for WPF is huge and that was back in 2007 so I'm definitely behind the times. Some say WPF is dead, I disagree but either way it's newer and I want to learn something new.
 

This is just a sample design of the new startup screen. Still has a tiny bit more work. Mostly just experimenting with WPF.
 
Automated Online Database
To save time, there will be a mostly automated SQL database which will contain if a description of an update, if it's LDR/GDR (update.mum present), any known issues and if it can't be integrated or not. This should save time in extracting files, HDD usage and immediately make it so I don't have to release a new version when a problem update appears. It may also include it the update is superseded or out-of-date.
 
Dependencies
Win Toolkit relies on quite a few external tools which makes it size pretty big. It currently has imagex, 7z.exe, 7z.dll and some others built-in to the main exe which has made the exe itself a lot larger than it should be. I plan to hopefully get rid of imagex and replace it with WIMGAPI but also 7z with my own code. This will mostly benefit those on slow internet connections.
 
Component Removal
The vLite tab will be completely removed. Minor items such as removing themes will be moved to the normal Component Removal tab but more complicated ones such as 'Speech and Natural Language' will be removed. I will be sticking to the official methods of removing components.
 
Testing
Yes I admit, I can rush things and can leave or add new bugs because I didn't do enough testing. In Win Toolkit 2.0, I will be using automated testing. With just a click of the button it will automatically test the product and look for things which did work and no longer do. The automated testing is another key part of making Win Toolkit a high quality product by hopefully decreasing the amount of bugs.
 
As new bugs appear, I can add more testing to prevent it from re-occurring in the future. Unfortunately however, not everything can be tested automatically.

I should be releasing a build tomorrow night with the updated links to the ISOs. I will take a look at the bug you mentioned and a few others tonight

Bad News
My coursework is nearly done, just need to compare it with peers to see if I have missed anything. Once done my first task will be to update the Exclusive ISOs. I will be spending about 3/4 of my time revising whilst fixing bugs in Win Toolkit with the other 1/4
 
Good News
From 1st June 2014 to May 2015 I won't be going home to work during the summer like I did last summer so I will be working 9am-5pm pretty much every day on Win Toolkit for my Final Year Project. This won't be just coding though, The initial month or so will be research and taking advantage of all the new features such as multi-threading and .NET 4.5
 
Since I won't be working, all donations will DEFINITELY be appreciated.

All my coursework is done. Got some revision to do and then I'm home free to program Win Toolkit for a year with virtually nothing in the way

Just an update. Still doing coursework. If I don't pass this coursework then the Final Year Project idea will go right out the window
 
I will try and devote a night where I check out the bugs so not all bad news

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. 
 

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

The latest RunOnce issue is finally fixed in the latest test build.

EVRIKA !
 
with 1.4.37.10 Autounattend Works if you put it in %DVD%:\soucers folder !
 
Good luck to everyone !

.NET 4.5 offers lots more advantages and v2 when I start it for my FYP will be based on .NET 4.5. I will of course keep Win Toolkit v1.5 available for XP users and will only do bug fixes for it. So just to summarize:
 
Win Toolkit v1.4.x.x will remain available requiring .NET Framework 3.5 Win Toolkit v2.x.x.x will be on a separate download page and will require .NET Framework 4.5 I remember when I first started Win Toolkit on .NET 2.0 when 3.5 was available. I'm now on 3.5 whilst 4.5 is available and for once would like to jump to the latest and take advantage of all of its features. Especially when it comes to multi-threading. 

Feel free to donate, all donations are appreciated.
 
Donate Here
 
You will get a Win Toolkit key out of it to unlock some extra downloads
 
P.S. Feel free to PM me if you haven't received a key.

I've removed RicaNeaga link. I've also made it so any NEW downloaded files LastAccess, LastWrite, Creation date are all set the release date.

Following on from the first report. In decided to rewrite the entire error logging system due to many problems with the old version. Here are some of the new benefits:
Each type of error has their own unique ID so that they are group together and easier to manage Logs can now contain foreign characters so most of the non-english computers have the most issues. You get a balloon popup when a log has been saved and uploaded. Which you can click to view. Shows the user much more error information. The exception errors are in the users' own language. Much simpler and easier to manage code. Different types of errors which help prioritize errors Before I describe what stage 2 is. I will give details of the types of messages.
 
Large Errors Large errors are the ones you will hopefully not see. This are the boxes which give you the option to view more details and the entire exception information.
Small Errors These don't produce an error box, they just upload straight to the server. Mostly used in integration so that the process doesn't pause and wait for the user to click OK.
Unhandled Exceptions Basically anything I haven't put in a Try-Catch statement. These are the big ones which I usually try and fix ASAP.
Test Error These are for me and just uploads an example test log to the server for me to check if it's working. Click here to view a log file sample. 
 
Legacy Errors These are the errors which still use the old code. Although they use the latest code to save and upload (to support foreign characters). They are unfortunately crap in regards to detail. This is where stage 2 comes in.
 
Stage 2:
Stage to is to manually go update all the calls to the old writelog method and update it to the new one. These will take a while Moving onto the new system will allow you to view as much information as possible in a neat format whilst allow me to fix bugs

Just fixed the msu, was a stupid typo on my end. I was passing C:\...\1.msu" instead of "C:\...\1.msu" (quote missing).
 
P.S. Windows updates should be on their own tab anyway so that another bug.
 
UPDATE: Uploaded test version.

With Windows 7 you provide the key after Windows Installation if you need. Just make sure to select the right version the key is for.

Sorry guys. I had to delete ALL but 3 personal messages as my inbox got full If you have sent an important message which still requires a reply, feel free to resend the message.
 
However, please remember bugs should go in the bugs sub-forum and that general questions should go onto the forum.

Download an ISO via Win Toolkit then following the following link:
 
https://www.sctxca.org/suncity/clubs-groups/sites/computer/sigs/win7/articles/Win7_Retail-to-OEM.htm
 
In the sources folder open ei.cfg with notepad
 
 
Change retail to OEM: I'm pretty sure you can just delete the ei.cfg either way
 
You made need to change 'Ultimate' to 'HomeBasic', 'HomePremium' or whatever version you have.

No worries, as I always try to use youre "cutting edge" releases as I build Images solely only for my own personal purpose.
 
If no one would use those, and report any possible hiccups,  there would be no evolution and stable versions aswell...

Bad news is that I have a lot of work to do for the next year and half (at least) because the good news is that Win Toolkit got approved to be my final year project. I will write an article so you guys know what to expect from this apart from a much better program.   :albert:  :graduated:
 
You think Win Toolkit is great now? It's only just begun! I have to prepare to rewrite everything with efficiency, concurrency and simplicity in mind. Oh god the paperwork is going to be fun (sarcasm)

Thank you for the quick answer and info. Really, i appreciate it.
 
Let's hope they will remove it.