Was asked what is the GUI QT's version numbering system example GUI_QTv0.10.2.41, well the 0 after the v bit means is it is below final ,(or still in beta testing releases), that will change to v1 when beta testing has completed. The 10 bit is a nod to Windows 10, i may use 11 at a later stage, but so far i am personally not overly impressed with w11 , a bit better with latest one 2262x. The 2 is the milestone version - this changes when major additions/changes are done such as adding a new tab section. The last bit after the 2 above is a simple reference to which minor revision is current.
@Dubioza Kolektiv was the GUI QT faster in operation?, although it seems to mainly affect VM's or the LSTB/C OS's the most. I personally noticed the 1 to 12% was certainly faster than it was before.
Will do. Seem average is approx 12 to 18 seconds. Think that is a bit better than before. Im learning new techniques, just remembering them is my problem
Done Altered the code to allow saveonly with or without the - character suffix. Uploaded .42 -- only the above internal command line parameter code been changed from .41 been done.
Nope no other command line parameters apart from -help help or -?, sadly the GUI QT will not run in win_pe at moment as .net 2.0, 3.5 and 4.x will need to be installed in the winpe as some parts will require it to fully function. It may work for some of the results but SLIC/MSDM data will be limited.
I will add a save location selector once i work out how to make it work. It may be a while as error checking needs to be worked out.
GUI_QTv0.10.3.00 - yes milestone 3 reached as a major code update has been done. Added save folder/location requester when the scanning is completed this will show for normal full GUI or when using the -saveonly (saveonly) command line. If nothing selected (or error) then Desktop will be the default saved location. I cannot use the command line parameter to enter a user typed location as it can cause all sorts of hassle with error checking etc, so using the OS's folder location requester is a better way as that does all the hard work and gives me back either the valid location or a error which i just parse the results. Lazy method i know but why reinvent the wheel when the OS does all the hard work in checking ? Updated Post #3 with download link, hashes and other info.
MRP 148 will be ready by the weekend , a small delay as been busy with various life things, only be a couple of days late.