Legolash2o

8.1 DISM doesn't work on XP. WinToolkit does run on XP with some small features disabled. I will be using .NET 4.0 so XP users can still use it.

Because the RunOnce scans WinToolkit_Apps by default if it exists for backwards compatibility so it doesn't need to be specified in the install.ini. That one is there as an example. Basically within the RunOnce there is a list of locations of WinToolkit_Apps, Sources\WinToolkit_Apps and anything in the installdir variables (install.ini). When it comes to adding the install entries to scans all the locations for the files add then adds it. If you really wanted you can have files all of the place and move them about freely as long as the installdir is set correctly.

Already released.

Make sure you put %DVD%:\ and not just %DVD%\ (colon missing, but test 11 will support both). Already just added the %APP% value and it works UPDATE: Test 11 released.

#Any line starting with a # are comments and will be ignored.#Lets you specify the configuration of the installers#InstallDir is where your apps are located.#DriverDir is which directories to scan for inf files.#Reboot makes RunOnce reboot Windows after completion.[Config]INSTALLDIR=Sources\AppsDRIVERDIR=Sources\Drivers#Here are some other samples.#INSTALLDIR=E:\Software#DRIVERDIR=X:\MyDriverCollectionREBOOT=FALSE#Things which will always get installed. Anything after * is a switch i.e. /S /Q /Silent[Automatic]#KBXXXXXX-x64=%DVD%:\WinToolkit_Apps\Windows6.1-KBXXXXXX-x64\Windows6.1-KBXXXXXX-x64.msu#User will be asked to choose which of the following apps to install.[Manual]#Microsoft Office 2013=%DVD%:\WinToolkit_Apps\Office2013\Setup.exe*/configure %DVD%:\WinToolkit_Apps\Office2013\\config.xml#Example 1=%DVD%:\WinToolkit_Apps\ExampleProgram\Example.exe*/s I'm goinf to add %APP% which will go in the app directory. Office 2013=%DVD%:\WinToolkit_Apps\Office2013\Setup.exe*/configure %APP%\Config.xml In this case, %APP% would be X:\WInToolkit_Apps\Office2013\

I manged to reproduce the error and know exactly what the issue is. EDIT: Already fixed.

v10 has been re-uploaded to show the correct version.

Just ignore that v10 is out now anyway Fixed.

What's your spec? :-O

Try test 10 please It should write a log in the system32 folder.

Try test 10

Well previously Win Toolkit only used about 10-20% of my CPU my (8 cores) but with my experiments, it shoots up to about 80-90%. The HDD is really the limiting factor, SSD helps a lot but the results from a RAM Drive were mind blowing

.NET 4.0 is fine, has everything I need such as better threading, LINQ and Lambda expressions which I love. Just those 3 features alone will make a HUGE performance increase in Win Toolkit!

Yep, exactly what I was thinking. However the new test version of the minute only uses install.ini in the sources folder. One should be created as soon as you open WIM manager and select an image.

Ah :censored:. I forgot to make it check the registry for installs, I only coded it to use the install.ini. Silly me!!!!!!!!!!

Can people please test the latest test build. The RunOnce installer has had an upgrade in regard to threading and updates are installed separately. Also when you select/load a DVD in WIM Manager a sample install.ini is created in the sources folder to be used with the RunOnce. Thanks. I wish it was dead already or wish that Windows 7 came with .NET 4 instead of 3.5

Well with the RunOnce installer I've managed to keep it on .NET 3.5 but yet use a backported dll which lets me use the parallel and linq from .NET 4.0. But for WinToolkit I will use the latest .NET framework the university have.

What do you mean? Free, may probably even release the source code. After my project I may decide to go a next step further and do it in C++ instead of C# lmao. :crying_anim02: :sick01:

I know in the RunOnce im working on right now you can do something similar to: Setup.exe /configure %DVD%:\\Office2013\\config.xml UPDATE: Test 8 released with this feature

it does scan subfolders

Since RunOnce decided to screw up (partially my fault). I decided to put all my knowledge including the new multithreading knowledge I have into it, So far it's a lot less code and much simpler for me to read and so far the results have been excellent. For example: I had to wait about 10-13 seconds for it detects items to install (usually 2000+ drivers) before I see the main install screen. Now it does the same thing in 411ms 366ms so no complaints here. It now uses all cores to get the information.

I'm coding it now. Since RunOnce is .NET 4, i get a chance to use the new parallel threading code

Unfortunately some of the RunOnce installer got cuorrupted so got to do a lot of work to fix it. SVN didn't work properly

I want to implement it for the next release but it requires changing Win Toolkit from .NET 3.5 to .NET 4.0

So I can add them to the silent installers list?