Legolash2o

It searches a bunch of pre-defined locations and your custom folder. I then believe it will use the latest version it finds.

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.

Are you using install.ini or AIO Integrator? Is it EXE or MSI files? UPDATE: Nevermind, it's EXE and just fixed it

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.

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 manageLogs 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 errorsBefore I describe what stage 2 is. I will give details of the types of messages. Large ErrorsLarge 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 ErrorsThese 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 ExceptionsBasically anything I haven't put in a Try-Catch statement. These are the big ones which I usually try and fix ASAP. Test ErrorThese 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 ErrorsThese 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

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.

Thanks I will test when I get home. Just before I left I've implemented which will show why drivers haven't been added and an option disable it from automatically removing invalid drivers.

Anywhere you can online and just a small handful. If less than 2MB 7zipped up, then just attach it to your next post

Sorry for lots of releases in the past few days. I'm still receiving big issues on the old system which I've moved over to the new system in the latest release. This will allow me to find them once and for all. I've also fixed a few important bugs with the RunOnce tool so it was worth it. I'm currently tracking a really nasty bug which about 90% of the error logs I receive so it was really important that I move it over to the new system. I've also made it so that the 'Details' button on the error box shows you ALL the information it has collected rather than just a few bits and bobs of useless crap.

Thanks, much appreciated. I've already uploaded a new test version removing the console window and other fixes to the main Win Toolkit exe.

I can fix that, make sure you dont have it in both install.ini and registry. You may have integrated a few times into the same image

Maybe upload a few drivers?

The only thing I can imagine causing that is that the Drivers folder either has no *.inf files in it or that they are all x86 drivers.

Fixed, in the latest test build

Oh damn, you're right! I think it's adding it onto everything! EDIT: IT adding it to everything you add via AIO-Integrator but not install.ini, fixing it now!

Hmm, I will look into that right now, then I've got to write you guys an article

Everything working fine for but it can't be related to Win Toolkit as I don't have anything to do with the board.

Drivers folder in the usb stick, dvd or drive root, but not in the image i.e. D:\Drivers\* D:\Sources\Drivers\*

The only advantage is that I get paid when someone installs an offer. Apart from that, it's pointless and I don't see myself keeping it even if I do get paid. If i'm completely honest, I hate the software it offers and if I could have my own way it would offer useful programs such as Chrome, Firefox, CrapCleaner, Java, useful stuff. So that's the big reason that I wont end up keeping it. It offers to install toolbars and I HATE toolbars with a passion. The only reason it's still up is because I said to someone that I would try it. If you have some spare time please, and i mean PLEASE search the internet for installers that DO offer chrome, etc..

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)

So regarding my final year project do you want the good news or the bad news first?

With the successful release of it yesterday. I manage to fix 15 issues in about an hour. I've also made some changes to what the log looks like and how it's displayed on the server. Some enhancements: Using MD5 instead of GetHashCode to create more uniqueness as some errors had the same ID Included more CPU, RAM and HDD informationAdded a custom stack trace which will hopefully be a brilliant addition.Increased efficient of log uploading. Ran preparation code twice when it only needed to be ran once.Although you may think it's not a major feature, I believe it's the most important thing I've done for a long time! It allowed me to fix a bunch of issues within an hour and with this new system, I can fix more!Click here to view a log file sample. 1. Done 2. In the future once I've got the damn thing finished. I can provide the link to the logs so people can see if it's a big problem or a one off. It would also allow you guys if you're curious/bored to help see what the cause of a problem is by viewing different environments it's being run on. The logs don't contain anything personal or that can be linked back to the user anyway.

Yeah it does on close. Knowing me, there's probably something I've forgot to remove (via code) and would be nice to know these I know that the RunOnce installer does leave itself after installation of Windows and I will work out a solution for that.

I got a response:

Didn't know there was a WinToolkit Cleanup Tool. I'd rather someone had made a post about any left over files so I can make WinToolkit do it