Leaderboard

To improve Win Toolkit greatly and also a learning experience for me. I've decide do redo all exception handling, error boxes, log saving and uploading. I've been wanting to do this for a very long time as there has been a long standing issue when uploading error logs, which has affected about 95% of uploaded error logs. Basically the log file has weird ASCII characters, squares, etc... Which makes it unreadable. This issue of course helps nobody but rewriting it is a huge task! A lot of it will be backend code so you shouldn't really notice it. So now you're probably wondering how the changes will affect you. So here are the improvements I will be implementing. NOTE: No personal information is sent in logs. Just details about the computer hardware and the error details. Your benefits: Exceptions will be shown in YOUR language but when uploading and writing to a file. It will also add English if possible. This means in your log file, it will show both languages.Error logs file name will start with version number and then a unique error number. Easier to find a specific error. My benefits: Uploaded error logs will be uploaded in both languages so I can understand it.Upload logs will start with the unique identifier so that all errors which are the same will be group together. This will save me HUGE amount of time.Get rid of useless logs which help nobody Other Changes: Better log layout Error logs will automatically upload in the background there and then rather than at close. I may add a balloon tip near the clock to show when one has been uploaded/saved.Uploading will upload the string directly rather than the text file which is where most things of wrong with the characters.It's a huge task and I will be dedicating tonight to get it done. The biggest change you will notice is that exceptions will be shown in your language and bugs will get fixed quicker! Any questions, small requests or suggestions for this? Stage 1 (Done): Make new abstract class and efficient methods to get the job done.Record relevant details to help solve errors.Record more exception details such as stacktrace.BIG: Make logs readable from any language.Have a simple code to know which bugs are big, small or unhandled errors.Automatically give similar errors a unique ID so all the same bugs are grouped together.Show exceptions in user language.Stage 2 (W.I.P): Gradually upgrade old error messages into new ones with more detailShow more information to user by clicking a more detail button.

Package has been send, it should be there Monday. I'll PM tracking number.

I would send you some parts Rick, but the last time I sent you some parts shipment costs were hilarious

As part of my final year project (if approved). I will be focusing a lot on threading. Currently Win Tookit uses background workers with apparently are bad for performance. I've been experimenting and here are some results compare the current method used by Win Toolkit and a new method. Parallel will also use more CPU cores and I will let you choose in Options how many you want to use. By default it would be ProcressorCount - 1, so if you have a quad core with hyperthreading (8), it will use 7 by default. Test 1: The test was to get the MD5 values for 1300+ MSU files. -------------------------------------------- Not Updating GUI:- Current: 19270ms (19 seconds) New: 5499ms (5.4 seconds) 350% speed increase! When updating the GUI:- Current: 38417ms (38.4 seconds)New: 9576ms (9.5 seconds) 401% speed increase! -------------------------------------------- Test 2: The test was to get the MD5 values for 55652 files. Not Updating GUI:- Current: 466165ms (466 seconds / 7.7 minutes) New: 4943ms (4.9 seconds / 0.082 minutes) 9430% speed increase! When updating the GUI:- Current: 500754ms (501 seconds / 8.34 minutes) (testing....)New: 13334ms (13.3 seconds / 0.22 minutes) 3755% speed increase! ----------------------------------------------------------- The results so far look very promising! Imagine integrating EVERY gadget, EVERY wallpaper, EVERY custom files, EVERYTHING except Updates + Drivers being integrated at the same time as everything else. I'm still continuing my research...

In case you didn't know, I've been drafting up my proposal to finally work on a new Wintoolkit v2 as my final year project at university. It will be EPIC. I've received feedback and made changes to my proposal, just awaiting for further feedback. Once that is done, I will submit it I will keep you guys up-do-date in this thread as soon as I hear anything. Basically it will be starting WinToolkit from scratch. Here are a few things you should expect. · Make more use of mutli-tasking All-In-One Integrator will integrate wallpapers, gadgets and others at the same time as other tasks, saving even more time. Run other tools whilst integration is in progress. Converting files, downloading and so fourth.Click here for multi-threading experiment results. · Run speed profile tests to see if code can be made more efficient. I want Win Toolkit v2 to be very very efficient and run as fast a possible. This includes running automated tests which tell me the slow areas of my code and then I basically plan how I can make it fast. Every millisecond will count! This WILL improve ALL-In-One Integrator dramatically!!!!!!!! · Conduct extensive testing to ensure final software meets requirements. I will have to do testing reports and documentation, hopefully you guys can help too. · Design and implement automated testing. I will use the tools available in Visual Studio to design automated testing. This will ensure that if i make a change it wont screw up anything that worked previously. Each method will have multiple automated tests. · Automated online databases The only database using SQL will keep automatically keep track of what of updates are LDR or GDR saving previous extracting time. Keep tracking of what updates can and can't be integrated. Allow me to add notes to updates so if an issue appears with an update I can make it show notes without havign to download a new version.The above three implementations will be amazing. You would not have update WinToolkit to solve integration issues, it will all be done without lifting a finger by anyone! It also includes other benefits. Keep tracking of Win Toolkit updates. Track errors and bugs. · Automatic Updating Win Toolkit will update itself automatically (can be turned off) and will hopefully download only parts of the file which has changed saving your bandwidth. You will also have the option to download beta updates. · Consistent and predictable release cycle. Test Builds: Pretty much every night.Beta Builds: Every Saturday night.Main Builds: First Saturday of the month. WinToolkit v1Wanted to know what Win Toolkit looks like in its physical form? I decided to print out all the code and will be painfully going through it all to look for areas of improvement!

Since a couple of months, may be depending on some updates coming on the patch-day, this two KBs are not installed anymore (under SFX-Silent Installers) and WU asks for the two updates after the next login. I think, if WTK would have the possibility to put a reboot between programs, continuing the execution after reboot, or a section under "SFX-Silent-Installers" for programs to be installed after a reboot, this could be a solution. Thiersee

Nice find! ps. I PM'ed Kels. I guess we just need to wait for him to get back to us.

WOW you guys, found an even better one (INTEL DQ45CB) at the same price (difference is it can handle up to 16GB of ram, 6 vs 4 sata ports and can do raid)

I've sent you few bucks, now go get that mobo!

Thanks for the info compstuff, this should be noted on WinToolkit guide and/or stickied somewhere.