Leaderboard

Info: Microsoft Visual C++ 2005/2008/2010/2012/2013/2014/2015, Microsoft Visual F# 2.0, Microsoft Visual J# 2.0 redistributable packages (with setup junk removed.) Also includes "extra" Visual Basic and C runtimes (see list bellow) Same as above but excludes F# & J# runtimes Info: Microsoft Visual C++ 2005/2008/2010/2012/2013 redistributable packages (with setup junk removed.) Also includes "extra" Visual Basic and C runtimes (see list bellow) Some tools and resources for (re)creating your own installer Visual AIO SFX Maker v6 (installer repacker):http://adf.ly/1713566/visualsfxSilent "No GUI" SFX alternative v4:http://adf.ly/1713566/visualsfxngKB2538242 MST Windows Update fix v1.7:http://adf.ly/1713566/wufix5mstKB2538243 MST Windows Update fix v3:http://adf.ly/1713566/wufix8mstMsiTran.Exe -a <transform>.MST <installer>.MSI:http://adf.ly/1713566/msitranSlim down your vcredist 2005/2008 installers:http://adf.ly/1713566/msislim"Extra" Visual Basic/C runtimes installer sourceshttp://adf.ly/1713566/vbcsourceIf you cant find a hotfix try using the KB number w/ this URLhttp://support2.microsoft.com/hotfix/KBHotfix.aspx?kbnum=1234567 Hotfix list 2005: 2643995 2008: 2834565 2010: 2821701 2012: Release 4 Also includes: name version/*-- Microsoft Visual Basic Runtimes -----------------------------------*/ comct232.ocx 6.0.98.39comct332.ocx 6.7.0.9839comctl32.ocx 6.0.98.39comdlg32.ocx 6.1.98.41dblist32.ocx 6.1.98.39mci32.ocx 6.1.98.39mscomct2.ocx 6.1.98.39mscomctl.ocx 6.1.98.39mscomm32.ocx 6.1.98.39msdatgrd.ocx 6.1.98.39msdatlst.ocx 6.1.98.39msflxgrd.ocx 6.1.98.39mshflxgd.ocx 6.1.98.39msinet.ocx 6.1.98.39msmask32.ocx 6.1.98.39msstdfmt.dll 6.1.98.39msstkprp.dll 6.1.98.39mswinsck.ocx 6.1.98.39 picclp32.ocx 6.1.98.39richtx32.ocx 6.1.98.39sysinfo.ocx 6.1.98.39tabctl32.ocx 6.1.98.39vb40032.dll 4.0.29.22/*-- Microsoft Visual Basic Runtimes (16bit) ----------------------------*/vb40016.dll 4.0.24.22vbrun100.dll <none>vbrun200.dll 2.0.9.8vbrun300.dll 3.0.5.38/*-- Microsoft Visual Basic Virtual Machine -----------------------------*/msvbvm50.dll 5.2.82.44/*-- Microsoft Visual C Runtimes ----------------------------------------*/atl70.dll 7.0.9975.0atl71.dll 7.10.6119.0mfc70.dll 7.0.9975.0mfc70chs.dll 7.0.9975.0mfc70cht.dll 7.0.9975.0mfc70deu.dll 7.0.9975.0mfc70enu.dll 7.0.9975.0mfc70esp.dll 7.0.9975.0mfc70fra.dll 7.0.9975.0mfc70ita.dll 7.0.9975.0mfc70jpn.dll 7.0.9975.0mfc70kor.dll 7.0.9975.0mfc70u.dll 7.0.9975.0mfc71.dll 7.10.6119.0mfc71chs.dll 7.10.6119.0mfc71cht.dll 7.10.6119.0mfc71deu.dll 7.10.6119.0mfc71enu.dll 7.10.6119.0mfc71esp.dll 7.10.6119.0mfc71fra.dll 7.10.6119.0mfc71ita.dll 7.10.6119.0mfc71jpn.dll 7.10.6119.0mfc71kor.dll 7.10.6119.0mfc71u.dll 7.10.6119.0msvci70.dll 7.0.9955.0msvcp70.dll 7.0.9466.0msvcp71.dll 7.10.6052.0msvcr70.dll 7.0.9981.0msvcr71.dll 7.10.7031.4msvcrt10.dll <none>

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.

Thanks for the info! Cheers and Regards

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